From: Thomas Dickey <dickey@his.com>
To: "Adam Tlałka" <atlka@pg.gda.pl>
Cc: "Alexander E. Patrakov" <patrakov@ums.usu.ru>,
torvalds@osdl.org, bug-ncurses@gnu.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]console:UTF-8 mode compatibility fixes
Date: Sat, 18 Feb 2006 20:43:56 -0500 (EST) [thread overview]
Message-ID: <20060218204040.B36972@mail101.his.com> (raw)
In-Reply-To: <43F7310E.4070109@pg.gda.pl>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=UTF-8; format=flowed, Size: 1128 bytes --]
On Sat, 18 Feb 2006, Adam TlaÅ~Bka wrote:
> Hmm, I don't know how current ncurses treat terminfo definition in UTF-8 mode
> and what linux terminal definition you are using in you test system. There
> are different definitions floating around in different distributions which
Since we're talking about ncurses, there are not "different definitions
floating around". Different distributions may of course have their
favorite tweaks, but ncurses definition for Linux console doesn't change
that much over the past ten years.
> are slightly different especially as we talk about acsc chars and enacs,
> smacs and rmacs sequences. Which is also wrong approach so there should be
> one proper definition of the linux console. Maybe kernel developers should
> prepare some most compatible and acceptable one.
> I can post the one I am using today:
...of course, this one isn't like any of the variations I've seen.
But you knew that. (Aside from the acs/enacs/rmacs/smacs changes,
I'm curious what happened to ich/ich1).
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
next prev parent reply other threads:[~2006-02-19 1:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 23:33 [PATCH]console:UTF-8 mode compatibility fixes Adam Tla/lka
2006-02-18 10:59 ` Andrew Morton
2006-02-18 16:01 ` Adam Tlałka
2006-02-19 4:24 ` Alexander E. Patrakov
2006-02-19 12:45 ` Adam Tla/lka
2006-02-19 16:16 ` Adam Tla/lka
2006-02-19 17:07 ` Alexander E. Patrakov
2006-02-18 14:17 ` Alexander E. Patrakov
2006-02-19 1:53 ` Thomas Dickey
2006-02-19 4:33 ` Alexander E. Patrakov
2006-02-19 11:47 ` Adam Tla/lka
2006-02-20 1:20 ` Thomas Dickey
2006-03-07 15:05 ` Adam Tlałka
2006-02-19 5:42 ` Alexander E. Patrakov
2006-02-19 10:15 ` Adam Tla/lka
2006-02-19 23:19 ` [PATCH]console:UTF-8 mode compatibility fixes - new version Adam Tla/lka
2006-02-20 8:14 ` [PATCH]console:UTF-8 mode compatibility fixes - new version #1 Adam Tla/lka
[not found] ` <43F72A1E.1090707@ums.usu.ru>
2006-02-18 14:37 ` [PATCH]console:UTF-8 mode compatibility fixes Adam Tlałka
2006-02-19 1:43 ` Thomas Dickey [this message]
2006-02-19 10:45 ` Adam Tla/lka
2006-02-18 22:35 ` Adam Tla/lka
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060218204040.B36972@mail101.his.com \
--to=dickey@his.com \
--cc=atlka@pg.gda.pl \
--cc=bug-ncurses@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrakov@ums.usu.ru \
--cc=torvalds@osdl.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox