Quote:
Originally Posted by ahi
A "cover" probably should be treated as metadata, if technology allows. Are there reasons to avoid doing so? (Other than "it's not as easy for Sigil's users"?)
|
Oh I'd love it if the EPUB spec had some "cover image" metadata. That would be awesome. But it doesn't. What little it has that
could be used to specify the cover image is not mandatory.
EDIT: And even that cannot be used to specify the cover
image, only the cover
page!
Quote:
Originally Posted by kovidgoyal
Yes but users like to change the covers of ebooks.
|
Open it in Sigil, delete the cover image, insert a new one. Done. No need for a guide element.
Quote:
Originally Posted by kovidgoyal
If the user just imports an image file at the beginning of the document and doesn't specify that it's a cover, that's the users problem. But Sigil should at least present the possibility for a user to do it the right way.
|
Fair point. But the "right way" is arbitrary now, it's what you say is "right". I say "right" means putting an image at the beginning of the document. Again, there is no way to
semantically specify the cover image in an epub that all reading systems would have to respect.
Even ADE has its own proprietary extension for this I believe.
Quote:
Originally Posted by kovidgoyal
At the very least Sigil should not strip out existing guide elements, unless the file it points to is removed.
|
The file pointed to is not present after importing. Sigil disassembles the imported epub and creates the NCX, OPF etc on export. These files are not stored after they are imported.