Quote:
Originally Posted by Hitch
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.
|
Entities... yes. I agree. Those shouldn't be used in the NCX (named or otherwise). But the NCX file is perfectly capable of handling
actual "curly-quotes" (and other unicode characters). I use them all the time. It's still a utf-8 encoded document... it's just not (x)html.