W3C home > Mailing lists > Public > www-validator@w3.org > October 2004

Bug report

From: Vadik Okunev <vadik@aspol.ru>
Date: Sun, 3 Oct 2004 04:03:16 +0400
Message-ID: <000801c4a8dc$62bc5e00$3273000a@ptn>
To: <www-validator@w3.org>
Hello.

I met the following paragraph in one of the validation results:

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs". 
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters. 
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed. 


IMHO there is a mistake - does an entity reference '&Aelig;' really exist? IMHO there were two variants of this Latin letter: '&AElig;' and '&aelig;'...

Best regards, Vadik
Received on Sunday, 3 October 2004 09:48:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:15 GMT