tools

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 ? 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.

We have a list of wanted ebooks here: https://standardebooks.org/contribute/wanted-ebooks First-time contributors should select something from the appropriate section, because that gives you the greatest chance of succeeding and the least burden on our reviewers as you get started. Our toolset has a help wanted section and some outstanding issues: https://github.com/standardebooks/tools#help-wanted

Nothing particularly in The Castle, from my production of it. As this was not previously PD there wasn’t any Gutenberg (or other) transcription available, so I did my own from the OCR of the original scans. A large part of the feel of the work, to me at least, comes from the extreme sentence / paragraph lengths though. We do have a default typography across all our works (the “Standard” in “Standard Ebooks” refers to a standard imprint; think Penguin) but we usually retain specific famous things where possible in a reflowable format. For example, the Mouse’s Tail in Alice’s Adventures in Wonderland,[1] or the letter in E. A. Poe’s “Thou Art the Man”.[2] We don’t take on other languages, no. Our tooling[3] and style guides[4] are tailored specifically to English. Absolutely nothing stopping another project from forking the codebase (it’s G

> This incident was one of the most toxic things I’ve ever experienced, and it lasted for days. Yet when I look at the conversation itself, I cannot find anything that seems directly hostile towards them: https://archive.md/q8htc https://lobste.rs/c/mejg0v I do not see personal attacks from either side. I see a normal debate with some snark now and then, which is hardly unusual in online discussions. I may be missing something that happened out of view, but from what is available, the tone does not appear toxic. It looks like a normal debate, very prolonged, but a normal debate until the author gets banned: https://lobste.rs/~7u026ne9se I don't understand why they get banned though. I see no bad interaction from either side. A moderator rebukes the OP for starting a fight: https://lobste.rs/s/gkpmli#c_mejg0v I don't understand this either

For future reference this approach was tested at https://github.com/standardebooks/tools/issues/815. No errors were found in a selection of books.

Hardly AI, just a simple Python function that implements the Flesch reading ease algorithm: https://github.com/standardebooks/tools/blob/effcf0f6db05729...

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 :)

We use the Flesch Reading Ease algorithm. You can find the implementation at https://github.com/standardebooks/tools/blob/master/se/forma... https://en.wikipedia.org/wiki/Flesch%E2%80%93Kincaid_readabi...

Editorial commits are all marked as such and contain no non-editorial changes. The tools for compiling ebook files are available at https://github.com/standardebooks/tools, so creating your own versions with only the work you're interested in is straightforward (and can be at least partially automated).

Sorry to disappoint you, but https://github.com/standardebooks/tools/blob/184056d3112cef8...

Our source format is epub, and the conversion is part of our toolkit. Azw3 conversion is done using Calibre: https://github.com/standardebooks/tools

If anyone is interested in comparing and contrasting, the Standard Ebooks tooling has the same completions for: Bash: https://github.com/standardebooks/tools/blob/master/se/compl... ZSH: https://github.com/standardebooks/tools/blob/master/se/compl... Fish: https://github.com/standardebooks/tools/blob/master/se/compl...

Can you provide some pointers on the tech stack you use for producing these? Do you have something similar to https://github.com/standardebooks/tools ?

Shoutout to some excellent software for ebook wrangling. 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 How to use: https://standardebooks.org/contribute/producing-an-ebook-ste... The second is Sigil, which is a great editor if you prefer to work with a GUI: GitHub: https://github.com/Sigil-Ebook/Sigil Homepage: https://sigil-ebook.com/about/ [1] https://standardebooks.org/