Quote:
Originally Posted by jackie_w
Hi Sergio, It's too late here in the UK to start experimenting now, I'll have a look at your epub on my Sony tomorrow. By the way which Sony model do you have?
One thing which immediately stands out with your Extra CSS is that you seem to be missing the bit which tells calibre which html element(s) to apply the CSS changes to i.e. I'd expect to see something like
Code:
body {font-family: monospace; color: black; font-weight: bold}
or
p {font-family: sans-serif; color: black; font-weight: bold;}
You probably don't need color:black; as it is the default.
I seem to remember that my Sony's default monospace font used for epubs was a bit wishy-washy so I customised it. More on this tomorrow.
I have to tell you that I've never used Sigil so can't offer any advice on that. I put most of my efforts into getting the raw HTML/CSS right, do a simple convert to EPUB in Calibre and then just tweak (if necessary) with the appropriately named, Tweak-Epub utility.
It is perfectly OK to convert EPUB to EPUB in Calibre, for all sorts of reasons, but I'm not sure what happens when you convert a Sigil epub to a Calibre epub or edit a Calibre epub in Sigil. I vaguely thought I'd read somewhere that there are some differences with how the epub is constructed. The TOC springs to mind. Perhaps someone more knowledgeable will drop by.
Anyway it's 01:30am, I must go.  |
Sigil just lets you get at the pieces easily
and usually see what happens
What you don't get to see is reader specific deficiencies.
Another line that you might want to add.
font-size: 1.2em < the number affects the relative size (I use 1.2 on my PEz at mid zoom (3) level
(if you original css does not have this defined, the base is (default pt = 1em)