Quote:
Originally Posted by Monaghan
Just so that you do not misunderstand, I posted this thread because I want to be careful about not breaking any licence terms by embedding a font incorrectly. That was the entire point of my post.
|
I'd have to review their font licensing terms. I suspect that removing the encryption or obfuscation MIGHT, repeat, MIGHT violate their TOU, but again, I haven't looked in dog's years, because my attitude has been, if they wanted us to embed the entire font file in a bloody eBook, they wouldn't be encrypting it in the first place. I could absolutely be wrong about that.
Quote:
|
So this is incorrect? Subsetting, along with Amazon's encryption, is not enough to keep within the licence terms?
|
There's a difference between what's legit, what's legal and what violates TOU. At this precise moment, I have to look for the TOU and see what it actually SAYS.
Please note that that answer you're citing says "Adobe PURCHASED fonts." Not Cloud fonts.
EDITED TO ADD:
(This is the stuff I read, a few years back, when I first dug into this, vis: INDD and packages; I downloaded and reviewed the latest versions and they haven't changed really):
I reviewed the Adobe site, about font licensing for CC, Typekit-included fonts (all cloud fonts rather than licensed/bought fonts), and it says:
"Yes. The fonts are licensed for embedding in any ebook format which protects the font data such as EPUB, iBooks, Kindle (mobi), Adobe’s Digital Publishing Suite (DPS), and PDF."
Which is great. But THEN, it goes on to say:
"Any ebook authoring workflow which requires the user to move the font files themselves is not allowed under the Terms of Use, however."
Now, color me stoopid, but I'm 99% sure that removing the encryption or obfuscation, and then embedding the entire font file, etc. probably violates that provision.
I reviewed their "Adobe Additional Terms" document (incorporated by reference into their TOU; the link for the PDF is:
https://www.adobe.com/go/adobe-fonts-terms [downloads automagically, so don't be surprised]). I want to disclaim here: I am NOT AN ATTORNEY and I don't play one on TV. In what I read, you are skating dangerously close, by removing the Adobe-provided Obfuscation or encryption and then subsetting it. (n.b.: yes, yes, I concur that subsetting a font should protect it adequately. I'm talking hair-splitting the way that lawyers hair-split here.)
I mean, forgetting all the tech twisty, there are two provisions that give me the Heebie-Jeebies:
Under section "3.4(E) Prohibited Uses of the Licensed Content" it has various provisions that are not clear. Sections (2), (5), (7), (8), and honestly, maybe (4), too.
I mean, for crying out loud, you're not allowed to package or share the fonts, with service bureau designers or printers. But you can manipulate them to include them in an eBook that's being redistributed around the globe?
My advice is, ask a real lawyer to whom you pay real money, who has a speciality in Internet IP. I ran the Litigation Strategy Division of a large Real Estate Development firm, for a few decades, running the legal teams and reviewing and approving all the documents for both friendly acquisitions and not-so-friendly cases and it's my opinion that removing the obfuscation MIGHT be treading a path that Adobe would not look kindly upon. All the stuff we've seen so far seems to indicate that purchased fonts are viewed by them very, very differently than Cloud fonts.
The reason for that is liability--once you purchase a font, your agreement is effectively with the foundry, and Adobe can wash their hands of it. But, if you use a Cloud font, that Adobe licensed to you, from Foundry X, and then Foundry X learns that it's being used inside an eBook, when the font was licensed for (say) Desktop Publishing alone and not licensed for eBook or redistribution...the foundry would likely sue Adobe, not you. Now, again, I can't say this loudly enough: I am not an attorney and you should not pay attention to me.
That's my $.02 and worth less than that by far.
Hitch