title_body: Known Issues with Amazon's Converter What are the known issues with converting various document types to ebooks with Kindle's online or offline converters? I am not asking for a technical run-down of all of the things that could go wrong with a file; I'm asking for a list of the top errors that authors new to e-publishing are most likely to make.
  
  I know, for example, that Amazon publishes a guide called Building Your Book for Kindle, which covers much of this material. Topics from that would make good answers, particularly if you can shed additional light on potential problems with conversion.
  
  Summary examples of helpful potential answers:
  
  
  Stick to Word 2010 or text, not PDFs - PDFs lose lots of content and formatting, like spacing, tables.
  Use indents to start paragraphs, not spaces.
  If you need to create a table, do ....
  Lists convert poorly. To get good formatting of lists, do ...
upvoted_answer: Kindle uses ISO-8859-1 format, not UTF-8. So there are a lot of characters not natively included in Amazon's format. I am Spanish and I find issues with characters like — (em dash) or € (euro currency). Fortunately, you can use their html entity code instead. For instance, the html entity code for em dash is &amp; mdash ; and the html entity code for € is &amp; euro ; (without spaces).
  
  Here you are:
  
  
  ISO-8859-1 entry in Wikipedia. Incomplete support to Hungarian characters is mentioned by November 3rd 2014.
  List of html entity codes in the W3 Consortium.
  
  
  Amazon published a list of ISO-8859-1 characters in a gif image. This is my first post on stackexchange, so I cannot publish more than two links. This is the image distributed by Amazon (you can google it if you want to access the info by yourself):