[Tex2002ans]

Originally Posted by Notjohn

I can use the Unicode thin space?

Will an epub containing the thin space cause any problems outside the Kindle universe?

Many fonts do not have the Thin Space. It would most likely show up as �. For example, on my Nook, only 1 of the fonts has it (I don't have a Kobo on hand right this second to test).

As DaleDe mentioned, they most likely say to avoid those rarer spaces to be FULLY compatible with older Kindles/firmwares. I am not too sure of all of the fonts Kindles have/had available since the Kindle 1 + firmware 1.0.

Again, the more compatible substitution would be   ->  .

For example, in French:

<p>This is an example of a French quote&thinsp;:&thinsp;«&thinsp;Il est très beau&thinsp;!&thinsp;»</p>

This is a perfectly valid substitute:

<p>This is an example of a French quote&nbsp;:&nbsp;«&nbsp;Il est très beau&nbsp;!&nbsp;»</p>

In English, the Thin Space is rarely used. Notjohn, what is the use case where you were thinking of using a Thin Space? I can only think of a handful off the top of my head, and all can be handled fine with Kerning/Normal Space/Non-Breaking Space.

Originally Posted by eggheadbooks1

Amazon still promote the idea that Kindle books can only read Latin-1 (ISO-8859-1) characters.

May I ask where you saw this?

I don't recall ever seeing anything about that in the Amazon Kindle Publishing Guidelines:

https://kindlegen.s3.amazonaws.com/A...Guidelines.pdf

MAYBE that was just a troubleshooting step if you were doing some horrible Word -> Kindle conversion. Who knows what madness some WYSIWIG editor like Word might introduce. I have seen some really scary files, and I just shudder to think what kind of horrors Amazon has seen.

Side Note: I bet as Amazon/Kindles expanded internationally they made sure to expand the characters included in their default fonts (via firmware updates). I mean, it would be preposterous selling Russian ebooks without Cyrillic characters.

Originally Posted by eggheadbooks1

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.)

To be a valid EPUB, HTML files must be UTF-8 or UTF-16. Calibre/Sigil already makes files UTF-8 on import.