Quote:
Originally Posted by JSWolf
I find that if I use ePUBOptimizer to reduce the size of TTF fonts, I can still get a little bit more by using Calibre after that to subset. It works better than either one on it's own. Also ePUBOptimizer optimizes images to be smaller without changing the resolution or quality. Try it, it will work rather well and it will make your book that much better. I have to say that hate is a good word in describing authors (who make their own eBook) and publishers who use graphics instead of an embedded font for some characters. This is a serious no-no and should never be done. You did it and I now hate your eBook.
|
Jon, mon sweetie curmudgeon:
Now, now. I have done this MANY times, when there is no choice. It's all well and good to blithely state that one should never embed an image instead of a font--but you are ignoring that many of us are making books that will be read on Kindle devices/readers, in addition to ePUB. Were I solely building ePUBs, I would never use an image instead of a font, but if you're building for Kindle, at the very least, you're stuck using an image for KF7. And the're brutes to do halfway decently, inline, mind you.
Don't assume that the people doing it are lazy. WE are not. We do it because we don't have a viable alternative. Or, hell, even an non-viable alternative.
@AlanHK: is your client sideloading the AZK to their iPad Kindle reader? or is s/he loading the MOBI file to their iPad? And, do you know what generation iPad s/he has?
Hitch