25 ms·
Well, composed characters may or may not have been a good idea, although they're a pain for text search if you ask me. But why oh why did they have to specify
by nottorp 9y ago
Well, composed characters may or may not have been a good idea, although they're a pain for text search if you ask me.
But why oh why did they have to specify FOUR normalization forms?
Ref: http://www.unicode.org/reports/tr15/#Norm_Forms http://www.unicode.org/reports/tr15/#Norm_Forms
- Piskvorrr 9y ago¯\_(ツ)_/¯
- TazeTSchnitzel 9y agoBecause you need a normalisation form fit for your particular purpose.
- the_mitsuhiko 9y ago> But why oh why did they have to specify FOUR normalization forms? Ignoring compatibility normalizations there are really only two and neither of those two you can remove. So that's a bit of an odd question. If you want to remove the compatibility forms that's fair but nobody is force to use them. You can consider them "partially normalized" or "not normalized at all" for all intents and purposes
- cryptonector 9y agoPre-composed characters were needed to make transcoding to ISO-8859-* fast. Also, for Hangul, though decomposition is the better form to use normally (since it's phonetic, not syllabic), conversion to pre-composed syllabic form is very useful sometimes. Even without pre-composition there would have been multiple equivalent forms of writing any character that requires more than one combining codepoint. The only way to have avoided normalization altogether would have been to have no combining codepoints, and only a complete set of pre-compositions. This would have been less flexible, and very obnoxious for Hangul and possibly others. I believe the need for normalization was simply unavoidable. It's not the fault of Unicode but the fault of humans' script designs. And it's OK.
- cryptonector 9y agoYou can ignore the K forms. So that's two forms, really, NFC and NFD.