linux-kernel - Re: [console] CSI (128+27) vs BIG5 (and possibly others)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090420112937.78ec67d5@lxorguk.ukuu.org.uk>
Date:	Mon, 20 Apr 2009 11:29:37 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Samuel Thibault <samuel.thibault@...-lyon.org>
Cc:	linux-kernel@...r.kernel.org, linux-console@...r.kernel.org
Subject: Re: [console] CSI (128+27) vs BIG5 (and possibly others)

On Sat, 18 Apr 2009 23:06:38 +0200
Samuel Thibault <samuel.thibault@...-lyon.org> wrote:

> Hello,
> 
> A chinese user reported that some characters don't show up fine on
> its console.  This happens to be because character 128+27 is handled
> specially by the linux Console.  I believe the same issues can happen
> with other characters sets.  Since linux' terminfo makes applications
> use \E[ anyway, would it be ok to add an option to disable the 128+27
> handling?

I'm reluctant to do so because its extra complication we don't need (at
least nobody has needed for over fifteen years), it's bound to confuse
some other application, and given almost everyone has already gone UTF-8
it's really debating a corner case only relevant to the past anyway.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/