On Jul 14 11:12, Warren Young wrote: > On Jul 14, 2016, at 9:24 AM, Warren Young <w...@etr-usa.com> wrote: > > > > If you look at such a file name in Explorer, Cygwin (?) seems to be mapping > > double-quotes to U+F022, which is currently not defined within Unicode: > > > > http://www.fileformat.info/info/unicode/char/f022/ > > I think this may be a typo in whatever code is doing the translation, > because U+FF02 is a typographically distinct variation of the > double-quote character: > > http://www.fileformat.info/info/unicode/char/ff02/index.htm > > That would give the visual appearance of double-quotes in file names > in Explorer without violating the restriction on 0x22 characters in > NTFS. > > In fact, it might be a thinko rather than a typo: 0x22 -> 0xF022. It > looks like someone thought they could just add 0xF000 to the character > value, when the correct value os 0xFF02.
Nope. The idea(*) was *not* to provide a typiographically similar character, the idea was to allow to express characters disallowed in the Windows namespace but allowed in the POSIX namespace by transposing them into the private use area on creating the filename and converting it back to the untransposed ASCII char when reading the filename from disk. You can't perform this action by converting the character to another *valid* character. Btw., there's a section in the Cygwin User's Guide on special characters: https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars Corinna (*) Original idea by the Interix folks, picked up by Cygwin for compatibility.
signature.asc
Description: PGP signature
