Bugzilla – Bug 1009
consider dropping the warning for Unicode Normalization Form C violations
Last modified: 2014-11-07 10:54:47 CET
see chat with :Waldo here: http://krijnhoetmer.nl/irc-logs/whatwg/20141107#l-348 I suspect the "Text run is not in Unicode Normalization Form C" warnings are of extremely limited utility in practice, since when most users see them, they have no idea how to actually fix the problem and make the warnings go away. Yeah, we could inject a link to, e.g., one of Richard Ishida's i18n user guides that explains what Unicode Normalization is about and how to deal with it, but I really wonder if the more-helpful thing for users would be to just drop the warnings.
To be clear, I propose we just turn this off for the default HTML checker. I'm not suggesting we drop the backend code, or not make it possible for others running their own instances of the service or using the "bring your own schema" UI at http://validator.nu/ to opt into it if they really want it.
Some feedback from Anne suggesting we should not drop the warning: http://krijnhoetmer.nl/irc-logs/whatwg/20141107#l-608 # [10:22] <annevk> MikeSmith: please keep the NFC warning # [10:23] <annevk> MikeSmith: I appreciate someone finding an exception to the rule, but in practice that stuff can end up being very confusing if your code is infected by it So maybe we should go in the other direction, and consider actually adding NFC conformance as a document conformance requirement to the HTML spec.