> 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. Have you (or kmuto) tried a Japanese install with all defaults? 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.
