Re: [9front] [PATCH] introduce code points above BMP to /lib/unicode

[qwx@sciops.net]

On Sun Oct 23 16:27:01 +0200 2022, ori@eigenstate.org wrote:
> Currently 9front only works well with the latinoid languages, and
> with Moody's work, I suspect passably with Chinese and Japanese.
> 
> Languages like hebrew (the only non-latin language I know) are
> unusable, though with hebrew the larger problem is the lack of
> right to left support.
> 
> as far as what people do when it's missing? use english; I can't
> do hebrew on 9front. doesn't work.
> 
> saying "it will never work" is an option; I think our UI will
> always be in English, for example, but it seems like it would
> be a nice goal to type and view any language correctly.
> 
> at the same time, it *is* a lot of complexity.
[...]
> > Again, I can't speak for anyone, but personally I'd always expect one
> > single backspace to erase any megarune, which is also what I've seen
> > in virtual keyboards on the shitphones I've touched.  I'd be very
> > confused if some characters in the middle of a sentence refuse to be
> > removed at once.
> 
> In hebrew input, at least, I'd expect the opposite; I think it will
> end up depending on culture what behavior is 'normal', but  on this
> sort of thing, we can set our own expectations.


Makes sense.  There's other scripts that are very difficult as well
and, as you say, put together it involves quite a lot of work.  There
are lots of ideas about changing rio and libdraw and what not in some
future, but perhaps in the mean time, if these unicodedata and
composition changes would actually help on their own, imho it makes
sense to pursue them.

Just my 2¢, and thanks for clarifying :)

Cheers,
qwx