From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: Thomas Dickey <dickey@his.com>
Cc: "Adam Tla/lka" <atlka@pg.gda.pl>,
torvalds@osdl.org, bug-ncurses@gnu.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]console:UTF-8 mode compatibility fixes
Date: Sun, 19 Feb 2006 09:33:37 +0500 [thread overview]
Message-ID: <43F7F521.2060308@ums.usu.ru> (raw)
In-Reply-To: <20060218204407.L36972@mail101.his.com>
Thomas Dickey wrote:
> On Sat, 18 Feb 2006, Alexander E. Patrakov wrote:
>
>> If ncurses attempt to add some Chinese character to the Linux text
>> screen, Linux (correctly) prints this replacement character and advances
>> the cursor by one position. Ncurses think that the cursor has moved two
>> positions forward. The effect is that when you view the testcase in Lynx
>> (compiled --with-screen=ncursesw) on Linux console and press PageDown,
>> the fourth line contains "Thek" instead of "The" in the end.
>>
>> This disagreement has to be solved somehow.
>
>
> yes. ncurses has no better information for this than the result from
> wcwidth(). Shall we add another kludge to accommodate Linux console?
Maybe yes, since putting wcwidth() into the kernel is a bigger kludge,
because linux kernel will never draw CJK, and because after glibc
update, kernel and glibc might disagree upon wcwidth of some characters.
So on linux console, ncurses should draw two 0xfffd characters when a
character with wcwidth > 1 is requested.
> (Are there other terminal emulators with this specific problem?)
Not sure. I will test putty a bit later. Anyway, an environment variable
for this kludge may be a good idea.
--
Alexander E. Patrakov
next prev parent reply other threads:[~2006-02-19 4:32 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 [this message]
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
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=43F7F521.2060308@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--cc=atlka@pg.gda.pl \
--cc=bug-ncurses@gnu.org \
--cc=dickey@his.com \
--cc=linux-kernel@vger.kernel.org \
--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