Quote:
Originally Posted by user_none
I don't think warnings are appropriate in this case. With unused files you've explicitly marked (by adding them to the OPF) that you want them used. Hence the warning.
|
Adding a file to the manifest just means it is "part of the publication", whatever that means. For instance, when I have a specific CSS file that is only used by my custom epub2pdf script, I add it to the manifest, but it's otherwise unused. And if I add a cover/thumbnail image just to be used in a <meta> tag, is it used or not? is it to be manifested or not?
Quote:
In this case there are plenty of files that you would add to the EPUB and not actually want or need them listed in the manifest.
Also, lets say warning are appropriate, here is where it gets fun. ePubCheck ignores files in certain places within the EPUB. So where do we draw the line about what get's warned on and what doesn't especially when un-manifested are perfectly legitimate.
|
True. Without wanting to bloat FC, what about an option to list all unmanifested files? Then the creator can decide whether they are intended or not.