|
|
#1 |
|
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 292
Karma: 364036
Join Date: Jul 2026
Location: Planet Earth
Device: Kobo Forma
|
If you were designing EPUB today, what would you change?
In the epublift thread, KevinH asked why WebP and why not just zip -9, and JSWolf argued that everything should be left as it is. They made me want to ask a bigger question, and not about any tool:
If you were designing the ebook format today, in 2026, what would you keep, what would you change, and what would you leave out? Technically and philosophically both. Publishers, people who make books by hand in Sigil and calibre, people who mostly read, and people who write reading software all see different parts of this, and I would like to hear all of them. I will keep a summary of the ideas raised at the end of this post and update it as the thread goes on, so a newcomer can catch up without reading every page. Two things to start from. Mostly, though, I would like to hear what you do today and why. 1. Compression An EPUB is a ZIP, and the compression inside it is deflate, applied to each file on its own. Deflate is about thirty years old and works with a 32 KB window, so it cannot use what the chapters of a book share with each other. Newer codecs such as Zstandard compress better and decompress faster, but where the gain really comes from, a newer codec or compressing the book as one stream, is something I want to measure properly before I put numbers here. I opened a discussion with the EPUB working group about Zstandard in the container: epub-specs discussion #3025. 2. Images: the spec and the devices disagree EPUB 3.3 lists WebP as a core media type, and the EPUB 3.4 draft adds AVIF and JPEG XL. On the devices I could check myself, stock Kobo (Forma, Sage) shows WebP as blank pages, while Apple Books renders it. Kindle, PocketBook and the Adobe-engine readers do not list WebP in their own documentation. So today a book that follows the newest spec can show blank pages on the readers many of us own. Questions to start with
My own starting point, to disagree with The first thing I would fix is the name. EPUB 2 and EPUB 3 come from two very different worlds, yet they share one name and one extension, so nobody can tell which one a file is without opening it up. The one thing we can fairly ask of someone who just wants to read is to know whether their device reads EPUB 2 or EPUB 3. Everything past that, image formats, font formats, 3.0 versus 3.3, is a burden for editors, publishers, device makers and people who write software. We should carry it; we cannot hand it to the reader. Today we cannot even give the reader that one fact. Nothing that exists should break. Every book made so far should keep working, and the old way should stay as the baseline. But new technology arrives all the time, and modern devices deserve a more efficient format that can take it in over time. I also think an ebook should age like a book, not like a web application: boring and durable, strict enough that someone can still write a reader for it in fifty years. A book should still read in full on a basic e-ink reader. Interactive things that cannot do that belong in a different format with a different name. Notes and highlights belong outside the book, not written into it. And if EPUB grows profiles, I would rather see restrictive ones, an archival subset in the spirit of PDF/A, than supersets that fragment what a reader has to support. That is one view. I would like to hear where it is wrong. Summary of ideas so far (Nothing yet. I will add each idea here as it comes up, with a link to the post that raised it.) Last edited by Kayadelenium; 10-03-2026 at 08:38 AM. |
|
|
|
|
|
#2 |
|
null operator (he/him)
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 22,930
Karma: 34252880
Join Date: Mar 2012
Location: Sydney Australia
Device: none
|
I'd start by trying to implement a stitched together codex rather than a papyrus scroll - IOW I would not start with HTML.
Last edited by BetterRed; 10-03-2026 at 06:24 PM. |
|
|
|
|
|
#3 |
|
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 85,755
Karma: 154365285
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
I would dump all of the mutli-media and I would look at what else everything Apple managed to get added in and see if it needs to go or be changed.
I would also make ePub3 more simple. I would bring back things changed from ePub2 that did not need to be changed because the changes do the same thing. I would make ePub3 accessible by default without the need for the code. I would simplify it. It's a bit (IMHO) more complicated then it need to be. |
|
|
|
|
|
#4 |
|
Fanatic
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 571
Karma: 2268308
Join Date: Nov 2015
Device: none
|
But those formats are the same: some hyperlinked content of images, stylesheets, and XML-serialized HTML within a ZIP archive. You work with them and render them with the same libraries.
|
|
|
|
|
|
#5 | |
|
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 170
Karma: 100000
Join Date: Dec 2024
Device: Tolino Shine 5
|
Quote:
Last edited by Falkor; 11-15-2026 at 09:42 AM. |
|
|
|
|
|
|
#6 | |
|
A Hairy Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,522
Karma: 21099999
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
Quote:
And.... ePub support is not required...and even if they do provide rudimentary support, they are not required to update their software to support the latest version... I'm looking at you Kobo & ADE ![]() If you consolidated ePub into a standard software package that everyone was required to use, and allowed their devices to be manually updated by the user, you might see a little improvement...for awhile. How is Java looking lately... or Flash. Companies would just find a workaround - especially if the ePub maintainers were too slow to support the latest big thing. That's how companies draw customers - they have to provide something that others don't ![]() As far as removing features - that's a dead end. People who complain about certain things (media support) just don't find a use for it. The real answer is: They just don't need to use it if they don't like it. ePub support just needs to be consistent enough across devices/apps that they gracefully ignore something they don't grok. That way coders can still use the features they want with proper fallback to ones the devices support. [/ramble] |
|
|
|
|
![]() |
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Change date to today when moving book between library | reup | Library Management | 4 | 11-22-2025 06:31 AM |
| Designing for Kobo | AlexBell | ePub | 45 | 01-21-2013 02:09 AM |
| Designing a document for both print and epub | adieu | ePub | 6 | 10-19-2011 10:10 PM |
| Today is the Day the Internet may Change Forever | kennyc | Lounge | 6 | 04-08-2011 05:47 PM |