View Single Post
Old 07-06-2009, 11:12 AM   #206
llasram
Reticulator of Tharn
llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.
 
llasram's Avatar
 
Posts: 618
Karma: 400000
Join Date: Jan 2007
Location: EST
Device: Sony PRS-505
Quote:
Originally Posted by kindleformatting View Post
The outlines issue I mentioned is a pretty common problem. While you can make a nested list in HTML and give list-style-type properties to the lists, those outline-type lists do not translate into Mobipocket. I have had to create a hack to make nested lists work properly in Mobi, and they look especially good on the Kindle.
I'll give the samples you attached a look this evening. It would certainly be possible to translate 'display: list-item' elements into something other than Mobipocket HTML <li/> elements if it yields better results across most Mobipocket renderers.

Quote:
Originally Posted by kindleformatting View Post
Another issue is that calibre does not support the <mbpagebreak/> tag. I know it is not valid HTML, but it is valid for Mobi files so it would be nice to see calibre use it.
I'm not too keen on adding support for Mobipocket-specific markup when there is an exactly comparable standards-compliant mechanism available. In this case, CSS 'page-break-before' and 'page-break-after' will let you do exactly the same thing. That said, the OPS specification provides a mechanism for allowing markup to contain XML from foreign namespaces that not all processing applications understand. Adding support for that to calibre could potentially allow it to understand Mobipocket-specific markup it could ignore when generating any other output types.

Quote:
Originally Posted by kindleformatting View Post
calibre also requires that any attached NCX file be added to the end of the document, even when there is a TOC in the HTML, and that NCX-generated TOC takes the focus of the TOC guide element.
If you generate the Mobipocket book from an OPF file instead of a directly from the HTML, and in the OPF specify a //guide/reference of @type="toc", then calibre won't generate an HTML TOC from the NCX file and will use the provided TOC guide reference in the Mobipocket output.

Quote:
Originally Posted by kindleformatting View Post
I have also noticed some differences in how calibre interprets and displays some basic formatting, like line heights and heading font sizes.
Line-height I'm a little confused on, as I don't recall a way to control line-height in Mobipocket markup. Does mobigen do special processing for blocks with e.g. a line-height greater than 2x the default line-height?

Headers will definitely be a little different though -- instead of passing through <hn> tags, calibre just groks the (possibly default) CSS and produces pure-formatting output as-similar-as-possible to the supplied styling.

-Marshall
llasram is offline   Reply With Quote