Re: agenda+ Normalization in HTML and CSS

Erk! Perhaps i need to change my glasses. Yes, i was looking at the 
wrong line. Sorry.

So why isn't the checker picking up the non-NFC attribute name?  I 
suspect it's because i used an NCR to write it (világ, so that i 
could see what i was doing, and find the example again later), and the 
checker code doesn't resolve those before checking.  Having said that, 
if NCRs are being used that's not really the use case we're checking 
for, because the encoding has been clearly exposed.  The checker is 
really looking for identical-looking items that are not the same underneath.

Perhaps that answers the question?

ri


Atsushi Shimono (W3C Team) wrote on 24/08/2022 16:52:
>   hi,
>
> On 2022/08/24 19:03, r12a wrote:
>>> 2. i18n checker
>>>
>>>   When I've put the page into i18n checker referenced at the last 
>>> section, I've got
>>>> Non-NFC class or id names : None
>>> https://validator.w3.org/i18n-checker/check?uri=https%3A%2F%2Fw3c.github.io%2Fi18n-drafts%2Fquestions%2Fqa-html-css-normalization.en.html#validate-by-uri+ 
>>>
>>>
>>>   This page surely have both NFC and NFD class name in example part. 
>>> Is this usage
>>> wrong?
>>
>> I do see a report under the heading Markup when clicking on the link 
>> you provide which says:
>
>   I do see that, but there is two row in markup, one is "non-ascii 
> class or id names" as pointed
> below, and one another as "non-NFC class or id names", which I'd 
> wanted to point.
>
>> Non-ascii class or id names     *2*
>>
>>  1. |<p lang="hu" class="világ" style="font-size: 2rem;">|
>>  2. |<p lang="hu" class="világ" style="font-size: 2rem;">|
>>
>>
>> So that seems to be working?
>>
>> ri
>>