[email protected] wrote:

I learned also that KompoZer now has forked or somehow became BlueGriffon.
I succeeded in changing the DOCTYPE, but the html validator of the W3C group 
finds an error in my charset. Apparently, some windows 1252 has creeped into my 
files, while I chose ISO 8859-1. Nowhere to find that sticky windows charset 
code...

Is it possible that you are either authoring in HTML 5 or
the validator believes that you are ?  If so, the problem
may well be with the draft spec. rather than with Composer :


Warning /Line 11, Column 30/: Using windows-1252 instead of the declared
encoding iso-8859-1.

|       <meta charset="ISO-8859-1" /*>*|


And yet, on the top of the validation page in the result list it says
Encoding: iso-8859-1, and the combobox reads (detected auotomatically)

Yes, this is confusing. That part reflects how the checking was started.
The HTML5 Conformance Checker may treat ISO-8859-1 as windows-1252, as
the message says. You can avoid this by explicitly selecting "HTML5" in
the "Doctype" dropdown menu. Strange.

If you do that and the document actually contains an octet that is
defined in windows-1252 but undefined in ISO-8859-1, you get a message
like "Forbidden code point U+0092." and checking is suppressed. Though
theoretically odd, this can be useful in practice if you really want to
use ISO-8895-1. But in practice, browsers mostly read ISO-8859-1 as
windows-1252.

There is, by the way, no difference whether I write iso in small or
capital letters.

Neither shall there be any difference. Character encoding names are by
definition case-insensitive.

By the way: It says on top of the warning


      Validation Output: 2 Warnings

but there is only one.

I guess the statement "Using experimental feature: HTML5 Conformance
Checker." counts as a warning. If there are no other complaints of any
kind in the validator response, you get "1 warning(s)". This is probably
intentional, trying to make people remember the checker is experimental
(and HTML5 is mutable).

--
Yucca, http://www.cs.tut.fi/~jkorpela/

Philip Taylor
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to