MobileRead Forums - View Single Post

DiapDealer · 08-22-2018, 09:01 AM

EPUB2
Flightcrew: "Error schema not satisfied : no character data is allowed by content model near column 1"

EpubCheck: Col: 1: ERROR(RSC-005): Error while parsing file 'text not allowed here; expected the element end-tag or element "address", "blockquote", "del", "div", "dl", "h1", "h2", "h3", "h4", "h5", "h6", "hr", "ins", "noscript", "ns:svg", "ol", "p", "pre", "script", "table" or "ul" (with xmlns:ns="http://www.w3.org/2000/svg")'.

EPUB3
Flightcrew: doesn't work
EpubCheck: doesn't care

I'm assuming since Epubcheck doesn't seem to flag it, that naked text allowable in EPUB3/HTML5.

I'm going to take the opportunity to remind everyone that Sigil's Well-Formed Check is not to be considered any kind of specification validation. As its name implies, it merely checks to see that html is, in fact, parseable. Parseable meaning that tags are all closed and none are improperly nested. Nothing more. It will not catch html/css/xml/epub specification warnings/errors. That is what the validation plugins are for. The Well Formed Check is a quick and dirty "can-I-do-some-automated-processing-on-this-code-without-worrying-about-doing-any-further-syntactical-damage" kind of thing.

08-22-2018, 09:01 AM	#3
DiapDealer Grand Sorcerer Posts: 28,605 Karma: 204624552 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	EPUB2 Flightcrew: "Error schema not satisfied : no character data is allowed by content model near column 1" EpubCheck: Col: 1: ERROR(RSC-005): Error while parsing file 'text not allowed here; expected the element end-tag or element "address", "blockquote", "del", "div", "dl", "h1", "h2", "h3", "h4", "h5", "h6", "hr", "ins", "noscript", "ns:svg", "ol", "p", "pre", "script", "table" or "ul" (with xmlns:ns="http://www.w3.org/2000/svg")'. EPUB3 Flightcrew: doesn't work EpubCheck: doesn't care I'm assuming since Epubcheck doesn't seem to flag it, that naked text allowable in EPUB3/HTML5. I'm going to take the opportunity to remind everyone that Sigil's Well-Formed Check is not to be considered any kind of specification validation. As its name implies, it merely checks to see that html is, in fact, parseable. Parseable meaning that tags are all closed and none are improperly nested. Nothing more. It will not catch html/css/xml/epub specification warnings/errors. That is what the validation plugins are for. The Well Formed Check is a quick and dirty "can-I-do-some-automated-processing-on-this-code-without-worrying-about-doing-any-further-syntactical-damage" kind of thing. Last edited by DiapDealer; 08-22-2018 at 09:03 AM.