From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: user42_kevin@yahoo.com.au, 26396@debbugs.gnu.org
Subject: bug#26396: 25.1; char-displayable-p on a latin1 tty
Date: Mon, 17 Apr 2017 21:32:05 +0300 [thread overview]
Message-ID: <83tw5mdgwq.fsf@gnu.org> (raw)
In-Reply-To: <b9c48971-f7d6-df8e-9cfe-771f6c3963a6@cs.ucla.edu> (message from Paul Eggert on Mon, 17 Apr 2017 11:08:09 -0700)
> Cc: user42_kevin@yahoo.com.au, 26396@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Mon, 17 Apr 2017 11:08:09 -0700
>
> On 04/17/2017 01:08 AM, Eli Zaretskii wrote:
>
> > My reading of the code is that at least some of these unsupported
> > characters will NOT be displayed as \uNNNNN, but rather as some
> > fallback glyph produced by the console itself, which is not what we
> > want, I think.
> Yes, that's what happens. It's not ideal, and perhaps it could be
> improved. (I hope by someone else....)
Lat's hope.
> There are similar display problems even in unibyte mode on the Linux
> console. Sometimes a character above U+00FF is displayed as '\uNNNN',
> sometimes as '?', sometimes the same character is displayed in different
> forms depending on what else is in the buffer, and I don't know why.
> (And likewise, I don't want to spend time worrying about this, as the
> 1990s are long gone....)
Yes, the TTY code that handles such characters has some very weird
logic.
Can you show an example of a character displayed in different forms
depending on buffer contents? I'd like to look what the code does and
why.
Thanks.
next prev parent reply other threads:[~2017-04-17 18:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 2:20 bug#26396: 25.1; char-displayable-p on a latin1 tty Kevin Ryde
2017-04-08 7:42 ` Eli Zaretskii
2017-04-09 5:16 ` Kevin Ryde
2017-04-10 6:47 ` Eli Zaretskii
2017-04-10 7:05 ` Eli Zaretskii
2017-04-10 7:45 ` Eli Zaretskii
2017-04-13 6:19 ` Paul Eggert
2017-04-13 7:16 ` Eli Zaretskii
2017-04-13 20:58 ` Paul Eggert
2017-04-14 3:01 ` Kevin Ryde
2017-04-14 18:59 ` Paul Eggert
2017-04-14 12:37 ` Eli Zaretskii
2017-04-14 18:56 ` Paul Eggert
2017-04-15 8:48 ` Eli Zaretskii
2017-04-15 21:12 ` Paul Eggert
2017-04-16 5:59 ` Eli Zaretskii
2017-04-16 20:25 ` Paul Eggert
2017-04-17 6:19 ` Eli Zaretskii
2017-04-17 3:00 ` Kevin Ryde
2017-04-17 3:26 ` Paul Eggert
2017-04-17 5:56 ` Paul Eggert
2017-04-17 7:33 ` Eli Zaretskii
2017-04-17 17:22 ` Paul Eggert
2017-04-17 6:24 ` Eli Zaretskii
2017-04-17 6:41 ` Paul Eggert
2017-04-17 7:27 ` Kevin Ryde
2017-04-17 8:08 ` Eli Zaretskii
2017-04-17 18:08 ` Paul Eggert
2017-04-17 18:32 ` Eli Zaretskii [this message]
2017-04-18 17:49 ` Paul Eggert
2017-04-18 18:19 ` Eli Zaretskii
2017-04-13 22:07 ` Richard Stallman
2017-04-13 22:18 ` Paul Eggert
2017-04-14 19:48 ` Richard Stallman
2017-04-11 7:22 ` Kevin Ryde
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=83tw5mdgwq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26396@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=user42_kevin@yahoo.com.au \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.