Quote:
Originally Posted by kiwidude
@theducks - what my check does is look for whether there are files in the ePub that are not listed in the .opf manifest. It doesn't look in the html files or stylesheet files at all.
So my assumption is that any file that is intended is part of your ePub should be listed in the manifest.
It would appear that whoever has authored those books from Feedbooks has decided that they do not consider it relevant to include their stylesheet in the manifest. I don't know the ePub specification to know whether this is "valid" or not. I know Valloric watches the spec pretty closely, so if Sigil treats these as "unused" it sounds like they should be. Or it could just be a bug, Sigil has plenty of those.
I know that ePubs will "work" without having files listed in the manifest, but of course this plugin is about identifying "less than ideal" scenarios. If in fact it is seen as an acceptable convention to not include .css files in the manifest then perhaps I have to make a special case exemption. Alternatively I could change finding such situations into a "warning" and just displaying in the log.
I welcome anyone's input on how these should be treated, if any differently than currently.
|
Thanks for your reply.
I figured Valloric would chime in sometime (he has a new job so his time is limited) or one of the other EPUB /CSS spec gurus.
I had 22 that showed, many Feedbooks (used the same stylesheet). Others I have been looking hard at some to figure out
what is the file.