From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Tolpin <dvd@davidashen.net>
Message-Id: <200403092000.i29K0SMu094231@adat.davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bidi
In-Reply-To: <2ee2ff33ac36a17c304b97238571142f@vitanuova.com>
Date: Wed, 10 Mar 2004 00:00:28 +0400
Topicbox-Message-UUID: 2768680a-eacd-11e9-9e20-41e7f4b1d025

> > I think libframe is a good place to add it. It will work both for acme and
> > rio.
>
> do we really want non-displaying characters in acme/rio?  how does one
> deal with selection (have i selected this zero-width character i've
> just clicked on or not?)

This has no relation to bidi. Unicode bidi does not imply use
of any extra characters; just the opposite, the display media
should automatically re-order the text. Explicit bidi marks
are used only for codepoints with weak directionality, and
this feature can be easily dropped if strong bidirectionality
is supported.

> and if i've got l-r and r-l text on the same line, and i drag a
> selection...  how can it work?  either i've got a discontinuous
> selection in the underlying file, or a discontinuous selection on
> screen.

You get discontinuous selection in the underlying file. If it
does not work with the current model, then it is a limitation
of the current model.

> glyphs as display markup don't make a great deal of sense to me (but
> i'm sure others will tell me they're the only way forward).

What is it about?