Answers.Body: <p>I don't disagree with the above answer. </p>
  
  <p>I just wanted to say that on the Title/Credits HTML page (which contains copyright, date, etc) I included this line: </p>
  
  <p>The HomemadeApple Font embedded in this ebook is copyrighted 2010 by Font Diner, Inc. under a Apache 2.0 license.  (and I linked to the license). </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-07T00:57:10.430Z
Answers.LastActivityDate: 2016-03-07T00:57:10.430Z
Answers.UserDisplayName: idiotprogrammer
Answers.Body: <p>As the license requirements state "easily viewed by the user" you should include the full license in the EPUB zip files META-INF directory as e.g. <code>open_font_license.txt</code>, in addition to that add a stanza:</p>
  
  <pre><code> &lt;dc:license&gt;Open Font Software distributed as per open_font_license.txt&lt;/dc:license&gt;
  </code></pre>
  
  <p>to the <code>META-INF/metadata.opf</code> file.</p>
  
  <p>The latter should show up when viewing the metadata info in EPUB readers. If
  the copyright text is short, you can forego the <code>open_font_license.txt</code> file and directly include everything in the <code>metadata.opf</code> stanza.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-06T19:12:57.447Z
Answers.Text: Does it need to be `META-INF/metadata.opf`? I am using Sigil to build my ebook and it doesn't have a `metadata.opf` in `META-INF`. But there is `OEBPS/content.opf`which contains a `<metadata>` tag and in it are elements like `<dc:language>en</dc:language>`. Could I place it there?
Answers.UserDisplayName: Keavon
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-06T20:29:41.620Z
Answers.Text: @Keavon Probably yes. Make sure to check afterwards in an epub viewer (e.g. the one from Calibre) that the information shows up when you click "Show book metadata")
Answers.UserDisplayName: Anthon
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-06T09:48:02.470Z
Answers.LastActivityDate: 2016-03-06T09:48:02.470Z
Answers.UserDisplayName: Anthon
Answers.Body: <p>As I had not seen this question, I have asked <a href="https://opensource.stackexchange.com/q/2844/5047">another one</a> very similar somewhere else.</p>
  
  <p>I have tested the solution proposed by Anthon, but the addition of a <code>&lt;dc:license&gt;</code> element into the <code>content.opf</code> is unfortunaltely pointed as an error when checking the file with Sigil and FlightCrew:</p>
  
  <blockquote>
    <p>Error XML child not recognized: the <code>&lt;licence&gt;</code> element is not an allowed child of the <code>&lt;metadata&gt;</code> element </p>
  </blockquote>
  
  <p>Consequently, I opted for <a href="https://opensource.stackexchange.com/a/2859/5047">an alternate method</a> for embedding such a license file, by creating an <code>ofl.xhtml</code> file using the <code>copyright-page</code> guide element.</p>
  
  <p>This method has also the advantage to grant an easy access to the license text (especially if a specific line is added in the <code>title.xhtml</code>, as pointed by idiotprogrammer)</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-13T07:05:37.657Z
Answers.LastActivityDate: 2016-05-13T07:05:37.657Z
Answers.LastEditDate: 2017-04-13T13:00:32.060Z
Answers.UserDisplayName: P. Mergey
Body: <p>I am using a font that is licensed under the Open Font License which states:</p>
  
  <blockquote>
    <p>2) Original or Modified Versions of the Font Software may be bundled,
    redistributed and/or sold with any software, provided that each copy
    contains the above copyright notice and this license. These can be
    included either as stand-alone text files, human-readable headers or
    in the appropriate machine-readable metadata fields within text or
    binary files as long as those fields can be easily viewed by the user.</p>
  </blockquote>
  
  <p>Where can I place this license file in my EPUB where it complies with the license requirements?</p>
  
Tags: <epub><fonts><license>
Title: Where should font licenses be embedded?
UserDisplayName: Keavon
ThreadText: # Where should font licenses be embedded?
  
  (Asked by: username_0 on 2016-03-06)
  
  I am using a font that is licensed under the Open Font License which states:
  
  > 2) Original or Modified Versions of the Font Software may be bundled,
  > redistributed and/or sold with any software, provided that each copy
  > contains the above copyright notice and this license. These can be
  > included either as stand-alone text files, human-readable headers or
  > in the appropriate machine-readable metadata fields within text or
  > binary files as long as those fields can be easily viewed by the user.
  
  Where can I place this license file in my EPUB where it complies with the license requirements?
  
  **Tags:** epub, fonts, license
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_1 on 2016-03-07. Score: 6 | Accepted answer
  
  I don't disagree with the above answer.
  
  I just wanted to say that on the Title/Credits HTML page (which contains copyright, date, etc) I included this line:
  
  The HomemadeApple Font embedded in this ebook is copyrighted 2010 by Font Diner, Inc. under a Apache 2.0 license. (and I linked to the license).
  
  
  ---
  
  ### Answer by username_2 on 2016-03-06. Score: 2
  
  As the license requirements state "easily viewed by the user" you should include the full license in the EPUB zip files META-INF directory as e.g. open_font_license.txt, in addition to that add a stanza:
   Open Font Software distributed as per open_font_license.txt
  
  to the META-INF/metadata.opf file.
  The latter should show up when viewing the metadata info in EPUB readers. If
  the copyright text is short, you can forego the open_font_license.txt file and directly include everything in the metadata.opf stanza.
  
  > **Comments:**
  > **username_0**: Does it need to be `META-INF/metadata.opf`? I am using Sigil to build my ebook and it doesn't have a `metadata.opf` in `META-INF`. But there is `OEBPS/content.opf`which contains a `<metadata>` tag and in it are elements like `<dc:language>en</dc:language>`. Could I place it there?  
  > **username_2**: @username_0 Probably yes. Make sure to check afterwards in an epub viewer (e.g. the one from Calibre) that the information shows up when you click "Show book metadata")  
  
  ---
  
  ### Answer by username_3 on 2016-05-13. Score: 1
  
  As I had not seen this question, I have asked [another one](https://opensource.stackexchange.com/q/2844/5047) very similar somewhere else.
  
  I have tested the solution proposed by username_2, but the addition of a  element into the `content.opf` is unfortunaltely pointed as an error when checking the file with Sigil and FlightCrew:
  
  > Error XML child not recognized: the  element is not an allowed child of the  element
  
  Consequently, I opted for [an alternate method](https://opensource.stackexchange.com/a/2859/5047) for embedding such a license file, by creating an `ofl.xhtml` file using the `copyright-page` guide element.
  
  This method has also the advantage to grant an easy access to the license text (especially if a specific line is added in the `title.xhtml`, as pointed by username_1)
  
  
  ---
  
  