9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Latchesar Ionkov <lucho@ionkov.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bidi
Date: Tue,  9 Mar 2004 15:29:14 -0500	[thread overview]
Message-ID: <20040309202914.GB10796@ionkov.net> (raw)
In-Reply-To: <101e1d3477ddc2d90dba62df1f391f86@vitanuova.com>

I think the better way is to have discontinuous selection on the screen. It
is more straightforward, and doesn't look that bad.

You can check both in Mozilla and IE how the selection works with mixed
direction text:

	http://ppewww.ph.gla.ac.uk/~flavell/charset/dir-sample.html

Thanks,
	Lucho

On Tue, Mar 09, 2004 at 08:18:59PM +0000, rog@vitanuova.com said:
> > 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.
> 
> it is indeed a limitation of the current model.  for instance sam and
> acme's command language assumes that dot, the current selection, can
> be represented by two numbers, and changing that would change many
> fundamental assumptions in the code.
> 
> acme(4) exposes its selections externally too; how would that
> work?
> 
> i wouldn't say it'd be impossible, but it might be easier to code the
> whole thing from scratch. would it be worth it (against, say,
> having a heuristic to determine directionality for the whole
> of a window)?
> 
> > What is it about?
> 
> it?


  reply	other threads:[~2004-03-09 20:29 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 [this message]
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
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=20040309202914.GB10796@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).