View Single Post
Old 11-10-2019, 12:25 PM   #25
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
Surprisingly enough, EpubCheck doesn't seem to care one bit about an xml entity being in an opf manifest href. It cares more about the space in the href (and that's just a warning, not an error). Even if checked before Sigil attempts to urlencode the href.

Clearly, the file name itself can't have an actual xml entity in it. Neither Sigil nor Epubcheck seem to allow that. Surprises the heck out of me.

I can confirm that your fix seems to handle this situation well enough, though.

Last edited by DiapDealer; 11-10-2019 at 12:31 PM.
DiapDealer is offline   Reply With Quote