Re: [whatwg/encoding] Important warnings getting lost in the noise (#97)

The command-line checker and the network API to the checker currently don’t provide any way to configure which warnings get emitted. The only option is to show all warnings along with errors, or else to show only the errors and show no warnings.

Anyway I think the particular noise problem at https://travis-ci.org/whatwg/encoding/builds/204200335 would be a non-problem if I just made the checker quit emitting the “Text run is not in Unicode Normalization Form C“ warning.

That message used to be an error but years ago I demoted it to being a warning. See https://bugzilla.validator.nu/show_bug.cgi?id=838. The reason I demoted it that the HTML spec does not any normative requirements at all that text being in Unicode Normalization Form C—no “must” requirements and not even any “should” requirement. In fact I think the HTML spec doesn’t mention Unicode Normalization Form C at all.

So the reason I have the checker emitting any message about Unicode Normalization Form C isn’t because of any requirements in the HTML spec but I think instead because of Internationalization best-practice guidance published elsewhere. But in that case it would also be something that the W3C Internationalization Checker https://validator.w3.org/i18n-checker/ is already checking.

And so as far as the HTML checker goes, that warning is a discretionary warning (not required by anything in the HTML spec) and we can use our own discretion to decide it should just be dropped from the HTML checker.

So do think we should just drop it or not? I guess maybe these generated files for the Encoding spec are kind of a special case but I now wonder if maybe they’re not and if other people trying to check documents in other encodings run into this same problem (that is, all errors and warnings about more-serious problems just get drowned out in all the noise from the “Text run is not in Unicode Normalization Form C“ warnings.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/97#issuecomment-287588667