OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL)
Version 1.1-update1 - 31 March 2009
(See http//scripts.sil.org/OFL for updates)
1 ABOUT USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
1.1 Can I use the fonts in any publication, even embedded in the file?
Yes. You may use them like most other fonts, but unlike some fonts you may include an embedded subset of the fonts in your document. Such use does not require you to include this license or other files (listed in OFL condition 2), nor does it require any type of acknowledgement within the publication. Some mention of the font name within the publication information (such as in a colophon) is usually appreciated. If you wish to include the complete font as a separate file, you should distribute the full font package, including all existing acknowledgements, and comply with the OFL conditions. Of course, 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 OFL does not make the resulting artwork subject to the OFL.
1.2 Can I make web pages using these fonts?
Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended. Direct usage of fonts retrieved from a remote server - also referred to as font linking - using cross-platform open standards like @font-face is encouraged. This is considered to be use and distribution for which the OFL explicitly grants permission. The font file itself is not embedded in the webpage but referenced through a web address (i.e. a URI regardless of file format or access protocol) which will cause the browser to retrieve and use the corresponding font to render the webpage. This usage scenario is different from font embedding within a document (i.e. a PDF) where the font or some of its elements become part of the document. Note that embedding in a document is also permitted by the license as indicated in 1.1. (See 1.10 for details related to URL-based access restrictions methods or DRM mechanisms).
1.3 Can I make the fonts available to others from my web site?
Yes, as long as you meet the conditions of the license (do not sell by itself, include the necessary files, include the necessary copyright and license information, rename Modified Versions, do not abuse the Author(s)' name(s) and do not sublicense). In the case where you are hosting fonts to be served on the web, make sure the 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. If you are making the font available for use via the @font-face open standard, putting this information in the standard font metadata fields is sufficient. Other font formats, including EOT and proposed superior alternatives, already provide fields for this information.
1.4 Can the fonts be included with Free/Libre and Open Source Software collections such as GNU/Linux and BSD distributions?
Yes! Fonts licensed under the OFL can be freely aggregated with software under FLOSS (Free/Libre and Open Source Software) licenses. Since fonts are much more useful aggregated to than merged with existing software, possible incompatibility with existing software licenses is not a problem. You can also repackage the fonts and the accompanying components in a .rpm or .deb package and include them in distro CD/DVDs and online repositories.
1.5 I want to distribute the fonts with my program. Does this mean my program also has to be free/libre and open source software?
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.
1.6 Can I include the fonts on a CD of freeware or commercial fonts?
Yes, as long some other font or software is also on the disk, so the OFL font is not sold by itself.
1.7 Can I sell a software package that includes these fonts?
Yes, you can do this with both the Original Version and a Modified Version. Examples of bundling made possible by the OFL would include: word processors, design and publishing applications, training and educational software, edutainment software, etc.
1.8 Why won't the OFL let me sell the fonts alone?
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 honor and respect their contribution!
1.9 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?
Consult the copyright statement(s) in the license for ways to contact the original authors. Consult the FONTLOG for information on how the font differs from the Original Version, and get in touch with the various contributors via the information in the acknowledgment section. Please consider using the Original Versions of the fonts whenever possible.
1.10 What do you mean in condition 4? Can you provide examples of abusive promotion / endorsement / advertisement vs. normal acknowledgement?
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 web site 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 gray 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.
1.11 Can Font Software released under the OFL be subject to URL-based access restrictions methods or DRM mechanisms?
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 or bundle. 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.
1.12 What about distributing fonts with a document? Within a compressed folder structure like an OpenDocument file (.odt) for example? Is it redistribution, bundling or embedding?
The vast majority of the time, documents circulated in electroni
没有合适的资源?快使用搜索试试~ 我知道了~
资源推荐
资源详情
资源评论
收起资源包目录
前端前端静态模板-非响应式家具田园模板-学生作业毕设实训素材.zip (260个子文件)
style.css 35KB
prettyPhoto.css 27KB
jquery.slider.css 9KB
blue.css 1KB
green.css 1KB
lime.css 1KB
purple.css 1KB
red.css 1KB
titillium.css 1KB
carto.css 1KB
otari.css 1006B
adelle.css 1003B
quicksand.css 995B
delicious.css 994B
vegur.css 963B
copse.css 963B
arvo.css 947B
puritan.css 931B
classic.css 904B
mido.css 810B
ie8.css 566B
ie7.css 515B
ptsans.css 438B
museo.css 405B
charis.css 348B
ie9.css 222B
.DS_Store 21KB
.DS_Store 15KB
.DS_Store 12KB
.DS_Store 6KB
.DS_Store 6KB
adellebasic-bold-webfont.eot 186KB
style_194538.eot 86KB
copse-regular-webfont.eot 64KB
ptsans-italic-webfont.eot 60KB
CharisSILI-webfont.eot 54KB
ptsans-regular-webfont.eot 52KB
Puritan_Regular-webfont.eot 50KB
Arvo-Regular-webfont.eot 46KB
museo-500-webfont.eot 44KB
museo-300-webfont.eot 43KB
museo-700-webfont.eot 42KB
vegur-r_0.602-webfont.eot 26KB
Mido-webfont.eot 23KB
loader.gif 6KB
jquery-slider-theme.gif 3KB
loader.gif 2KB
post.html 21KB
StartHere.html 18KB
tab-toggle-table.html 18KB
portfolio-post.html 16KB
blog.html 16KB
button-boxes-images.html 14KB
pagewithsidebar.html 14KB
typography.html 14KB
portfolio.html 14KB
columns.html 14KB
index.html 14KB
contact.html 10KB
fullwidth.html 10KB
testimonials.html 9KB
form.html 3KB
index.html 2KB
bg1.jpg 166KB
bg6.jpg 110KB
s2.jpg 82KB
s4.jpg 70KB
s1.jpg 67KB
s3.jpg 46KB
post3.jpg 41KB
bg2.jpg 40KB
post1.jpg 39KB
about.jpg 36KB
post2.jpg 34KB
bg4.jpg 31KB
l12.jpg 30KB
pp12.jpg 24KB
bg5.jpg 24KB
l11.jpg 23KB
l5.jpg 23KB
bg3.jpg 22KB
l10.jpg 21KB
l7.jpg 21KB
l2.jpg 21KB
pp11.jpg 20KB
p12.jpg 20KB
l9.jpg 20KB
l3.jpg 19KB
pp2.jpg 18KB
pp5.jpg 18KB
pp15.jpg 17KB
p15.jpg 17KB
pp13.jpg 17KB
p11.jpg 16KB
p5.jpg 16KB
l4.jpg 16KB
pp10.jpg 16KB
pp7.jpg 16KB
l1.jpg 16KB
p7.jpg 16KB
共 260 条
- 1
- 2
- 3
资源评论
芝麻粒儿
- 粉丝: 6w+
- 资源: 2万+
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功