Quote:
Originally Posted by murg
I use the css to define how the tags work, rather than using css classes. I have a standard css file that goes into each epub.
Use <body> rather than <body class="calibre7">
Use <p> rather than <p class="calibre7">
Use <i>, <b>, <sup> rather than <span class="calibre7">
Use <h3> rather than <h3<span class="calibre7"><span class="calibre8"><span class="calibre9">
Section breaks are: <p class="center">——</p>
This makes them very visible, especially at the bottom and top of a page.
I generally only use <span> for things like smalling the font (small caps) or messing with the formatting.
This all keeps the html as simple as possible. And lets me use the adjustments on the devices to do a chunk of the format handling.
I also do the following to override formats: <p class="noindent FontSansSerif FontSize08">
|
That is roughly what I do. Styles for the tags and only use classes for the exceptions. About the only thing different I do is to use a class to separate the section breaks unless it has an asterisk or two in it.
Quote:
Nope, I've been reading a series of books, all recently formatted. The first few didn't have this problem, the later ones do.
I am doing a lot of annotion in the books, though.
|
Interesting, I could see annotations messing up the position calculation, if it works how I think it works. But, I have taken a lot of annotations in the book I finished today and I had no reopening position problems with it.
Also, you might want to look at the book Lynx-Lynx (who I hope lives in Woy Woy or Wagga Wagga) mentioned. It has some in-line pictures that might help with your other problem.