6 липня 2005 о 23:17 +0200 Christian Perrier написав(-ла): > > Package: localechooser > > Severity: normal > > Tags: l10n d-i > > > > I tried to install system in Ukrainian language but chose locale > > uk_UA.UTF-8 to be default on new system. After reboot to second stage > > console was setup to use UTF-8 as encoding (locale was uk_UA.UTF-8 as > > expected). Then termwrap probably tried to start jfbterm and failed > > (it was not present, termwrap only loaded framebuffer module). After that > > base-config was run with no cyrillic letters at all. > > Well, as you mention a failure to load jfbterm, I suspect the bug not > being in localechooser (at least in forst approximation) but rather in > jfbterm failing to load. jfbterm is failing to load because it is not present, it is not required for Ukrainian install, so localechooser did not install it. Problem with localechooser it that it sets up console to use KOI8-U instead of UTF-8. There is also problem with termwrap that it tries to use jfbterm for Ukrainian install.
> > Have you (or kmuto) tried a Japanese install with all defaults? I haven't but I think that install with both UTF-8 and EUC-JP locales will be successful for Japanese. > > Anyway, such breakage is not really surprising : up to now, everything > in d-i assumed that, for a given language, only one encoding is > used...which now becomes untrue as you clearly show here. > > I suspect that choosing fr_FR.UTF-8 would lead to some display problem > in 2d stage. That will be minor problems compared to Ukrainian: you at least will be able to read some text and not only words "Debian" :) -- Eugeniy Meshcheryakov Kyiv National Taras Shevchenko University Information and Computing Centre http://icc.univ.kiev.ua
signature.asc
Description: Digital signature
