From mboxrd@z Thu Jan  1 00:00:00 1970
From: Latchesar Ionkov <lucho@ionkov.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bidi
Message-ID: <20040309202450.GA10796@ionkov.net>
References: <d410324c1d59d0cf66efe0616f4ddb40@9netics.com> <2ee2ff33ac36a17c304b97238571142f@vitanuova.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2ee2ff33ac36a17c304b97238571142f@vitanuova.com>
User-Agent: Mutt/1.4.1i
Date: Tue,  9 Mar 2004 15:24:50 -0500
Topicbox-Message-UUID: 2777fa22-eacd-11e9-9e20-41e7f4b1d025

What is the point of having full Unicode support in Plan9, if people
that use r-l languages cannot use it? How are they supposed to write in
these languages if rio/acme doesn't render the text correctly? 

If bidi support doesn't add too much complexity, I don't see why we, the
majority that uses l-r languages, should object to something that doesn't
affect us much.

Thanks,
	Lucho

On Tue, Mar 09, 2004 at 08:02:23PM +0000, rog@vitanuova.com said:
> > 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?)
> 
> 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.
> 
> 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).
> 
> bidi *display*, certainly.
> 
> but in rio/acme... bad idea, i think.