From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 30505@debbugs.gnu.org
Subject: bug#30505: Starting console/terminal Unicode support
Date: Tue, 27 Feb 2018 10:25:36 +0100 [thread overview]
Message-ID: <87a7vu6ay7.fsf@gnu.org> (raw)
In-Reply-To: <20180226232302.08c60250@scratchpost.org> (Danny Milosavljevic's message of "Mon, 26 Feb 2018 23:23:02 +0100")
Hi,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Mon, 26 Feb 2018 18:09:53 +0100
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> 1. status quo, i.e., tcsetattr without %G in the ‘term-ttyN’ services;
>>
>> 2. remove the tcsetattr call, write “1” to
>> /sys/module/vt/parameters/default_utf8;
>>
>> 3. do nothing (no tcsetattr, no /sys, no %G).
>>
>> It seems that systemd does everything: %G, tcsetattr, and /sys.
>
> We have the following options as a distribution:
>
> (a) Hope that the user sets up everything as he should - iff they set up
> the kernel as non-utf8, they also must set up an non-utf-8 console font.
> (b) Force their hand by decreeing that GuixSD is utf-8 only. That's what
> we are doing now I think - and a lot of projects (GNOME etc) assume UTF-8
> nowadays anyway.
>
> Since we just want to fix the bug and leave everything else as it is (b),
> I'd vote for your (2.).
>
> (2.) needs to be done early before the VTs are actually there.
OK, makes sense, I agree.
> default_utf8 is a default, and it will be read only when defaulting, so
> in this case it will be read when Linux is constructing a tty.
>
> %base-services contain both console-font-service and mingetty-service which
> both access the ttys. Linux VTs are created on demand.
>
> Once the VTs are created, us setting default_utf8 is too late.
>
> We should set default_utf8 before anyone touches tty[123456].
>
> Where will that be?
>
> Should we just set it in boot-system ? That's probably a nice way -
> also since I think this setting is quite Linux-specific.
Alternately we could introduce a ‘virtual-terminal’ service that every
‘term-*’ service would depend on. That ‘virtual-terminal’ service would
simply write “1” to /sys/…/default_utf8.
How does that sound?
Ludo’.
next prev parent reply other threads:[~2018-02-27 9:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 0:01 bug#30505: marionette/virtio-console issues lead to test failures Ludovic Courtès
2018-02-18 10:48 ` Danny Milosavljevic
2018-02-19 15:54 ` Ludovic Courtès
2018-02-19 17:08 ` Danny Milosavljevic
2018-02-19 20:35 ` Ludovic Courtès
2018-02-19 22:35 ` Danny Milosavljevic
2018-02-21 22:21 ` bug#30505: Starting console/terminal Unicode support Ludovic Courtès
2018-02-21 23:01 ` Danny Milosavljevic
2018-02-23 21:41 ` Ludovic Courtès
2018-02-25 12:31 ` Danny Milosavljevic
2018-02-25 12:57 ` Danny Milosavljevic
2018-02-26 17:09 ` Ludovic Courtès
2018-02-26 22:23 ` Danny Milosavljevic
2018-02-27 9:25 ` Ludovic Courtès [this message]
2018-03-15 10:41 ` Ludovic Courtès
2018-02-19 21:53 ` bug#30505: marionette/virtio-console issues lead to test failures Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7vu6ay7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30505@debbugs.gnu.org \
--cc=dannym@scratchpost.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).