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

Re: [VE][139] Error Message Feedback

From: Lachlan Hunt <lachlan.hunt@iinet.net.au>
Date: Wed, 13 Oct 2004 12:50:51 +1000
Message-ID: <416C980B.6010302@iinet.net.au>
To: Fons <vrouenraths@planet.nl>
CC: www-validator@w3.org

Fons wrote:
> http://validator.w3.org/check?uri=http%3A%2F%2Fwww.fotokennis.nl&charset=%28detect+automatically%29&doctype=%28detect+automatically%29
> Somewhere around Error 26 something goes wrong in the layout of
> your validator.

I could not see any error around error 26, but I tried the page in both 
Firefox and IE6.  There was a strange bug around error 48 at the above 
validation page that makes everything after it appear in bold.  This 
kind of problem usually indicates an error with the markup, but it 
validates correctly and does not occur in Firefox.

>   3.. Line 626, column 419: non SGML character number 133

These kind of errors most often indicate that you are using 
Winodows-1252 as the chacter encoding, yet declaring it as ISO-8859-1. 
The difference between them occurs because the characters using in 
Windows-1252 from decimal 128 to 159 are control characters in 
ISO-8859-1, yet Windows-1252 uses them as printable characters.  This 
most often occurs with elipsis (… - decimal 133), and single/double, 
left and right quotation marks (‘ ’ “ ” - decimal 145 to 148).  The 
solutions for this are to either:

* declare windows-1252 as the character encoding
(not recommended for reasons of portability between non-windows systems)

* Remove all occurances of the offending characters and substitute with 
equivalent characters that are found in ISO-8859-1. eg. three dots (...) 
for the elipsis (…), ASCII quotes (" and '), etc.
(not recommended for typographical reasons.  It is best to use the 
correct characters if you can)

* Encode each of the offending characters using character references to 
their Unicode code points. (either hex or decimal references can be used)
eg. &#x2026; for the elipsis used in the quoted error.  Don’t make the 
mistake and encode them using the windows-1252 decimal numbers. eg. 
&#133; (elipsis) and &#145; to &#148; (quotes) are incorrect.
   This is the easiest recommended solution.

* The final solution is to configure your editor to save and edit files 
as UTF-8.  However, you should be aware of the problems this can cause 
in some situations, especially with the Byte Order Mark (BOM), however 
this is the best solution if you can manage it.  The biggest problem is 
that not all editors and server side technologies support UTF-8, so 
check that yours does before using this solution.

Lachlan Hunt
http://getfirefox.com/    Rediscover the Web
http://spreadfirefox.com/   Igniting the Web
Received on Wednesday, 13 October 2004 02:51:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 14:17:43 UTC