View Full Version : W3C validation problem

07-12-2007, 02:07 PM

I don't want my pages tobe automatically translated by Google so I inserted <meta name="google" content="" value="notranslate"/> in them. The problem is, now they won't validate. Here's the error message I got:

Line 10 column 37: there is no attribute "value".

<meta name="google" content="" value="notranslate"/>

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Any tips on how to fix this ?

Thanks for your help !

07-12-2007, 02:17 PM
Yeah stop trying to make up your own attributes.

<meta name="robots" content="notranslate" />
Using robots for the name is probably a little more appropriate.

07-12-2007, 03:03 PM
The page now validates, thanks !

07-16-2007, 02:18 AM
Just realized it blocks the translation done by Google but not by Systran. Is there any way to block as many automatic translators as possible ?

07-16-2007, 09:00 AM
Why are you so worried about this anyways? Who cares if a page is translated by some search engine?

07-16-2007, 01:56 PM
2 reasons:

1) I'm currently working my own translations
2) A user I banned by denying their IP address in an htaccess file is now using translation sites to access my site again.