On 2023-04-14 14:17, Gionatan Danti via Cygwin wrote:
Il 2023-04-14 21:00 Corinna Vinschen ha scritto:
There's no (good) solution from inside Cygwin.
Yeah, I can only imagine how difficult is to be compatible with posix, win32 and
the likes.
Any chance you can just rename the files?
I renamed the files, in fact.
However, it seems that users working with (older?) Office for MAC use U+F020
more frequently than I expected, maybe because of that [1]:
"Microsoft's defunct Services For Macintosh feature used U+F001 through U+F029
as replacements for special characters allowed in HFS but forbidden in NTFS, and
U+F02A for the Apple logo."
Any chances to enable a "bypass" for these characters (excluding the one you
reserved for compatibility as explained detailed in the "Forbidden characters in
filenames")? Maybe hidden behind a configurable option (even disabled by
default), so to not interfere with the current behavior?
[1] https://en.wikipedia.org/wiki/Private_Use_Areas#Vendor_use
Now if MS SfM and Cygwin had both registered with U/CSUR, they would not be
fighting over Unicode code points, although it looks like there is a lot of
competition for the code points! ;^>
Would it make more sense to add custom file name character filters into some
utility, such as unix2dos/mac2unix, cygpath, or some other, and add (Cyg)win, or
create such a utility, so those could be added to processes?
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
--
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
