Quote:
Originally Posted by jcsalomon
I’ve included the font’s License.txt in the Misc folder (following Sigil’s convention; if you’re using another tool you might keep it in the Fonts directory). Excerpt from content.opf:
Code:
<manifest>
…
<item id="RM-Ginger.ttf" href="Fonts/RM-Ginger.ttf" media-type="application/vnd.ms-opentype"/>
<item id="RM-Ginger-License.txt" href="Misc/RM-Ginger-License.txt" media-type="text/plain"/>
<item id="RM-Ginger-Readme.txt" href="Misc/RM-Ginger-Readme.txt" media-type="text/plain"/>
…
</manifest>
The Readme and License files are not in the <spine> at all, and are not linked to in the book, but if someone unzips the EPUB file to get at the font, my responsibilities under the redistribution license are satisfied.
If you want to (or if the font’s license requires you to) do more, you might include a colophon somewhere, perhaps something like—
Chapter headings have been set with Super Cool Font, <url here>, © 2010 Ty Pographer. For license terms click here.
—with “here” being a link to that information, formatted as you will.
(In my particular case, I’ve included similar language but without linking to the license terms.) |
Y'know, I did that, with a font that a client just could NOT let go of; he would not accept a "close" substitute, etc. Man, they went apes**t over the colophon, which I put as (traditionally) the very last page. You'd think I'd put in some pamphlet going on and on about fonts in general, or the like. Last time I tried it. Now, I just do what you've done--put a .txt file in the misc, don't list it, etc.
@IronChaim: indeed, many don't support encryption or ofuscation, but they ALL "support" subsetting.
Easiest and absolutely effective way to prevent font copyright infringement.
Hitch