<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 12/14/2025 9:57 AM, Doug Ewell via
Unicode wrote:<br>
</div>
<blockquote type="cite"
cite="mid:SA5PR03MB8401EB99841F2A39DDA2593DCAACA@SA5PR03MB8401.namprd03.prod.outlook.com">
<pre class="moz-quote-pre" wrap="">Normalization (NFC or NFD, not NFK*) for characters like this comes into play only when the character exists as both a precomposed unitary character and a combining sequence. When there is only one or the other, normalization to NFC or NFD yields the same result, and is thus a no-op, and not particularly adventurous.</pre>
</blockquote>
<p><font face="Candara">This is actually incorrect. (And Doug
actually knows better :) ).</font></p>
<p><font face="Candara">It would be correct for a sequence of a base
character with <b><i>single </i></b>combining mark, but as
soon as you have two or more combining marks, their order is
defined by NFC. The idea is that that if two combining marks
don't interact (such as by stacking), different orders could
result in the same display and normalization enforces a
preferred ordering. </font></p>
<p><font face="Candara">To make matters more complex, some combining
marks are defined to not reorder. Those can be in any order
defined by the author and could lead to duplicate encoding for
the same display. The reasons behind supporting that are a bit
complex, but generally it's done for scripts other than Latin.</font></p>
<p><font face="Candara">But in general, <b><i>canonical reordering</i></b> is
a thing and is part of normalization.</font></p>
<p><font face="Candara">A./</font></p>
</body>
</html>