Re: bidi-display-reordering is now non-nil by default

[Eli Zaretskii]

> From: Chong Yidong <address@hidden>
> Cc: address@hidden, address@hidden,
>         address@hidden
> Date: Tue, 09 Aug 2011 12:07:05 -0400
> 
> Eli Zaretskii <address@hidden> writes:
> 
> > Seriously, though: why do you need any conditions here?  An LRM will
> > have no effect if str is not reordered, so why not put it there
> > unconditionally?
> 
> Suppose a user kills some text from a Gnus summary buffer which contains
> these LRM characters, and yanks it into a latin-1 file.  Suddenly, that
> file can't be saved, even though there is no non-latin-1 script in the
> buffer clearly visible.

When you type "C-x C-s", Emacs clearly shows the characters that
cannot be encoded as Latin-1.  We all bump into such issues from time
to time, especially when communicating via email or news articles.  I
see no particular problem here.

> >   (get-char-code-property (aref str i) 'bidi-class)
> >
> > If this returns 'R for any character, it means the string _might_ need
> > LRM to be appended.
> 
> OK, let's go with this unless someone comes up with a better idea.

I think separating fields by TABs covered by `invisible' text
properties might be an alternative worth considering.