Re: intermediate summary (Re: filename encoding)

[Markus Kuhn <Markus.Kuhn@xxxxxxxxxxxx>]

Tomohiro KUBOTA wrote on 2001-02-02 16:23 UTC:
> Then how about this:
> 
> -------------------+-----------------+----------------+---------------
>                    |        1        |       2        |       3
> -------------------+-----------------+----------------+---------------
> encoding for       |own encodings    |own encodings   |locale
> physical media     |                 |                |
>    ^               |                 |                |
>    | conversion    |locale-indep.    |locale-dep.     |(no conversion)
>    | by kernel     |filesystem-dep.  |filesystem-dep. |
>    v               |                 |                |
> parameter for      |UTF-8            |locale          |locale
> open()             |                 |                |
>    ^               |                 |                |
>    | conversion    |(no conversion)  |(no conversion) |(no conversion)
>    | by libc       |                 |                |
>    v               |                 |                |
> parameter for      |UTF-8            |locale          |locale
> fopen()            |                 |                |
>    ^               |                 |                |
>    | conversion    |locale-dep.      |(no conversion) |(no conversion)
>    | by softwares  |filesystem-indep.|                |
>    v               |                 |                |
> encoding for       |locale           |locale          |locale
> end user           |                 |                |
> -------------------+-----------------+----------------+---------------

Character forward and backward conversion at three layers thanks to
substantial added non-standard mechanisms to the kernel and libc! Great.
Thanks for illustrating so nicely the exact unmanageable and needless
mess that we want to avoid here. But may be you still haven't understood
that you are talking to the World Mental Health Organization's global
ISO2022/ISO8859/JIS/GB/KSC/KOI-8RCUVW/CPxxx eradication project here,
which has very well understood what it wants to get away from, namely
the above horror vision. Can we move this off linux-utf8 now please?

Let's focus here on how to get things running smoothly under UTF-8
locales. That's a simple and achievable cause. Anyone interested in more
is free to set up the linux-totalrecoding@xxxxxxxxxxxx mailing list
where you can discuss the nightmares of fopen(..., "r/ISO2022-JP").

Markus

-- 
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org,  WWW: <http://www.cl.cam.ac.uk/~mgk25/>

-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/