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

I certainly get these warnings quite often, and i think always ignore them because there are good reasons for using a non-NFC sequence of content where i do.  Iirc, the i18n checker only looks for non-NFC sequences in class or id names.  Maybe that would be a better check to throw out blow by blow warnings. If there's non-NFC content, i think i'd prefer to just have a single message at the end to say so, but not create a ruckus over it, since it could well be intentional.  

(Btw, this advice is consistent with our article about normalization at https://www.w3.org/International/questions/qa-html-css-normalization)

-- 
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-293208265