Re: Re: Handling invisible text in bidirectional display

> From: David Kastrup <[email protected]>
> Date: Mon, 18 Jan 2010 07:42:53 +0100
> Cc: [email protected]
> 
> Eli Zaretskii <[email protected]> writes:
> 
> >> From: David Kastrup <[email protected]>
> >>
> >> There also is a difference between invisibility and display properties
> >> here: if there is a display property on a letter "x", it is hard to see
> >> why several consecutive images should be reordered to be L->R.  Of
> >> course, one should argue that in the presence of L->R, people should
> >> take care to use the right "shadowed" character to match the intended
> >> left/rightness of the image.  But I think that is not really sane.  If
> >> we want display property material to have an explicit direction, it
> >> should be set with properties, not by some magic derivation from the
> >> underlying invisible text.
> >
> > I don't understand the use-case, and without it this reads like a
> > charade (what "x"? which "shadowed" characters? what images?).  Please
> > show a complete example, then I'll be able to reason about it.
> 
> Just find some JPG file into an Emacs buffer and look at the underlying
> presentation.

If you are talking about a display property whose value is an image,
then the discussion until now in this thread did not cover that
use-case.  At least what I wrote did not cover it.  I was talking only
about display properties whose value is a string.