Re: Validator error

2012-11-27 10:16, Pelayo Garcia wrote:

> I recently CSS validated a web site, and discovered that the alt tag in
> Spanish version, of the valid CSS code for pasting in site has
> prohibited UTF characters. After validating CSS I tried to revalidate
> XHTML and then I was given that error for copy-pasting the XHTML.
>
> http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fwww.grupofspenergia.es%2F

The CSS is in error, and the CSS Validator reports it. It reports two 
errors, but they are essentially one error: a color value is prefixed by 
two "#" characters, instead of just one.

But I presume that this error was introduced very recently and that you 
validated successfully and got a suggestion to include an icon for 
"valid CSS". Such suggestions are best ignored. The icons add nothing to 
the value of the page, and they create a potential distraction from the 
content and purpose of the page (unless the page is about CSS!). A 
longer argument: http://www.cs.tut.fi/~jkorpela/html/validation.html#icon

> alt="*¡*CSS V*á*lido*!*" />

I suppose you mean that when trying to use a markup validator (HTML 
validator) on a page that contains such an attribute, you get an error 
message that flags the characters "¡" and "á" as erroneous. This is 
strange. Can you please specify exactly how this happens - URL of the 
specific page, and URL or other identification of the validator you used?

The only explanation I can imagine without additional facts is that 
perhaps the code was copy-pasted in a manner that caused it to be 
inserted into an UTF-8 encoded document in another encoding, probably 
windows-1252 or iso-8859-1. This would make the data malformed. But this 
should cause an error message like this:

"Sorry, I am unable to validate this document because on line [...] 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 "\xA1" does not map to Unicode"

(The last line is misleading and should be read as saying that the byte 
is not valid in UTF-8.)

Yucca

Received on Tuesday, 27 November 2012 11:24:08 UTC