Quote:
Originally Posted by pdurrant
Although in practise, this is a silly fear. It might have been valid once, when computer fonts first came in back in 1987 and digital distribution was harder. In 2012, when if you want a font without paying for it there are numerous pirate sites and torrents, worrying about your fonts being embedded in documents is silly.
Just like publishers and DRM, really.
|
It may be silly, but the reality is that those of us who make ebooks commercially have to live with it. I'm all for embedding subsets if it can be done without a lot of gyrations. I use disclaimers (e.g., "we assume that if you're giving us a font file, you've properly licensed it," etc.) but I do worry, given what's happened with cases of image licensing infringements, etc., that someday I'll have Adobe on my doorstep because some doofus didn't properly license one of their fonts. My alternative is to run out and do the licensing myself, and charge the client, but quite bluntly, that starts to get on my nerves for a variety of reasons, which aren't relevant to this discussion.
Is any of this moving forward? Or did the discussion that Calibre might do it or be made to do it kill the momentum? We don't use Calibre for production--although I adore it for our cataloging--so I'd be interested in this. Can someone advise, if they're actively working on it? I can't code for beans (in Python or whatever), but if I could assist some other way...?
Hitch