Quote:
Originally Posted by pdurrant
[EDIT: I misunderstood]
Seriously - ePub Font obfuscation is a standard (well, two actually - Adobe's and the IDPF's). Any PC-based ePub reading program will automatically handled obfuscated fonts.
If you've tried it and it doesn't work, the ePub isn't using standard obfuscation, and so there won't be any tools to help. Not that there are likely to be such tools readily available for obvious reasons.
|
Yes, I wish that there were! I recently went through all sorts of gyrations to determine the name of a font that I found in a given eBook. (It was a mobi, as it happens). I finally downloaded the MOBI to my K4PC and er...
took a look under the hood.
ALAS, inside the mobi were simply "font001, font002," etc. I couldn't even be sure which was which. I tried to view the font001, etc., files, but, more alas, I couldn't do so. I had to infer the name of the font from the CSS, and of course,
anybody could name
any font
anything, in their own CSS.
Amazon uses their own obfuscation as well, and I suspect that the font was subset and encrypted in INDD, before being exported to ePUB from whence the MOBI was made (as it's a Random House book). So, I was triple-screwed, dang it.
I wish there were a way to de-encrypt and display fonts, for those times when I decide I just "gotta have that," (and thus need the name), but the truth is, if that existed, people would abuse the holy hell out of it and steal fonts. No point in arguing it, we all know it's true. Sad--but true.
Hitch