Thread: KFX Format
View Single Post
Old 04-29-2017, 02:38 PM   #593
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 jhowell View Post
There are instructions on how to format drop caps in the Amazon Kindle Publishing Guilelines section 9.3.5. The conversion to KFX looks for that formatting.
JHowell:

I haven't had a chance to look at that yet, but if that's the same-old, same-old coding for DCs that has been in now for some PGs, that doesn't work worth two craps when you cross the Device Line--from Fires to the KF8 eInks (PPW, etc.). The PPW, to be particularly capricious, basically requires the user to actively select "Publisher Font," and if they don't, it's nearly impossible to get the Drops to work, in that environment. As drops, that is.

We use about five million lines of code/HTML/CSS, with about 10 media queries, just to TRY to get those right. It's a royal pita. If the new KC somehow magically overcomes that, I'll be ripping those mobis/KFX/KPFs apart, to see what they're doing.

Offered solely FWIW.

Hitch
Hitch is offline   Reply With Quote