Oh... I totally get it. Packing the Klingon font in the book is the way it ought to be. I'm just sayin'...

I'm not sure what the spoiler picture is demonstrating...

BTW, I have a touch 5.3.2. Your klingon.mobi does have Klingon glyphs in it. But it doesn't always work right; lots of Klingon show up, but the rest is stacked Tibetan characters (which, at 2am, seems half funny, half profound).

And that might be the problem. Klingon lives in the private use area of Unicode, and so does everyone else's great idea for a glyph. Tibetan has it's own range, so the fact that Tibetan stacking characters show up instead of Klingon suggests to me, anyway, that the Tibetan font put pre-composed stacked characters in the private use range, for, well, private use. I've also seen little-used Chinese characters showing up in the private use area until I set the font to what I put in /mnt/us/fonts, and they're from one of the stock CJK fonts. So maybe your Klingon is just getting stepped on (poor Klingon).

Hard to be sure without more tinkering. Do you have fonts in /mnt/us/fonts? It might also need 5.3.2. ?.

Annoying, but possible approaches, would be remapping your Klingon font to a range not used in stock kindles (maybe to Tibetan? Klingons would like that.), replacing the Klingon with html entities just to see if they survive through mobi/kindle gen better.

Is there a way to bypass this problem? My future v0.5 dictionary needs this font to properly render Klingon translations!

If you really want to generate a Kingon dictionary for the Kindle, you're in luck. Thanks to the code2000.ttf fallback font, eInk Kindles support most Klingon glyphs (and glyphs for most Tolkien conlangs) out of the box.

However, they're encoded in the Private Use Area (F8D0 - F8FF) and both books and dictionary obviously would need to use the same encoding.

(The source files are embedded in the .mobi file; use 7Zip to extract them.)

If you really want to generate a Kingon dictionary for the Kindle, you're in luck. Thanks to the code2000.ttf fallback font, eInk Kindles support most Klingon glyphs (and glyphs for most Tolkien conlangs) out of the box.

However, they're encoded in the Private Use Area (F8D0 - F8FF) and both books and dictionary obviously would need to use the same encoding.

(The source files are embedded in the .mobi file; use 7Zip to extract them.)

If you really want to generate a Kingon dictionary for the Kindle, you're in luck. Thanks to the code2000.ttf fallback font, eInk Kindles support most Klingon glyphs (and glyphs for most Tolkien conlangs) out of the box.

However, they're encoded in the Private Use Area (F8D0 - F8FF) and both books and dictionary obviously would need to use the same encoding.

(The source files are embedded in the .mobi file; use 7Zip to extract them.)

Exactly Doitsu! How about that : I previously went to the trouble of embedding my font for nothing. Just by luck the klingon glyphs are already present in the fallback builtin font and since I am already using the U+F8D0 to U+F8FF encoding, once I remove my embedded font everything is still rendered perfectly for that "ordinary" book.

But my original problem remains, it is within a "dictionary" that I want to display these glyphs. And I think that unless I can produce a KF8 dictionary (Kindlegen seeing indexing only creates a KF7 mobi) the fallback font is not used. See Chelloveck :
On Kindle Keyboard 3.4 vs Kindle Previewer

I had a look at the source files and noticed some syntax errors in the .opf file.
After commenting out the .ncx, script and font sections, it seems to work.

Fantastic Mobi Master. I will study the corrections and will do-it-so.

Initialy your .mobi gave me the same problem. But then, I removed the (Droid) font hack I had installed and everything started to work fine after. Also, my original .mobi (the one with the syntax errors) now works fine too!

Looks like the builtin fallback font is possibly overridden by the fonthack.

...
Do you have fonts in /mnt/us/fonts?
...
Good Luck! Kaplagh, or whatever!

Turns out the stock fonts contains the klingon glyphs as Doitsu demonstrated. No need to embed that font in the dictionary. But your question triggered the other half of the solution. I had the Droid font hacked installed. Once removed the klingon glyphs are rendered properly.