EpubCheck Error…

PerspexSphinx · 11-29-2024, 11:19 PM

Hi,
when using EpubCheck (the Pagina version) on an epub I created with Sigil, it found a few errors, most of which I managed to sort of understand and correct but this one I don’t understand or know how to correct.

Error while parsing File: A document must not contain both a meta element in encoding declaration state (http-equiv=“content-type”) and a meta element with the charset attribute present.

The offending line…

<meta content="text/html; charset=UTF-8" http-equiv="content-type"/>

in the… /OEBPS/text/nav.xhtml

Any ideas what’s wrong and how to correct it?

Sarmat89 · 11-30-2024, 08:17 AM

Remove either the charset= clause from the content-type meta, or <meta charset> element.

KevinH · 11-30-2024, 09:21 AM

Actually, that entire meta line is not needed anymore. The xml header line declares the encoding, and the media-type determines the content type. This is not a standalone html file being served up by a server. It is an xhtml file that is part of an epub.

PerspexSphinx · 11-30-2024, 12:09 PM

Hi,

Tried the first approach, but only seemed to get worse results with EpubCheck (I may have edited the line wrong).
But removing the entire meta line seemed to do the trick…

I did not write the line in the first place, so Sigil must have generated it, I guess. But if it is not needed any more, why? Is it because I am using an older version of Sigil (version 1.9.30)? Which unfortunately I have to use because it is the last version which runs on Mac OS 10.15.5 Catalina. Unless anyone knows how to run the latest version on Catalina, without resorting to compiling it myself or using MacPorts or Brew.

Thanks, everyone.

DiapDealer · 11-30-2024, 05:28 PM

Sigil's not going to remove it, but I don't think Sigil created it in the first place. Regardless of the version. Even as far back as 1.9.30, Sigil didn't generate the:

<meta content="text/html; charset=UTF-8" http-equiv="content-type"/>

line in the NAV:

https://github.com/Sigil-Ebook/Sigil...cessor.cpp#L58

It must gotten pasted (or imported) into the epub in Sigil when the epub was created.

KevinH · 11-30-2024, 05:32 PM

Sigil does not generate lines like that but will not remove them if already present.

PerspexSphinx · 12-01-2024, 11:10 AM

Aha,
I must have inadvertently included it all by myself, when nonchalantly copying and pasting some code.
Thanks, again.

11-29-2024, 11:19 PM	#1
PerspexSphinx Junior Member Posts: 9 Karma: 10 Join Date: May 2022 Device: Kobo Arc 7HD	EpubCheck Error… Hi, when using EpubCheck (the Pagina version) on an epub I created with Sigil, it found a few errors, most of which I managed to sort of understand and correct but this one I don’t understand or know how to correct. Error while parsing File: A document must not contain both a meta element in encoding declaration state (http-equiv=“content-type”) and a meta element with the charset attribute present. The offending line… <meta content="text/html; charset=UTF-8" http-equiv="content-type"/> in the… /OEBPS/text/nav.xhtml Any ideas what’s wrong and how to correct it?

11-30-2024, 09:21 AM	#3
KevinH Sigil Developer Posts: 8,759 Karma: 5706256 Join Date: Nov 2009 Device: many	Actually, that entire meta line is not needed anymore. The xml header line declares the encoding, and the media-type determines the content type. This is not a standalone html file being served up by a server. It is an xhtml file that is part of an epub. Last edited by KevinH; 11-30-2024 at 09:34 AM.

11-30-2024, 05:28 PM	#5
DiapDealer Grand Sorcerer Posts: 28,568 Karma: 204127028 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Sigil's not going to remove it, but I don't think Sigil created it in the first place. Regardless of the version. Even as far back as 1.9.30, Sigil didn't generate the: <meta content="text/html; charset=UTF-8" http-equiv="content-type"/> line in the NAV: https://github.com/Sigil-Ebook/Sigil...cessor.cpp#L58 It must gotten pasted (or imported) into the epub in Sigil when the epub was created. Last edited by DiapDealer; 11-30-2024 at 05:31 PM.

11-30-2024, 05:32 PM	#6
KevinH Sigil Developer Posts: 8,759 Karma: 5706256 Join Date: Nov 2009 Device: many	Sigil does not generate lines like that but will not remove them if already present. Last edited by KevinH; 11-30-2024 at 05:35 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
epubcheck Error	mdpeterson42	Conversion	37	05-24-2024 03:58 AM
EpubCheck Error	gstock97	Editor	7	07-23-2021 08:58 AM
EPUBCheck error	gsosigil	Sigil	3	03-21-2021 06:24 PM
Error epubcheck	Buble	ePub	43	08-15-2014 01:53 AM
Error on epubcheck	Brazz	ePub	5	09-01-2011 03:17 AM

11-30-2024, 08:17 AM	#2
Sarmat89 Fanatic Posts: 516 Karma: 2268308 Join Date: Nov 2015 Device: none	Remove either the charset= clause from the content-type meta, or <meta charset> element.

11-30-2024, 12:09 PM	#4
PerspexSphinx Junior Member Posts: 9 Karma: 10 Join Date: May 2022 Device: Kobo Arc 7HD	Hi, Tried the first approach, but only seemed to get worse results with EpubCheck (I may have edited the line wrong). But removing the entire meta line seemed to do the trick… I did not write the line in the first place, so Sigil must have generated it, I guess. But if it is not needed any more, why? Is it because I am using an older version of Sigil (version 1.9.30)? Which unfortunately I have to use because it is the last version which runs on Mac OS 10.15.5 Catalina. Unless anyone knows how to run the latest version on Catalina, without resorting to compiling it myself or using MacPorts or Brew. Thanks, everyone.

12-01-2024, 11:10 AM	#7
PerspexSphinx Junior Member Posts: 9 Karma: 10 Join Date: May 2022 Device: Kobo Arc 7HD	Aha, I must have inadvertently included it all by myself, when nonchalantly copying and pasting some code. Thanks, again.

Advert

Advert