View Single Post
Old 03-01-2012, 12:38 PM   #10
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,664
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
In keeping with the above mentioned CSS conversion issues:

If you're trying to maintain one unified document for ePub and MOBI, keep in mind that kindlegen's css conversion logic can't cope with more than one class being assigned to a single element. so...
Code:
<p class="first-class second-class">text here</p>
just won't work.

Something like:
Code:
<p class="first-class"><span class="second-class">text here</span></p>
will have a much better chance of being successfully converted to mobi (while still being valid for ePub). Or you could combine the attributes of the two classes into one if possible. Just don't plan on being able to "stack" CSS classes to achieve your desired effect (Note: the KF8 format has no such limitation).
DiapDealer is offline   Reply With Quote