Ok
Quote:
Originally Posted by KevinH
Just for the record, if I am developing an epub for someone (ie. have complete control of the design and layout that has not been made publicly available yet) then I do follow the KISS principle advocated by JSWolf, and do not in general add complexities that may not be well supported by any number of older epub e-readers out there. Of course Accessibility must still be thought about and supported as fully as possible.
I just do not modify other people epub designs and layout without very good reason.
|
With all respect, I disagree. The KISS rule is deprecated, maximun if we have the complete control of the layout and design. The modern epub must be a perfect epub3 ebook, with all the epub3 features, plus a perfect epub2 inside (epub2 ereaders can open epub3 ebooks and you know that more than anyone Kevin). Of that way, if the ereader (the device) supports the epub3 protocols, then the human reader will have the best reading experience; on the other hand, if the device is an old one, then the epub2 code will take place. The KISS rule is an old rule (of course, we have to work more but results are optimal).
And there is a big notice; the epub2 protocol is next to be deprecated. Why? Because KOBO have added practically full epub3 supports to its reades (in my tests, the only thing seems not to be implemented yet are popup footnotes/endnotes and there are issues with MathML). Anyone can test that with the Kobo readers for Android and iOS. I don't know if all eink models of Kobo have been uptades with the last version of the rendering engine but what I saw in android and ios is amazing! To read, for example, "Alice in Wonderland" (illustrated version) with epub3 code, compared with an epub2 version, is like to compare a Ferrari with a bike.