Quote:
Originally Posted by RbnJrg
By using .svg images as I told you in my previous post, you can get the following:
1. To show a raised a cap.
2. The raised cap can be of any custom font you like.
3. There is no need to the user to enable "publisher fonts" to see the raised cap.
4. The raised cap can change its size when the user change the device font size.
5. There is no problem with the Amazon's line-height limitation.
6. The raised cap looks great in Kindle devices that support .kf8; you can judge by yourself:
Attachment 121901
What you see above is a screenshot of my Kindle.
Conclusion: is posible to have raised cap for the .kf8 format. Of course, that will take a bit of time (more than if you could work only with css), but YOU CAN DO IT 
Regards
Rubén |
Rubén:
Her difficulty lies with the fact that she would have picked an image--a Cap--based on her desired, embedded font, generally speaking. A Raised Initial that goes with, say...Open Sans, just for giggles, won't look very spiffy with Times New Roman, or, say, Trebuchet. So, she has two challenges, given her view on the Paperwhite--how to get people to make the extra effort to see the font she wants them to see, and ensuring that her Raised Initial "matches" whatever font they select. It wouldn't be that simple to find an elegant Raised Initial to match all possible Paperwhite fonts.
This is why--as elegant and lovely as your solution is--using an actual letter works better, in the sense that you don't have to worry that your imaged Raised Initial matches ALL the possible fonts. THAT is the "issue."
See what I mean? Your solution really is quite nice, don't misunderstand me. It's just a bit of a challenge when she has no control over the PPW. On the other devices, she can reasonably expect the user to see her embedded fonts. Not so on the Paperwhite. It's a challenge that affects us all. Her real answer is simply to live with the leading, like everyone else does.
Hitch