From: Latchesar Ionkov <lucho@ionkov.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bidi
Date: Tue, 9 Mar 2004 15:24:50 -0500 [thread overview]
Message-ID: <20040309202450.GA10796@ionkov.net> (raw)
In-Reply-To: <2ee2ff33ac36a17c304b97238571142f@vitanuova.com>
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.
next prev parent reply other threads:[~2004-03-09 20:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 16:55 [9fans] non-english keyboard? David Tolpin
2004-03-09 17:02 ` andrey mirtchovski
2004-03-09 17:07 ` David Tolpin
2004-03-09 17:12 ` Fco.J.Ballesteros
2004-03-09 17:40 ` andrey mirtchovski
2004-03-09 18:21 ` Dave Lukes
2004-03-09 18:37 ` [9fans] information <-> knowledge rog
2004-03-09 18:42 ` [9fans] non-english keyboard? David Tolpin
2004-03-09 18:45 ` Dave Lukes
2004-03-09 18:50 ` David Tolpin
2004-03-10 0:04 ` David Presotto
2004-03-09 19:02 ` Latchesar Ionkov
2004-03-10 7:36 ` Fco.J.Ballesteros
2004-03-09 19:17 ` 9nut
2004-03-09 20:02 ` [9fans] bidi rog
2004-03-09 20:00 ` David Tolpin
2004-03-09 20:18 ` rog
2004-03-09 20:29 ` Latchesar Ionkov
2004-03-09 20:39 ` David Tolpin
2004-03-10 20:54 ` Derek Fawcus
2004-03-10 21:07 ` rog
2004-03-10 21:43 ` Latchesar Ionkov
2004-03-10 22:17 ` 9nut
2004-03-10 1:53 ` Scott Schwartz
2004-03-10 21:09 ` rog
2004-03-09 20:24 ` Latchesar Ionkov [this message]
2004-03-10 15:47 ` Fco.J.Ballesteros
2004-03-10 17:20 ` David Tolpin
2004-03-11 1:04 ` Kenji Okamoto
2004-03-09 23:51 ` [9fans] non-english keyboard? boyd, rounin
2004-03-10 9:47 ` Dave Cummings
2004-03-10 16:04 ` a
2004-03-10 19:45 ` Michael Baldwin
2004-03-09 23:49 ` boyd, rounin
2004-03-10 11:22 ` Aharon Robbins
2004-03-10 16:10 ` Dave Lukes
2004-03-09 23:45 ` boyd, rounin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040309202450.GA10796@ionkov.net \
--to=lucho@ionkov.net \
--cc=9fans@cse.psu.edu \
/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.
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 NNTP newsgroup(s).