bug#30505: Starting console/terminal Unicode support

2018-03-15 Thread Ludovic Courtès
Hello! l...@gnu.org (Ludovic Courtès) skribis: > Danny Milosavljevic skribis: [...] >> 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-s

bug#30505: Starting console/terminal Unicode support

2018-02-27 Thread Ludovic Courtès
Hi, Danny Milosavljevic skribis: > On Mon, 26 Feb 2018 18:09:53 +0100 > l...@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; >> >>

bug#30505: Starting console/terminal Unicode support

2018-02-26 Thread Danny Milosavljevic
Hi Ludo, On Mon, 26 Feb 2018 18:09:53 +0100 l...@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

bug#30505: Starting console/terminal Unicode support

2018-02-26 Thread Ludovic Courtès
Hey, Danny Milosavljevic skribis: >> Usually I'm not a fan of overriding user settings (in this case the kernel >> command line) but in this case it's OK since the rest of the system at least >> can be sure that we have UTF-8 VTs. > > Aha, the gnu/services/base.scm tries to make sure that an UTF

bug#30505: Starting console/terminal Unicode support

2018-02-25 Thread Danny Milosavljevic
> Usually I'm not a fan of overriding user settings (in this case the kernel > command line) but in this case it's OK since the rest of the system at least > can be sure that we have UTF-8 VTs. Aha, the gnu/services/base.scm tries to make sure that an UTF-8 aware unicode font is already loaded bef

bug#30505: Starting console/terminal Unicode support

2018-02-25 Thread Danny Milosavljevic
Hi Ludo, On Fri, 23 Feb 2018 22:41:19 +0100 l...@gnu.org (Ludovic Courtès) wrote: > Yeah, we could simply write “1” to that file I guess. > > Let’s do that? I've thought about it and since non-UTF8 terminal probably only can be found in museums (famous last words), yeah, let's do that. Usually

bug#30505: Starting console/terminal Unicode support

2018-02-23 Thread Ludovic Courtès
Hello! Danny Milosavljevic skribis: > On Wed, 21 Feb 2018 23:21:34 +0100 > l...@gnu.org (Ludovic Courtès) wrote: > >> >> This ‘unicode-start’ procedure is essentially a port of the >> >> ‘unicode_start’ script from ‘kbd’. I suppose the justification is to >> >> make sure we’re using UTF-8 input

bug#30505: Starting console/terminal Unicode support

2018-02-21 Thread Danny Milosavljevic
Hi Ludo, On Wed, 21 Feb 2018 23:21:34 +0100 l...@gnu.org (Ludovic Courtès) wrote: > >> This ‘unicode-start’ procedure is essentially a port of the > >> ‘unicode_start’ script from ‘kbd’. I suppose the justification is to > >> make sure we’re using UTF-8 input regardless of what the kernel defaul

bug#30505: Starting console/terminal Unicode support

2018-02-21 Thread Ludovic Courtès
Hi Danny, Danny Milosavljevic skribis: > On Mon, 19 Feb 2018 21:35:05 +0100 > l...@gnu.org (Ludovic Courtès) wrote: > >> > It was a bad idea to do the "\x1b%G" in the first place. >> >> Because it’s redundant with IUTF8? > > I meant because the Linux kernel does it already and it's better not