Re: [PATCH v2 1/4] vt: preserve unicode values corresponding to screen characters

2018-06-17 Thread valdis . kletnieks
On Sun, 17 Jun 2018 19:17:51 -0400, Nicolas Pitre said: > On Sun, 17 Jun 2018, valdis.kletni...@vt.edu wrote: > > This preprocessor variable seems to be dangling in the breeze, with > > no way for it to get set? As a result, we pick up the #else define by > > default. > > That's actually what's i

Re: [PATCH v2 1/4] vt: preserve unicode values corresponding to screen characters

2018-06-17 Thread Nicolas Pitre
On Sun, 17 Jun 2018, valdis.kletni...@vt.edu wrote: > On Sun, 17 Jun 2018 15:07:03 -0400, Nicolas Pitre said: > > > diff --git a/drivers/tty/vt/vt.c b/drivers/tty/vt/vt.c > > index 1eb1a376a0..7b636638b3 100644 > > --- a/drivers/tty/vt/vt.c > > +++ b/drivers/tty/vt/vt.c > > @@ -317,6 +317,171 @@

Re: [PATCH v2 1/4] vt: preserve unicode values corresponding to screen characters

2018-06-17 Thread valdis . kletnieks
On Sun, 17 Jun 2018 15:07:03 -0400, Nicolas Pitre said: > diff --git a/drivers/tty/vt/vt.c b/drivers/tty/vt/vt.c > index 1eb1a376a0..7b636638b3 100644 > --- a/drivers/tty/vt/vt.c > +++ b/drivers/tty/vt/vt.c > @@ -317,6 +317,171 @@ void schedule_console_callback(void) > schedule_work(&console

[PATCH v2 1/4] vt: preserve unicode values corresponding to screen characters

2018-06-17 Thread Nicolas Pitre
The vt code translates UTF-8 strings into glyph index values and stores those glyph values directly in the screen buffer. Because there can only be at most 512 glyphs, it is impossible to represent most unicode characters, in which case a default glyph (often '?') is displayed instead. The original