Re: Export Options

John Albaugh <>, 2012-06-06 09:57 -0400:

> Thank you for that link Michael.  
> Unfortunately the error(s) and count(s) are different from the
> webservice and the validator.  Using as an example, I only
> get 4 errors from the webservice
> and it
> looks like it had to stop whereas the validator found 16 errors and 8
> warnings. is what shows 16
errors and 8 warnings. shows only 4 errors.

Those are two different services, with different backends and parsers.

The behavior of the parser used by the service
closely matches actual browser behavior: It expects a character encoding to
either be declared in the Content-Type header or in a meta element in the
first 1024 bytes of the document, and if it doesn't find one, it assumes
windows-1252 as the default encoding (which matches what most browsers do
for most cases, except that browsers also further try to determine a
default encoding based on the user's locale). But then when it finally gets
to the meta element at byte 1800 or whatever of that document, it gives up
and quits parsing it any further -- because your document is basically
asking it to switch to a different encoding.

You can fix the document by putting the meta element with the charset
declaration closer to the top of the document. Or you can explicitly tell
the validator to use a particular encoding and not look for a
character-encoding declaration at all. If you do that for this document
you'll see it parses the whole document and reports a lot more errors:

Michael[tm] Smith

Received on Thursday, 7 June 2012 08:40:15 UTC