The bug is epubcheck throwing an exception, not that obfuscation is correctly used on other resources in 3.0 spec. Perhaps this is part of 3.2 spec? The silly thing, if you do not compress that resource and instead pad it with a 1040 byte xml comment at the top, you will have achieved nothing in the form of "protection".
DRM to protect files I understand, but obfuscation here (non-font) is not something all mainstream readers are going to grok so you lose readers and gain no real protection.
|