View Single Post
Old 03-27-2012, 03:36 AM   #11
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Two notes of interest:

1. br tags really are bad coding. I'm not trying to be the html police, but you're far better off (and get infinitely smoother results) using top- and bottom-margin settings and/or break-before/after. HOWEVER, there's not a bloody thing wrong with the mbp pagebreak command, it's not actually deprecated. Amazon put that section in the Guidelines to stop those people who are addicted to the damn "enter" key, whacking the holy crap out of it to "force" page breaks and vertical whitespace. the mbp pagebreak command works fine.

2. More importantly to this discussion, kids, is this: don't use curlies or smartquotes in your ncx (and/or your chapter headers, if you're building your TOC therefore, either in Calibre and/or MBPC and/or KG); it will break the ncx. You have to be extremely careful about what encoded entities you use for anything that could end up in the ncx. Avoid Curlies if you can, including apostrophes and other "smart" Word-style entities.

HTH,
Hitch
Hitch is offline   Reply With Quote