From: marco <[EMAIL PROTECTED]>
On Tue, 3 Dec 2002, Edmund GRIMLEY EVANS wrote:
> Assume it's a null-terminated octet string. It shouldn't be empty,
> and it shouldn't contain (ASCII) '/'. You can't assume the string
> is valid character data in any particular encoding.
Thank you Edmund,
So, that means that there is no way for me to understand the encoding
unless I look at some mount options ... right?
Wrong.
There is no way to understand the encoding period.
That is, there is no encoding. A filename is just a
null-terminated octet string, like Edmund says.
No character set involved.
In the same filesystem some users may write French
in ISO 8859-1, while others write Russian in KOI-8.
The only source of information is the user.
(And the environment variables she set.)
Andries
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
