Thread: KFX Format
View Single Post
Old 03-02-2017, 01:01 AM   #548
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by AaronShep View Post
eggheadbooks1, it's not clear how you generated or viewed your first tests, but your final test is invalid. The MOBI file generated by Previewer 3 is not in KFX, it's an intermediary step before the final conversion. Previewer 3 does not offer any file that you could load onto your Kindle Fire. (And an older Kindle Fire might not display KFX's Enhanced Typesetting anyway.) You have to view your test in Previewer 3 itself -- and frankly, even that doesn't always show you exactly what you'll get after KDP processing.

I haven't tested the nonbreaking space in Previewer 3 recently, but I not only saw proof that they were being ignored, I also confirmed it with the head of the Kindle engineering team responsible. He told me they did it to prevent authors from sticking together phrases that run off the edge of the screen. And despite my strident arguments, I could not convince them to change their minds.

OK, I just ran this HTML into Previewer 3, and it again shows the nonbreaking space being totally ignored. I'm not sure it will show up here properly, but it's a set of numbers 1 to 5 repreated numerous times, with nonbreaking spaces between the number of each set. In Previewer 3, you'll see that the number sets are broken anywhere at all, not at the end of each set as they should be. I also ran the same test using the Unicode character in place of the entity, with the same results. They're both treated as simple spaces, just as reported earlier.

<div>1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5 1&nbsp;2&nbsp;3&nbsp;4&nbsp;5</div>

You should forget about controlling em dashes. (I've started putting a space before and after, as in newspaper typography, so it won't look so bad.) And if you really need to show formatted text such as CIP, your best bet is probably a GIF.

Aaron

In the normal course of things, we don't have a lot of spare time to test things like this, but we recently have tested it a bit due to a client's requirements. Our tests--not that extensive, but still--indicate that the nbsps are being ignored/converted to a space.

Offered FWIW.

Hitch
Hitch is offline   Reply With Quote