Quote:
Originally Posted by AlanHK
It was just an aside. I know some things go screwy on conversion, but this seemed simple enough.
If it was necessary, I'd make sure.
(The only thing that I'd have to fix are pagebreaks, since a straight conversion didn't respect the "display: inline-block" styling. So I guess I'd put in hard pagebreaks before the sections that need to be continuous.)
You mean that embedded fonts still work? That seems sensible enough.
Actually recently I made a ebook for a publisher who was very specific that it use the same font as the print edition. So of course I embedded them. There'd be hell to pay if that ended up in a default font.
But in this book I didn't specify a font beyond "'pre" implying a monospaced font. Surely that has to work.
|
No. I mean that all fonts, whether embedded or called from the firmware (e.g., device fonts) are being stripped. This doesn't affect books that have already been through the process; only new ones. If your client's book is up and selling, s/he is fine.
All the usual ways of creating MOBIs, with fonts, are currently not working. One of our closest competitors called me today, looking for a way to get monospaced to work.
Hitch