Hi,
At Wed, 01 May 2002 20:02:57 +0100,
Markus Kuhn wrote:
> I have for some time now been using UTF-8 more frequently than
> ISO 8859-1. The three critical milestones that still keep me from
> moving entirely to UTF-8 are
How about bash? Do you know any improvement?
Please note that tcsh have already supported east Asian EUC-like
multibyte encodings. I don't know it also supports UTF-8.
How about zsh?
For Japanese, character width problems and mapping table problems
should be solved to _start_ migration to UTF-8. (This is why
several "Japanese localization patches" are available for several
UTF-8-based softwares such as Mutt. We should find ways to stop
such localization patches.)
Also, I want people who develop UTF-8-based softwares to have
a custom to specify the range of UTF-8 support. For example,
* range of codepoints
U+0000 - U+2fff? all BMP? SMP/SIP?
* special processings
combining characters? bidi? Arab shaping? Indic scripts?
Mongol (which needs vertical direction)? How about wcwidth()?
* input methods
Any way to input complex languages which cannot be supported
by xkb mechanism (i.e., CJK) ? XIM? IIIMP? (How about Gnome2?)
Or, any software-specific input methods (like Emacs or Yudit)?
* fonts availability
Though each software is not responsible for this, "This software
is designed to require Times font" means that it cannot use
non-Latin/Greek/Cyrillic characters.
Though people in ISO-8859-1/2/15 region people don't have to care
about these terms, other peole can easily believe a "UTF-8-supported"
software and then disappointed to use it. Then he/she will become
distrust "UTF-8-supported" softwares. We should avoid many people
will become such.
---
Tomohiro KUBOTA <[EMAIL PROTECTED]>
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/
