leech VS tools

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

This violates the "One Tool" constraint that OP requested, but the Standard Ebooks tool chain is available on Github for anyone interested: https://github.com/standardebooks/tools

The code is GPL-3 and the templates are CC0: https://github.com/standardebooks/tools/blob/master/LICENSE....

Feel free to ask on the mailing list if you have any questions, more likely to be picked up there than in a random HN thread :)

I'll give a shoutout to some other excellent software.

The first is the "Standard Ebooks"[1] toolset, which is a suite of Python scripts to create, process, and build ebooks in all common formats. The results on the Standard Ebooks site speak for themselves. They're impeccable in every way, and far better than many big name, commercially produced efforts.

GitHub: https://github.com/standardebooks/tools

This question comes up a lot. The source to our production pipeline is GPLed and freely available,[1] but the biggest part of why we produce good work is that we have a high quality manual of style.[2] Unfortunately, that second part is very specific to English, and that’s the difficult part to replicate for other languages.

[1] https://github.com/standardebooks/tools/

[2] https://standardebooks.org/manual/