From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: non-breaking hyphens
Date: Tue, 18 Oct 2011 06:00:15 +0200 [thread overview]
Message-ID: <83r52buey8.fsf@gnu.org> (raw)
In-Reply-To: <87ehybm0i0.fsf@gnu.org>
> From: Chong Yidong <cyd@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Mon, 17 Oct 2011 23:39:35 -0400
>
> I'm not sure I understand the goal of `nobreak-char-display'. Is it for
> warning the user when there is an ASCII look-alike character that isn't
> really ASCII? I guess that's mainly to avoid issues with source code?
Yes, probably. But I'm only guessing here. Can you find any traces
of discussing this in the archives?
> If so, handling only U+A0 and U+AD would be incomplete, as you say.
> Also, the name and documentation of `nobreak-char-display' is misleading
> or incomplete---it shouldn't be limited to non-breaking or shy
> characters, since there are many other non-ASCII lookalikes like U+2010
> (the "true" hyphen), U+2002 (the "en space"), and U+2007 (the "figure
> space").
I agree.
> I'm guessing the reason U+A0 and U+AD are treated specially is that
> those characters happened to be in Latin-1 (i.e. hysterical raisins).
Most probably.
next prev parent reply other threads:[~2011-10-18 4:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 13:56 non-breaking hyphens Chong Yidong
2011-10-17 14:45 ` Eli Zaretskii
2011-10-18 3:39 ` Chong Yidong
2011-10-18 4:00 ` Eli Zaretskii [this message]
2011-10-18 12:08 ` Chong Yidong
2011-10-18 13:11 ` Stefan Monnier
2011-10-18 17:43 ` Drew Adams
2011-10-19 8:28 ` Juri Linkov
2011-10-19 13:59 ` Drew Adams
2011-10-19 14:37 ` Stefan Monnier
2011-10-18 13:41 ` Eli Zaretskii
2011-10-19 8:27 ` Juri Linkov
2011-10-19 8:39 ` Eli Zaretskii
2011-10-19 13:59 ` Drew Adams
2011-10-19 15:12 ` Eli Zaretskii
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=83r52buey8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@gnu.org \
--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 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.