Tomohiro KUBOTA <[EMAIL PROTECTED]>:
> There are a few possibilities:
>
>
> ---------------------------------------------------------------------
> encoding for parameter for parameter for encoding for
> physical media[1] open(kernel)[4] fopen(libc)[5] the end user[6][7]
> ---------------------------------------------------------------------
> 1. own encodings[2] UTF-8 UTF-8 locale
> 2. own encodings locale locale locale
> 3. locale[3] locale locale locale
> 4. mixture of 2 and 3
> ---------------------------------------------------------------------
I think this table is misleading because it lists encodings instead of
conversions. Aren't 1 and 3 really the same, because both mean that
there is no locale-dependent conversion on the kernel side of fopen?
In both cases a program can use any encoding it wants - EBCDIC or
whatever - because the string is just passed through unconverted. I
would recommend UTF-8, but I wouldn't want to (and wouldn't know how
to) enforce it.
Edmund
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
