Quote:
Originally Posted by HarryT
But that's not true. One does not list embedded graphics in the manifest.
|
One most certainly does! If one didn't one would be creating non-conforming epub files that would quite probably fail on numerous devices! A Reading System is
not required to present any media not referenced in the OPF file.
I'll refer you to
section 2.3 of the Open Packaging Format.
Quote:
Originally Posted by HarryT
I don't know if ePub does the same, but with Mobi (which also uses OPF files), if you include your graphics files in the manifest, they end up being included twice in the book. The fact that they are linked to is sufficient to build them into the book. I know that ePub is different, in that there's no book "built" as such, but do any adverse effects result from omitting the graphics files from the manifest?
|
How Mobi does it is completely irrelevant. Mobi is not epub. And adverse effects are most certainly possible, if not probable. I believe that currently ADE handles it, but other Reading Systems may not. I'm sure that a lot of tools designed for epub manipulation & transformation would fail on this error in some way.
ADE handles it because it embeds WebKit which does all the loading. IMO, they point it to the directory structure in the epub file and it loads all the images as they are referenced in the HTML. It (webkit) does not use the OPF directly.