Quote:
Originally Posted by HarryT
Can you name a device that it would fail on, please?
|
I have no intention of testing each and every device out there to see if it fails on this specific issue. The whole point of a defined standard is that one
doesn't need to check how their books display on all devices: one just needs to check against the standard.
Quote:
Originally Posted by HarryT
It's not "irrelevent" what Mobi does if you wish to create source which can be built for both Mobi and ePub, and if ePub works without the graphics files being listed in the manifest section of the OPF file, I have to ask "does it matter, at a practical level?"
|
Yes it does. You can not state that "ePub works without the graphics files being listed in the manifest section of the OPF file". ADE works with this error present. Maybe other Reading Systems handle it too. But others don't.
They don't have to. Future Reading Systems may not handle it either.
If you don't list all you files in the manifest, you are disregarding the whole point of that section. There are numerous tools out there that convert or transform the epubs in some way and they don't employ HTML renderers. They
will break on this. If you for instance feed an epub file to a converter that checks only the OPF file (which it should do), the conversion will fail.
Harry, during my time here on MobileRead you have come across as a very intelligent person. I obviously do not know how to convince you to follow the prescribed standard. Honestly, I'm amazed that I even have to.
I will tell you that if you make epub books with this error you--or someone else using your books--will
most definitely encounter a system that will fail in some way because of it.
I guarantee it.
Please do
not ignore the manifest, or any other part of the epub spec.