Quote:
Originally Posted by AliceWonder
Many people have different vision issue. Dyslexic people often have a font that works wonderfully for them but that is ugly to others, for example. They should be able to specify that font if they want to and be able to read the book w/o missing any nuance.
|
Quote:
Originally Posted by AliceWonder
I did get to test a lot of Android ePub readers and it seems Lithium does the best at properly displaying my ePub (which only has minimal CSS at the moment) and also seems to be the least annoying to use.
|
Never heard of Lithium, but I'm betting it's another Webkit-based one.
On the computer, what you want to test on is Adobe Digital Editions (ADE).
This uses RMSDK (EPUB2) + Readium (EPUB3) engines. This is what most of the actual ereaders + major publishers use.
If it's in the Android wild west, you can try your best to create clean code that has graceful fallbacks, but you can't satisfy all of them (because of the previously listed issues).
It's why I try to keep my code as KISS as possible.
Side Note: Most Android readers work on the basic books, but begin to fail once you start getting into EPUB edge cases:
Quote:
Originally Posted by Hitch
I know that client. Been there, done that--and he had 40--FORTY--characters. Forty different fonts--forty-one with the main narrative font. I cannot tell you what I went through during that quote, trying to explain to him that what he wanted to do was a freaking nightmare.
|
lol, I remember that one. There's a reason why most Typographers stick with 3, maybe 4 per document.
40 is beyond madness.
Side Note: All this font talk dredged up memories of this forum post.