Quote:
Originally Posted by KevinH
One other question:
How should embedded fonts be handled if saving to a folder or reading from a folder when it comes to obfuscating the fonts.
<snippety-snip-snip-snip>
What would be the best approach?
|
Hi:
I can't speak for anyone else, but we never use the built-in obfuscation, simply because it renders (ha!) the ePUB unusable for our clients. We can't upload them at B&N, iBooks, KoboBooks, GooglePlay, and we can't build MOBIs from them. We subset fonts instead, which is, for all intents and purposes and legalities, the equivalent.
I would urge a move away from trying to make the obfuscation "your" problem, leaving it instead to the bookmaker to take the extra care, if they decide to work as you've described, tweaking the file/OPF/fonts after the fonts have been obfuscated (which, even with subsetting, is always a problem).
I don't see a reasonably safe or simple way that you can solve that--the moment you tweak content, you wreak havoc, potentially, with the obfuscation OR subsetting. This is on the bookmaker, not the software. It should always be the truly-last thing you do, for obvious reasons, and if a client comes back with more edits--and whose don't?--you just slap the entire font file in, make the changes and either obfuscate or subset again. How else, realistically, can it be done, if you think about the mechanics?
Hitch