From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 3452@emacsbugs.donarmstrong.com, cyd@stupidchicken.com
Subject: bug#3452: 23.0.94; display
Date: Mon, 08 Jun 2009 17:10:27 +0900 [thread overview]
Message-ID: <E1MDZw3-0002b5-Gq@etlken> (raw)
In-Reply-To: <E1MDWmz-0001XD-Tm@fencepost.gnu.org> (message from Eli Zaretskii on Mon, 08 Jun 2009 00:48:53 -0400)
In article <E1MDWmz-0001XD-Tm@fencepost.gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> > On terminal, if a zero-width character doesn't follow a base
> > character, Emacs composes that character by prepending SPACE
> > hoping that the terminal treats that zero-width character as
> > zero-width too.
> So these characters should be currently displayed as SPACE?
Yes, that's my intention.
> Is it a good idea to rely on the terminal in this situation? Do we
> know for a fact that many (most?) terminals indeed behave like that
> with zero-width characters?
I'm not sure but I thought that it's reasonable to assume
that a character defined as zero-width by Unicode does not
occupy a screen column by itself.
Not for U+202D, but such combining characters as U+0300 are
treated correctly by xterm (not by gnome-terminal).
> > To conclude, I think there's not that much we can do for
> > this situation. I think the current behaviour of
> > gnome-terminal (displaying standalone U+202D as a space of
> > width 1) is a bug.
> If other terminals behave correctly, I would agree. But if not,
> perhaps we need to work around this, if possible. For example, we
> could have an entry in display tables for these characters.
It seems xterm, gnome-terminal, GNU/Linux console, and
mlterm treat U+202D as spacing character, but, Konsole
(KDE's terminal) and kterm treats it as non-spacing
character.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-06-08 8:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 3:47 bug#3452: 23.0.94; display Chong Yidong
2009-06-07 9:16 ` Eli Zaretskii
2009-06-07 13:56 ` Chong Yidong
2009-06-07 14:30 ` Eli Zaretskii
2009-06-07 20:41 ` Chong Yidong
2009-06-07 22:53 ` Eli Zaretskii
2009-06-08 1:51 ` Kenichi Handa
2009-06-08 4:48 ` Eli Zaretskii
2009-06-08 8:10 ` Kenichi Handa [this message]
2009-06-08 8:44 ` Eli Zaretskii
2009-06-08 11:57 ` Kenichi Handa
2009-06-08 14:47 ` Chong Yidong
2009-06-09 18:00 ` Chong Yidong
2009-06-10 0:35 ` Kenichi Handa
-- strict thread matches above, loose matches on Subject: below --
2009-06-06 2:48 Chong Yidong
2009-06-03 2:53 Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1MDZw3-0002b5-Gq@etlken \
--to=handa@m17n.org \
--cc=3452@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).