Kenneth Whistler wrote:
>
> Dipti Srivastava asked:
>
>> If I set my LC_TYPE to en_US.UTF8 do I need to convert the non-Ascii
>> characters like '\' in the filename for functions like open, etc.
>
> '\' *is* an ASCII character. 0x5C in ASCII to be exact. It is
> also 0x5C in UTF-8, so no (other) co
On Mon, 23 Feb 2004, Dipti Srivastava wrote:
> Dipti Srivastava asked:
>
> > If I set my LC_TYPE to en_US.UTF8 do I need to convert the non-Ascii
> > characters like
> > '\' in the filename for functions like open, etc.
It seems like your original question led Ken to believe you're working
on P
PROTECTED]
Sent: 2004å2æ24æ 8:36
To: 'Kenneth Whistler'
Cc: [EMAIL PROTECTED]
Subject: RE: Filenames with non-Ascii characters
What if the filename contains contains Japanese characters e.g. the Japanese
file separator.
Dipti
-Original Message-
From: Kenneth Whistler [mailto:[EMAIL
What if the filename contains contains Japanese characters e.g. the Japanese
file separator.
Dipti
-Original Message-
From: Kenneth Whistler [mailto:[EMAIL PROTECTED]
Sent: Monday, February 23, 2004 6:33 PM
To: Dipti Srivastava
Cc: [EMAIL PROTECTED]
Subject: Re: Filenames with non-Ascii
Dipti Srivastava asked:
> If I set my LC_TYPE to en_US.UTF8 do I need to convert the non-Ascii
> characters like
> '\' in the filename for functions like open, etc.
'\' *is* an ASCII character. 0x5C in ASCII to be exact. It is
also 0x5C in UTF-8, so no (other) conversion is required.
UTF-8 is de
Hi,
If I set my LC_TYPE to en_US.UTF8 do I need to convert the non-Ascii
characters like
'\' in the filename for functions like open, etc.
Thanks,
Dipti
6 matches
Mail list logo
