From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#30505: Starting console/terminal Unicode support Date: Tue, 27 Feb 2018 10:25:36 +0100 Message-ID: <87a7vu6ay7.fsf@gnu.org> References: <87vaevi2sk.fsf@gnu.org> <20180218114833.7d5e7848@scratchpost.org> <87r2phezzv.fsf@gnu.org> <20180219180849.3a509e80@scratchpost.org> <87d110g1l2.fsf@gnu.org> <20180219233553.31aeef1a@scratchpost.org> <87bmgic7bl.fsf_-_@gnu.org> <20180222000105.46d017ca@scratchpost.org> <87lgfjbczk.fsf@gnu.org> <20180225133131.76260198@scratchpost.org> <20180225135704.3c437152@scratchpost.org> <87sh9nvfry.fsf@gnu.org> <20180226232302.08c60250@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34274) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eqbWP-0001rk-HA for bug-guix@gnu.org; Tue, 27 Feb 2018 04:26:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eqbWM-0006hH-Cu for bug-guix@gnu.org; Tue, 27 Feb 2018 04:26:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:54633) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eqbWM-0006hB-8j for bug-guix@gnu.org; Tue, 27 Feb 2018 04:26:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eqbWL-0000Ut-W7 for bug-guix@gnu.org; Tue, 27 Feb 2018 04:26:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20180226232302.08c60250@scratchpost.org> (Danny Milosavljevic's message of "Mon, 26 Feb 2018 23:23:02 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Danny Milosavljevic Cc: 30505@debbugs.gnu.org Hi, Danny Milosavljevic skribis: > On Mon, 26 Feb 2018 18:09:53 +0100 > ludo@gnu.org (Ludovic Court=C3=A8s) wrote: > >> 1. status quo, i.e., tcsetattr without %G in the =E2=80=98term-ttyN=E2= =80=99 services; >>=20 >> 2. remove the tcsetattr call, write =E2=80=9C1=E2=80=9D to >> /sys/module/vt/parameters/default_utf8; >>=20 >> 3. do nothing (no tcsetattr, no /sys, no %G). >>=20 >> 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= =20 > 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 whi= ch > 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 =E2=80=98virtual-terminal=E2=80=99 service= that every =E2=80=98term-*=E2=80=99 service would depend on. That =E2=80=98virtual-te= rminal=E2=80=99 service would simply write =E2=80=9C1=E2=80=9D to /sys/=E2=80=A6/default_utf8. How does that sound? Ludo=E2=80=99.