I used EPublish for my first novel, Means and Motive, just published here, DRM-free: https://www.amazon.com/dp/B0GYCZJVGX
So far I haven't heard of compatibility issues, so I think EPublish has hit the sweet spot of EPUB targeting. I agree, however, that it feels like the old days of targeting IE6 on the web. Old readers still exist out there, so we have to aim for the lowest common denominator.
Kobo's added features on top of ePUBs are nice, and their renderer is much better than Adobe's standard pipeline.
So, it's a free upgrade with a terrific local library added on top.
Got a refurbished pocketbook in the end and very happy with it, it reads all imaginable file formats and I can just send books to it via email or cable.
https://informatecdigital.com/en/Send-to-Kindle%3A-all-ways-...
"This service is free and works with both Kindle devices such as with the Kindle appIt also automatically converts many files to Amazon's internal format (such as AZW3 or KFX), as long as you respect its supported file types and size limits."
Read: requires internet connectivity to put documents on your Kindle. Depends on Amazons 'blessing'. Ends when Amazon ends support for your device. Is limited to whatever document formats (and sizes) Amazon decides to support. Internal formats on your Kindle may be DRM locked. Amazon could snoop any document transferred through that service. Could be turned into a paid service @ some point. Amazon could effectively brick your device if so desired.
(please correct if I misunderstand any of the above)
Sure, this may work for many users & they may be happy with that arrangement. But it's quite a few drawbacks. And the "planned obsolesence" smell is strong here. Me... I'll pass.
I have a 16 year old Kindle (Keyboard) that Amazon actually decided to turn into a brick last month [0]. Still works just fine and will continue to do so thanks to Calibre, but buying books from Amazon, or using their "Send to device" feature (both through the e-mail convert and for books already in my Amazon library) is now forever closed for me and de-registering the device will brick it with no recourse.
[0]: https://www.techrepublic.com/article/news-amazon-ends-suppor...
Any reader will turn into a brick one day. What matters is what you're getting before that point. For me, I'd rather use Send-to-Kindle and never bother with SD cards again. Naturally, YMMV.
The question is I guess if you trust pocketbook or Amazon more. I tend towards the former since that is their main business and not one of 1000 things they do.
My last Pocketbook lasted for 12+ years until something heavy fell on the screen one day. But I hear that kindles are similarly robust until amzn decides to brick them.
I have never seen someone explain the adobe software so perfectly. Using any adobe software is exactly this.
Everything else is better with koreader and it’s super easy to install alongside nickel. And it works very well with calibre + the kobo plugin.
According to the author, Kobo uses CSS from 2013. A quick check with an AI says RMSDK supports CSS 2.1 and parts of 3.
So it's not that the renderer is broken, it's that he believed that epubcheck actually checks against devices and the versions of CSS that those devices support.
This is exactly the issue with test tools: the test tool tests to a spec, but the platform is the gold standard. If you don't like it tough shit.