From: Clint Adams <clint@zsh.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: multibyte backwarddeletechar
Date: Sun, 21 Oct 2001 14:21:06 -0400 [thread overview]
Message-ID: <20011021142106.A19465@dman.com> (raw)
In-Reply-To: <1011021171339.ZM14059@candle.brasslantern.com>; from schaefer@brasslantern.com on Sun, Oct 21, 2001 at 05:13:38PM +0000
> I'm a bit surprised that this wouldn't cause significant confusion in
> the ZLE display code. How did the multi-byte character get input in
> the first place? Is it displayed as occupying one character position
> on the screen, or several? If only one, doesn't the cursor end up in
> the wrong place on most word- or line-oriented motions that cross it?
That depends on the terminal emulator and font. If I run
LANG=zh_TW.Big5 crxvt -ls -fm taipei16 -fn 8x16 -km big5 ,
each BIG5 character (2 octets) appears to take up the
vertical space on one ASCII character, and horizontal space
of two ASCII characters. If I run
LANG=zh_TW.Big5 crxvt -ls -fm taipei14 -fn 8x16 -km big5 ,
each BIG5 character (2 octets) appears to take up the
vertical space on one ASCII character, and horizontal space
of two and a half (2.5) ASCII characters, although crxvt
does some ugly overlapping resulting in ZLE not getting confused.
If I run LANG=ja_JP.UTF-8 xterm -class UXTerm ,
each UTF-8 Kanji character (3 octets) appears to take up
the same (2 horizontal, 1 vertical) space. In this case,
ZLE does get horribly confused. If I run
LANG=ru_RU.UTF-8 xterm -class UXTerm ,
each UTF-8 Cyrillic character (3 octets) appears to take
up the horizontal and vertical space of one ASCII character.
This also makes ZLE horribly confused. If I run
LANG=fr_FR.UTF-8 xterm -class UXTerm ,
each UTF-8 French non-ASCII character (2 octets)
appears to take up the horizontal and vertical space of one
ASCII character. Again, this confuses ZLE.
I imagine that 6-byte characters will generally take up
less horizontal space than 6 ASCII characters as well.
> If we're going to support wide and/or multi-byte characters, I think we
> should Do It Right, not by pasting a zillion workarounds into individual
> editor functions.
I suspect that Doing It Right involves changing char *line to
wchar_t *wline, and modifying all dependencies accordingly.
Additionally, we'd need to figure out how much space each
individual character consumes.
next prev parent reply other threads:[~2001-10-21 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-21 15:42 Clint Adams
2001-10-21 17:13 ` Bart Schaefer
2001-10-21 18:21 ` Clint Adams [this message]
2001-10-22 0:57 ` Geoff Wing
2001-10-22 1:50 ` Clint Adams
2001-10-22 3:23 ` Geoff Wing
2001-10-22 11:27 ` Clint Adams
2001-10-22 5:20 ` Borsenkow Andrej
2001-10-22 11:32 ` Clint Adams
2001-10-22 12:02 ` Borsenkow Andrej
2001-10-24 13:57 ` Clint Adams
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=20011021142106.A19465@dman.com \
--to=clint@zsh.org \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).