Quote:
Originally Posted by charleski
This has been discussed a while ago on the epub forum. inDesign obfuscates the fonts (there's no real encryption) in order to dissuade people from removing them from the epub. It inserts an encryption.xml to signal this fact.
|
I'm aware of the fact that InDesign can do this, I just wasn't aware that it did it
by default.
Quote:
Originally Posted by charleski
This is not the problem, since some font licences require obfuscation.
|
This is debatable. It is
thought that obfuscating a font in the Adobe or IDPF method is enough to placate the foundries, but I've yet to see someone from the foundries confirm that.
Quote:
Originally Posted by charleski
The real problem is that the epub standard specifies a different obfuscation scheme to that used by Adobe (though frankly this is another area in which the standard is just a result of silly political manoeuvring, since they didn't want to adopt the system already developed by Adobe).
|
Yes, the IDPF specifies
one method and Adobe uses
another.
Quote:
Originally Posted by charleski
The solution is exactly as I stated: don't embed fonts from inDesign and you won't get the encryption file.
|
You weren't as specific the first time. You just said that the solution was to "not embed the fonts", and not that it was to "not embed the fonts with InDesign". The first one implies a problem with Sigil, and the second one a problem with InDesign.
I was a bit touchy since you appeared to be the third person today to imply that Sigil has problems with embedded fonts, when the root cause is InDesign being brain-dead.
Quote:
Originally Posted by HarryT
A font may be legally embeddable, but not redistributable. I imagine that is why InDesign is encrypting embedded fonts. What can be done other than encryption to prevent a user from simply copying a font out of an ePub file?
|
Take a look at the methods I linked to above. A twelve-year-old could write a program to de-obfuscate the fonts that were obfuscated with either method... in about 10 minutes. And the program would only be a few lines of code.
In fact, that's just what I'm about to add to Sigil. A Book Browser right-click context menu for fonts that enable the user to obfuscate or de-obfuscate the font with either method. By default, whatever state the font was in when the epub was opened will be the state in which it will be saved.