Ian Abbott <[EMAIL PROTECTED]> writes:
> Could this also be a problem on Unix systems using multibyte encoded
> (UTF-8) filesystems, if not now then in the future?
I doubt it. Historically Unix has always used bytes, not characters,
to name files. So it doesn't care about your encoding. I doub
Ian Abbott wrote:
> Wouldn't it be possible to link against unicows.dll to support
> Win95/98/ME?
No. unicows.dll is a closed-source library which is not normally part
of a Woe32 installation. You cannot distribute unicows.dll with the
binaries of a GPLed program - this would be a violation of the
On 27/04/2005 15:56, Bruno Haible wrote:
Tor Lillqvist <[EMAIL PROTECTED]> brought this up:
The technique of searching for directory separators in strings through the
ISSLASH macro does, on Woe32, not support non-ASCII pathnames in most CJK
locale encodings. Why? ISSLASH looks for a _byte_ with val
Tor Lillqvist <[EMAIL PROTECTED]> brought this up:
The technique of searching for directory separators in strings through the
ISSLASH macro does, on Woe32, not support non-ASCII pathnames in most CJK
locale encodings. Why? ISSLASH looks for a _byte_ with value 0x5C. However,
in these locale encodi
