View Single Post
Old 04-27-2024, 12:19 AM   #3
RbnJrg
Wizard
RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.
 
Posts: 1,567
Karma: 7043711
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by Ken_Moorhead View Post
...
With that information you could (in theory) branch which HTML files are in play, or even (possibly) branch the markup itself, to adapt to user settings or device settings.

Is this possible?

Ken
On epub2, no (or very poorly). On epub3 you have javascript and with it, you can know a lot of things about the device (or app) where the epub was opened (and the position and size of the elements contained in that ebook) and to adapt the layout accordingly. For example, one old epub3 ereader is Gitden; is deprecated, but even so is quite good. But it has a drawback; you can't set -with the app- the margins of the body text; with javascript you can know that the epub is being opening on Gitden and then set margin by means of css styles (those styles are only applied if the epub was opened under Gitden).

Last edited by RbnJrg; 04-27-2024 at 12:28 AM.
RbnJrg is offline   Reply With Quote