View Single Post
Old 09-08-2019, 05:00 PM   #9
pdurrant
The Grand Mouse 高貴的老鼠
pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.
 
pdurrant's Avatar
 
Posts: 74,082
Karma: 315558332
Join Date: Jul 2007
Location: Norfolk, England
Device: Kindle Oasis
Quote:
Originally Posted by AliceWonder View Post
Tested the obfuscation script and fixed a bad bug - when I read the ePub obfuscation specification, I read that the first 1024 bytes get obfuscated but its actually the first 1040 - my eyes, when they get tired, they fill in the blanks and sometimes not correctly.

But that is fixed and I tested it with several different readers.

Interestingly when I obfuscate an SVG file - it works but ePubCheck plugin in Calibre does not run. It exits w/o giving a report. The ePub files work just fine. I tested by obfuscating SVG first just to make sure broken fonts weren't being replaced by same fonts from my system.

When I obfuscate fonts (what obfuscation is intended for) ePubCheck plugin with Calibre works as expected.
Note that there are two versions of font obfuscation in ePubs. The one Adobe used, and the one the IDPF adopted. I can't remember which way round they are, but that's the reaosn for the 1024/1040 difference.
pdurrant is offline   Reply With Quote