2012-03-14 17:13, Erik Westman wrote:
> your website http://validator.w3.org/ can't handle valid dns-names.
>
> The website http://www.systemingenjörer.se/ should be translated to
> xn--systemingenjrer-ktb.se . Instead the application show dns-name error.
I tested this on Firefox, IE, and Chrome, and in all cases the validator
correctly processed the URL.
However, if the browser has been set to use an encoding other than UTF-8
(e.g., ISO-8859-1) when visiting the page http://validator.w3.org/
then the processing fails. So there would be either something wrong with
the browser or its settings, as a properly declared encoding (as on the
validator page) should not be overridden.
As a completely different issue, the validator reports several errors
because it does not recognize the document type declaration
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 FRAMESET//EN">
The report does not say this very explicitly, but it can be inferred
from the error messages (e.g., 'element "FRAMESET" undefined') and from
the note
'the Document Type (-//W3C//DTD HTML 4.0 FRAMESET//EN) is not in the
validator's catalog'
(under 'Unable to Determine Parse Mode!').
The reason is that the declaration should be
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN">
or the newer
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN">
The part in quotation marks in a doctype declaration is case-sensitive.
I suppose the validator defaults to HTML 4.01 Transitional but does not
seem to say it.
Please note that your documents are served with no character encoding
information, i.e. neither HTTP headers nor meta tags specify a charset
parameter. Therefore browsers and other software are forced to infer
(guess) the encoding, potentially resulting in misinterpretation of
data. See http://www.w3.org/International/O-charset.en.php
Yucca