This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
2009/11/29 Linda Walsh:<http://unicode.org/mail-arch/unicode-ml/Archives-Old/UML018/0289.html>
I'm aware that this would reserve the 'display forms'
of those chars and map them them to their real forms when
interpreted within cygwin. I don't see this to be a problem.
But it is a problem. It would make it impossible to use the wide forms of those deadly chars in Cygwin filenames.
Btw, does anyone know why those wide ASCII chars exist in the first place?
Do they occur in East Asian character sets?They are actually listed in all CJK character sets (checking i18n data). Whether this was really used or not, it makes their view as "presentation forms" weaker.
Sounds like a good proposal. On the other hand, I can also understand Linda._I_ use those [wide ASCII chars] in filesnames,
and know of no compatibility problems having them
treated as 'real' ascii characters under cygwin --
since I am just using them for 'display' purposes
in file names like like "Music:the group:title 1/3".
Sounds like you've found a good solution there already. The wide forms show up correctly in Explorer, Cygwin, and via Samba, don't they?
To make them more convenient to use, you could add them to your
keyboard layout using Microsoft's Keyboard Layout Creator, e.g. with
AltGr+':' for the wide colon.
-- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |