View Single Post
Old 03-27-2012, 02:42 PM   #14
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,705
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Hitch View Post
Diap:

Are we talkin' Mobi or ePUB here? I see I wasn't explicit, in my language, but I was talking about the mobi ncx, which will break in the devices and in K4PC (for whatever the latter is worth).

H.
I'm talking either/or. I have epubs that have curly-quotes and special unicode characters (acutes, umlauts, etc...) in the NCX file that work just fine. I convert those epubs to mobis using kindlegen and they still work fine on Kindle devices/apps. Using Kindle Previewer, I can verify all the special characters are still in the NCX of the resulting mobi.

It's true you can't use entities like & rsquo; in the NCX file, but you can put the actual right single-quote (’) unicode character in there with no problems (the forum doesn't render that quote very "curly" but I assure you it is ).
DiapDealer is online now   Reply With Quote