MobileRead Forums - View Single Post

Quoth · 08-30-2023, 12:52 PM

ADE exists to support a closed system, Adobe DRM on epub. Also the epub specs are a subset of Web. A Website isn't an ebook. A lot of epub3 stuff doesn't apply to novels.

Poor formatting on ebooks is due to poor design choices, or trying to be too clever, or lack of expertise. You can have ebooks that look almost the same in an ereader sized window in wordprocessor, ADE epub and Kindle azw3. The kepub and kfx will render less like the original.

@nabsltd
You need to produce ebooks that suit what 95%+ of people are reading them on, not chase after what either paper or web browsers can do. Also every day I encounter appallingly designed websites, or websites that only work perfectly in Chromium and I don't encounter so many bad ebooks. The really bad ones (people that are too clever, or misusing InDesign, Vellum etc) are easily fixed in Calibre and then a pleasure to read, if well written.

Over 90% worldwide in English sales of ebook are Amazon. Slightly more than 1/2 read on Kindle App on phone/tablet (and till recently much poorer on iOS Kindle App), the rest on Kindles.
And then older Kindles are HTML3 and no embedded fonts.
You also can't make Kindle users use the Publisher settings/fonts. The default is an Amazon Theme.

Edit:
There are loads of things I would have done differently in an ebook spec. But no-one asked me.

08-30-2023, 12:52 PM	#113
Quoth Still reading Posts: 14,353 Karma: 105899727 Join Date: Jun 2017 Location: Ireland Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper	ADE exists to support a closed system, Adobe DRM on epub. Also the epub specs are a subset of Web. A Website isn't an ebook. A lot of epub3 stuff doesn't apply to novels. Poor formatting on ebooks is due to poor design choices, or trying to be too clever, or lack of expertise. You can have ebooks that look almost the same in an ereader sized window in wordprocessor, ADE epub and Kindle azw3. The kepub and kfx will render less like the original. @nabsltd You need to produce ebooks that suit what 95%+ of people are reading them on, not chase after what either paper or web browsers can do. Also every day I encounter appallingly designed websites, or websites that only work perfectly in Chromium and I don't encounter so many bad ebooks. The really bad ones (people that are too clever, or misusing InDesign, Vellum etc) are easily fixed in Calibre and then a pleasure to read, if well written. Over 90% worldwide in English sales of ebook are Amazon. Slightly more than 1/2 read on Kindle App on phone/tablet (and till recently much poorer on iOS Kindle App), the rest on Kindles. And then older Kindles are HTML3 and no embedded fonts. You also can't make Kindle users use the Publisher settings/fonts. The default is an Amazon Theme. Edit: There are loads of things I would have done differently in an ebook spec. But no-one asked me. Last edited by Quoth; 08-30-2023 at 12:59 PM.