Quote:
Originally Posted by what
Is there some overview like https://caniuse.com/ that shows which ebook reader supports which formats and features? |
Yes, although not as good/thorough:
http://epubtest.org/
Although it looks like the old info/tests haven't been converted over to the redesigned site.
From ~2014-2018 they tested lots of different apps/devices.
For example, I wrote about WOFF in
"Font Best Practices".
You could still use Archive.org to crawl through the old site:
But, for the most part, KISS (Keep It Simple Stupid). Too many of the fancy things would break across readers.
If you know you're only focused on selling in a single store (like Apple iBooks), you might be able to get away with a bit more...
But trying to sell an ebook wide, stick with the lowest common denominator. Like
scene breaks with simple centered asterisks, not CSS3 ::after.
Quote:
Originally Posted by Quoth
No, NO-ONE sensibly uses XHTML or XML as a source format to write books. They are an intermediate format for formatting. You MIGHT create very short documents in them.
And no publishing house uses XML as source format for books. They might have XML in the workflow. Fiction is via wordprocessor -> PDF proof.
Non-fiction is potentially more complicated if formulas etc involved.
|
You must've missed the 2019 thread:
"Workflow for simultaneous EPUB and PDF production?"
You may also be interested in this talk given at
ebookcraft 2018: "HTML-First at Wiley, or, How We Learned to Stop Worrying and Love the DOM".
There's also
JATS, which is XML mostly used in journals.