4 ms·

Author here, happy to answer any questions / clarify anything.

• ivansavz 10mo ago
  Thanks for all the explanations. I always thought it was regular HTML, but now I know to watch out for the differences. Can you say a few more words about the library https://github.com/standardebooks/tools https://github.com/standardebooks/tools ? Can it generate ePub3 from markdown files or do I have to feed it HTML already. Any repo with usage examples of the `--white-label` option would be nice.
  • robin_reala 10mo ago
    The tooling does two main things: create a valid epub3 skeleton for your content, and build your book into “compatible”, Kobo and Kindle versions. You need to supply the valid XHTML. There’s more info on the build process at https://news.ycombinator.com/item?id=46469341 https://news.ycombinator.com/item?id=46469341
• pavon 10mo ago
  Are there any sites that provide e-reader engine support charts for ePub, similar to what MDN provides for HTML?
  • robin_reala 10mo ago
    No, not really, and given the length of time ereaders stick around, you’re really probably best off assuming the worst. If there’s something complex layout-wise that I want to do then I often use @supports blocks. For example, in a recent book I worked on I had a layout that would be be accomplished with flexbox, but I started with floats instead and overrode that for better ereaders: https://github.com/standardebooks/harry-harrison_planet-of-the-damned/blob/master/src/epub/css/local.css#L188-L196 https://github.com/standardebooks/harry-harrison_planet-of-t...
• tomjen3 10mo ago
  Thank you, this was very interesting. I knew about XHTML in EPUB, but not that it was extendible - I had assumed it was mostly frozen. Others have requested a list of features supported in different E-readers. i second this request.