Re:APFS does not normalize Unicode filenames
by Asooka on Saturday March 25, 2017 @07:02AM
(#13955011)
You don't, there is only one unicode representation of those characters.
[ Parent
| on HN ]
Re:APFS does not normalize Unicode filenames
by huxley on Saturday March 25, 2017 @07:54AM
(#13955170)
Interestingly that created its own annoyances for some since normalization occurs at a different stage.
Unicode and UTF-8 unify many Traditional & Simplified Chinese Characters as well as Japanese Kanji and Korean Hanja.
There were some extremely angry reactions to Han Character Unification[1], though efforts have been made to overcome many of the initial complaints.
[1] "Why Unicode Won’t Work on the Internet: Linguistic, Political, and Technical Limitations" http://www.hastingsresearch.com/net/04-unicode-limitations.s...
Re:APFS does not normalize Unicode filenames
by srssays on Saturday March 25, 2017 @09:12PM
(#13958439)
Not the case for Arabic. There's hundreds of ligature code points, for example ﰻ (kl), ﷵ (ṣl'm) and ﷳ (akbr). And of course ﷽
Re:APFS does not normalize Unicode filenames
by jrochkind1 on Saturday March 25, 2017 @07:11PM
(#13958009)
I don't believe that's literally true, some all legal and correct Japanese unicode sequences will be transformed under at least some of the unicode normalization forms, no?
Re:APFS does not normalize Unicode filenames
by sametmax on Saturday March 25, 2017 @07:20AM
(#13955061)
So what does mac do with those ?
Re:APFS does not normalize Unicode filenames
by icebraining on Saturday March 25, 2017 @07:24AM
(#13955077)
Use that representation? The problem only happens when there is more than one way to represent the same text.