Quote:
Originally Posted by KevinH
What about improved Accessibility? SMIL - Audio overlays? Support for RTL and vertical languages? CSS3? And yes even regular Audio, Video? CSS3?
|
Never used any of that, them, have no expectation I ever will.
I do books in English, almost all converted from ones I did for print.
Target device is Kindle or iBooks.
Quote:
Originally Posted by KevinH
And what makes it harder to edit and style for standard fiction?
|
All those extra features you mention. All the encrustation of semantic tags, etc.
Annoyances like only allowing numeric codes instead of mnemonics like   for instance, making source code look like a hex dump.
The NAV file always appearing in Kindle coversions whether I want it or not. (An Amazon problem, but one I don't have with epub2.)
I'm not saying these features have no use, just none for me.
I've looked at code for hundreds of books, commercial and amateur, always interested to see how others code them up, and never seen one that did use any of these features to do anything useful.
I'm not going to rant against epub3. I can and do use epub3, but not from choice.
Quote:
Originally Posted by DiapDealer
Nothing. "Complex and fussy" = I can't be bothered to learn the few simple differences EPUB3 presents for novels.  |
No need to be insulting. I understand how to do it. Have been making epub3 since about 2014, when I was coding up the NAV file by hand before this plugin came along. It's just tedious, like filling out a tax form.