Thread: Opus First impressions of the Opus
View Single Post
Old 07-31-2009, 12:23 PM   #37
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,055
Karma: 147977995
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by Jellby View Post
The problem, as I see it, is not in the format, but in the software implementation (ADE). There's no reason why an ePUB reader should not let the user select a default font, or several (for the different base css families). Most browsers can do that, after all. It's just frustrating that a potentially more powerful and flexible format such as ePUB is spoiled by a limited reader software, which everyone uses even though the format is open and they could create their own better-featured readers...
When I convert to ePub or remove the DRM, I specify Fontin as the main reading font and that works fine. Looks quite nice too. The default ADE font is not all that good and it does look like it's rendering italics from the normal font. But ADE for the 505 does not slow down using embedded fonts. So it's not an issue and I can keep the fonts on the reader without having to have them in each ePub file. I use Fontin as the base font and Fontin_Sans as the header/title font and it works well as it very closely matches Fontin.
JSWolf is offline   Reply With Quote