Top
Best
New

Posted by sohkamyung 21 hours ago

Your ePub Is fine(andreklein.net)
841 points | 286 commentspage 2
pmontra 16 hours ago|
I understand the frustration of the author but how many readers do have an old, unupgraded, maybe unupgradable epub reader? If authors want to make their work available to all readers they have to build for the least common denominator. If it happens to be something from 2013, sorry but that's the reality of the market.
graeme 15 hours ago||
I read this as saying a new Kobo in 2026 uses Adobe drm software that has css rules stuck in 2013.
qubidt 7 hours ago||
The issue the author is explaining is relevant for the Kobo devices currently being sold
TeaVMFan 19 hours ago||
When building EPublish ( https://frequal.com/epublish/ ), an HTML-to-epub converter, I faced similar hurdles. Trying to keep compatibility with numerous e-readers built with different stacks and varying degrees of EPUB versions is frustrating.

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.

rglover 7 hours ago||
Mentioned at the end, but Kobo's gel better with the KEPUB format. Calibre has a nice converter for this (I think it may be built-in now or still a plugin), but works great. Got a Kobo Clara Colour about ~2 years ago now and I couldn't highlight across pages until I bulk converted my library to KEPUBs. After that, you'd never know there was an issue. This post makes the whole mess make a lot more sense now.
bayindirh 11 hours ago||
When using Kobo readers, using Calibre and Kobo utilities, which transparently "upgrades" your ePUBs to KePUBs without altering the copy on your disk is a must, and a huge win.

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.

icantevenhold 12 hours ago||
I recently was in the market for a new e-reader and steered away from Kobo and Kindle because of their non-free ecosystem. I don’t know how exactly it would negatively impact me but I didn’t want to find out.

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.

dakolli 12 hours ago|
I don't really have an issue with kindle, I just download anything off of z-library and use the email to kindle tool. I haven't given Amazon a penny other than from the original purchase of the kindle. I only have used epub/pdf (and will never have a need for another format).
RetroTechie 8 hours ago|||
Quoted from here:

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.

thg 2 hours ago|||
> Amazon could effectively brick your device if so desired.

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

maratc 7 hours ago|||
All of that is technically correct, however my non-Amazon readers (Sony, Nook, ...) reached the end of their useful life when their batteries died or their screens broke. All of them were "unsupported" at that stage (3-4 years after announcement), so not much to do about it. With that, I have a very old Kindle (7 years or so) that is still working -- with "Amazon's blessing" of course.

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.

icantevenhold 33 minutes ago||
Fwiw the pocketbook has the same kind of feature.

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.

maratc 7 minutes ago||
I can count on Amazon being there in 10 years from today. I can't count on pocketbook.
boredhedgehog 9 hours ago|||
Technically you already have need of another format, because Kindles don't support epub, and your books get converted before the transfer.
maratc 9 hours ago|||
The "Send to Kindle" page only accepts ePub, as to whatever format is used internally I couldn't care less.
WorldMaker 4 hours ago|||
The latest Kindle formats are just epub with a different DRM hat. Amazon still prefers to wrap the entire container in DRM whereas most epub DRM schemes are inside the container (ZIP file), but that's the only big difference now.
insumanth 14 hours ago||
> that bloated pinnacle of software that is 80% about DRM, 20% about the reading experience

I have never seen someone explain the adobe software so perfectly. Using any adobe software is exactly this.

matwood 13 hours ago|
Unfortunately this is any reader software that deals with publishers who require DRM. IME, the vast majority of bugs also come from the DRM.
KerrickStaley 6 hours ago||
I use KOreader on my Kobo, which is an alternative open-source ebook renderer. It installs pretty easily without rooting the device. In addition to better standards compliance it also is a lot more performant and has niceties like auto cropping of PDFs.
projektfu 6 hours ago||
This was originally posted with the full title, which made sense. Why was it truncated?
Retr0id 6 hours ago|
Presumably to make it sound less like LLM output.
projektfu 5 hours ago||
I just don't get it when the title changes to something uninteresting. It wasn't click-bait before, but now it's almost meaningless.
ornornor 12 hours ago||
If you use a kobo you have to give koreader a whirl! The only thing missing for me is the unified view of the library: koreader requires you to navigate to the subdirectory to open your ebook whereas nickel (kobo’s UI) will list them all in one library regardless of how deeply nested they are.

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.

martin- 8 hours ago|
There are several plugins that give you a library view based on metadata instead of folders and filenames. Two examples that are both great:

https://github.com/AndyHazz/bookshelf.koplugin

https://github.com/joshuacant/ProjectTitle

ornornor 7 hours ago||
Thanks, I had no idea, these look great!
mannyv 16 hours ago|
"Epubcheck does basic CSS checking of course, but it can’t validate CSS against a renderer which is fundamentally broken!"

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.

WorldMaker 4 hours ago|
The CSS 1 spec says to robustly ignore lines you don't understand. Adobe didn't need to predict CSS 4, they needed to better implement CSS 1.
More comments...