(Please use the bts, I'm not the only one working on this stuff, and can easily miss mails. I'm also the worst possible person of base-config's several maintainers to talk about this stuff to, since I don't understand encodings, fonts, or localisation at all, really.) Recai Oktas wrote: > As you may recall, despite the fact that it setups console correctly on > startup, termwrap leaves the console in a bad state while exiting, and > requires the user to reboot or issue the '/etc/init.d/console-screen.sh > restart' command. I can't figure out why the exit code exists (that is, > the block at the end which starts as 'case $ENCODING in'). This code > block should be simply removed, if there is no spesific reason behind > it. I'm currently trying to get a usable base-config into testing to use for the tc1 release, and since recent, insufficiently tested, font changes have led to the current mess, the last thing I want to do is make any more changes in this area right now. I'll look at it again after tc1 is released. I suspect that the code was added for a reason though. > After looking the screenshots, another change which seems to be > mandatory is that, we should change the 'iso02.f16' to 'lat2-sun16' in > the following line for iso02 (FYI, I've reverted back my changes to > languagechooser for iso02): > > ISO-8859-2) > # Load ISO-8859-2 charset mapping into console > try_load_charset "$ENCODING" iso02 iso02.f16 There is no chance of making languagechoser changes for tc1. If necessary we can do this kind of change in a tc2. If this is a release critical issue for rc1, you need to explain *why* it would be worth the bother of throwing away tc1 and spending weeks retesting with a tc2; saying it's "mandatory" is not good enough. -- see shy jo
Attachment:
signature.asc
Description: Digital signature