leech VS epub3-samples

If you check out https://github.com/kemayo/leech you'll learn how to create a personal copy (not to be shared with others due to copyright infringement laws)

WebtoEpub Firefox addon, Leech, WebNovelConverter

I use a command-line tool called leech, which comes with some pre-built configurations for various sites and stories - including Worm. There are other story converter tools out there, and since FanFiction.net's recent API screwup changes I've used WebToEpub for that.

What problem are you running into getting Leech to work? I looked it up, and it seems like you mean this. I tested out locally, and it worked for me out of the box. Pip successfully installed poetry, and poetry installed all of the required components when called from inside leech-master. I did have to download with Royal Road instead of the original Fictionpress, possibly due to cloudflare blocking me for scraping too fast.

It's all at a very approachable level, too. I had to write an epub-maker as a necessary component for a project, and it turned out to be ~150 lines of python. You have to make a few indexes in XML and stick them into a zip file, basically.

https://github.com/kemayo/leech/blob/master/ebook/epub.py

I use this: https://github.com/kemayo/leech

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.