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:
Quote:
|
"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."
|
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:
Quote:
|
"Any ebook authoring workflow which requires the user to move the font files themselves is not allowed under the Terms of Use, however."
|
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.