[kbd] unicode_start should not call setfont

Alexey Gladkov gladkov.alexey at gmail.com
Sun Jun 1 03:54:21 MSD 2008

Michael Schutte wrote:
> Hi,
> I think that unicode_start should not mess with the user’s console font.
> It should only put the console into Unicode mode and be done with it.
> The problem with the current approach is that the default Unicode fonts
> considered by the script are often not what the user wants to see.
> Every font should be fine to display enough characters to be readable,
> anyway, and users who need a larger subset of Unicode characters can run
> setfont manually.  It would also make sense because unicode_stop never
> changes font.
> The obvious counter-argument is backwards compatibility, but then, most
> users will not call unicode_start themselves but leave it to their
> distribution’s init scripts.  What do you think?

We could do another thing:

diff --git a/src/unicode_start b/src/unicode_start
index 82ef457..63c9967 100755
--- a/src/unicode_start
+++ b/src/unicode_start
@@ -83,7 +83,6 @@ case "$#" in
                 setfont "$1"
-               setfont "$DEFAULT_UNICODE_FONT"
                 echo "usage: unicode_start [font [unicode map]]"

Most distributions load own fonts after executing unicode_start. I 
think we can remove the setting of default font.

Without any arguments unicode_start will only set unicode mode and 
will not set font.

How about that?

Rgrds, legion

More information about the kbd mailing list