W3C home > Mailing lists > Public > www-validator@w3.org > February 2017

Re: ⅓ ERROR on w3c validator.

From: Jukka K. Korpela <jukkakk@gmail.com>
Date: Tue, 7 Feb 2017 19:11:36 +0200
Message-ID: <CAGHxYa41wgAti28=pX8fEiZdwjTG5PYSMaUJYnzinGJt7AmsMA@mail.gmail.com>
To: "www-validator@w3.org" <www-validator@w3.org>
Cc: Eric Richards <2eric.richards@gmail.com>
On Fri, Feb 3, 2017 at 11:35 PM, Philip Taylor <P.Taylor@rhul.ac.uk> wrote:

Can't find &frac13 in https://www.w3.org/TR/xhtml-modularization/dtd_module_
> defs.html#a_module_XHTML_Special_Characters,

Yes, that explains the error messages.

The issue was indeed reported by Eric Richards a few times in 2014, first as
but without specifying the DOCTYPE or URL. It’s still a pity that there was
no answer then,
but it would have been the same as today.

To put it more explicitly, the &frac13; entity (and many other similar
entities) is not defined in any HTML specification prior to HTML. Thus, if
you have used it, your options are:

1) Ignore the messages. This is not a good option, since you could easily
miss real errors caused by typos in entity names.

2) Use numeric character references instead, such as &#x2153;.

3) Use the vulgar fraction characters themselves, such as ⅓ (using the
UTF-8 encoding for your HTML document, which is a good idea anyway). This
may cause some problems in your authoring tools.

4) Validate against HTML5. You would start from changing the DOCTYPE string
to simply <!DOCTYPE html>. Beware that there are things that are valid in
previous versions of HTML but reported as errors by the W3C Markup
Validator when testing against HTML5. It’s impossible to say how serious
the transition problems would be, as they greatly depend.


P.S. You might be interested in the *practical* issues with such vulgar
fraction characters, namely font problems, see e.g.
Received on Tuesday, 7 February 2017 17:12:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 7 February 2017 17:12:15 UTC