Thread: Problem with inline image
View Single Post
Old 10-25-2016, 09:58 PM   #34
eggheadbooks1
Read, don't parrot.
eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.
 
Posts: 224
Karma: 110242
Join Date: Apr 2011
Device: Kindle Fire, Kobo Touch, Aldiko for Android
Quote:
Originally Posted by Tex2002ans View Post
That is just absurd. From a quick look through the pages there, it seems like nearly all of that information is geared towards Microsoft Word as an input format.
It is aimed at the DIY crowd, most of whom upload either a Word doc (in the earlier days) or an HTML file exported from Word (and possibly tweaked a bit by the publisher). Many are still uploading poor-quality mobi files made in programs like Scrivener. Or using auto-conversion software like Jutoh or Calibre to convert Word docs to mobi.

Quote:
Originally Posted by Tex2002ans View Post
I bet this is just a case of REALLY dumbing information down to try to minimize the amount of Customer Support Amazon has to do.
Yes, because Amazon still want to promote the concept of easy. You cannot even find the Publishing Guidelines PDF unless you first go to Getting Started then click on the link to Simplified Formatting Guide, then happen to notice there is a new left menu pane where there is a link to File Formatting Tips, click on that, then on HTML, then click on the link to the PDF. It's that convoluted. And the KDP website, like the Publishing Guidelines, are "updated" by software engineers instead of proper writers. The KDP website is an absolute mess.

Which brings me back to the PDF. If the Publishing Guidelines are the official coding guidelines, why not make mention of Unicode? This may be a question no one except Jeff Bezos -- who has demonstrated repeatedly that he follows a logic not often shared by others -- can answer.

But about the question regarding exporting Word to HTML for importing into Sigil: I vaguely recall a conversation I had with John Schember about Sigil mapping Windows-1252 characters to UTF-8 upon import, but I notice that if one exports to HTML using Windows defaults, and then imports into Sigil, the charset is still listed as Windows-1252 even though the header code in Sigil says the file itself is UTF-8.

So now I am wondering if there is any situation where that would cause problems on Kindle or ePub. Should one change the defaults in Word to export to HTML as UTF-8 when following the workflow of Word to HTML to Sigil to ePub? Or should one just change the header code in Sigil to say the charset is UTF-8 since Sigil has already automatically mapped the character set?

Or, to put it another way, does it make any difference, or cause any problems, if the charset (Windows-1252) differs from the file encoding (UTF-8)?
eggheadbooks1 is offline   Reply With Quote