Quote:
Originally Posted by Hitch
You said, a few posts back:
So, naturally, I assumed that you did intend to do a mobi. If you're not, fine. And if you're happy with the result, great.
|
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.)
Quote:
Originally Posted by Hitch
You may run into issues at the KDP, if you were going to upload at Amazon, as it's taken to stripping ALL fonts, font-calls (rather than embedded fonts, even stuff like "monospaced") from mobis, for the last few weeks, but if yours is working, good!
Hitch
|
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.