Re: ERROR Message from pages that were valid

On Thu, 23 Oct 2008 21:21:48 +0100
Came this utterance fomulated by Joseph Gourvenec - GB Networks to my

> Dear W3C,
> I had finished building the main building blocks of my site conforming
> to the high standards of W3C and went to check a couple of new pages
> with new content and they worked fine and passed.
> Then I just wanted to test a couple of pages I changed the wording in
> the database and added a little bit of code and now none of the pages
> will validate.
> Print screen attached
> Links I tested: that needed testing:
> and
> Links I tested that were prefect:
> and and
> - in
> fact every other page was prefect. 
> Error message:
> 1.              Sorry, I am unable to validate this document because
> on line 132 it contained one or more bytes that I cannot interpret as
> utf-8 (in other words, the bytes found are not valid values in the
> specified Character Encoding). Please check both the content of the
> file and the character encoding indication. 
> The error was: utf8 "\xA3" does not map to Unicode

I tested
and it reported an error on line 240. All i could see myself were faulty
characters in the alt tags of the banner adds that for me started at
line 254. The difference between what i see and what the validator gets
may be due to sending differences based on browser sniffing - not sure.

Anyway Hex A3 does not map to unicode (it is not a legal unicode
character). But it does map to the pound(currency) sign in iso-8859-1
character encoding. You may not have any control over the character
encoding of your adds, or someone may be inadvertenly copying and
pasting iso-8859-1 characters from Word or similar onto your site.


All shall be well, and all shall be well, and all manner of things shall
be well

 - Julian of Norwich 1342 - 1416

Received on Friday, 24 October 2008 08:30:28 UTC