Quote:
Originally Posted by nabsltd
|
But that's pure BS. ePub does not keep up. That would mean all the programs for your computer, phones, Readers, etc. would have to be updated to keep up with the latest HTML spec. That doesn't happen. Look at a lot of programs for iOS and Android. They don't even keep up with the ePub 2 spec nevermind something new.
When you create an eBook, the way to do it is to keep it simple. For example, in CSS for ePub 3, you can use rem instead of em. But don't when em works in so many more cases and it's the same thing.
There are times when you will want to use something that won't work in older software (or some software). So in that case, you use fallbacks where possible. The way to do it (IMHO) is to install ADE 2.0.1 and look at your eBook with that and see how it looks. That way you'll know it's good enough for older software. You don't want your book to fail on older software. Look at Standard EBooks. They use the most convoluted code on eBooks where the formatting is very simple. They problem is that their eBooks fail to display properly a lot of the time. And in the case of older ADE such as on Kobo and Sony Readers, they fail completely. There's no need for this.
So keep the code as simple as possible so it works in most cases. Don't use the latest and greatest code just because the program you are using to view may support it. If you find it works best, create an ePub 2 and convert to ePub 3 for the accessibility. But always make any ePub 3 backwards compatible with ePub 2 and make sure the eBook works well enough (even if not perfect) with ePub 2.