ggplotnim VS epub3-samples

That is certainly true (and why added a general "embed plot data as bitmap into SVG/PDF" option to https://github.com/Vindaar/ggplotnim that works not only for raster heatmaps). But realistically such plots are often not ideal anyway (too many data points in a plot is often a sign that a different type of plot would be better; typically one that aggregates in some way) and it's just another argument to make the data for plots available as well.

Well, personally as I write almost all my code in Nim and am the developer of ggplotnim [0], I simply write a source code snippet with some short Nim code, generate a plot and dump the filename into the Org file.

If I had more time and wanted something more convenient and magical, I would probably write a elisp function that takes X Y (Z) columns and generates a plot from those using a simple Nim program in the back that receives the data, generates the plot and returns it somehow. Haven't given this much thought though.

[0]: https://github.com/Vindaar/ggplotnim

I have been using Nim for all of my recent data munging and analysis. There's https://github.com/Vindaar/ggplotnim for plots (among others) and everything else has just been normal code. There's also https://github.com/SciNim/Datamancer if you need something more like tidyverse.

With MathML epubs can look decent. For example take a look at the sample MathML epub "A First Course In Linear Algebra" [0] (in a reader that supports MathML of course). It looks pretty good. The problem is Amazon STILL doesn't support MathML, so publishers just churn out a gross version where all the equations are images and so then it doesn't scale properly with the text and the book becomes 300+ MB because of it. And they can't be bothered to make two versions for readers like Kobo that do support MathML.

[0]: https://github.com/IDPF/epub3-samples/releases/download/2017...

For example, if you want to open epub files like https://github.com/IDPF/epub3-samples/releases/download/20170606/accessible_epub_3.epub inside Brave, you will have to install an epub reader extension then instead of downloading it will open inside Brave, if you want to change that behavior you have to disable the extension or limit the extension's domain list, or you right click and "save link as file", but unless the extension has the settings, there is no way to tell Brave to use extension or download manager depending on extensions, unless the extension gets disabled. And if you have an external epub reader, well, you can automatically open the extension when you tell Brave to do it as well.

I've worked on a ePub parse and renderer and the issues you're describing sound pretty familiar.

The three main components of the ePub (aside from the actual pages) are the TOC, the spine and the manifest. The manifest basically tells you where everything is, the TOC is the table of contents which can link to various pages and the spine gives you the traversal order.

Some mistakes I've seen are using the TOC to traverse the book. Using the spine to traverse the book but not handling hidden pages properly. Not handling two page spread properly.

So yeah the spec is nuanced and it would be easy to make a reader that worked with a lot of books but then had weird issues on another set of books that aren't particularly different.

I recall using this repo (https://github.com/IDPF/epub3-samples) to test specific functionality to make sure it was in line with the spec.