Re: LFN Utilities for Win32

["Robert Holmgren" holmgren@xxxxxxxx]

** Reply to message from "M.C."  on Wed, 18 Feb 2004 12:26:16
+0100


> I have discovered a minor issue that crashes the whole program, either
> with Ansified XyWrite or Standard Xywrite. It appear when long names of
> the files include high-ascii/ansi characters (stressed vowels and others
> like "¤", " ", "?", "é", etc.). It's not an important problem but keep
> in mind that european languages very often use those signs.

Well, that _is_ a problem. Never considered that -- actually, I can't remember
if I've ever _seen_ a file with a high-order character in the name! But I also
can't think what would make it become a problem... weelllll, on second thought,
I imagine there would be difficulty with translating u acute to U acute if
there is no U acute in the CodePage! What does the operating system do in such
a case? US-ASCII (CP437) doesn't include U acute. But because Win32 mainly
seems to run in CP1252, that shouldn't matter. Hmmm. Give me some examples of
this, will you? Example filenames. Especially, I wonder what happens when one
of those high-order characters >127 appears among the first six characters of
the long filename, i.e. in the part that appears before the tilde when the
filename is converted to 8.3? Is it only a problem in those cases, or is it a
problem if they appear *anywhere* in the LFN? ZIP up a few tiny test files
with those kinds of filenames, and send it to me privately, please! (I could
do this myself, but I'd like to see what real world problems you're having.)
Thanks for the warning. What OS are you using? Win98?