From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Adjust point to move it off zero-width characters
Date: Mon, 08 Aug 2011 06:02:56 +0300 [thread overview]
Message-ID: <83pqkgzjtr.fsf@gnu.org> (raw)
In-Reply-To: <jwvei0wltkm.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: emacs-devel@gnu.org
> Date: Sun, 07 Aug 2011 20:50:23 -0400
>
> So you're saying that it should always be fused with the next char?
> Then my question becomes:
> Is there a reason to fuse it with the next char rather than fusing
> it with the preceding char? ;-)
There is a good reason for the directional control characters, see
below. For others, I think it's immaterial.
> > There's one other complication: to _really_ DTRT, there's one
> > directional control that needs to be fused with the preceding
> > character: the PDF, u+202c (POP DIRECTIONAL FORMATTING). That's
>
> That was my impression as well: the fusing should not always be done in
> the same direction.
> I'd still like to hear your reasoning about why it only depends on the
> particular zero-width char and not on the surrounding context.
I explained that, for the directional control characters: the need to
be able to interactively copy/paste text and be sure it displays the
same. The directional controls affect the _following_ characters. If
we "fuse" LRM/RLM/LRO/RLO/LRE/RLE with the previous character, they
can only be copy/pasted with the text that precedes them, where they
have no effect whatsoever. That's why PDF is different: it affects
the characters that precede it.
> > But hard-coding the special treatment of PDF on the C level sounds too
> > kludgey, no?
>
> Without knowing why you think LRM needs to be fused one way and PDF in
> the other way, it's hard to know for sure whether hard-coding them is
> a kludge, but yes: it doe sound likely to be so.
So what are the alternatives? Another char-table?
next prev parent reply other threads:[~2011-08-08 3:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 14:47 Adjust point to move it off zero-width characters Eli Zaretskii
2011-08-07 16:13 ` Stefan Monnier
2011-08-07 16:39 ` Eli Zaretskii
2011-08-07 16:46 ` Eli Zaretskii
2011-08-07 17:10 ` Eli Zaretskii
2011-08-08 0:50 ` Stefan Monnier
2011-08-08 3:02 ` Eli Zaretskii [this message]
2011-08-08 4:12 ` 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=83pqkgzjtr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).