Quote:
Originally Posted by jcsalomon
Here’s a screwy thought, but one I’ve not seen mentioned in this thread: is it possible that the failing font’s permission bits are set to prohibit embedding (this can be different from what the human-readable font license says is permissible), and something in Amazon’s process catches this and removes such fonts?
(Probably not, I’m sure; this would mean some fonts fail consistently while others work, and the difference would have been noticed by now.)
|
Caveat: I don't factually know the answer to this question--they've danced around answering it often--and I don't speak for the Zon.
I don't think that's it. I really don't. There was a guy on the KDP who had to be The GUY, you know, and he pontificated (as though this was simply FACT) that this was the reason why Arial didn't work--that the Zon deliberately disabled it because it "belonged to Microsoft."
Now, that's all well and good, if you don't take into account the fact that we, and others, have embedded Arial for this or that
for years now. I will say, however, that it's also true that
there is something quite hinky about Arial. It seems to have limits, in how MUCH it can be used in a KBook. Damned if I know the why. It's peculiar as hell.
AND, hell, if anything was going to be un-embeddable, due to licensing rights, or lack thereof, you'd think it would be Adobe fonts, right? And we've embedded them all over the place.
How would the Zon know, for example, whether I licensed Font X, or not? Anybody can type in some type of BS "dun bin licensed, y'all" statement. So...I can't see that as it. On the other hand, would I bet my life savings against that being true? Hells, no.
Quote:
Originally Posted by JSWolf
Why does Amazon remove embedded fonts? Is it because they have a thing for Bookerly?
|
Nyah. Hell, they were doing this long before Bookerly came to live on our Kindles. I do NOT know the reasons. I expected, when we got to the third set of tests mentioned above, that they were going to tell us to NOT embed fonts--and lo, I was wrong. They absolutely wanted the publisher's fonts, AND, it would have been a fail had we not done so, or not been able to get them to work. You see the post from...I think it was Quiris, above? Didn't s/he use the Stealth Attack CSS in a book, a few months back, and yet it still was stripped?
Murky waters we are swimmin' in now, indeed.
Update: NO update from the client. Last tested sample download was still missing fonts. <(*&^%$#@!>
Hitch