On Tue, Feb 12, 2002 at 09:58:58AM +0200, Shachar Shemesh wrote:
> Sorry for retreating in the thread, but an important note struck me from
> my past.
>
> Nadav Har'El wrote:
>
> >No, UNIX traditionally operates on strings of "chars" (bytes/octets). No
> >special treatment is ever given by system calls to any byte except null
> >(and "/" in pathnames)
> >
> Ok, what if the locale allows "/" as a valid byte?
>
> Think that is outragous? Then either think again, or try to port your
> app to Japanese. I am not 100% sure about "/", but "\" is a legitimate
> second-byte in some Japanese MBCS encoded characters. If your locale is
> Japanese, these characters are taken in as a whole, and just make out a
> path. If not, well, you can't use Japanese characters (unicode
> non-withstanding).
>
> Now, I don't know the UTF-8 encoding, so I don't know how likely it is
> to happen there. Some attempt was made to avoid problematic characters.
> MBCS made sure null cannot be a second byte, for example. I do know that
> trying to use non-UTF to encode Japanese will require some OS support in
> the parsing of the string.
In UTF-8 it's a non-issue. BTW, you don't have to go as far as STFW to
find that; simply do 'man utf-8' (which, BTW, was written in '95. Not
very new, and still few people know about it).
>
> Shachar
>
>
>
> =================================================================
> To unsubscribe, send mail to [EMAIL PROTECTED] with
> the word "unsubscribe" in the message body, e.g., run the command
> echo unsubscribe | mail [EMAIL PROTECTED]
Didi
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
