News for hackers. Stuff that matters.
Re:APFS is not safe to use with names which have Unicode nor... by netheril96 on Tuesday June 06, 2017 @10:32AM (#14497460)
Do "most non-English" languages have normalization issues? At least CJK users do not.
Re:APFS is not safe to use with names which have Unicode nor... by rurban on Tuesday June 06, 2017 @12:02PM (#14498238)
Actually Korean (Hangul) is the biggest user of NFD normalization, with very special logic. Hangul also has the only 2 still remaining identifier bugs in the unicode 9 database. HANGUL FILLER and HALFWIDTH HANGUL FILLER wrongly being valid ID_Cont, as such wrongly usable as identifier characters (such as in filenames).

Almost every script but Latin-1 has TR31, TR36 and TR39 issues. http://www.unicode.org/reports/tr39/

Re:APFS is not safe to use with names which have Unicode nor... by cryptonector on Tuesday June 06, 2017 @12:40PM (#14498624)
Hangul has composed and decomposed forms, but only the decomposed forms are used as canonical, even in NFC.

(Incidentally, NFC is closed to new compositions, though new compositions can be added to Unicode.)

Re:APFS is not safe to use with names which have Unicode nor... by cryptonector on Tuesday June 06, 2017 @05:32PM (#14501548)
Even English has things like "reëlect" instead of "reelect" and so on. http://www.newyorker.com/culture/culture-desk/the-curse-of-t...
Re:APFS is not safe to use with names which have Unicode nor... by anonymoushn on Tuesday June 06, 2017 @05:30PM (#14501542)
If you want to use characters like が, you will have normalization issues.