Quote:
Originally Posted by Freeshadow
Hm if you say 10 days... To change that behavior without notice would indeed be awkward. Y
A test run would be to take 1 whatever file you have properly licensed (that has the permission embedding bit unset) and make a minimal test mobi. Does some of your font previewers show the permissions?
|
No. (showing permissions). All of the previewers, Kindle Previewer desktop and Kindle Previewer Online, display fonts when they are embedded AND have made it past whatever dragons are lurking. The desktop version shows us what we've done, BEFORE the file is uploaded at the KDP. The one at the KDP shows us/confirms that our fonts have survived the upload--at least, until Thursday, that was so. I still do NOT have feedback from the client's client, so ...???
Quote:
|
PS I hope you cash customers extra if they want to profit from your own collection of licensed fonts.
|
Mea culpa. I did not explain adequately. I most certainly
do NOT lend out my licensed fonts to clients--and it wouldn't be legit if I did. Each font that is used
in an eBook has to be licensed for that book, under whatever licensing strictures exist. What I meant was, if we have, say, 10 clients that will be using (for the purposes solely of the example) Garamond, we license that 10x, but I don't bloody download it 10x, I use the AGaramond faces I have here. Oherwise, my directories would like like bunnies in love--mass overpopulation without suitable predators to reduce the herd. Naturally, if the client "buys" the font, they can download it for their own purposes, assuming that they bought that license, as well, from the font shop in which it's been purchased.
Obviously, for print, if we have the font licensed for commercial use and desktop publishing, no further licensing by the client is required. BUT, if they then want to use the same for the eBook, we either do the licensing, OR, we find them a free-for-eBook-use replacement font. Or, hell, we use the defaults.
Quote:
Originally Posted by JSWolf
Do you tell the client if the fonts used are not good for eInk screens? I strip out Garamond if it's used because it's not good for eInk.
|
GOD, YES.
Of course we tell them. I have one bookmaker that kicks against using ye olden Garamond for print, because the eBook aspect is so dire, but I'm rather partial to it for DTB. Most of my in-house designs use it, to emulate layout for clients. So...<shrug>, good for print, bad for E, unless it's already ON the device.
Of course--trying to get MOBI embedded fonts (on K devices, folks, let's not go all Calibre here) to play nicely with firmware fonts, not so simple.
Hitch