CINXE.COM
OFL-FAQ
<!doctype html><html lang=en><head><meta charset=utf-8><title>OFL-FAQ</title> <meta name=viewport content="width=device-width,initial-scale=1"><meta name=generator content="Hugo 0.120.4"><meta name=description content="SIL Open Font License"><link rel=stylesheet href=https://openfontlicense.org/plugins/bootstrap/bootstrap.min.css><link rel=stylesheet href=https://openfontlicense.org/plugins/themify-icons/themify-icons.css><link rel=icon href=../images/favicon.png type=image/x-icon><link rel=preconnect href=https://fonts.googleapis.com><link rel=preconnect href=https://fonts.gstatic.com crossorigin><link href="https://fonts.googleapis.com/css2?family=Merriweather:ital,wght@0,400;0,700;1,400;1,700&display=swap" rel=stylesheet><script src=https://cdnjs.cloudflare.com/ajax/libs/pdf.js/2.9.359/pdf.min.js></script><script src=https://cdnjs.cloudflare.com/ajax/libs/html2pdf.js/0.9.3/html2pdf.bundle.js></script><style>:root{--primary-color:#005CB9;--secondary-color:#00A7E1;--body-color:#f9f9f9;--text-color:#111111;--text-color-dark:#000000;--text-color-light:#333333;--white-color:#ffffff;--light-color:#00A7E1;--primary-light-color:#89A8CC;--secondary-light-color:#97DAF5;--font-family:Merriweather}</style><link href=https://openfontlicense.org/css/style.min.css rel=stylesheet media=screen><script src=https://openfontlicense.org/plugins/jquery/jquery-1.12.4.js></script><script src=https://openfontlicense.org/plugins/jquery/jquery-ui.js></script><script src=https://openfontlicense.org/plugins/bootstrap/bootstrap.min.js></script><script src=https://openfontlicense.org/plugins/match-height/jquery.matchHeight-min.js></script><meta property="og:image" content="https://openfontlicense.org/images/OFL23-Bluebig.png"><meta name=twitter:image content="https://openfontlicense.org/images/OFL23-Bluebig.png"><meta name=twitter:card content="summary"><meta property="og:image:width" content="512"><meta property="og:image:height" content="512"><meta property="og:image:type" content="image/png"><meta name=twitter:title content="OFL-FAQ"><meta name=twitter:description content="The website of the SIL Open Font License"><meta property="og:title" content="OFL-FAQ"><meta property="og:description" content="The website of the SIL Open Font License"><meta property="og:type" content="website"><meta property="og:url" content="https://openfontlicense.org/ofl-faq/"><meta name=twitter:card content="summary"><meta name=twitter:title content="OFL-FAQ"><meta name=twitter:description content="The website of the SIL Open Font License"></head><body><header class="banner overlay bg-cover" data-background=https://openfontlicense.org/images/Blue-Glyph-Pattern.png><nav class="navbar navbar-expand-md navbar-light"><div class="container px-2 px-md-0"><a class="navbar-brand px-2" href=../><img class=img-fluid src=https://openfontlicense.org/images/OFL23-Bluef32alt.png alt="SIL Open Font License"> SIL Open Font License </a><button class="navbar-toggler border-0" type=button data-toggle=collapse data-target=#navigation aria-controls=navigation aria-expanded=false aria-label="Toggle navigation"> <span class=navbar-toggler-icon></span></button><div class="collapse navbar-collapse text-center" id=navigation><ul class="navbar-nav ml-auto"><li class=nav-item><a class="nav-link text-dark" href=https://openfontlicense.org/open-font-license-official-text/>OFL Text</a></li><li class=nav-item><a class="nav-link text-dark" href=https://openfontlicense.org/how-to-use-the-ofl/>How</a></li><li class=nav-item><a class="nav-link text-dark" href=https://openfontlicense.org/why-use-the-ofl/>Why</a></li><li class=nav-item><a class="nav-link text-dark" href=https://openfontlicense.org/ofl-fonts/>Fonts</a></li><li class=nav-item><a class="nav-link text-dark" href=https://openfontlicense.org/history/>History</a></li></ul></div></div></nav></header><section class="single section-sm pt-3 pb-0"><div class=container><div class=row><div class=col-lg-12><div class="px-4 pt-3 pb-4 bg-white" id=content><i class="ti-direction-alt icon text-primary d-block mb-4"></i><h2 class="mb-4 text-primary" id=title>OFL-FAQ</h2><div class=content><p>Here is the latest (1.1-update7) collection of FAQ (Frequently Asked Questions) for the OFL. It is long but comprehensive. If you use the OFL, the time you spend reading through it will be well-spent. If you would prefer brief summaries of the most frequent questions on specific topics, see these pages:</p><ul><li><a href=../how-to-use-ofl-fonts>Using but not modifying OFL fonts</a></li><li><a href=../how-to-modify-ofl-fonts>Modifying and redistributing OFL fonts</a></li><li><a href=../how-to-apply-the-ofl>Applying the OFL to a font you’ve created.</a></li><li><a href=../ofl-reserved-font-names>Understanding and managing Reserved Font Names (RFNs)</a>.</li></ul><p><strong>You can also download the <a href=../documents/OFL-FAQ.txt>OFL-FAQ.txt version 1.1-update7 (plain text)</a>.</strong></p><p>The following questions and answers are color-coded to help make it easier to understand, but please do click on the question to reveal the answer and read through the details:</p><p><span class="faqlegend faqlegendgreen">Green</span> generally means yes. <span class="faqlegend faqlegendred">Red</span> generally means no. <span class="faqlegend faqlegendyellow">Yellow</span> means it depends on the situation. <span class="faqlegend faqlegendblue">Blue</span> means informational.</p><p> </p><h2 id=ofl-faq-version-11-update7-november-2023>OFL-FAQ version 1.1-update7 (November 2023)</h2><p><em>This document is Copyright © 2007–2023, SIL International (<a href=https://www.sil.org>https://www.sil.org</a>).<br>Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.</em></p><h3 id=1nbspnbspnbspusing-and-distributing-fonts-licensed-under-the-ofl>1 USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL</h3><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#4491f8b5ecc09d9de308ea37e6a23ad2dd66c256><span><em>1.1 Can I use the fonts for a book or other print publication, to create logos or other graphics or even to manufacture objects based on their outlines?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=4491f8b5ecc09d9de308ea37e6a23ad2dd66c256 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes. You are very welcome to do so. Authors of fonts released under the OFL allow you to use their font software as such for any kind of design work. No additional license or permission is required, unlike with some other licenses. Some examples of these uses are: logos, posters, business cards, stationery, video titling, signage, t-shirts, personalised fabric, 3D-printed/laser-cut shapes, sculptures, rubber stamps, cookie cutters and lead type.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#bd952513ae9dce3e914b4918eae08e1eddd37faa><span><em>1.1.1 Does that restrict the license or distribution of that artwork?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=bd952513ae9dce3e914b4918eae08e1eddd37faa class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No. You remain the author and copyright holder of that newly derived graphic or object. You are simply using an open font in the design process. It is only when you redistribute, bundle or modify the font itself that other conditions of the license have to be respected (see below for more details).</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#e3429934f4f3ac1c68dc8b2eef6c7df0aa7a7f9c><span><em>1.1.2 Is any kind of acknowledgement required?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=e3429934f4f3ac1c68dc8b2eef6c7df0aa7a7f9c class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No. Font authors may appreciate being mentioned in your artwork’s acknowledgements alongside the name of the font, possibly with a link to their website, but that is not required.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#8114b9dabe64741f5700c676da07d4182530a754><span><em>1.2 Can the fonts be included with Free/Libre and Open Source Software collections such as GNU/Linux and BSD distributions and repositories?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=8114b9dabe64741f5700c676da07d4182530a754 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes! Fonts licensed under the OFL can be freely included alongside other software under FLOSS (Free/Libre and Open Source Software) licenses. Since fonts are typically aggregated with, not merged into, existing software, there is little need to be concerned about incompatibility with existing software licenses. You may also repackage the fonts and the accompanying components in a .rpm or .deb package (or other similar package formats or installers) and include them in distribution CD/DVDs and online repositories. (Also see entry 5.9 about rebuilding from source.)</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#2afe7d50c10921ac0f9f899939231a737e7dc2b2><span><em>1.3 I want to distribute the fonts with my program, does this mean my program also has to be Free/Libre and Open Source Software?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=2afe7d50c10921ac0f9f899939231a737e7dc2b2 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No. Only the portions based on the Font Software are required to be released under the OFL. The intent of the license is to allow aggregation or bundling with software under restricted licensing as well.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#a26f83404b3689e9473b90563ae874b959b849ed><span><em>1.4 Can I sell a software package that includes these fonts?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=a26f83404b3689e9473b90563ae874b959b849ed class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes, you can do this with both the Original Version and a Modified Version of the fonts. Examples of bundling made possible by the OFL would include: text editors, word processors, design and publishing applications, training and educational software, games and entertainment software, mobile device applications, etc.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#aa8f289ebe6d4db1b4a1038b8931ec8c2b5399fb><span><em>1.5 Can I include the fonts on a CD of freeware or commercial fonts?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=aa8f289ebe6d4db1b4a1038b8931ec8c2b5399fb class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes, as long some other font or software is also on the disk, so the OFL font is not sold by itself.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#4693695d02f6236c431a6589af6dfdef6aa7fa31><span><em>1.6 Why won’t the OFL let me sell the fonts alone?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=4693695d02f6236c431a6589af6dfdef6aa7fa31 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">The intent is to keep people from making money by simply redistributing the fonts. The only people who ought to profit directly from the fonts should be the original authors, and those authors have kindly given up potential direct income to distribute their fonts under the OFL. Please honour and respect their contribution!</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#58e6d386c363c2665ea43e7a57f0a497da13416e><span><em>1.7 What about sharing OFL fonts with friends on a CD, DVD or USB stick?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=58e6d386c363c2665ea43e7a57f0a497da13416e class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">You are very welcome to share open fonts with friends, family and colleagues through removable media. Just remember to include the full font package, including any copyright notices and licensing information as available in OFL.txt. In the case where you sell the font, it has to come bundled with software.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#93ec1d5b0e5f86e667093d5857f65ca0fa9c557a><span><em>1.8 Can I host the fonts on a website for others to use?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=93ec1d5b0e5f86e667093d5857f65ca0fa9c557a class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes, as long as you make the full font package available. In most cases it may be best to point users to the main site that distributes the Original Version so they always get the most recent stable and complete version. See also discussion of webfonts in Section 2.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#936931368287d72a5bda62a8a3e0d2ed6638fa8f><span><em>1.9 Can I host the fonts on a server for use over our internal network?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=936931368287d72a5bda62a8a3e0d2ed6638fa8f class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes. If the fonts are transferred from the server to the client computer by means that allow them to be used even if the computer is no longer attached to the network, the full package (copyright notices, licensing information, etc.) should be included.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-warning p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Maybe, it depends on the situation 🤔" data-toggle=collapse href=#22a585885b5cb7cc58d60445ecf0d8ad6f76ef24><span><em>1.10 Does the full OFL license text always need to accompany the font?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=22a585885b5cb7cc58d60445ecf0d8ad6f76ef24 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">The only situation in which an OFL font can be distributed without the text of the OFL (either in a separate file or in font metadata), is when a font is embedded in a document or bundled within a program. In the case of metadata included within a font, it is legally sufficient to include only a link to the text of the OFL on <a href=https://openfontlicense.org>https://openfontlicense.org</a>, but we strongly recommend against this. Most modern font formats include metadata fields that will accept the full OFL text, and full inclusion increases the likelihood that users will understand and properly apply the license.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#14b46e8ec03c3008e57ed966a26b63495b68b9b7><span><em>1.11 What do you mean by ‘embedding’? How does that differ from other means of distribution?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=14b46e8ec03c3008e57ed966a26b63495b68b9b7 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">By ‘embedding’ we mean inclusion of the font in a document or file in a way that makes extraction (and redistribution) difficult or clearly discouraged. In many cases the names of embedded fonts might also not be obvious to those reading the document, the font data format might be altered, and only a subset of the font - only the glyphs required for the text - might be included. Any other means of delivering a font to another person is considered ‘distribution’, and needs to be accompanied by any copyright notices and licensing information available in OFL.txt.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#8dc5253966cff788bc78a0da8c1ec52e0bee16a8><span><em>1.12 So can I embed OFL fonts in my document?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=8dc5253966cff788bc78a0da8c1ec52e0bee16a8 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes, either in full or a subset. The restrictions regarding font modification and redistribution do not apply, as the font is not intended for use outside the document.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#e83d8b4ce4e1f6b2a7f7dfc5cd73b7fc2bb34b6e><span><em>1.13 Does embedding alter the license of the document itself?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=e83d8b4ce4e1f6b2a7f7dfc5cd73b7fc2bb34b6e class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No. Referencing or embedding an OFL font in any document does not change the license of the document itself. The requirement for fonts to remain under the OFL does not apply to any document created using the fonts and their derivatives. Similarly, creating any kind of graphic using a font under the OFL does not make the resulting artwork subject to the OFL.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#333d5e6322896ec8adbeda69bde705630fe78c01><span><em>1.14 If OFL fonts are extracted from a document in which they are embedded (such as a PDF file), what can be done with them? Is this a risk to author(s)?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=333d5e6322896ec8adbeda69bde705630fe78c01 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">The few utilities that can extract fonts embedded in a PDF will typically output limited amounts of outlines - not a complete font. To create a working font from this method is much more difficult and time consuming than finding the source of the original OFL font. So there is little chance that an OFL font would be extracted and redistributed inappropriately through this method. Even so, copyright laws address any misrepresentation of authorship. All Font Software released under the OFL and marked as such by the author(s) is intended to remain under this license regardless of the distribution method, and cannot be redistributed under any other license. We strongly discourage any font extraction - we recommend directly using the font sources instead - but if you extract font outlines from a document, please be considerate: respect the work of the author(s) and the licensing model.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#72f0fdd827431d15bd7445782d99c436ac588ee6><span><em>1.15 What about distributing fonts with a document? Within a compressed folder structure? Is it distribution, bundling or embedding?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=72f0fdd827431d15bd7445782d99c436ac588ee6 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Certain document formats may allow the inclusion of an unmodified font within their file structure which may consist of a compressed folder containing the various resources forming the document (such as pictures and thumbnails). Including fonts within such a structure is understood as being different from embedding but rather similar to bundling (or mere aggregation) which the license explicitly allows. In this case the font is conveyed unchanged whereas embedding a font usually transforms it from the original format. The OFL does not allow anyone to extract the font from such a structure to then redistribute it under another license. The explicit permission to redistribute and embed does not cancel the requirement for the Font Software to remain under the license chosen by its author(s). Even if the font travels inside the document as one of its assets, it should not lose its authorship information and licensing.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-warning p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Maybe, it depends on the situation 🤔" data-toggle=collapse href=#562e2573cf8f5627618ba69dc213ed93dff800b9><span><em>1.16 What about ebooks shipping with open fonts?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=562e2573cf8f5627618ba69dc213ed93dff800b9 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">The requirements differ depending on whether the fonts are linked, embedded or distributed (bundled or aggregated). Some ebook formats use web technologies to do font linking via @font-face, others are designed for font embedding, some use fonts distributed with the document or reading software, and a few rely solely on the fonts already present on the target system. The license requirements depend on the type of inclusion as discussed in 1.15.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#324bc7cb0b310e1ff557d69e2328525bd78df9ed><span><em>1.17 Can Font Software released under the OFL be subject to URL-based access restrictions methods or DRM (Digital Rights Management) mechanisms?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=324bc7cb0b310e1ff557d69e2328525bd78df9ed class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes, but these issues are out of scope for the OFL. The license itself neither encourages their use nor prohibits them since such mechanisms are not implemented in the components of the Font Software but through external software. Such restrictions are put in place for many different purposes corresponding to various usage scenarios. One common example is to limit potentially dangerous cross-site scripting attacks. However, in the spirit of libre/open fonts and unrestricted writing systems, we strongly encourage open sharing and reuse of OFL fonts, and the establishment of an environment where such restrictions are unnecessary. Note that whether you wish to use such mechanisms or you prefer not to, you must still abide by the rules set forth by the OFL when using fonts released by their authors under this license. Derivative fonts must be licensed under the OFL, even if they are part of a service for which you charge fees and/or for which access to source code is restricted. You may not sell the fonts on their own - they must be part of a larger software package, bundle or subscription plan. For example, even if the OFL font is distributed in a software package or via an online service using a DRM mechanism, the user would still have the right to extract that font, use, study, modify and redistribute it under the OFL.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#6ce245771a09227fe7eff01895554c005be8f84b><span><em>1.18 I’ve come across a font released under the OFL. How can I easily get more information about the Original Version? How can I know where it stands compared to the Original Version or other Modified Versions?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=6ce245771a09227fe7eff01895554c005be8f84b class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Consult the copyright statement(s) in the license for ways to contact the original authors. Consult the FONTLOG (see section 6 for more details and examples) for information on how the font differs from the Original Version, and get in touch with the various contributors via the information in the acknowledgement section. Please consider using the Original Versions of the fonts whenever possible.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#2697e97c7498c132266d9d83f54a5016cb289634><span><em>1.19 What do you mean in condition 4 of the OFL’s permissions and conditions? Can you provide examples of abusive promotion / endorsement / advertisement vs. normal acknowledgement?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=2697e97c7498c132266d9d83f54a5016cb289634 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">The intent is that the goodwill and reputation of the author(s) should not be used in a way that makes it sound like the original author(s) endorse or approve of a specific Modified Version or software bundle. For example, it would not be right to advertise a word processor by naming the author(s) in a listing of software features, or to promote a Modified Version on a website by saying “designed by …”. However, it would be appropriate to acknowledge the author(s) if your software package has a list of people who deserve thanks. We realize that this can seem to be a grey area, but the standard used to judge an acknowledgement is that if the acknowledgement benefits the author(s) it is allowed, but if it primarily benefits other parties, or could reflect poorly on the author(s), then it is not.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-warning p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Maybe, it depends on the situation 🤔" data-toggle=collapse href=#286ccc9935b4ac7d2ba372b561c5ce9a5ae609dd><span><em>1.20 I’m writing a small app for mobile platforms, do I need to include the whole package?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=286ccc9935b4ac7d2ba372b561c5ce9a5ae609dd class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">If you bundle a font under the OFL with your mobile app you must comply with the terms of the license. At a minimum you must include the copyright statement, the license notice and the license text. A mention of this information in your About box or Changelog, with a link to where the font package is from, is good practice, and the extra space needed to carry these items is very small. You do not, however, need to include the full contents of the font package - only the fonts you use and the copyright and license that apply to them. For example, if you only use the regular weight in your app, you do not need to include the italic and bold versions.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#da2b05fe49dbe7bbcb6dba017927f9054958b926><span><em>1.21 What about including OFL fonts by default in my firmware or dedicated operating system?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=da2b05fe49dbe7bbcb6dba017927f9054958b926 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Many such systems are restricted and turned into appliances so that users cannot study or modify them. Using open fonts to increase quality and language coverage is a great idea, but you need to be aware that if there is a way for users to extract fonts you cannot legally prevent them from doing that. The fonts themselves, including any changes you make to them, must be distributed under the OFL even if your firmware has a more restrictive license. If you do transform the fonts and change their formats when you include them in your firmware you must respect any names reserved by the font authors via the RFN mechanism and pick your own font name. Alternatively if you directly add a font under the OFL to the font folder of your firmware without modifying or optimizing it you are simply bundling the font like with any other software collection, and do not need to make any further changes.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#bb849ade5797c31102a7b11a4d506f28df46c7cf><span><em>1.22 Can I make and publish CMS themes or templates that use OFL fonts? Can I include the fonts themselves in the themes or templates? Can I sell the whole package?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=bb849ade5797c31102a7b11a4d506f28df46c7cf class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes, you are very welcome to integrate open fonts into themes and templates for your preferred CMS and make them more widely available. Remember that you can only sell the fonts and your CMS add-on as part of a software bundle. (See entry 1.4 for details and examples about selling bundles).</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#1ee00eff570301a50a46ab268c48c07f87eaf093><span><em>1.23 Can OFL fonts be included in services that deliver fonts to the desktop from remote repositories? Even if they contain both OFL and non-OFL fonts?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=1ee00eff570301a50a46ab268c48c07f87eaf093 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes. Some foundries have set up services to deliver fonts to subscribers directly to desktops from their online repositories; similarly, plugins are available to preview and use fonts directly in your design tool or publishing suite. These services may mix open and restricted fonts in the same channel, however they should make a clear distinction between them to users. These services should also not hinder users (such as through DRM or obfuscation mechanisms) from extracting and using the OFL fonts in other environments, or continuing to use OFL fonts after subscription terms have ended, as those uses are specifically allowed by the OFL.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#6a9c01731bde02939caf37561e95ba5e6dabb9c2><span><em>1.24 Can services that provide or distribute OFL fonts restrict my use of them?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=6a9c01731bde02939caf37561e95ba5e6dabb9c2 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No. The terms of use of such services cannot replace or restrict the terms of the OFL, as that would be the same as distributing the fonts under a different license, which is not allowed. You are still entitled to use, modify and redistribute them as the original authors have intended outside of the sole control of that particular distribution channel. Note, however, that the fonts provided by these services may differ from the Original Versions.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#8e007eaa50596962d906691a8918a5553b30ff22><span><em>1.25 Can a font released under the OFL be used as a source by an AI (Artificial Intelligence), an ML (Machine Learning) model, a NN (neural network), or similar system to create a new font and release it under a different license?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=8e007eaa50596962d906691a8918a5553b30ff22 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No. Any font produced from such systems whose input or training data contains any source file from a font project licensed under the OFL should be considered a derivative work. All Font Software released under the OFL and marked as such by the author(s) must remain under the OFL regardless of the way the sources might have been transformed, in whole or in part. If you would like to use font sources to produce a font to be released under a different license, then you need to contact the corresponding authors directly to ask for their explicit permission.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-warning p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Maybe, it depends on the situation 🤔" data-toggle=collapse href=#ecd437df4df246f49e06655a34291d71b5a61d78><span><em>1.26 Can OFL fonts be used by AI-based design tools?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=ecd437df4df246f49e06655a34291d71b5a61d78 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes, as long as the resulting work is not intended to be a font. Using such automated systems to produce graphical output - something that is not a font - is considered similar to normal usage. It is equivalent to using an OFL font in the graphic design process as discussed in question 1.1.</div></div></div><h3 id=2nbspnbspnbspusing-ofl-fonts-for-webpages-and-online-webfont-services>2 USING OFL FONTS FOR WEBPAGES AND ONLINE WEBFONT SERVICES</h3><p>This section often refers to a separate paper on ‘Webfonts & Reserved Font Names’. This is available at <a href=../webfonts-and-reserved-font-names>webfonts-and-reserved-font-names</a>.</p><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#31f566259c1a3f810256e3679e10faa457bb4a0b><span><em>2.1 Can I make webpages using these fonts?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=31f566259c1a3f810256e3679e10faa457bb4a0b class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes! Go ahead! You could ask visitors to download and install the fonts, but loading the fonts dynamically as webfonts through CSS @font-face declarations is a much better method. The referenced fonts can be hosted on the same server as other site assets and content, or loaded from a separate webfont service. This is recommended and explicitly allowed by the licensing model because it is distribution.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-warning p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Maybe, it depends on the situation 🤔" data-toggle=collapse href=#d0d5f5f3d469570bf8d9559b0daabada2e4fadfc><span><em>2.2 Can I make and use WOFF (Web Open Font Format) versions of OFL fonts?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=d0d5f5f3d469570bf8d9559b0daabada2e4fadfc class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes, but you need to be careful. A change in font format normally is considered modification, and Reserved Font Names (RFNs) cannot be used. Because of the design of the WOFF and WOFF2 formats, however, it is possible to create a WOFF/WOFF2 version that is not considered modification, and so would not require a name change.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-warning p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Maybe, it depends on the situation 🤔" data-toggle=collapse href=#bf64dd8c92190417a38d834b0c92eee4be757761><span><em>2.2.1 How can I make sure that a WOFF/WOFF2 version is not considered modification?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=bf64dd8c92190417a38d834b0c92eee4be757761 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">You are allowed to create, use and distribute a WOFF version of an OFL font without changing the font name, but only if the original font data remains unchanged except for WOFF compression, and WOFF-specific metadata is either omitted altogether or present and includes, unaltered, the contents of all equivalent metadata in the original font.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#53847c48faeb5e255ebcdd1a4762a53f7163d7f0><span><em>2.2.2 Do WOFF conversion tools and services automatically meet these requirements?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=53847c48faeb5e255ebcdd1a4762a53f7163d7f0 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No. Some WOFF conversion tools and online services do not meet the two requirements listed above, and so their output must be considered a Modified Version. So be very careful and check to be sure that the tool or service you’re using is compressing unchanged data and completely and accurately reflecting the original font metadata.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-warning p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Maybe, it depends on the situation 🤔" data-toggle=collapse href=#ce0d88c5002b6cf7664052f1fc7d652cbdadccec><span><em>2.3 What about other webfont formats such as EOT/EOTLite/CWT/etc.?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=ce0d88c5002b6cf7664052f1fc7d652cbdadccec class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">In most cases these formats alter the original font data more than WOFF, and do not completely support appropriate metadata, so their use must be considered modification and RFNs may not be used. However, there may be certain formats or usage scenarios that may allow the use of RFNs. See <a href=../webfonts-and-reserved-font-names>webfonts-and-reserved-font-names</a>.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#98a16af997b52cb888232ab5d79a527b0716561c><span><em>2.4 Can I make OFL fonts available through webfont online services?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=98a16af997b52cb888232ab5d79a527b0716561c class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes, you are welcome to include OFL fonts in online webfont services as long as you properly meet all the conditions of the license. The origin and open status of the font should be clear among the other fonts you are hosting. Authorship, copyright notices and license information must be sufficiently visible to your users or subscribers so they know where the font comes from and the rights granted by the author(s). Make sure the font file contains the needed copyright notice(s) and licensing information in its metadata. Please double-check the accuracy of every field to prevent contradictory information. Other font formats, including EOT/EOTLite/CWT and superior alternatives like WOFF, already provide fields for this information. Remember that if you modify the font within your library or convert it to another format for any reason the OFL restrictions apply and you need to change the names accordingly. Please respect the author’s wishes as expressed in the OFL and do not misrepresent original designers and their work. Don’t lump quality open fonts together with dubious freeware or public domain fonts. Consider how you can best work with the original designers and foundries, support their efforts and generate goodwill that will benefit your service. (See entry 1.17 for details related to URL-based access restrictions methods or DRM mechanisms).</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#555a5c5c92b230dccab828d90e89ec66847ab9ce><span><em>2.5 Some webfont formats and services provide ways of ‘optimizing’ the font for a particular website or web application; is that allowed?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=555a5c5c92b230dccab828d90e89ec66847ab9ce class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes, it is permitted, but remember that these optimized versions are Modified Versions and so must follow OFL requirements like appropriate renaming. Also you need to bear in mind the other important parameters beyond compression, speed and responsiveness: you need to consider the audience of your particular website or web application, as choosing some optimization parameters may turn out to be less than ideal for them. Subsetting by removing certain glyphs or features may seriously limit functionality of the font in various languages that your users expect. It may also introduce degradation of quality in the rendering or specific bugs on the various target platforms compared to the original font from upstream. In other words, remember that one person’s optimized font may be another person’s missing feature. Various advanced typographic features (OpenType, Graphite or AAT) are also available through CSS and may provide the desired effects without the need to modify the font.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#e21c87eaf180f705db4871bedae833637e72e1e4><span><em>2.6 Is subsetting a webfont considered modification?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=e21c87eaf180f705db4871bedae833637e72e1e4 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes. Removing any parts of the font when delivering a webfont to a browser, including unused glyphs and smart font code, is considered modification. This is permitted by the OFL but would not normally allow the use of RFNs. Some newer subsetting technologies may be able to subset in a way that allows users to effectively have access to the complete font, including smart font behaviour. See entry 2.8 and <a href=../webfonts-and-reserved-font-names>webfonts-and-reserved-font-names</a>.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#61f754d329436f9aa95574340276305f3b5d212a><span><em>2.7 Are there any situations in which a modified webfont could use RFNs?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=61f754d329436f9aa95574340276305f3b5d212a class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes. If a webfont is optimized only in ways that preserve Functional Equivalence (see entry 2.8), then it may use RFNs, as it reasonably represents the Original Version and respects the intentions of the author(s) and the main purposes of the RFN mechanism (avoids collisions, protects authors, minimizes support, encourages derivatives). However this is technically very difficult and often impractical, so a much better scenario is for the webfont service or provider to sign a separate agreement with the author(s) that allows the use of RFNs for Modified Versions.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#368ca55f0f4c6b77876e8bfadc9f650f1c6d984f><span><em>2.8 How do you know if an optimization to a webfont preserves Functional Equivalence?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=368ca55f0f4c6b77876e8bfadc9f650f1c6d984f class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4"><p>Functional Equivalence is described in full in the ‘Webfonts and Reserved Font Names’ paper at <a href=../webfonts-and-reserved-font-names>webfonts-and-reserved-font-names</a>, in general, an optimized font is deemed to be Functionally Equivalent (FE) to the Original Version if it:</p><ul><li>Supports the same full character inventory. If a character can be properly displayed using the Original Version, then that same character, encoded correctly on a webpage, will display properly.</li><li>Provides the same smart font behavior. Any dynamic shaping behavior that works with the Original Version should work when optimized, unless the browser or environment does not support it. There does not need to be guaranteed support in the client, but there should be no forced degradation of smart font or shaping behavior, such as the removal or obfuscation of OpenType, Graphite or AAT tables.</li><li>Presents text with no obvious degradation in visual quality. The lettershapes should be equally (or more) readable, within limits of the rendering platform.</li><li>Preserves original author, project and license metadata. At a minimum, this should include: Copyright and authorship; The license as stated in the Original Version, whether that is the full text of the OFL or a link to the web version; Any RFN declarations; Information already present in the font or documentation that points back to the Original Version, such as a link to the project or the author’s website.</li></ul><p>If an optimized font meets these requirements, and so is considered to be FE, then it’s very likely that the original author would feel that the optimized font is a good and reasonable equivalent. If it falls short of any of these requirements, the optimized font does not reasonably represent the Original Version, and so should be considered to be a Modified Version. Like other Modified Versions, it would not be allowed to use any RFNs and you simply need to pick your own font name.</p></div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-warning p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Maybe, it depends on the situation 🤔" data-toggle=collapse href=#01fa77eedfbdd7455e8cf0cf239a4deb3041acfd><span><em>2.9 Can fonts released under the OFL be used with Incremental Font Transfer (IFT) or similar on-the-fly subsetting and compression technologies?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=01fa77eedfbdd7455e8cf0cf239a4deb3041acfd class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes, if they provide a sufficient level of Functional Equivalence. Extra care should be taken to make sure that such processes - both on the server and on the client - do not break glyph coverage and smart features especially for lesser-known and lesser-resourced languages in the resulting document or app. See the ‘Webfonts and Reserved Font Names’ paper on <a href=../webfonts-and-reserved-font-names>webfonts-and-reserved-font-names</a> for more about the goals and the rationale.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#f7a5459fb04ec1583a82c76d344fcd15a2d625e8><span><em>2.10 Isn’t use of webfonts another form of embedding?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=f7a5459fb04ec1583a82c76d344fcd15a2d625e8 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No. Unlike embedded fonts in a PDF, webfonts are not an integrated part of the document itself. They are not specific to a single document and are often applied to thousands of documents around the world. The font data is not stored alongside the document data and often originates from a different location. The ease by which the webfonts used by a document may be identified and downloaded for desktop use demonstrates that they are philosophically and technically separate from the webpages that specify them. See <a href=../webfonts-and-reserved-font-names>webfonts-and-reserved-font-names</a>.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#d2887955d786a05f70bf20f883e573dcda44ef31><span><em>2.11 So would it be better to not use RFNs at all if you want your font to be distributed by a webfont service?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=d2887955d786a05f70bf20f883e573dcda44ef31 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No. Although the OFL does not require authors to use RFNs, the RFN mechanism is an important part of the OFL model and completely compatible with webfont services. If that webfont service modifies the fonts, then the best solution is to sign a separate agreement for the use of any RFNs. It is perfectly valid for an author to not declare any RFNs, but before they do so they need to fully understand the benefits they are giving up, and the overall negative effect of allowing many different versions bearing the same name to be widely distributed. As a result, we don’t generally recommend it.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#c2d21ab4688f9cc970b64bfb37bc131a0bb04d74><span><em>2.12 What should an agreement for the use of RFNs say? Are there any examples?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=c2d21ab4688f9cc970b64bfb37bc131a0bb04d74 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4"><p>There is no prescribed format for this agreement, as legal systems vary, and no recommended examples. Authors may wish to add specific clauses to further restrict use, require author review of Modified Versions, establish user support mechanisms or provide terms for ending the agreement. Such agreements are usually not public, and apply only to the main parties. However, it would be very beneficial for webfont services to clearly state when they have established such agreements, so that the public understands clearly that their service is operating appropriately.</p><p>See the separate paper on ‘Webfonts and Reserved Font Names’ for in-depth discussion of issues related to the use of RFNs for webfonts. This is available at <a href=../webfonts-and-reserved-font-names>webfonts-and-reserved-font-names</a>.</p></div></div></div><h3 id=3nbspnbspnbspmodifying-ofl-licensed-fonts>3 MODIFYING OFL-LICENSED FONTS</h3><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#916a3b37862d25c71eb7293f7b653e91636f92a7><span><em>3.1 Can I change the fonts? Are there any limitations to what things I can and cannot change?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=916a3b37862d25c71eb7293f7b653e91636f92a7 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">You are allowed to change anything, as long as such changes do not violate the terms of the license. In other words, you are not allowed to remove the copyright statement(s) from the font, but you could put additional information into it that covers your contribution. See the placeholders in the OFL header template for recommendations on where to add your own statements. (Remember that, when authors have reserved names via the RFN mechanism, you need to change the internal names of the font to your own font name when making your modified version even if it is just a small change.)</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#47ffd93865bc60f6431831db2605565dffbb7509><span><em>3.2 I have a font that needs a few extra glyphs - can I take them from an OFL licensed font and copy them into mine?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=47ffd93865bc60f6431831db2605565dffbb7509 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes, but if you distribute that font to others it must be under the OFL, and include the information mentioned in condition 2 of the license.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-warning p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Maybe, it depends on the situation 🤔" data-toggle=collapse href=#a9c68c54449dd45e3ffc6d16d2e2e55125c2895d><span><em>3.3 Can I charge people for my additional work? In other words, if I add a bunch of special glyphs or OpenType/Graphite/AAT code, can I sell the enhanced font?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=a9c68c54449dd45e3ffc6d16d2e2e55125c2895d class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Not by itself. Derivative fonts must be released under the OFL and cannot be sold by themselves. It is permitted, however, to include them in a larger software package (such as text editors, office suites or operating systems), even if the larger package is sold. In that case, you are strongly encouraged, but not required, to also make that derived font easily and freely available outside of the larger package.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#f23a602910dc8852626969ed2cab4934b4ae5d5b><span><em>3.4 Can I pay someone to enhance the fonts for my use and distribution?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=f23a602910dc8852626969ed2cab4934b4ae5d5b class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes. This is a good way to fund the further development of the fonts. Keep in mind, however, that if the font is distributed to others it must be under the OFL. You won’t be able to recover your investment by exclusively selling the font, but you will be making a valuable contribution to the community. Please remember how you have benefited from the contributions of others.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#c3e66c166813c6ccb5819daf234787040c248650><span><em>3.5 I need to make substantial revisions to the font to make it work with my program. It will be a lot of work, and a big investment, and I want to be sure that it can only be distributed with my program. Can I restrict its use?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=c3e66c166813c6ccb5819daf234787040c248650 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No. If you redistribute a Modified Version of the font it must be under the OFL. You may not restrict it in any way beyond what the OFL permits and requires. This is intended to ensure that all released improvements to the fonts become available to everyone. But you will likely get an edge over competitors by being the first to distribute a bundle with the enhancements. Again, please remember how you have benefited from the contributions of others.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#bac4b03419be9dd1ca94c3c927e170560d480f68><span><em>3.6 Do I have to make any derivative fonts (including extended source files, build scripts, documentation, etc.) publicly available?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=bac4b03419be9dd1ca94c3c927e170560d480f68 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No, but please consider sharing your improvements with others. You may find that you receive in return more than what you gave.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#429e189fa2d4c23ea77005965fd0739a718894e3><span><em>3.7 If a trademark is claimed in the OFL font, does that trademark need to remain in modified fonts?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=429e189fa2d4c23ea77005965fd0739a718894e3 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes. Any trademark notices must remain in any derivative fonts to respect trademark laws, but you may add any additional trademarks you claim, officially registered or not. For example if an OFL font called “Foo” contains a notice that “Foo is a trademark of Acme”, then if you rename the font to “Bar” when creating a Modified Version, the new trademark notice could say “Foo is a trademark of Acme Inc. - Bar is a trademark of Roadrunner Technologies Ltd.”. Trademarks work alongside the OFL and are not subject to the terms of the licensing agreement. The OFL does not grant any rights under trademark law. Bear in mind that trademark law varies from country to country and that there are no international trademark conventions as there are for copyright. You may need to significantly invest in registering and defending a trademark for it to remain valid in the countries you are interested in. This may be costly for an individual independent designer.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-warning p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Maybe, it depends on the situation 🤔" data-toggle=collapse href=#f5b7c2ab603729527be3f6a212c411bcaf06e4f7><span><em>3.8 If I commit changes to a font (or publish a branch in a DVCS) as part of a public open source software project, do I have to change the internal font names?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=f5b7c2ab603729527be3f6a212c411bcaf06e4f7 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Only if there are declared RFNs. Making a public commit or publishing a public branch is effectively redistributing your modifications, so any change to the font will require that you do not use the RFNs. Even if there are no RFNs, it may be useful to change the name or add a suffix indicating that a particular version of the font is still in development and not released yet. This will clearly indicate to users and fellow designers that this particular font is not ready for release yet. See section 5 for more details.</div></div></div><h3 id=4nbspnbspnbsplicensing-your-original-fonts-under-the-ofl>4 LICENSING YOUR ORIGINAL FONTS UNDER THE OFL</h3><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#782650dad14a47661ff5170fb27c2a5610214cf9><span><em>4.1 Can I use the SIL OFL for my own fonts?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=782650dad14a47661ff5170fb27c2a5610214cf9 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes! We heartily encourage everyone to use the OFL to distribute their own original fonts. It is a carefully constructed license that allows great freedom along with enough artistic integrity protection for the work of the authors as well as clear rules for other contributors and those who redistribute the fonts. The licensing model is used successfully by various organisations, both for-profit and not-for-profit, to release fonts of varying levels of scope and complexity.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#3a20090f6629e82dc86182a58926523409ffdf49><span><em>4.2 What do I have to do to apply the OFL to my font?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=3a20090f6629e82dc86182a58926523409ffdf49 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4"><p>If you want to release your fonts under the OFL, we recommend you do the following:</p><p>4.2.1 Put your copyright and Reserved Font Names information at the beginning of the main OFL.txt file in place of the dedicated placeholders (marked with the <> characters). Include this file in your release package.</p><p>4.2.2 Put your copyright and the OFL text with your chosen Reserved Font Name(s) into your font files (the copyright and license fields). A link to the OFL text on the OFL website is an acceptable (but not recommended) alternative. Also add this information to any other components (build scripts, glyph databases, documentation, test files, etc). Accurate metadata in your font files is beneficial to you as an increasing number of applications are exposing this information to the user. For example, clickable links can bring users back to your website and let them know about other work you have done or services you provide. Depending on the format of your fonts and sources, you can use template human-readable headers or machine-readable metadata. You should also double-check that there is no conflicting metadata in the font itself contradicting the license, such as the fstype bits in the os2 table or fields in the name table.</p><p>4.2.3 Write an initial FONTLOG.txt for your font and include it in the release package (see Section 6 and Appendix A for details including a template).</p><p>4.2.4 Include the relevant practical documentation on the license by adding the current OFL-FAQ.txt file in your package.</p><p>4.2.5 If you wish you can use the <a href=../promotion>OFL graphics</a> on your website.</p></div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#e5d05199b7d43b0bd203a9cf2e8e874dad4ff45f><span><em>4.3 Will you make my font OFL for me?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=e5d05199b7d43b0bd203a9cf2e8e874dad4ff45f class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">We won’t do the work for you. We can, however, try to answer your questions. Unfortunately we do not have the resources to review and check your font packages for correct use of the OFL. We recommend you turn to designers, foundries or consulting companies with experience in doing open font design to provide this service to you.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#83883f9a9f04a04af0c790df93d414e14826cfb7><span><em>4.4 Will you distribute my OFL font for me?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=83883f9a9f04a04af0c790df93d414e14826cfb7 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No. The easiest way for users to always get the most current version of the font is for you to distribute it through your own website. You can also distribute your own font source files, or host them on services such as GitHub or GitLab. You can use various channels, including social media, to promote and get attention to your project. If you want someone else to distribute the font, consider services and sites that already distribute OFL fonts. Some of those are listed on <a href=../ofl-fonts>ofl-fonts</a>. Contact them to find out how to submit fonts to them. We do not endorse any particular catalog or hosting service. It is your responsibility to determine if the service is right for you and if it treats authors with fairness.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#59a7597c10f2e831aaf8a6526fb9a13e25ea680e><span><em>4.5 Why should I use the OFL for my fonts?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=59a7597c10f2e831aaf8a6526fb9a13e25ea680e class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4"><p>Here are a few of the many good reasons:</p><ul><li>to meet needs for fonts that can be modified to support lesser-known languages</li><li>to provide a legal and clear way for people to respect your work but still use it (and reduce piracy)</li><li>to involve others in your font project</li><li>to enable your fonts to be expanded with new weights and improved writing system/language support</li><li>to allow more technical font developers to add features to your design (such as OpenType, Graphite or AAT support)</li><li>to renew the life of an old font lying on your hard drive with no business model</li><li>to allow your font to be included in Libre Software operating systems like Ubuntu</li><li>to give your font world status and wide, unrestricted distribution</li><li>to educate students about quality typeface and font design</li><li>to expand your test base and get more useful feedback</li><li>to extend your reach to new markets when users see your metadata and go to your website</li><li>to get your font more easily into one of the webfont online services</li><li>to attract attention for your commercial fonts</li><li>to make money through webfont services</li><li>to make money by bundling fonts with applications</li><li>to make money adjusting and extending existing open fonts</li><li>to get a better chance that foundations, NGOs, charities, or companies who commission fonts will pick you</li><li>to be part of a sharing design and development community</li><li>to give back and contribute to a growing body of font sources</li></ul></div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#31918ec11813e2a958c673c0624094b8c07c76a0><span><em>4.6 Can I cancel or undo the OFL license for a font that I’ve already released under it?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=31918ec11813e2a958c673c0624094b8c07c76a0 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No, as an author, you cannot cancel or undo the permissions you have granted earlier by releasing a font under the OFL. But as an original author of that specific font you can always re-release it separately under another license of your own choosing. Of course, you cannot re-license a font for which you are not the author. If there are multiple authors they need to be all in official written agreement with the re-licensing. For practical reasons, a different name than an existing and publicly available open font should be chosen.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-warning p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Maybe, it depends on the situation 🤔" data-toggle=collapse href=#f359294216f13f5ddfd9c4b1c166c97d6ba5622f><span><em>4.7 Should I apply the OFL early in the design process, even before the font is complete, or wait until I want to release a completed version?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=f359294216f13f5ddfd9c4b1c166c97d6ba5622f class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">It is really up to you and the circumstances of your project. But in any case, we would recommend you place appropriate warning messages in your public repository or website to say something like “Please wait for a finished release before using and redistributing this font”. We recommend you have a clear versioning scheme and repository tagging to make it as easy as possible to see if the font is a released version or still under development. You can also consider choosing a separate name (or suffix) for the development version, and only give the final name to a released version.s</div></div></div><h3 id=5nbspnbspnbspchoosing-reserved-font-names>5 CHOOSING RESERVED FONT NAMES</h3><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#6746a82081d852d58b152584407d5b80d3ac43f3><span><em>5.1 What are Reserved Font Names?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=6746a82081d852d58b152584407d5b80d3ac43f3 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">These are font names, or portions of font names, that the author has chosen to reserve for use only with the Original Version of the font, or for Modified Version(s) created by the original author.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#4380b93c5f9e9e252ac9ac548449d65f955603c4><span><em>5.2 Why can’t I use the Reserved Font Names in my derivative font names? I’d like people to know where the design came from.</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=4380b93c5f9e9e252ac9ac548449d65f955603c4 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">The best way to acknowledge the source of the design is to thank the original authors and any other contributors in the files that are distributed with your revised font (although no acknowledgement is required). The FONTLOG is a natural place to do this. Reserved Font Names ensure that the only fonts that have the original names are the unmodified Original Versions. This allows designers to maintain artistic integrity while allowing collaboration to happen. It eliminates potential confusion and name conflicts. When choosing a name, be creative and avoid names that reuse almost all the same letters in the same order or sound like the original. It will help everyone if Original Versions and Modified Versions can easily be distinguished from one another and from other derivatives. Any substitution and matching mechanism is outside the scope of the license.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#e710dd44fa12f98194f8bba2bb20cba7bee18ff6><span><em>5.3 What do you mean by ‘primary name as presented to the user’? Are you referring to the font menu name?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=e710dd44fa12f98194f8bba2bb20cba7bee18ff6 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes, this applies to the font menu name and other mechanisms that specify a font in a document. It would be fine, however, to keep a text reference to the original fonts in the description field, in your modified source file or in documentation provided alongside your derivative as long as no one could be confused that your modified source is the original. But you cannot use the Reserved Font Names in any way to identify the font to the user (unless the Copyright Holder(s) allow(s) it through a separate agreement). Users who install derivatives (Modified Versions) on their systems should not see any of the original Reserved Font Names in their font menus, for example. Again, this is to ensure that users are not confused and do not mistake one font for another and so expect features only another derivative or the Original Version can actually offer.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#2e764b34bb9cf18ff85fc0a77c2cd10063248c10><span><em>5.4 Am I not allowed to use any part of the Reserved Font Names?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=2e764b34bb9cf18ff85fc0a77c2cd10063248c10 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">You may not use individual words from the Reserved Font Names, but you would be allowed to use parts of words, as long as you do not use any word from the Reserved Font Names entirely. We do not recommend using parts of words because of potential confusion, but it is allowed. For example, if “Foobar” was a Reserved Font Name, you would be allowed to use “Foo” or “bar”, although we would not recommend it. Such an unfortunate choice would confuse the users of your fonts as well as make it harder for other designers to contribute.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#5f66ffa0d783df84c67ba37533f91b9f3782a063><span><em>5.5 So what should I, as an author, identify as Reserved Font Names?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=5f66ffa0d783df84c67ba37533f91b9f3782a063 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Original authors are encouraged to name their fonts using clear, distinct names, and only declare the unique parts of the name as Reserved Font Names. For example, the author of a font called “Foobar Sans” would declare “Foobar” as a Reserved Font Name, but not “Sans”, as that is a common typographical term, and may be a useful word to use in a derivative font name. Reserved Font Names should also be single words for simplicity and legibility. A font called “Flowing River” should have Reserved Font Names “Flowing” and “River”, not “Flowing River”. You also need to be very careful about reserving font names which are already linked to trademarks (whether registered or not) which you do not own.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#a2246273db175b4d951c8ae09a9b87d55b422463><span><em>5.6 Do I, as an author, have to identify any Reserved Font Names?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=a2246273db175b4d951c8ae09a9b87d55b422463 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No. RFNs are optional and not required, but we encourage you to use them. This is primarily to avoid confusion between your work and Modified Versions. As an author you can release a font under the OFL and not declare any Reserved Font Names. There may be situations where you find that using no RFNs and letting your font be changed and modified - including any kind of modification - without having to change the original name is desirable. However you need to be fully aware of the consequences. There will be no direct way for end-users and other designers to distinguish your Original Version from many Modified Versions that may be created. You have to trust whoever is making the changes and the optimizations to not introduce problematic changes. The RFNs you choose for your own creation have value to you as an author because they allow you to maintain artistic integrity and keep some control over the distribution channel to your end-users. For discussion of RFNs and webfonts see section 2.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#5f5d4f6e0458dabaec2721a7d16765ac6d643567><span><em>5.7 Are any names (such as the main font name) reserved by default?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=5f5d4f6e0458dabaec2721a7d16765ac6d643567 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No. That is a change to the license as of version 1.1. If you want any names to be Reserved Font Names, they must be specified after the copyright statement(s).</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-warning p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Maybe, it depends on the situation 🤔" data-toggle=collapse href=#77526ddfb1469f41739fcab554059141c36d9329><span><em>5.8 Is there any situation in which I can use Reserved Font Names for a Modified Version?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=77526ddfb1469f41739fcab554059141c36d9329 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">The Copyright Holder(s) can give certain trusted parties the right to use any of the Reserved Font Names through separate written agreements. For example, even if “Foobar” is an RFN, you could write up an agreement to give company “XYZ” the right to distribute a modified version with a name that includes “Foobar”. This allows for freedom without confusion. The existence of such an agreement should be made as clear as possible to downstream users and designers in the distribution package and the relevant documentation. They need to know if they are a party to the agreement or not and what they are practically allowed to do or not even if all the details of the agreement are not public.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-warning p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Maybe, it depends on the situation 🤔" data-toggle=collapse href=#9ea990cdc04de03985119ec4c7b120cccd122e1d><span><em>5.9 Do font rebuilds require a name change? Do I have to change the name of the font when my packaging workflow includes a full rebuild from source?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=9ea990cdc04de03985119ec4c7b120cccd122e1d class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes, all rebuilds which change the font data and the smart code are Modified Versions and the requirements of the OFL apply: you need to respect what the Author(s) have chosen in terms of Reserved Font Names. However if a package (or installer) is simply a wrapper or a compressed structure around the final font - leaving them intact on the inside - then no name change is required. Please get in touch with the author(s) and copyright holder(s) to inquire about the presence of font sources beyond the final font file(s) and the recommended build path. That build path may very well be non-trivial and hard to reproduce accurately by the maintainer. If a full font build path is made available by the upstream author(s) please be aware that any regressions and changes you may introduce when doing a rebuild for packaging purposes is your responsibility as a package maintainer since you are effectively creating a separate branch. You should make it very clear to your users that your rebuilt version is not the canonical one from upstream.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#aaeea59ce7310ec7acaa0649f92510e828b57b02><span><em>5.10 Can I add other Reserved Font Names when making a derivative font?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=aaeea59ce7310ec7acaa0649f92510e828b57b02 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Yes. List your additional Reserved Font Names after your additional copyright statement, as indicated with example placeholders at the top of the OFL.txt file. Be sure you do not remove any existing RFNs but only add your own. RFN statements should be placed next to the copyright statement of the relevant author as indicated in the OFL.txt template to make them visible to designers wishing to make their separate version.</div></div></div><h3 id=6nbspnbspnbspabout-the-fontlog>6 ABOUT THE FONTLOG</h3><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#58258c05de79d267cff0777b650c09dd0e24396f><span><em>6.1 What is this FONTLOG thing exactly?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=58258c05de79d267cff0777b650c09dd0e24396f class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">It has three purposes: 1) to provide basic information on the font to users and other designers and developers, 2) to document changes that have been made to the font or accompanying files, either by the original authors or others, and 3) to provide a place to acknowledge authors and other contributors. Please use it!</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#986a6a7bbe6a4ae5c1502558f013f6ed6b9ae6f2><span><em>6.2 Is the FONTLOG required?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=986a6a7bbe6a4ae5c1502558f013f6ed6b9ae6f2 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">It is not a requirement of the license, but we strongly recommend you have one.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#03c10c50990743199cc887aaacd3f88a0a0a026e><span><em>6.3 Am I required to update the FONTLOG when making Modified Versions?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=03c10c50990743199cc887aaacd3f88a0a0a026e class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No, but users, designers and other developers might get very frustrated with you if you don’t. People need to know how derivative fonts differ from the original, and how to take advantage of the changes, or build on them. There are utilities that can help create and maintain a FONTLOG.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#417d179a4f3241a4606707a9e09e76d7e1110ac3><span><em>6.4 What should the FONTLOG look like?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=417d179a4f3241a4606707a9e09e76d7e1110ac3 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4"><p>It is typically a separate text file (FONTLOG.txt), but can take other formats. It commonly includes these four sections:</p><ul><li>brief header describing the FONTLOG itself and name of the font family</li><li>Basic Font Information - description of the font family, purpose and breadth</li><li>ChangeLog - chronological listing of changes</li><li>Acknowledgements - list of authors and contributors with contact information</li></ul><p>It could also include other sections, such as: where to find documentation, how to make contributions, information on contributing organizations, source code details, and a short design guide. See Appendix A for an example FONTLOG.</p></div></div></div><h3 id=7nbspnbspnbspmaking-contributions-to-ofl-projects>7 MAKING CONTRIBUTIONS TO OFL PROJECTS</h3><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#ec8e800b130e88f8d15b2c092b8d2fd1e5eaa830><span><em>7.1 Can I contribute work to OFL projects?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=ec8e800b130e88f8d15b2c092b8d2fd1e5eaa830 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">In many cases, yes. It is common for OFL fonts to be developed by a team of people who welcome contributions from the wider community. Contact the original authors for specific information on how to participate in their projects.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#9d90f00e19f5543904caf9ab2abd5b800e0613c0><span><em>7.2 Why should I contribute my changes back to the original authors?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=9d90f00e19f5543904caf9ab2abd5b800e0613c0 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">It would benefit many people if you contributed back in response to what you’ve received. Your contributions and improvements to the fonts and other components could be a tremendous help and would encourage others to contribute as well and ‘give back’. You will then benefit from other people’s contributions as well. Sometimes maintaining your own separate version takes more effort than merging back with the original. Be aware that any contributions, however, must be either your own original creation or work that you own, and you may be asked to affirm that clearly when you contribute.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#f96c51c3d98f021d42ee8c458ed421add6b4adde><span><em>7.3 I’ve made some very nice improvements to the font. Will you consider adopting them and putting them into future Original Versions?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=f96c51c3d98f021d42ee8c458ed421add6b4adde class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Most authors would be very happy to receive such contributions. Keep in mind that it is unlikely that they would want to incorporate major changes that would require additional work on their end. Any contributions would likely need to be made for all the fonts in a family and match the overall design and style. Authors are encouraged to include a guide to the design with the fonts. It would also help to have contributions submitted as patches or clearly marked changes - the use of smart source revision control systems like subversion, mercurial, git or bzr is a good idea. Please follow the recommendations given by the author(s) in terms of preferred source formats and configuration parameters for sending contributions. If this is not indicated in a FONTLOG or other documentation of the font, consider asking them directly. Examples of useful contributions are bug fixes, additional glyphs, stylistic alternates (and the smart font code to access them) or improved hinting. Keep in mind that some kinds of changes (esp. hinting) may be technically difficult to integrate.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#f40141584308035bb03b454584dbe23925c8bab3><span><em>7.4 How can I financially support the development of OFL fonts?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=f40141584308035bb03b454584dbe23925c8bab3 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">It is likely that most authors of OFL fonts would accept financial contributions - contact them for instructions on how to do this. Such contributions would support future development. You can also pay for others to enhance the fonts and contribute the results back to the original authors for inclusion in the Original Version.</div></div></div><h3 id=9nbspnbspnbspabout-the-license-itself>9 ABOUT THE LICENSE ITSELF</h3><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-warning p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Maybe, it depends on the situation 🤔" data-toggle=collapse href=#3057df8efd3ace80a979fd70d1020648fe2450b5><span><em>8.1 I see that this is version 1.1 of the license. Will there be later changes?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=3057df8efd3ace80a979fd70d1020648fe2450b5 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">Version 1.1 is the first minor revision of the OFL. We are confident that version 1.1 will meet most needs, but are open to future improvements. Any revisions would be for future font releases, and previously existing licenses would remain in effect. No retroactive changes are possible, although the Copyright Holder(s) can re-release the font under a revised OFL. All versions will be available on our website: <a href=https://openfontlicense.org>https://openfontlicense.org</a></div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#75aa23f731a1b4429847582dd5bf90b10185b8f1><span><em>8.2 Does this license restrict the rights of the Copyright Holder(s)?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=75aa23f731a1b4429847582dd5bf90b10185b8f1 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No. The Copyright Holder(s) still retain(s) all the rights to their creation; they are only releasing a portion of it for use in a specific way. For example, the Copyright Holder(s) may choose to release a ‘basic’ version of their font under the OFL, but sell a restricted ‘enhanced’ version under a different license. They may also choose to release the same font under both the OFL and some other license. Only the Copyright Holder(s) can do this, and doing so does not change the terms of the OFL as it applies to that font.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#a626a25b7b500f9214acf310b1376506a11f0de8><span><em>8.3 Is the OFL a contract or a license?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=a626a25b7b500f9214acf310b1376506a11f0de8 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">The OFL is a worldwide license based on international copyright agreements and conventions. It is not a contract and so does not require you to sign it to have legal validity. By using, modifying and redistributing components under the OFL you indicate that you accept the license.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#532cb5b70a3f71ce180c165205647e8909d4e8a0><span><em>8.4 I really like the terms of the OFL, but want to change it a little. Am I allowed to take ideas and actual wording from the OFL and put them into my own custom license for distributing my fonts?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=532cb5b70a3f71ce180c165205647e8909d4e8a0 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">We strongly recommend against creating your very own unique open licensing model. Using a modified or derivative license will likely cut you off - along with the font(s) under that license - from the community of designers using the OFL, potentially expose you and your users to legal liabilities, and possibly put your work and rights at risk. The OFL went though a community and legal review process that took years of effort, and that review is only applicable to an unmodified OFL. The text of the OFL has been written by SIL (with review and consultation from the community) and is copyright (c) 2005-2023 SIL International. You may re-use the ideas and wording (in part, not in whole) in another non-proprietary license provided that you call your license by another unambiguous name, that you do not use the preamble, that you do not mention SIL and that you clearly present your license as different from the OFL so as not to cause confusion by being too similar to the original. If you feel the OFL does not meet your needs for an open license, please contact us.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#d1f15683c2b3e08fe96ef083dd1427b28321d1a3><span><em>8.5 Can I quote from the OFL FAQ?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=d1f15683c2b3e08fe96ef083dd1427b28321d1a3 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4"><p>Yes, SIL gives permission to quote from the OFL FAQ (OFL-FAQ.txt), in whole or in part, provided that the quoted text is:</p><ul><li>unmodified,</li><li>used to help explain the intent of the OFL, rather than cause misunderstanding, and</li><li>accompanied with the following attribution: “From the OFL FAQ (OFL-FAQ.txt), copyright (c) 2005-2023 SIL International. Used by permission. <a href=https://openfontlicense.org/OFL-FAQ>https://openfontlicense.org/OFL-FAQ</a>”.</li></ul></div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-success p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="generally yes ✅" data-toggle=collapse href=#cb7710e4d7963a4b9df7bd948339fc4ab721c883><span><em>8.6 Can I translate the license and the FAQ into other languages?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=cb7710e4d7963a4b9df7bd948339fc4ab721c883 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4"><p>SIL certainly recognises the need for people who are not familiar with English to be able to understand the OFL and its use. Making the license very clear and readable has been a key goal for the OFL, but we know that people understand their own language best.</p><p>If you are an experienced translator, you are very welcome to translate the OFL and OFL-FAQ so that designers and users in your language community can understand the license better. But only the original English version of the license has legal value and has been approved by the community. Translations do not count as legal substitutes and should only serve as a way to explain the original license. SIL - as the author and steward of the license for the community at large - does not approve any translation of the OFL as legally valid because even small translation ambiguities could be abused and create problems.</p><p>SIL gives permission to publish unofficial translations into other languages provided that they comply with the following guidelines:</p><p>Put the following disclaimer in both English and the target language stating clearly that the translation is unofficial: “This is an unofficial translation of the SIL Open Font License into <language_name>. It was not published by SIL International, and does not legally state the distribution terms for fonts that use the OFL. A release under the OFL is only valid when using the original English text. However, we recognize that this unofficial translation will help users and designers not familiar with English to better understand and use the OFL. We encourage designers who consider releasing their creation under the OFL to read the OFL-FAQ in their own language if it is available. Please go to <a href=https://openfontlicense.org>https://openfontlicense.org</a> for the official version of the license and the accompanying OFL-FAQ.”</p><p>Keep your unofficial translation current and update it at our request if needed, for example if there is any ambiguity which could lead to confusion. If you start such an unofficial translation effort of the OFL and OFL-FAQ please let us know.</p></div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-danger p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Generally no ❌" data-toggle=collapse href=#66ccb38985dbc1aaf37a35297fd7b9b305e8f5f3><span><em>8.7 Does the OFL have an explicit expiration term?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=66ccb38985dbc1aaf37a35297fd7b9b305e8f5f3 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">No, the implicit intent of the OFL is that the permissions granted are perpetual and irrevocable.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#a69ae0f996dcc9751fc067472635b460cddd4010><span><em>8.8 Why is there no automatic upgrade clause, a ‘version 1.1 or later’ like in the GPL?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=a69ae0f996dcc9751fc067472635b460cddd4010 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">This is by design, with the goals of establishing clear trust and of preventing any situation where the actual terms could be changed from underneath any user of the license. That would introduce uncertainty and confusion. Any perceived benefits of automatic incremental licensing under newer versions is strongly outweighed by the inherent risks and confusion it would cause. If a new version becomes officially available, Copyright Holder(s) can review the new version and decide whether to re-release their fonts under it. Derivative fonts could not be re-licensed unless the original versions were re-released first.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#bcf5a87562be4372c34b6a754080bae1785f0a49><span><em>8.9 How do you pronounce the name of the license?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=bcf5a87562be4372c34b6a754080bae1785f0a49 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">The OFL is pronounced as three individual letters /ˈɑː.əf.əl/ or OH-EFF-ELL.</div></div></div><h3 id=9nbspnbspnbspabout-sil-international>9 ABOUT SIL INTERNATIONAL</h3><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#d28690954e2e5987f92bd27e0f4409ee779a4943><span><em>9.1 Who is SIL International and what do they do?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=d28690954e2e5987f92bd27e0f4409ee779a4943 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">SIL is a global, faith-based nonprofit that works with local communities around the world to develop language solutions that expand possibilities for a better life. SIL serves language communities worldwide, building their capacity for sustainable language development, by means of research, translation, training and materials development. SIL makes its services available to all without regard to religious belief, political ideology, gender, race, or ethnic background. SIL’s members and volunteers share a Christian commitment.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#0a16e203872bcacabe78d1385e9c7faf62c4c5be><span><em>9.2 What does this have to do with font licensing?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=0a16e203872bcacabe78d1385e9c7faf62c4c5be class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4">The ability to read, write, type and publish in one’s own language is one of the most critical needs for millions of people around the world. This requires fonts that are widely available and support lesser-known languages. SIL develops - and encourages others to develop - a complete stack of writing systems implementation components available under open licenses. This open stack includes input methods, smart fonts, smart rendering libraries and smart applications. There has been a need for a common open license that is specifically applicable to fonts and related software (a crucial component of this stack), so SIL developed the SIL Open Font License with the help of the Free/Libre and Open Source Software community.</div></div></div><div class="card mb-1 rounded rounded-top-bottom shadow border-0"><div class="card-header bg-white border-primary p-0 border-4"><a class="card-link h4 d-flex tex-dark mb-0 pt-2 pb-0 px-4 justify-content-between" title="Extra information ℹ️" data-toggle=collapse href=#e1f7a3a299f62225cba076fc6d3d6e677f303482><span><em>9.3 How can I contact SIL?</em></span> <i class="ti-plus text-primary text-right"></i></a></div><div id=e1f7a3a299f62225cba076fc6d3d6e677f303482 class=collapse data-parent=#accordion><div class="card-body font-secondary text-color pt-0 pb-0 px-4"><p>Our main website is: <a href=https://www.sil.org>https://www.sil.org</a></p><p>Our main site about fonts and software is: <a href=https://software.sil.org/>https://software.sil.org/</a></p><p>Our site about complex scripts is: <a href=https://scriptsource.org>https://scriptsource.org</a></p><p>Information about this license (and contact information) is at: <a href=https://openfontlicense.org>https://openfontlicense.org</a></p></div></div></div><h3 id=appendix-a---fontlog-example>APPENDIX A - FONTLOG EXAMPLE</h3><p>Here is an example of the recommended format for a FONTLOG, although other formats are allowed.</p><pre tabindex=0><code>FONTLOG for the GlobalFontFamily fonts This file provides detailed information on the GlobalFontFamily Font Software. This information should be distributed along with the GlobalFontFamily fonts and any derivative works. Basic Font Information GlobalFontFamily is a Unicode typeface family that supports all languages that use the Latin script and its variants, and could be expanded to support other scripts. NewWorldFontFamily is based on the GlobalFontFamily and also supports Greek, Hebrew, Cyrillic and Armenian. More specifically, this release supports the following Unicode ranges... This release contains... Documentation can be found at... To contribute to the project... ChangeLog 10 December 2010 (Fred Foobar) GlobalFontFamily-devel version 1.4 - fix new build and testing system (bug #123456) 1 August 2008 (Tom Parker) GlobalFontFamily version 1.2.1 - Tweaked the smart font code (Branch merged with main) - Provided improved build and debugging environment for smart behaviours 7 February 2007 (Pat Johnson) NewWorldFontFamily Version 1.3 - Added Greek and Cyrillic glyphs 7 March 2006 (Fred Foobar) NewWorldFontFamily Version 1.2 - Tweaked contextual behaviours 1 Feb 2005 (Jane Doe) NewWorldFontFamily Version 1.1 - Improved build script performance and verbosity - Extended the smart code documentation - Corrected minor typos in the documentation - Fixed position of combining inverted breve below (U+032F) - Added OpenType/Graphite smart code for Armenian - Added Armenian glyphs (U+0531 -> U+0587) - Released as "NewWorldFontFamily" 1 Jan 2005 (Joe Smith) GlobalFontFamily Version 1.0 - Initial release Acknowledgements If you make modifications be sure to add your name (N), email (E), web-address (if you have one) (W) and description (D). This list is in alphabetical order. N: Jane Doe E: <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="4228232c2702372c2b342730312b363b6c272637">[email protected]</a> W: https://art.university.edu/projects/fonts D: Contributor - Armenian glyphs and code N: Fred Foobar E: <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="3b5d495e5f7b5d5454595a491554495c">[email protected]</a> W: https://foobar.org D: Contributor - misc Graphite fixes N: Pat Johnson E: <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="a2d2c3d6e2c4cdccd6d1d6d7c6cbcd8ccdd0c5">[email protected]</a> W: https://pat.fontstudio.org D: Designer - Greek & Cyrillic glyphs based on Roman design N: Tom Parker E: <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="e0948f8da0838f8d90818e99ce838f8d">[email protected]</a> W: https://www.company.com/tom/projects/fonts D: Engineer - original smart font code N: Joe Smith E: <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="573d38321731383923242322333e3879382530">[email protected]</a> W: https://joe.fontstudio.org D: Designer - original Roman glyphs Fontstudio.org is an not-for-profit design group whose purpose is... Foobar.org is a distributed community of developers... Company.com is a small business who likes to support community designers... University.edu is a renowned educational institution with a strong design department... </code></pre><p class="post-meta text-center text-muted small fw-lighter pb-0 mb-0 mt-5">Last updated on 24 January 2024</p></div></div></div></div></section><footer class="section pb-4"><div class=container><div class="row align-items-right"><div class="col-md-12 text-md-center text-center"><p class="mb-md-0 text-md-center mb-12">The SIL Open Font License is maintained by Victor Gaultney and Nicolas Spalinger. <a href=../contact>Contact us</a>.</br>This site is Copyright © 2005–2024 <a href=https://www.sil.org>SIL International (sil.org)</a> | <a href=../privacy>Privacy policy</a> | <a href=../colophon>Colophon</a> | <a href=../full-site-map>Site map</a></p></div></div></div></footer><script data-cfasync="false" src="/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js"></script><script src=https://openfontlicense.org/js/script.min.js></script></body></html>