|
From: | Martin J. Dürst |
Subject: | Re: [emacs-bidi] Re: improving bidi documents display |
Date: | Thu, 03 Mar 2011 15:11:06 +0900 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4 |
On 2011/03/03 13:07, Eli Zaretskii wrote:
From: Miles Bader<address@hidden> Cc: address@hidden, address@hidden, address@hidden, address@hidden Date: Thu, 03 Mar 2011 10:32:49 +0900 Eli Zaretskii<address@hidden> 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 reason for this is that things have to be reevaluated/fixed anyway every time some buffer changes (e.g. insertion or deletion of a character) happens. So if the text is copied to a buffer that doesn't do any explicit reordering on top of the bidi algorithm, the special overlays/properties/whatever will just be purged out.
On the other hand, it may also make sense to copy a piece of TeX *with* the explicit TeX-specific reordering, because otherwise it may look like garbage. Please remember that the goal of all these activities is to make TeX or HTML/XML *legible*, because it's often illegible just with the basic bidi algorithm.
Regards, Martin. -- #-# Martin J. Dürst, Professor, Aoyama Gakuin University #-# http://www.sw.it.aoyama.ac.jp mailto:address@hidden
[Prev in Thread] | Current Thread | [Next in Thread] |