Backward-compatible EPUB 3 files in 4 steps?

[zonker]

Hi, I'm writing an ebook template with Sigil and I'd like it could be a backward compatible epub 3 file.

Is it enough change the following things?

• put version="3.0" instead of 2.0 inside <package>
• insert a Navigation document
• indicate cover in <manifest>: <item id="cover-image" properties="cover-image" href="Images/front_cover.jpg" media-type="image/jpeg"/>
• add “dc:terms modified” metadata

something else? should be this fully compatible with old ereaders?

[JSWolf]

Unless you are doing something that needs to be ePub 3, stick with ePub 2. It's a lot more compatible and a lot less hassle when you get complaints that your ePub 3 (that should have been ePub 2) it doesn't work on some readers.

[zonker]

Ok, but those changes make it less compatible? And anyway are they enough to to make it a backward-compatible EPUB 3 file?

[JSWolf]

Originally Posted by zonker

Ok, but those changes make it less compatible? And anyway are they enough to to make it a backward-compatible EPUB 3 file?

Are you making these changes just because you can or are you makes a true ePub 3? If you aren't making a true ePub 3, just make an ePub 2.

I cannot say if just those changes will work. I've not fiddled with ePub 3 as I have no need for it.

[zonker]

thanks, yes probably it's better to make an epub 2. but I'd like a better-looking index for example in iBooks.

[Jellby]

Originally Posted by zonker

should be this fully compatible with old ereaders?

The <meta> tag should not affect old readers at all. The navigation document, as long as it's valid XHTML, and properly included in the manifest and spine, is OK. The properties="cover-image" and version="3.0" could potentially cause a problem if some reader is particularly picky in its validation, but I don't think it will matter in practice. Still, by declaring the epub as version 3, you are looking for problems, any epub 2 reader could refuse to open the file without further parsing.

[zonker]

and if I don't declare epub as 3.0 etc., should the navigation document still work in iBooks?

[JSWolf]

Originally Posted by zonker

thanks, yes probably it's better to make an epub 2. but I'd like a better-looking index for example in iBooks.

When you are making an eBook for iBooks, it's OK to do it however it works in iBooks. Just don't expect to make an ePub that does what you want in iBooks and works elsewhere. Best way to do it is to make to different version. One being ePub 2 and the other being for iBooks.

[zonker]

Ok, epub 3 can wait.
Thanks.

[JSWolf]

Originally Posted by zonker

Ok, epub 3 can wait.
Thanks.

Oh and speaking of iBooks, it is possible to make an eBook that will work in iBooks for iOS 7, but not in iBooks for iOS 5 (1st generation iPad).

[zonker]

sure, we don't like easier things...

but what's the best solution for making an epub 3 just for iBooks (iOs 7)? four steps above with sigil?

[JSWolf]

In making ePub 3 for iBooks, Sigil is not what you want. It's ePub 2 and doesn't handle all the iBooks stuff.

[odedta]

zonker, just download a sample ePub 3 from the google sample section (google: epub 3 examples) and go from there.