W3C home > Mailing lists > Public > www-validator-cvs@w3.org > April 2013

[Bug 21577] NFC issues reported wrong way: wrong char highlighted, wrong total amount

From: <bugzilla@jessica.w3.org>
Date: Sun, 21 Apr 2013 01:20:05 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-21577-169-eHtefXePgB@http.www.w3.org/Bugs/Public/>

Michael[tm] Smith <mike@w3.org> changed:

           What    |Removed                     |Added
          Component|HTML5                       |check
           Assignee|mike+validator@w3.org       |dave.null@w3.org

--- Comment #3 from Michael[tm] Smith <mike@w3.org> ---
(In reply to comment #2)
> The character in my demo case is “·” U+0387 GREEK ANO TELEIA, not “·” U+00B7
> MIDDLE DOT. I have added a URL of an online version of the case for clarity.

Ah, thanks

> The bug is triggered by any non-NFC character and even by a character
> reference denoting such a character, e.g. &#x387;.


(In reply to comment #0)
> When the HTML5 validator issues warnings about deviations from Normalization
> Form C (NFC), it highlights the last character of the text run, not the
> offending character. It also reports the number of warnings as too large.

When I try the document at http://www.cs.tut.fi/~ jkorpela/test/nfc.html8 with
both validator.nu and http://validator.w3.org/nu/ I get exactly the same result
as far as the highlighting and number of warnings.

> These problems are not present in validator.nu: it highlights the entire
> text run, and it does not report the number of warnings.

http://validator.w3.org/nu/ also highlights the entire text run and does not
report the number of warnings...

> Excerpt from validator output, when using direct input:
> Validation Output: 4 Warnings
> Below is a list of the warning message(s) produced when checking your
> document.

Ah, so you mean you're checking the document using http://validator.w3.org/

Please use http://validator.w3.org/nu/ directly instead.

There are a number of known issues with the post-processing that the legacy
validator does on output from the validator.nu backend. Those issues are not
likely to ever be fixed. I don't maintain the code for it and have never even
touched the code directly. It was all set up before my time. And actually,
nobody is actively maintaining it now. Not for a year or two now.

Anyway, the long-term solution to this problem is that we just need to move the
http://validator.w3.org/nu/ UI to become http://validator.w3.org/ and finally
retire the current http://validator.w3.org/ to http://validator.w3.org/legacy
or something. It's long overdue. If it were completely up to me to decide, we'd
have already done that a long time ago. In them mean time, I can't commit to
investigating any problems in the reports from http://validator.w3.org/ that
aren't reproducible at http://validator.w3.org/nu/

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 21 April 2013 01:20:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:03:18 UTC