Hi! Since it didn't work out of the box, I modified my /etc/init.d/consolefont.sh to respect the UNICODE config variable. If set, it interprets CONSOLETRANSLATION as a unicode console translation map from /usr/share/unimaps. This is what is needed on a unicode terminal, and setting the UNICODE var does set the terminals to unicode, so I think this is the way things are supposed to work. I have used this setup for 3 years now - I am Hungarian, so I need latin2 on the console, which I have. The settings I use are: UNICODE="yes" CONSOLEFONT="iso02.14" CONSOLETRANSLATION="iso02.uni"
Created attachment 94990 [details] Modified /etc/init.d/consolefont Check the part where it loads the console translation.
Created attachment 95013 [details] New consolefont Try this script instead. It allows UNICODEMAP to be set alongside CONSOLETRANSLATION as sometimes both are needed. Requires kbd-1.12-r8 as prior versions mangled the unimaps path thanks to a Debian patch we're using.
BTW, next time send patches please :P
Created attachment 95014 [details] unicodemap support for consolefont This one allows both :)
I agree, leaving both is best.
Created attachment 95069 [details, diff] Look for unimaps in /usr/share/unimaps I think it's reasonable to seek unicode maps in /usr/share/unimaps, instead of relying on the user to set the full path.
Comment on attachment 95069 [details, diff] Look for unimaps in /usr/share/unimaps no, the util needs to know where to search ... forcing the path is wrong
(In reply to comment #7) > (From update of attachment 95069 [details, diff] [edit]) > no, the util needs to know where to search ... forcing the path is wrong > Which is why I said it requires kbd-1.12-r8 as that has the path fix :) I'll commit the fixed init script one that kbd version goes stable.
This was fixed in baselayout-1.13.0_alpha7
