Re: quail, hebrew, gtk coding question
> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
Stephen J. Turnbull writes:
> But if it goes into the packages it must be *readable* by 21.4,
As I wrote to Aidan, I won't put UTF-8 into the packages at this
point
in time, but I won't veto it if he wants to do it.
Steve
In the past I have been complaining about backwards
compatibility, that
is why I think in this case I should chose a solution which does not
break backwards compatibility.
I did some checks: GNU emacs (24) handles all the niqqud +
Cantillation as far as I can tell.
Xemacs 21.5.X can only handly niqqud, Xemacs 21.4 cannot handle niqqud.
However whether I save a hebrew.el (quail file) in UTF8 or in
ISO-2022-7bit, does not "help" 21.4 if I open such a file, it will see
"rubbish"
In case of ISO-2022-7bit for example ("qj" ?^[%Gױ^[%＠)
So I think I will save in this format. And I will also have to modify
leim-list.el.
BTW (and I don't want to start a flame war) I googled and wikipediaed
around.
It seems to be that ISO-2022-7bit can handle all that UTF8(16) can
handle, and even UTF8 has been criticized for having shortcoming for
example for thai.
So why was UTF-8(16) chosen over ISO-2022-7bit?
thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta