Paul Eggert wrote:
> I agree with you that file names should just use one encoding. If the
> user wants an UTF-8 world, the user should specify all the file names
> components in UTF-8, and then everything will work. If the user wants
> an EUC-JP world (not doable in Windows apparently, but the t
Bruno Haible <[EMAIL PROTECTED]> writes:
> In approach (2) LIBDIR will be an UTF-8 encoded pathname. The ISSLASH
> operation will therefore work correctly. However, fopen() expects a
> string in locale encoding, not in UTF-8 encoding. Therefore we have
> to replace the last line with
OK, I'm star
Paul Eggert wrote:
> Why would gnulib itself need to care
> about the difference between (2) and (4)? Either way, gnulib can
> easily look for '/' and '\' in path names. Isn't it up to the
> supplier of the underlying system-call implementation, and/or the
> gnulib user, to decide whether (2) or
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
