From: Alexey Gladkov <gladkov.alexey@gmail.com> To: Linux console tools development discussion <kbd@lists.altlinux.org> Subject: Re: [kbd] unicode_start should not call setfont Date: Sun, 01 Jun 2008 03:54:21 +0400 Message-ID: <4841E52D.5090807@gmail.com> (raw) In-Reply-To: <20080531073115.GB3877@debian.homenet> 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" ;; 0) - 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
next prev parent reply other threads:[~2008-05-31 23:54 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-31 7:31 Michael Schutte 2008-05-31 23:54 ` Alexey Gladkov [this message] 2008-06-01 7:55 ` Michael Schutte
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4841E52D.5090807@gmail.com \ --to=gladkov.alexey@gmail.com \ --cc=kbd@lists.altlinux.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Linux console tools development discussion This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/kbd/0 kbd/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 kbd kbd/ http://lore.altlinux.org/kbd \ kbd@lists.altlinux.org kbd@lists.altlinux.ru kbd@lists.altlinux.com public-inbox-index kbd Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.kbd AGPL code for this site: git clone https://public-inbox.org/public-inbox.git