Re: [I18n][call for comments] XTerm patch to invoke luit

[Tomohiro KUBOTA <tkubota@xxxxxxxxxxx>]

Hi,

At Fri, 7 Jun 2002 15:06:09 +0200 (CEST),
Bruno Haible wrote:

>     CP1255  (Hebrew)
>     CP1258, TCVN  (Thai)
> 
> Either you hardwire them, or you document that xterm should not be
> used with 8-bit fonts in these encodings. (Are there 8-bit fonts for
> CP1255, CP1258, TCVN at all??)

For TIS-620 (ISO-8859-11) Thai, I don't like documentation way
because luit already supports TIS-620 and Thai people apparently
benefit from it.

For CP1258 and TCVN Vietnamese, I think luit will easily support
them, though it doesn't support them now.

For Hebrew, I don't think we have to care about it so far, because
XTerm doesn't support bidi and we are still not agreed whether to
support bidi or not.

I can add ISCII for complex 8bit encodings list.  However, since
XTerm doesn't support complex Indic scripts, I think it can be
neglected so far.


IMO, documentation way should be avoided as far as possible.
It is because, if we need to write a documentation for a language,
speakers of the language will probably need to read tens of documents
to use tens of softwares.  It is just Japanese people are localted
and I imagine people from other countries such as Thai and Vietnam
are also.


Thus, I think hard-coding of "th" and "vi" is a good way so far.

And also, I heard that systems without locale (with X_LOCALE)
do not have MB_CUR_MAX.  If it is true, we also have to have
a fallback for this.

---
Tomohiro KUBOTA <kubota@xxxxxxxxxx>
http://www.debian.or.jp/~kubota/
"Introduction to I18N"  http://www.debian.org/doc/manuals/intro-i18n/
--
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/linux-utf8/