View Full Version : Busted Curlies


brewt
03-24-2009, 08:35 PM
This USED to work........

I've got some ebooks I've been updating recently in MobiCreator.

The Curly Quotes and Curly Apostrophes are now showing as unprintable characters in MobiPocket. (a box)

To my ever-lovin'-best-knowledge, I did not change the encoding on either the source files nor the opf.

Did I turn something off?

This is using mobiPocket Creator V4.2 build 41.

In fact - I'm looking at 2 files, both with the curly apostrophe encoded as [’] one works in Mobi, the other doesn't.

Are there Brilliances to be had?
-bjc

wallcraft
03-24-2009, 08:56 PM
This is typically caused by an encoding mismatch. Either the base HTML (or whatever) is specifying windows-1252 but using UTF-8 or isn't specifying anything and you are getting windows-1252 by default. The default can be changed to UTF-8 under Tools -> Settings -> Default Encoding. If the imported document has the wrong setting then this needs to be changed too.

brewt
03-24-2009, 09:16 PM
Hmmm. My old friend Word (which is what I concocted the html in - don't say it) says it is encoding in Western European ISO, when I Open the file in TED, it says the carriage returns are in Win/Ansi, the file header says <meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">, and Mobi says it's default (and document-specific) encoding is Western Windows 1252.
The code used for the apostrophe is [& # 8 2 1 7 ;] (had to space it to keep from making one when posted).

If I make a New Document out of the air, it all seems fine.

Wonder how I broke what I had......

-bjc

Jellby
03-25-2009, 07:32 AM
Maybe you are using a font that does not have those characters?

Vesper
03-25-2009, 08:44 AM
Wonder how I broke what I had......

-bjc

Installed the most recent mobipocket creator is my guess.

DrS

nrapallo
03-25-2009, 09:50 AM
I found (http://www.mobileread.com/forums/showthread.php?p=351575#post351575) that, using the recent build of Mobipocket Creator, you need to insert into your .html, in the <head> section, the following line for all those nice HTML entities to be properly represented:<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">


Strange that they don't support this as THE default!

Jellby
03-25-2009, 01:07 PM
I believe that if the quotes are written with &# 8271; or & rsquo; or whatever, the particular encoding used does not matter at all.