View Single Post
Old 06-26-2019, 07:25 PM   #18
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by DNSB View Post
One issue I've found quite quite a few epub2 renderers is that they implement a subset of the epub2 spec (and no two programmers manage to agree on which subset will be used ) so a epub that reads happily on ADE/RMSDK will display but you get to live with no centering, dropcaps that look like crap, embedded fonts not being supported, images that do not display if the pixel count is too high, etc. ADE/RMSDK is not perfect -- smallcaps is my pet peeve with Adobe and there are other items with their code that have not been fixed in the last decade but it does implement a fairly large subset of the epub2 spec.

As for a web stack? Both epub2 and epub3 subset html/xhtml so there is a close resemblance between an epub renderer and a web stack.
I mostly agree with you. But epub3 is the entire html5+css3,

So you can expect conformat epub2 with a little epub3 subset (RTL, CJK vertical text, even an audio player) ereaders.

The whole epub3 spec is a bad joke for embedded devices nowadays.

Gitden is probably the most close-to-standard epub reader out there.
pazos is offline   Reply With Quote