On Nov 11, 2019, at 1:49 PM, Jose Isaias Cabrera <jic...@outlook.com> wrote:
>
> If there is a combination, is just like the accented e, é, why not use the
> one character vs the combination?
Big “if.” There isn’t always a pre-composed character.
Typically, pre-composed characters exist in Unicode for compatibility with
legacy encodings so that you can have lossless mappings from e.g. ISO 8859-1 to
Unicode and back. In an ideal world, Unicode would have no pre-composed
characters, only base characters and accents.
That is, in fact, the way the macOS native file systems HFS+ and APFS handle
Unicode in file names. It’s called Normalization Form D: input is decomposed
and stored that way, always. It’s done to ensure that sorting happens
predictably.
See:
https://www.unicode.org/standard/where/#Duplicates
https://www.unicode.org/reports/tr15/
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
