[RbnJrg]

Originally Posted by jackie_w

Thanks for that suggestion, Rubén. Unfortunately if I do that, it will upset the same epubs also stored on my Kobos. You would think that 'font-family:serif' would be a fairly benign bit of css, but unfortunately on a Kobo it may stop me being able to change fonts at will.

Hmmm, I'm not sure but I think Kobo allows you to use fonts you like, even when the font in the epub css stylesheet is defined (at least, Kobo for Android allows that).

Ah, yes, I guess if you only want to use one app for many formats then Mantano would be limited. My suggestion was only really aimed at epub. I just let Calibre Companion suggest which of my (many) loaded reading apps will read the various formats. FWIW, when it comes to creating css, I tend to limit it to the kind of simple flat css calibre creates during conversion, i.e. no pseudo-thingies, no combos (p+p, h1>p etc).

I understand you. Pseudo-classes and pseudo-elements is important to me because those properties allow me to add drop-caps, fleurons, etc. with very little effort. For example, suppose that an epub doesn't have drop-caps (at the begining of chapters) and you want add them. Then by writing the following code in the css stylesheet of such epub

h1 + p:first-letter { /* or any other <h> tag */
     float: left;
     font-size: 3em;
     font-weight: bold;
     margin: 0 5px 0 0; /* here values can change a bit */
}

we'll have our drop-caps Regrettably, very few apps support those kind of properties (Kindle for Android and Kobo for Android have support).

Just FYI, in Mantano margins and fonts are handled by the Themes option. I only used Mantano Lite for a very short time so I can no longer remember which features are only in the Pro version. Mantano expects to find sideloaded fonts in the directory <device main mem>:/Mantano/fonts/

Many thanks for the info, Jackie. I will investigate what you said me.

Regards
Rubén