On Apr 14 19:53, Gionatan Danti via Cygwin wrote: > Dear list, > I have an issue with unreadable files with contain utf char U+F020 (which > appear as "middle dot with some space after") in their name. > > stat on such a file results in "no such file or directory" > > From here [1] it seems that a patch was contemplated many years ago, but I > don't know its status now. > > Any ideas or workaround?
There's no (good) solution from inside Cygwin. Keep in mind that the Unicode area from U+E000 up to U+F8FF is called "Private Use Area". So none of the chars are mapped into any singlebyte, doublebyte, or multibyte charset. Typically we don't expect that filenames contain any of these chars, and we're only using a very small subset of them for our own, dubious purposes anyway: https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars > [1] https://sourceware.org/legacy-ml/cygwin/2009-11/msg00043.html While this patch would have fixed your problem, a later followup patch broke your usage of U+F020 (space replacement) and, FWIW, of U+F02E (dot replacement) again: https://cygwin.com/cgit/newlib-cygwin/commit/?id=8802178fddfd This was done to accomodate filesystems implementing the idiotic approach to support only DOS filenames, i. e., not allowing leading or trailing spaces and not allowing trailing dots. These are Netapp and Novell Netware filesystems. See the last paragraph of https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars Any chance you can just rename the files? Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
