Re: Fallback to UTF-8

olivier Thereaux wrote:

> I am disappointed by some of the name calling

If as indcated by Karl's article the joke in...

| With this trick your proposals are equivalent
| (looking at it as a blackbox), and if you team
| up you could try to overrule Olivier... ;-)

...really upsets you so much use your killfile :-(
> feedback would be welcome.

| Software error:
| Undefined subroutine &W3C::Validator::EventHandler::abort_if_error_flagged | called at /home/link/web/HEAD/httpd/cgi-bin/check line 2756.
(The two test cases for bugs 5279 and 5280)

(Another "line 2756", it used to work, valid HTML 2.0 Strict)
(Another "line 2756", it used to work, well formed XML)
(Another "line 2756", it used to work, well formed XML)

[warning] Unable to Determine Parse Mode!
| Type (-//IETF//DTD HTML i18n//EN) is not in the validator's catalog
(SGML is correct - RFC 2070 DTD republished by IANA)

[warning] Missing "charset" attribute for "text/xml" document.
(this text/xml document really uses encoding US-ASCII)

[warning] Mismatch between Public and System identifiers
(the released validator has no problem with using System
 identifiers pointing to its own catatlog, maybe it's an
 artefact of the != setup)

[warning] Character Encoding mismatch!
| The character encoding specified in the HTTP header
| (iso-8859-1) is different from the value in the <meta>
| element (windows-1252). I will use the value from the
| HTTP header (iso-8859-1) for this validation. 
(Nikita consistently hates u+0080 based on an iso-8859-1
 assumption, and the document uses a windows-1252 0x80 )

| This Page Is Valid XHTML 1.0 Transitional!
(the <img> in <span> in <pre> magic fools DTD validators,
 no bug, working as designed, nothing to do)


Received on Monday, 28 April 2008 06:51:24 UTC