It becomes a problem when someone does a search and normalizing the search string does not make it match the corresponding data. And this might happen with many different systems, where the normalization is done in various layers.Alan Bunning wrote: ↑October 29th, 2017, 9:35 amSo if indeed these characters are not “deprecated”, is the fact that these oxia characters are not the normalized form a sufficient reason not to use them? Normalization is for comparing characters, but that does not mean that the non-normalized form is necessarily wrong does it? Where might it become a problem down the road?
And it becomes a problem when fonts display the two equivalent forms differently and people wonder why the same character displays two different ways.
If there is any data where the distinction really matters, then it becomes a problem when you actually intended the oxia. But it's not clear to me whether such cases exist.