Quote:
Originally Posted by KevinH
Yes, this is known bug just reported a few days back by BeckyEbook now fixed in master.
FWIW, keeping fonts obfuscated works just fine that were obfuscated on input. And keeping fonts unobfuscated works as well.
But changing to or from obfuscation does not appear to overwrite any existing encryption.xml contents so any newly added fonts are not properly handled.
This was fixed in master by this change:
https://github.com/Sigil-Ebook/Sigil...e6f93ca9270ff0
The only workaround is to keep everything unobfuscated at the start (no META-INF/encryption.xml exists on import) and only obfuscate right before the final save.
Sorry. Font subsetting has basically removed the need for obfuscation for most users so this code has not been heavily tested of late.
If you need a Windows or Mac build with this fix in place, just let me know and I can post one for you based on current master which has very few other changes since Sigil-1.9.2.
|
If you could post the Windows build, it would be appreciated. I haven't had to encrypt fonts very often since most sites seem to accept subsetting or just don't care but the author of the book I was cleaning up informed me that one site she was going to use would not accept embedded fonts that were not encrypted.