Kindle Monospaced Fonts: Fail

A mixed bag:

The Kindle has Greek characters, but not complete math (in the image below, there should be a ⇔ <=> character).

It converts Courier (at least) to monospaced, but does not auto-convert Consolas:

As you can see, neither the Courier nor the Consolas work (just look at the difference in space taken by ||||| and mmmmm).

This is a PDF conversion, so it’s possible that a different authoring route (perhaps Kindle specific) is necessary to get monospaced fonts (See update below…) . Bad news for programmers:



Update: Ah hah!

I managed to trigger the Kindle monospaced font by converting from HTML and using the <pre> tag:


More bad news, though: using an explicit HTML <font face=”Courier”> tag does not work.

5 thoughts on “Kindle Monospaced Fonts: Fail

  1. That doesn’t look monospaced to me. A better test would be a bunch of “i”s versus a bunch of “m”s.

    Also, your blog software is doing two odd things with your photo. First, the “thumbnail” is *larger* than the actual image. Secondly, the thumbnail is being constrained by CSS rules to 450px (p img { max-width=100% }, .widecolumn { width = 450px }), but the thumbnail image is actually 627px wide, and, since the height is unaffected, this is changing the aspect ratio.

    1. Yeah; my original post was far too hasty. PDF conversion is very bad. I am now experimenting with other authoring.

    1. It’s doubtful that the new hardware would make a difference. The conversion process happens on Amazon’s servers: I assume that they use the same process for both the Kindle 1 and 2.

  2. The Greek font was of most interest to me. I have been able to put the Greek New Testament (NA27) on my Kindle, loading a text document with UTF-8 encoding. Straight text didn’t work, but with the encoding the text renders properly, to include diacritical marks.

Comments are closed.