Quote:
Originally Posted by GeoffR
I'm not sure what you mean, but whatever font you select from the font menu on your device will be used for the font-family style on <body> (or <body> and <p>for alternative 2.) It doesn't matter what the name of the font is.
Edit: I have a feeling I might have misunderstood what you wanted when I said this patch would do what you want. There isn't any way to select more than one font from the device, the user can just select one font and all the others have to be specified in the book. This patch just prevents the user-selected font from overriding all the fonts specified in the book, making the KePub reader behave more like the ePub reader.
|
No, I wasn't precise enough. What I meant was that I have in ebook something like this:
pre {font-family: DejaVuSansMono;}
and nothing about styling of body or p.
So the first part of your post, before editing, answers my question - I can use specific font name (for everything that I don't want to be in user selected font) and not just font family name.
To say it simple - everything in ebook that
is not <p> or <body> and has its font-family defined, will be using this defined font-family, whether it is font family (e.g serif) or specific font (e.g DejaVuSansMono).
Tomorrow I will test it after firmware update.