unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: bruce.connor.am@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: On the masking of undisplayable characters
Date: Tue, 07 Jul 2015 05:43:26 +0300	[thread overview]
Message-ID: <83vbdwvga9.fsf@gnu.org> (raw)
In-Reply-To: <CAAdUY-L+RkaP1KMhZgb+EZbqd5_aSZDRVKgvAfPacwLo=ce4Kw@mail.gmail.com>

> Date: Mon, 6 Jul 2015 20:57:08 +0100
> From: Artur Malabarba <bruce.connor.am@gmail.com>
> Cc: emacs-devel <emacs-devel@gnu.org>
> 
> > What characters are you talking about, specifically?
> 
> Round quotes were displayed as hard quotes. The reason this happened on my pc
> was a bug, but I understand that for systems that really can't display them
> this is what will happen. 
> 
> I didn't check whether this applies to any other characters. I was just
> surprised to find out the file was not being displayed as-is without so much as
> a notice.

It should happen only with quotes, and presumably only in
documentation-related buffers.  The rationale is that we cannot afford
showing illegible documentation to users just because their terminal
is incapable of displaying these important characters.

I suggested to limit this to windows showing *Help* buffers, but it
was decided to wait until someone complains.

> > It's hard to respond without knowing the details. Most of the uses of
> > display tables I know of are there for ages, so adding some kind of
> > message about that now would seem inappropriate. (And when exactly do
> > we display that message? when the character is first displayed?)
> 
> When visiting the file and when the character is typed for the first time,
> would be an option.

Not really: the display engine doesn't examine any of those
characters, until they are on or very near to the visible portion of
the buffer.

> > the glyphless-char-display feature,
> 
> I don't know which characters are affected by this.

Those that cannot be displayed by any fonts.



  parent reply	other threads:[~2015-07-07  2:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 17:38 On the masking of undisplayable characters bruce.connor.am
2015-07-06 18:16 ` Eli Zaretskii
2015-07-06 19:57   ` Artur Malabarba
2015-07-06 23:07     ` Juri Linkov
2015-07-07  2:44       ` Eli Zaretskii
2015-07-07 14:53         ` Eli Zaretskii
2015-07-07  2:43     ` Eli Zaretskii [this message]
2015-07-07  9:32       ` Artur Malabarba
2015-07-07 12:17         ` Yuri Khan
2015-07-07 12:29           ` Artur Malabarba
2015-07-07 13:14             ` Yuri Khan
2015-07-07 13:23               ` Artur Malabarba
2015-07-20 11:02             ` N. Jackson
2015-07-07 15:51         ` Stefan Monnier

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=83vbdwvga9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bruce.connor.am@gmail.com \
    --cc=emacs-devel@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).