Re: [charmod-norm] Removing meaning

Since no conformant process is required to make a distinction between 
canonically equivalent forms it's more than foolish to rely on that 
distinction - especially in a distributed environment.

That said, there's no guarantee that absolutely everything will work 
the same. Any buffer-overrun bug might be triggered by a decomposed 
string, while the equivalent composed string passes fine. Just to give
 one example where neither intention nor conformance is involved.

For purposes of this document, the proposed change is appropriate and 
good.

-- 
GitHub Notification of comment by asmusf
Please view or discuss this issue at 
https://github.com/w3c/charmod-norm/issues/85#issuecomment-206416267 
using your GitHub account

Received on Wednesday, 6 April 2016 14:59:55 UTC