Thread: Embedding Adobe Fonts into a Kindle title
View Single Post
Old 10-13-2021, 06:01 PM   #26
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by phillipgessert View Post
Oh, ok--so it seems the reason is that they aren't using Adobe's obfuscation anymore. That's what would've broken it on Kindle. It hadn't occurred to me that they were obfuscated and then de-obfuscated, for some reason.

From a technical perspective it makes sense, other than that I suppose it's worth noting that the process undid something Adobe wanted done with those fonts, so I would just make sure you read the EULA/terms on em real carefully.
Wait, Phillip:

"They" whom? Who are the "they" that aren't using Adobe's obfuscation any longer? I wonder when the hell that happened. You mean InDD? No, that doesn't make sense, that's nuts, they're both Adobe products.

Who? And I wonder when the hell this happened?

Oh and OH YES, given that Adobe was the plaintiff in the infamous Adobe Systems, Inc. v. Southern Software, Inc. case, I'd be exceedingly careful, indeed.

Hitch
Last edited by Hitch; 10-13-2021 at 06:03 PM. Reason: ETA about font embedding and obfuscation, licensing, etc.
Hitch is offline   Reply With Quote