View Single Post
Old 04-10-2014, 06:21 AM   #7
mandy314
Connoisseur
mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.mandy314 ought to be getting tired of karma fortunes by now.
 
Posts: 71
Karma: 200092
Join Date: Mar 2014
Device: kindle pw1
@RbnJrg
Thank you for this working solution.
Only one downside (beside the hassle to get the margin-corrections right for the embedded font): if the user selects a different font on the Kindle PW (I tested this on my rig) the cap's position is wrong as the margin offsets seem to be dependant on the font metrics.

@HarryT
Could it be that simple? No - I did some testing. Even with <big> you get additional leading in the line. <big> isn't that big on the PW, so not much leading is added and you could say "it doesn't matter".

I really don't do fancy formatting. But to see a simple things like raised caps (with css) not working as expected is a KF8-"pita"!
mandy314 is offline   Reply With Quote