Well, there is some urgency now in fixing this bug as the D-I release manager puts pressure on it after we switched most languages to UTF-8:
22:35 < fjp> bubulle: I see all kinds of weirdness after reboot that I think is caused by UTF-8. Have you already been testing for this? 22:44 < fjp> bubulle: Example is that info pages are a lot less readable http://people.debian.org/~fjp/d-i/utf8weirdness2.png. Another is that I see strange characters from aptitude http://people.debian.org/~fjp/d-i/utf8weirdness1.png (block chars in line "Temporary failure..." around the hostname). 23:06 < bubulle> fjp: I haven't made such tests after an install 23:07 < fjp> Please do if you have time. If not, I think the UTF-8 change should be reverted. 23:07 < bubulle> however, as my own system runs a UTF-8 locale for ages, I have some experience of UTF-8 on console which is quite positive, despite some quirks 23:07 < fjp> I really hate the weirdness in info. 23:07 < bubulle> the major quirk is a very well known bug in console-common and the consoel being switched to UTF-8 only for the first console 23:08 < fjp> Well, IMO the two examples I printed above are very basic stuff. If that does not work correctly, we should not switch. 23:09 < bubulle> well, I at least can't reproduce them on my own system 23:10 < fjp> This is in vmware installing sid with English/Netherlands. 23:11 < fjp> You have to ifdown eth0 to reproduce the second one :-) 23:12 < bubulle> fjp: are you in console 1? 23:13 < fjp> I may have been in 2 23:13 < bubulle> that's a very important difference 23:14 < bubulle> fjp: if it happens in console 2 and not in 1, this is probably #271013 23:15 < bubulle> if it disappears in console 2 after launching "unicode_start" from console1 then it's definitely #271013 23:17 < bubulle> fjp: I'd be delighted to reproduce it...if I can put my hands on a working sid_d-i image.... 23:18 < fjp> bubulle: The graphical installer is sid_d-i. joeyh 's builds are dead because of a missing builddep. joeyh seems unavailable ATM to fix it. 23:19 < bubulle> fjp: btw, I was today seeking for alink to the joeyh daily builds and couldn't find one anywhere 23:19 < fjp> It looks likely this is the problem. IMO this should be set to RC if we want to switch to UTF-8 or we should delay UTF-8 until this is fixed. 23:19 < bubulle> not a build as they're dead but at least a link..:-) 23:20 < fjp> bubulle: older links are deleted automatically. 23:20 < bubulle> fjp: well, before raising the severity to RC I tried to ring a bell to Alastair on Nov 20th in the #271013 bug... 23:21 < bubulle> after al, in this very bug he said he would work on it "immediately after sarge release"..:-) 23:21 < fjp> Yes, read that :-P 23:22 < fjp> bubulle: I'll leave it for now, but I will revert the UTF-8 change for beta2 if it's not fixed. 23:23 < bubulle> fjp: ouch...then I guess I should urge Alastair to at least apply the dirty hack proposed in #271013 23:24 < fjp> bubulle: Main reason is that I don't want us to have to deal with hundreds of installation reports about this. 23:24 < fjp> Also, I think this is to basic for dirty hacks. IMO it should be solved properly. 23:26 < bubulle> fjp: the clean solution doesn't seem that simple....and the "dirty" one is currently harmless (switching all first 11 consoles to UTF-8) -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
