Eine kurze deutsche Zusammenfassung der OFL finden Sie auf: http://de.wikipedia.org/wiki/SIL_Open_Font_License 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 electronic form reference a font name '=)>=S\D<  *sY'h{Kj ^xcO>K6m1Z^-52[9p%S7+%#NBw8XDW3q""&vc5񥦽Ooo.ۼB,sްAkﲋwhq=s`8O`HVڨ_'wRPboX8"UM ;ֿoX7Ũ<]Ic) /)cuI|ْ13a;V5^&`d2jV#N;r^=O,lt=rKv8ot]QOOõh=Ɨ>HeH~XN9=|&qc K&i$n"7ǥT2N摣FlS1Y3mt?bdӤU;=j&aaKdVQq._&;)n 9sߛ{wYl $0xKRլlfK Jai1 7q/štw\+4xr:68~zQ MnaHr=+^u Y\Eyف\Fv cVii-#֋g`++;  uߴ˦Zy$9ldT1eiso)>~wуҾqm\W6miX)dTWWMJ*Xp6p-%}K$"b9$uxb~ВT#Ku$bJP n_x`߹+ 9,w$ǽDF>VOJVLP_Iuc:I$V%r1| H_xHog$ Hz?LBI|F(;sIEjXW^];ͨǡIKy$WUzn^qM;i߉$:lK<%vE W5|7-D#cXg9]xVKK8m y y ,OS[۟9$^3f{FN'u-7( TS7x͝-t@"|<(Yw$#^xcJj:p*oeKWC%HЀۜFH⽋[MLcDH C$++cw`Mq$JH; 4y)=M^hi3N&IRG]e"8!kX ֵX{qw 4.<]6u`q08㻏TbW dԐ p~5RWY^/¥b`T0' WG\Wi\IZIF0D`7T٥;jݵ.Gbjݾ;{GSu<9Nv+7icͯ笠՞M9^6 Y3(޺}[jM#?8% Oڹw݊*! q vO<=<72bFFwү$a+A.mtgd`11絭B'JK\Da%Kb7KhmR#r/]4Ad>N 3X-I&hфhHeIa`wſ5-+O{uY>Ucs +Ҽ/}ƨoe#Fڤռ7g[sF]N#$8 Ǫz=w}pL5URGdޖ,Va`Asc|7,֞h#|HH9zzdӝm.f5 C&V+t%T]䋻eo}ezѲAL#g[Z5;}"QH$u3n;Mw&rZ~f$ך\4XIJJ2v󴌏?eM){˯quI>w?Du wrGzL02EThEc\3~x/OM?7)R#8\ԍ{t>4"%kwsy6Ϫ4#+EGVWR;9S~P}1Q\|Ƀmc#.q^&U}? 0I<{vfyO}Hg Ն2J6 c@U|¼{4|s^+;SVBDFxVvG|{}b`jnGjHvw`~F;Nx/σ W9L߷qR ǿ>]qRB،֥jO݀Hޢ?x<VPESHϸj@Eꧦ 9>UHi'"9R9ͻr8M =*7OSN~lF? 70njB 9mpi0Ƞ s(^zCeY>l}ho,5#&`tRFJλUE{KzR:NO8߹ےy?ʀZqwg !'qS¨Gq|7#9JwަO'Pc,=*`moץX{zzfT)$r̄W([hG'ѸX?0ά~/^,S@3$9Ntcӵ .v-\rsªSr043mn{~$!a!zt;^ձmG,dݾ >Oo˜ʘ۷|j]q]lUV88\oL u1U&>v&5#DL[=e⮤iq{>C<[G's=}].6~U c1r|zTOU  뚡{ir,g u Fk W$#ggD}Xߗ9hL`7[pG_i .cGP3Jȴ|W4XBy^~fHdYG11zo #I2|7Lg2mM U=AI` ZF0O9>Ow ܷ}jd7%c\9}+tA\%b~Z+w \MbnbbQcY&v=]DuQ4жi\'=:5OEurH!g%W??5􀬌D;IL`tx˛ebʲlb/;gIxfP D9R0{[o8Qgp*7*Bzmu]qmjsO7siSIWuזkG{?,у?+x c[Լ1eiouaˀKC5ku9燌zs&8îp)'nty)9<¾7 Ƨl"崔wP+FҶi`n<`/ֺ%Z kyQ'č64[dxt9]emx6s/5㺯gCy 9X0vd+EeR:1:jGѐk5[L\ s6)`Ue8󭞫ڳmCV7>,Bb&9OJnV"Od{xLF>V:9 IּLyXΡel@ҥMk#xԫ+(/'iA_y${wgT3oYI(~LҾV92%qul1v?\fuh+Ril!ԭP%$)Mpoxcq7a^4QqnGQ9/0@9z8|Ody"Z{s+NmkfY+ c ᛡ_m"Jݴ j97 ;8Դ~jFP+.tLjo\ ʫ? *~x. #޸=o6 F׭}kf}ߵCylqϚƞ+sJ8ϥZ#g>RMtSRtIՇb=[x&xk4cH.X6Ws$S؂q]ӵGk)jWlԔ^%MRi񉃩$'9c*|Ӭ5 =BPYѕW7Rh%Ԓ1ocui'<.0QG~Gʾ'񦡣EciՓOp&8 +x;:MCm P)f@E}ѭx~URr>P#EU X10,PR1Gn64 18فCn۴7@Aϥd|=ym;,ĕ'z։*=k.Oك@Vn@IXf:TFcbk!|P.|'"B$T0[_%V &ZY4Kl8л1 Fk~>(ULQBWs<* m^9;I"D{plWB!AN Z+sZ=O~-$6vҼqyE RAMzw5Kk+[RGＦl#9W+UQA22;7#i#;vV; fbR2Yg xc[n<:S2ڕv"U7 ׊F%x|96Yvt'[ϮMM;ӿl\P~$㛈.kh eT1H[ _"y9*/1}ΓW]:N+=5îɜ>:k@,3cIUc y2XRqg G{DJFX8,Byr\C"O/(Oˎv(.+?f4G5\3K!82I#Hm2D~rxǯiKrQi4?|¼E xgeMܳ0']jSY+w4knJ~]כs\ǯkmw2Y($O~)|CH{YY>fpycZ rO`iGvKf⏱nW˹e%rŎakͼ?{"GfrEc)D1eA}H6Ė݅At ^$uPʫ@ ^g|5Oj7V^]o>ՔFH1`0y'?.%mcռ`,@wn#85j*hڏ:8f guvK+93!i mUU c{xcܗ 4۞5I(l଼䊘sF6}Mg4{mwيs/ePqOJZ⦩e+ Id^ dCM&S7ZYXcVqֹ=Fտ"ijیI '}+H5"01EXIOڧ\;u $91SP]ZK+H\Y REG}gc8I8! >&dM*$R ]U7(vrlz񅅖i4Q\K`ąS:4uF8gL˔vUMhGmTjjXnW8$}:VY^E9:78!@\+_fb=zأV $ 9b=kFŐC4Y[M1$Ŋ@8}KEG6b[[NDT zþ6z%[60/ nW=q]W+KdZ23b,8Fz tGq(u(' 8bR{ֽ^ɧë dt allowed to use any part of the Reserved Font Names? You may not use the words of the 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. 2.10 So what should I, as an author, identify as Reserved Font Names? 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. A font called "Flowing River" should have Reserved Font Names "Flowing" and "River", not "Flowing River". 2.11 Do I, as an author, have to identify any Reserved Font Names? No, but we strongly encourage you to do so. This is to avoid confusion between your work and Modified versions. You may, however, give certain trusted parties the right to use any of your Reserved Font Names through separate written agreements. For example, even if "Foobar" is a 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. 2.12 Are any names (such as the main font name) reserved by default? 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). 2.13 What is this FONTLOG thing exactly? It has three purposes: 1) to provide basic information on the font to users and other 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 the authors and other contributors. Please use it! See below for details on how changes should be noted. 2.14 Am I required to update the FONTLOG? No, but users, designers and other developers might get very frustrated at 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. 3 ABOUT THE FONTLOG The FONTLOG can take a variety of formats, but should include these four sections: 3.1 FONTLOG for This file provides detailed information on the Font Software. This information should be distributed along with the fonts and any derivative works. 3.2 Basic Font Information (Here is where you would describe the purpose and brief specifications for the font project, and where users can find more detailed documentation. It can also include references to how changes can be contributed back to the Original Version. You may also wish to include a short guide to the design, or a reference to such a document.) 3.3 ChangeLog (This should list both major and minor changes, most recent first. Here are some examples:) 7 February 2007 (Pat Johnson) Version 1.3 - Added Greek and Cyrillic glyphs - Released as "" 7 March 2006 (Fred Foobar) Version 1.2 - Tweaked contextual behaviours - Released as "" 1 Feb 2005 (Jane Doe) 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 "" 1 Jan 2005 (Joe Smith) Version 1.0 - Initial release of font "" 3.4 Acknowledgements (Here is where contributors can be acknowledged. If you make modifications be sure to add your name (N), email (E), web-address (W) and description (D). This list is sorted by last name in alphabetical order.) N: Jane Doe E: jane@university.edu W: http://art.university.edu/projects/fonts D: Contributor - Armenian glyphs and code N: Fred Foobar E: fred@foobar.org W: http://foobar.org D: Contributor - misc Graphite fixes N: Pat Johnson E: pat@fontstudio.org W: http://pat.fontstudio.org D: Designer - Greek & Cyrillic glyphs based on Roman design N: Tom Parker E: tom@company.com W: http://www.company.com/tom/projects/fonts D: Engineer - original smart font code N: Joe Smith E: joe@fontstudio.org W: http://joe.fontstudio.org D: Designer - original Roman glyphs (Original authors can also include information here about their organization.) 4 ABOUT MAKING CONTRIBUTIONS 4.1 Why should I contribute my changes back to the original authors? It would benefit many people if you contributed back to what you've received. Providing your contributions and improvements to the fonts and other components (data files, source code, build scripts, documentation, etc.) could be a tremendous help and would encourage others to contribute as well and 'give back', which means you will have an opportunity to 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. 4.2 I've made some very nice improvements to the font, will you consider adopting them and putting them into future Original Versions? 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, svk, mercurial, git or bzr is a good idea). Examples of useful contributions are bug fixes, additional glyphs, stylistic alternates (and the smart font code to access them) or improved hinting. 4.3 How can I financially support the development of OFL fonts? 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. (In case of the font, that comes with this copy of the FAQ-file, you will find a paypal(tm) donation link on the fonts-page of www.peter-wiegel.de) 5 ABOUT THE LICENSE 5.1 I see that this is version 1.1 of the license. Will there be later changes? 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 web site: http://scripts.sil.org/OFL. 5.2 Can I use the SIL Open Font License for my own fonts? Yes! We heartily encourage anyone 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 contrib+{I U9=(ŨaKߋ4^{H6%`y'^.Si(|[ F?6A+_G7+RJpÎ1T̓ $lyp7wL_S\yc9"<}=鑈‰A8 $JK/0E )rm\Vy} T ~zzNy\G8Z%unUJ./Rrzb]pjb*Y|CA;mI 4/x$!}w:t&U]w%qx9MpxmeMEb\9#c^O\6Z:J]ln/'OjRn eb.nj zV寍S;ȯY7,i`[O=bĥH;_qx,4 |:4He}FT*\oS9QRoMIwuq#Î{P̒]jfpB r}*C{K |P95^4%$J%&D`K/\ʥ>Y7(+h2a4+I*~zϦu #ֶ$^):]>OEu$6ogqq8zxdz{ EV8< Am ǚ̗lIe*{=s]o`mSM,dw}ܓZR:QNζ"Q4]KXQ"#-O^x.eE"ŝ> p8* ˋxuoTD{w!dpj24iS("(}1^![yi#@r>Uמ,b,%>RrFxuךPw32E5TU,0I'=. MFuTma=p$2$}eXۥ|0'U sm,vAc q=;Ti<@n@y'j2-RY >\h#IkZMĒ(ԆӊWs"&B\b*ll`tT^Cfoq9>P U(ᶨ<5a䱝|Eۗ Zmʷďx-]}o=#Lxm3ʫ>\3أeoԼ1MvM "(JJs;%R_NϦG[32J𾋥Ys=V@Y$eStxVM>U7.~ϵfkՏ$ik7G})}p8qz$3jvh]̠}r7 uDԜ!thvUU]\/ޑ`c[\{zvWZy4#;h`H5~!};y\5ݔ0\fR+ۚGԒ[*<6I'szWUX[1#mXy`ዝ-߹j,a-\Ȭ]&;;vz ImM`l(\0qPhElq`$9G5gSò%̩XmF<0?RkYZ7 RW3Z 'u{T>Bʌ d9繯qtԼO%q۪1RI&m 8x%hj$5Ⱦ#;6OVޓ5˛+{H-J3G.n3R]ϡtb[ R$:ػH\. |3ųXxt~$\G#:mZXyi0c>qPpN8m6MLKw ~A99c*Q-ƫnmB(lq>W!a7uho_1cL@yڪ$'aEl V?'ң}F*efUcplUn(I9Er* #q OZ.OP/g,auA) gjC`/u.8BNH>ձ;?tx2~E_5⸌n$ gzb{7k7[I%rA9$?h+]Z{]?P!|;Fq S=7v񶳂2FDr: 3|umkW6y: T܎ya{Ŷ,UߋP \b8b,^_/>lH 0lު2H >(QTKqr`\E',q|>|/DC[y戄2{w5Zu>"[8to+ᾁ{\h2n`Wi!w 0I~\ԓjtw$byT:5J;^ ɓCD'eǭ`~~Ȋ+|L[5X[Hijl~|s[?F&UH}$nr(%?_`?f݆CUd3H#4gw߲Cʣ#ʃE`_~;04;~E'CO ,z?:c֕q3>wcE}%j7˂sR.eT[Q}}jy2㠪J~qIsl~9篵 e ?2GpԌu9 ӹ_Dff*'RWoRz:R(Xmxґo8<Ňo֤͞Xwdgڴ#w'%=ODߍ5cn5&ݸ$)u!ʌь}ޚ6pAsRޢK) :Q`$L7~↌3dЊdlv?^}Em8?Q#dO =jWcF e va`ׯ|C:XT ~ 0l$qR"[\va3c`GPzgll$?Z: Đ\ԫ'q߶[\!DPk.o,Wq_۾+~ fGg$.V?Q<*NYI{N~a<"Tnq@s<܎GzY6=+0;@c;nZpnt#8R۶@9Jp'ږ&2i8^==ܒ:gLͺ@0kW.9G$cڸ \-D{ciح^޾~Shٶ(]M5nm' Zi6O5ʽCsrZDx-,rmٝ?R.Rc[dD)rNHQ|c+>]Υ.L'A%Vp?Nxy?|#c-zW]Z4,Q_$y;[gô~V`y9?I -M^Rn'*ќmR+ח.C C