Re: poor additions in quail/latin-ltx

[Dave Love]

Stefan Monnier <address@hidden> writes:

> There was a bug in the handling of non-ASCII chars in multibyte "command
> strings".  I.e. binding "λ" to a key didn't work.  Now it does.
> But even before my fix, it worked to simply use a vector instead of
> a string.  See patch below.

OK, good.  I hadn't realized it was just non-ASCII strings that didn't
work.
>
> BTW, with my recent changes, all the chars that can be encoded in the user's
> locale will be displayed "correctly" (tho only if the fonts cooperate) with
> both the Lucid and Motif menus.  E.g. in a utf-8 locale, it should work
> about as well as with gtk.

That's surely wrong.  Making the text unibyte will only work with
iso-8859 coding systems (and maybe a few more).  It needs to be
encoded in the locale coding system.  Then the menu code has to use X
multibyte functions and maybe some other changes.  I don't remember
the details as it must be a couple of years ago I did it.  I guess I
still have the changes somewhere for what they're worth.

The Xawplus (?) widget set supports utf-8 text, and presumably someone
could copy what that does.  That would be reasonably useful now, but I
guess it doesn't do complex text processing and definitely wouldn't be
as good as rendering the text from a buffer.  It also wouldn't be
consistent with Emacs face selection.