Thread: Problem with inline image
View Single Post
Old 10-25-2016, 02:01 PM   #28
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:
Again, seems to me like this is some horrid writing.

From what I could tell by looking at previous guidelines (2014.3), there used to be two separate subsections:
Other Encoding Are Supported
Talked about using UTF-8 OR other encodings (why you would use non-UTF-8 in this day and age, I have no clue).
Spaces and Unicode Characters
This just discussed the   + ‌ + gave the same warning about Unicode characters.

Somewhere along the line, they merged both and added in the line: "XML entities are strictly required for "<" (&lt, ">" (&gt, and "&" (&amp.".

Their previous version seemed to make a lot more sense in my mind. Merging them together just created some needless confusion.
Tex: Thanks for the clarification. I have noticed that the Kindle Guidelines and the website are indeed badly written. Which, as you noted, just creates needless confusion, particularly around us non-coders.

Another point to this issue: Amazon still promote the idea that Kindle books can only read Latin-1 (ISO-8859-1) characters. Yet after I learned here about using Unicode to create the musical symbol, I began experimenting more. I randomly chose 10 Unicode characters and tested them in both Previewer and my Kindle Fire device. In Previewer all the characters display correctly except for the older Kindle DX, which could only display 3 of the 10 characters. My Fire displays all fine.

So why would Amazon not want to promote the use of Unicode, seeing as it solves a number of issues? If they promote KF8 formatting, which the DX also cannot read, why not promote Unicode too?

Last question (she says): when exporting to HTML from Word, should we now select UTF-8 encoding or leave it as the default Windows-1252, before importing into Sigil? And does it make a difference if PC or Mac?

I ask because on the KDP website is written: "If you are experiencing conversion failures when trying to upload HTML content, please open the HTML file in Notepad and save it with "Encoding: ANSI" (this is an option in the 'Save As' Notepad dialog). On non-Windows platforms, make sure to save it as ANSI or ASCII, avoiding 'UTF-8' or 'Unicode' as the encoding type."

I'm wondering if that is restricted to Mac and/or restricted to the auto-conversion from HTML to mobi, or if it affects Sigil ePub-to-mobi conversions. When I look at my early Sigil ebooks, built from a Word-to-HTML file, the charset is Windows-1252 but the encoding is of course UTF-8. (I have never experienced an issue in my ebooks but wondering if I just got lucky.)

It also doesn't makes sense to me to tell users to avoid UTF-8, especially as in the Publishing Guidelines (Section 6.6) Amazon give as an example UTF-8 coding. So is the above issue a Mac or Linux (or other non-Windows platform) thing?
eggheadbooks1 is offline   Reply With Quote