Quote:
Originally Posted by Turtle91
I understand the dangers of assuming people have common sense...lol
However, if it specifically allows you to use the font in the creation of an ebook:
Then it follows that such embedding, along with obfuscation and/or subsetting, etc., is an acknowledged process which is allowed. An end user would not be required to "move the font files themselves", they would be moving the ebook file and would not have access to the original, unprotected in some way, font file. I'm interpreting the word "themselves" here to mean "the font files", not an individual. When an individual is moving an ebook file it is a package, not an individual font file.
From what I gather - although I didn't see the actual question from the FAQ - someone asked the specific question about using those fonts in an ebook and were answered (I also assume it was from an Adobe employee) specifically that it was OK as long as they were embedded. This is supported by the section:
which would require the ebook creator to actually embed the font into the ebook file as part of their workflow (thus ensuring the protections afforded by the format) - not requiring the user/reader to access the font file separately. (no side loading)
Again, just my .02. I don't have a dog in this fight as I only use free fonts when I do decide to embed them.
|
Turtle, I admire your attempted dexterity with this, but the bottom line is that User is a defined Term. It's the customer that has the Adobe Subscription, NOT the end user.
https://www.adobe.com/legal/terms.html
And use of the word "embedded"--that's too ambiguous by far.
Legal documents don't stand alone, on a single paragraph or sentence. Sure, something can and often does, turn on a word--but each word, sentence and paragraph has to be read in the context of the rest of the document, by itself and with any and all incorporated other documents. An answer on an FAQ, by (presumably) an Employee of Adobe, may mean something--or it may not. The doctrine of Respondent Superior may not apply--or maybe it does. Without diving into it further, I can't say.
For that matter, the Additional Terms also says you can only use the Licensed Fonts as long as you have a subscription. I'd love to see the hair-splitting if Adobe decided that ALSO meant, inside an eBook! As in, you embed font X in February and cancel your subscription in April....after all, they flatly state (and mechanically, it's understandable) that you can't use their fonts on your website, once you cancel your subscription. Obviously, the server can't serve them then. But as I said, what's an eBook if not a portable website meant to continue to be usable without an internet connection?
You're hanging everything on this "move" concept. Because the workflow here is de-encrypt the fonts (I mean, anybody think about THAT one?
Removing the encryption that Adobe provided, to prevent exactly this????), in order to then reuse the font, redistribute the font, with the Media, in an embedded way. I mean, where's the common sense thinking around this?
If they meant you to embed them and that was the only requirement, why encrypt the goddamn fonts in the first blanking place?
Look folks can do their own research. But User <> end user. It's the person who licensed the font in the first place and Adobe's TOU and T&C make that very clear.
Hitch