Re: Re: improving bidi documents display
"Martin J. Dürst" <[email protected]> Thu, 03 Mar 2011 15:11:06 +0900
| Newsgroups | gmane.emacs.bidi,gmane.emacs.devel |
|---|---|
| Organization | Aoyama Gakuin University |
| Message-ID | <[email protected]> |
On 2011/03/03 13:07, Eli Zaretskii wrote: >> From: Miles Bader<[email protected]> >> Cc: [email protected], [email protected], [email protected], em= [email protected] >> Date: Thu, 03 Mar 2011 10:32:49 +0900 >> >> Eli Zaretskii<[email protected]> writes: >>>> Sure, but that's a general issue in Emacs, so there are already >>>> mechanisms in place to help deal with it >>>> (e.g. yank-excluded-properties). >>> >>> This one's different, believe me: no other text property changes the >>> _order_ of characters on display in creative ways. It could easily >>> render the text illegible, under just the right circumstances. >> >> But isn't the "changed order" natural for the characters it's attached >> to? > > Only in the context of the kind of text (e.g., TeX) it was copied > from. The copying may work if the feature is switched on for all buffers. The=20 reason for this is that things have to be reevaluated/fixed anyway every=20 time some buffer changes (e.g. insertion or deletion of a character)=20 happens. So if the text is copied to a buffer that doesn't do any=20 explicit reordering on top of the bidi algorithm, the special=20 overlays/properties/whatever will just be purged out. On the other hand, it may also make sense to copy a piece of TeX *with*=20 the explicit TeX-specific reordering, because otherwise it may look like=20 garbage. Please remember that the goal of all these activities is to=20 make TeX or HTML/XML *legible*, because it's often illegible just with=20 the basic bidi algorithm. Regards, Martin. --=20 #-# Martin J. D=C3=BCrst, Professor, Aoyama Gakuin University #-# http://www.sw.it.aoyama.ac.jp mailto:[email protected]