Do we need to generate Kindle mobi files?

TEIC / TEI

The Text Encoding Initiative Guidelines

https://www.tei-c.org

Other

282 stars 84 forks source link

Do we need to generate Kindle mobi files? #2574

Open martindholmes opened 4 months ago

martindholmes commented 4 months ago

The build process currently generates a special EPUB version and then processes it with the kindlegen tool to produce a .mobi file. However, Kindle now supports EPUB natively, and .mobi seems to be on the way out:

https://kdp.amazon.com/en_US/help/topic/G200634390

Since kindlegen itself is not open-source (one reason it's not installed on my build server), and .mobi isn't necessary, I suggest we completely remove this step from our build process, and offer only the PDF and EPUB formats for offline reading.

The relevant Makefile lines are here:

https://github.com/TEIC/TEI/blob/dev/P5/Makefile#L124

martindholmes commented 4 months ago

I have run the kindlegenpreviewer tool against the published Guidelines.epub and it shows no errors at all, so there's no additional work to do there.

peterstadler commented 4 months ago

That sounds very reasonable to remove the extra step of building the Kindle mobi files (which relies on an outdated and proprietary tool).

👍 from me

tuurma commented 4 months ago

Yes from me as well

ebeshero commented 4 months ago

This is such an easy change that we might forget we’ve implemented it, so we just need to make sure we document it in the release notes.

It should probably be done before the next major release of the Guidelines, yes? We’re getting ready to do a patch release on July 31 that’s specifically just for supporting the new website, so it’s probably not the best moment. I think we should not implement this change before the patch release, but make the change after that’s over for the next full release. Thoughts?