Hi,
At Tue, 30 Jan 2001 14:04:41 +0000 (GMT),
Robert Brady <[EMAIL PROTECTED]> wrote:
> I've got some fixes (mainly plane related) to sync in, are you planning a
> -k6 soon?
Now I have no plan of improvement. Though I wrote about great rewriting
using ucs4_t instead of wrong wchar_t and unsigned int, I think this is
of low priority. I have not found any bugs so far. However, I think the
following points should be fixed.
- we will have to insert more #ifdef's for nl_langinfo() and wcwidth()
and modify ./configure script. (I entirely don't know how to use
autoconf and automake.)
- I am now rewriting the manpage. I will at least write about my
options (-8, -u8, -lc, and -wc*) and my resources (encodingMode and
widthMode).
> Does ISO-2022 see much/any use as the locale encoding, or it it just used
> for interchange?
I think the fullset of ISO-2022 is not used as the locale encoding.
(It cannot be used as locale encoding for Linux/Glibc because Glibc
adopts UCS-4 as wchar_t.) However, a few (but popular in Japan)
softwares such as jless, lv, and so on use ISO-2022 as the default
encoding for output. This is because ISO-2022 is almost free from
'mojibake' - broken characters caused by encoding mismatching.
---
Tomohiro KUBOTA <[EMAIL PROTECTED]>
http://surfchem0.riken.go.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/lists/
