I wonder if there isn't a minor error somewhere in the tool chain used to
produce PG epub files from HTML sources.
An example:
- in the HTML of PG105, Persuasion by Jane Austen, at the head of the file
is the line:
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
- in the xhtml constituent files of the epub of PG105 is the line:
<meta http-equiv="Content-Type" content="text/htmlcharset=utf-8"/>
(This xhtml was presumably derived from the HTML above, but presumably
modified to declare that it is now in UTF-8 as required for xhtml not
ISO-8859-1 as in the HTML.)
BUT should it not say instead say:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
?
epubcheck V1.1 from google code doesn't raise an error at
"text/htmlcharset=utf-8", and of course one can argue that the fact that the
epub's xhtml files already have an overriding declaration:
<?xml version='1.0' encoding='UTF-8'?>
means that the above problem doesn't really matter even if it exists, but I
am wondering if I should correct it in my remastered epubs.
Bob Gibbins
