[PATCH] stdlib/sb_charsets.c: Don't leave untranslatable characters

[Corinna Vinschen]

On Sep 23 13:47, Schwarz, Konrad wrote:
> > That was apparently only half the truth.  My assertion was based on
> > testing three codepages.  A more thorough check revealed that 
> > in certain
> > codepages the undefined byte values are not converted to 
> > their identical
> > UTF-16 values.  Instead they are converted to unambiguous UTF 
> > values in
> > the UTF private use area between U+f700 and U+f8ff.  I don't 
> > know why that
> > is, but I checked that the values are identical over different Windows
> > versions (Windows 2000, Windows XP, Windows 7), as far as the 
> > codepages
> > are available on the machines.
> 
> This rings a bell: I have been told that the SFU/Interix product stores filename characters unsupported by NTFS (the Windows Explorer tells me that they are \, :, *, ?, >, <, |, ", and /, which doesn't count) as private use characters.

Yes, it does so by utilizing the private use area in the 0xf0XX range,
just only for a subset of the above chars.  Cygwin 1.7 uses the same
mechanism for all of the above chars, except '\' and (obviously) '/'.


Corinna

-- 
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat