unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: emacs-bidi@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Handling invisible text in bidirectional display
Date: Mon, 18 Jan 2010 07:42:53 +0100	[thread overview]
Message-ID: <87vdezykuq.fsf@lola.goethe.zz> (raw)
In-Reply-To: 831vho8nfl.fsf@gnu.org

Eli Zaretskii <eliz@gnu.org> writes:

>> From: David Kastrup <dak@gnu.org>
>>
>> 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.

-- 
David Kastrup

  reply	other threads:[~2010-01-18  6:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16 16:54 Handling invisible text in bidirectional display Eli Zaretskii
2010-01-16 18:43 ` martin rudalics
2010-01-16 20:32   ` Eli Zaretskii
2010-01-17  8:59     ` martin rudalics
2010-01-17 19:06       ` Eli Zaretskii
2010-01-18  8:11         ` martin rudalics
2010-01-18  9:54           ` Eli Zaretskii
2010-01-18 10:39             ` martin rudalics
2010-01-18 12:35               ` Eli Zaretskii
2010-01-16 19:15 ` David Kastrup
2010-01-16 20:37   ` Eli Zaretskii
2010-01-17 16:05     ` Richard Stallman
2010-01-17 19:29       ` Eli Zaretskii
2010-01-17 20:17         ` David Kastrup
2010-01-17 20:39           ` Ehud Karni
2010-01-17 20:51           ` Eli Zaretskii
2010-01-18  6:42             ` David Kastrup [this message]
2010-01-18  8:52               ` Eli Zaretskii
2010-01-16 19:56 ` Stefan Monnier
2010-01-16 20:53   ` Eli Zaretskii
2010-01-17 16:04     ` Richard Stallman
2010-01-17 18:24       ` Eli Zaretskii
2010-01-18 11:56         ` Richard Stallman
2010-01-22 13:41       ` Bidi TODO (was: Handling invisible text in bidirectional display) Eli Zaretskii
2010-02-01 14:48         ` [emacs-bidi] " Ehud Karni
2010-01-18  1:27     ` Handling invisible text in bidirectional display Kenichi Handa
2010-01-18  4:00       ` Eli Zaretskii
2010-01-18  7:40         ` Kenichi Handa
2010-01-18  8:56           ` Eli Zaretskii
2010-01-18 11:09             ` Kenichi Handa

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=87vdezykuq.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-bidi@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).