From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: cyd@gnu.org, emacs-devel@gnu.org
Subject: Re: non-breaking hyphens
Date: Wed, 19 Oct 2011 10:39:22 +0200 [thread overview]
Message-ID: <8339epv0hx.fsf@gnu.org> (raw)
In-Reply-To: <8762jlmofg.fsf@mail.jurta.org>
> From: Juri Linkov <juri@jurta.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> Date: Wed, 19 Oct 2011 11:27:15 +0300
>
> > The right way to implement this feature, as brought up in the 2004
> > thread, would be to specify the affected characters with a char-table
> > rather than hardcoding them. But we should probably leave such a change
> > till after 24.1.
>
> Since glyphless characters (like "ZERO WIDTH NO-BREAK SPACE") are
> displayed now using a char-table, it makes sense to display confusable
> characters with a similar char-table (e.g. `confusable-char-display')
> where display methods could specify how to display them (face, etc.)
>
> BTW, there is already a mapping in lisp/international/latin1-disp.el
> in `latin1-display-ucs-per-lynx' that can be used to match confusable
> characters.
Yes, we have several overlapping features that handle these and other
issues. One other related "overlap" is glyphless characters display
vis-a-vis display tables; currently they contradict. The current
situation is quite a mess, and we need to resolve it by designing a
coherent set of features to handle all that.
next prev parent reply other threads:[~2011-10-19 8:39 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
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 [this message]
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=8339epv0hx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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.