Quote:
Originally Posted by DiapDealer
I've never understood why InDesign can't be configured to NOT encrypt fonts when exporting to EPUB. You can't submit epubs with obfuscated fonts to Amazon. They will fail. There's also no need to obfuscate fonts if the epub is not being disseminated. Can InDesign not be configured to use fonts that don't need to be obfuscated?
|
In my opinion, it's simply because of course, Adobe is moving everyone as hard as they can to cloud fonts. They've been at it for ages now and of course, they want those obfuscated. I
honestly don't think it's a whole lot more complicated than that.
Quote:
|
As for Sigil... it is the opinion of its maintainers that font-obfuscation is a form of decryption. And while we're happy to give users the ability to make a conscious decision to decrypt (or encrypt) fonts in their epubs on a case by case basis, we're not comfortable giving them the ability to configure Sigil to automatically decrypt any encrypted fonts it might encounter. It's a decision users SHOULD have to think about. It's not a trivial thing. It shouldn't be a "set it and forget it" sort of thing. In my opinion, that's the mistake InDesign has made in this regard. Just in the opposite direction.
|
Yes, FWIW, I agree with you. Choosing to use a font, in a method for which is is unlicensed (for example, using, say, Avenir Next in an ePUB without paying a few thou), should be a conscious decision. The fines or legal issues around it could be onerous. And then some!
Hitch