Thread: Question
View Single Post
Old 10-09-2020, 11:46 AM   #5
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,664
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Actually... I take back what I said. That's NOT a properly formatted html comment. Those look to be emdashes, or endashes instead of two consecutive dashes that an html comment requires. Sigil's Preview Window, F7 Well-formedness check, and Epubcheck all correctly flag <!—?p—> as invalid for me.

Can you verify that the code in your epub is actually what you posted instead of two consecutive dashes?

Does the ePubTidy plugin attempt to "smarten" double-dashes to an emdash?

Also ... Sigil's "Mend" will correct the situation and turn that back into a valid html comment, so the question is whether this is something that ePubTidy is causing, or if it is already in your epub's code before running ePubTidy and Sigil is fixing it when you mend.

And the answer is, "yes." The ePubTidy plugin is breaking valid html comments with its default settings. I just checked. Keep in mind that ePubCheck is not a validator. As such, it cannot "agree" with other validators about problems. Validators don't make changes to code.

Last edited by DiapDealer; 10-09-2020 at 11:51 AM.
DiapDealer is online now   Reply With Quote