Quote:
Originally Posted by Jellby
It's very easy to turn a workflow that "requires" a user to "move the font files" into a workflow that does not "require" that. Just create a script/shortcut/whatever, so the user can simply "run something" instead of "move the font files". And the user does not even need to use it: as long as it's available, they are not "required" to "move the font files", although they may choose to do so.
|
Yabbut, Jellby, my sweet:
You're thinking MR readers. Not people getting the file from Amazon or B&N or Apple or Bob's Big Bookstore, after it's been processed in those places, too.
Isn't that correct, or are you thinking something self-extracting...nah, we'd never get it past KDP.
NEVAH.
Turtle, when you said:
Quote:
When I read that statement above, that Hitch quoted, I can see it meaning something different. Let me re-phrase the quote:
"Any ebook authoring workflow which would require your user to move the font files themselves is not allowed under the Terms of Use, however." ie "The font file must be embedded in the eBook which is produced with your workflow. You can not require the user (reader, customer) to get the font file from a separate location and side-load it, or somesuch."
|
I am not a lawyer. However, I ran the Litigation Strategy Division of a significant Real Estate Development corporation for decades, creating, reading and annotating, approving, legal documents of all kinds. I even wrote 300-page long CC&Rs and I've been reading this sh*t for a long-ass time. I can absolutely, positively tell you that when they say USER, they mean the licensee of the ACF (Adobe Cloud Fonts), not the end buyer.
I mean, let's take a similar example--you can use ACF for a website that you're making for John Doe, customer, right--except, John has to ALSO license the ACF to use on his site. You can't just make the site, plop the fonts in there and Bob's yer uncle. 3.3: "Publishers on whose behalf you create Websites must subscribe to the Service directly for access to the Licensed Content. You may NOT host the Web Fonts or Web Projects for the Publisher or resell the service to them."
Howzzat so different than an eBook? What's an eBook, other than a standalone website that works when not connected to the web? If anything, the eBook use case is worse, because the fonts have to be packaged with the eBook, not "grabbed" from a server on the fly (like so many web fonts and yup, I'm looking at YOU Google Fonts!).
Hitch