a0ayjrѕgh\n۱~iA^ hb|wyq9 ֺ-6,sىQzJڼLz3R_pDZ=q>&a?z O5|h,vﾷ:{a]ečR^/Y?+xhii;.ihft7[\s=qi 妝vď~ ]E<7?v#4fI9UN8z+jGjڅ~]/O6bv#&)rO?QO]oK?XuVDZWY#^SF 7yf:2j}rդv1<*m2}ޕPK$V_òg?'g_ėw=1Z󜦜B[n|*OёE۪bKg'Y GVZB+Wu#UKCx:ա[ˎ=rDž^sGkuf(ګH{WCR\a>&yuTFͳj?eejڕ;ڎ;.,-k rH  ˿n 5^}G/֭ie]R1h11Y-2?#IUʑ7Uv]U^gv5']/ElnK6I!h"q5#? gGWjUUJ|ZGGW#kmخ3ğ %e+JnڪUt/-6+c ԟmx扻Mh~_6"M͛ee+Z{ЬWULgPF0rWKmAmsC{ڻ3oj!_ACɝ?Ű+s! ǓloOx"⸸(5IwfYSʳ(Ú%Gdg x4G/_ B.͠iUgX-XMe[^)lv]Z/i"}m>NOCSK$SV7mV!LUs]^}QF1Woȹq VH|ҩ_I?QNMNzsXV+ wx?vk_eYrKuW" UOj5K_:6ѷQ̭XW^ڇ>becuK2%\\|iBͣѷ2Wѭx3uh\*5%QL/Ϸ[L?'MDJM>:}ʪ]ji1!ݓ7e/fƳ-u 푃ޕ^QwHv]^(%~?gmث3tZakmVdq\_ uc4Mzs_̫ltGN 73U2nuZVHV|^ɣ n_݈i^ Y^dpuq8kfη no!z=럼3,˓#L{j}bdyu5iy~ZS&"^&)c#n&ZwfQzx%lXl;6+zxSQ?#KTU^#)Ȣce*ijlg6[>Wb] Z;IeOsq66*Iz54*Ơ.'f rѴQ&IWX-v3략qŞj8v =qLtV;h!)~Gƫqo2ăޫDz?$wٻֿP5F$Q:k~"il} B&ax vW'Ɨ:}Es ms GMwVׇ[+,;t5d׃dxtVHJưşNץBJhucthMNtgCY/kY&bGp= Wsڱ:[ 6/jSTs%DR|WCKOϯ̙{=V4c팶}|z8=G\-wQX7ȧ{\a@;xAcX?^, ;k^&mo-$ uHu54ֳM2nq^]j]6K<ћ +Zp9[<EyXچ<^8U9%Zl/"j("_^-zE20[kk q˼ `vD:85XlQE#>>4Ue[ݜլ?+KMeA]RVѣoEx lv6{l`y+v+e${ɑUxU;< ׇw/yXn:( LI ZU{F&.nj5bGJ93аgQx emQP L?vp>,[M.-n毦u:oc|^hҡ-}Fdrz[zq^זܦ^mb"MQ]E+܇ ЭhګS-.c3Rl0+UVJWZWccQkyd;zm[P1`1UZ[rە䍻jV}¯UZ &g|ݿk/uI7q%7ek̭ьh.g,5m0pX:Xho;kMx|Dq[xv*cା<>sh,"Mhlû5V_um4" WL|e4Qbqsrkef0tpQ]{ UUfѫa$mA5<(tԼ:&V憨\F[5bTS$|c4zʉIW~hz.u UvQ~Ѻ3xqk𗋣gsUG[y?'~;k|=akq#Iu߳-扨]JlY cmy&1_k*F>aלDx8'2(Xz_zRgu.ʪ?:4{#KYON4O +f_j5x/T @ +qY4ڏkbSz"S{W&hʭVkȿ3G2MlUo9FRgoʾ[nZWVD7KܓYZB>jkuQM+[g^vtӔ#Nz3:O_o] ZoS!6_YF!]9ps׬߻kYlsznq +Ź?^ov3KO7 !fKEoJ 8? Zg3 *djvZ06nX|ɺSKY"ܿ0Z$r,\_2ʥUR\a,N_P՚L}oVG3}e_0 b_V\Xg[>]J[~5%NRi"q})hDs:cjCyԺDO ţkRʟU}NMIS]'u^Tw:o0oإ-w 礄Z޳cI^B3}8ըʞ/k\lيt^2rZ'N6H80#sqMQo7\26Q]{~*i%v/?5yD._1,I2trrUmĿ5iP){bw.͆o {W\-ƞ7_]ׂHhC>s\CϨM\-͔zmֵԞ~~z?.ޫ=HbTNmPԋ/y\1G;;-Vm&6&1:#z:k.F $tۧBiտnrMe^;wGY(zWK%vTO-08>T< jw>2F4,-'HY}Xpm{Qc·>(dӢ}Ǚ?^ZB2xΪw Y|Ut]XW>am b1K ٮ@ğijqeYFvaj> !y+SUl<.7E!^Z|?zɷ䚤ڲ.y8]pHڐ^Ei\X=1[w.v7|s?Wj l}]|0/ۆawwju ͩmenFY>[gkq&Oz;j24 $~+$E_*'<+Bdݾo"E{;[6G7m\Dz:jZլjwj?: GG"||;*0F!F6ItQqU]֏*'mnvXz)OVclD2dFm;})awUmv8r&76񡷹[kw vCQ2FLj<]-?qFߺ+JwmEo|ѡhY.IgkU{điWׁ)ο+;.Otp5ȴ[W$o^V8OsҼ'!ak I{|l7p_?'-乱ggc:& ;VQ*jzrGP70fM~lAZOieIC5zjƤ^W I+dcYwˍ ^YW7Wå:Ws|I;=rH"V+柈2Zq5oK5ta n N>,*adwcxk|mե?ɡ5v5m>n߻ח']u,M,M4g6Qu\Dֳ5ZBԴIp}.yK1jFӟZ|y9`hBx4X_ЩNRS{m/' -_Gb;7!77oi}K̍:~boN$v W]%ղ#m"TV0aq>k߈j?>TJ֎߽<|_7xWZyx?|1 5IeSV<2dkC؋UMfMߘщe9Uk<{^Gٮ.:74-=We~x^\Z .Oۑ{nir5Wwg3J؆*U19ޚ}TbdxePOUϖm^HÒjIډ=-ۚU4; C\׍5'tw(}1VWk_4%P̾\§->T)eKѤXm|mMY=e|wGK &2bf @OWYy~2i-V{~zQ}᷌\ik2j7=~VVdhen choosing a name be creative and avoid names that reuse almost all the same letters in the same order or sound like the original. Keep in mind that the Copyright Holder(s) can allow a specific trusted partner to use Reserved Font Name(s) through a separate written agreement. 2.8 What do you mean by "primary name as presented to the user"? Are you referring to the font menu name? Yes, the requirement to change the visible name used to differentiate the font from others applies to the font menu name and other mechanisms to specify a font in a document. It would be fine, for example, 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; see section 2.7). Users who install derivatives ("Modified Versions") on their systems should not see any of the original names ("Reserved Font Names") in their font menus, for example. Again, this is to ensure that users are not confused and do not mistake a font for another and so expect features only another derivative or the Original Version can actually offer. Ultimately, creating name conflicts will cause many problems for the users as well as for the designer of both the Original and Modified versions, so please think ahead and find a good name for your own derivative. Font substitution systems like fontconfig, or application-level font fallback configuration within OpenOffice.org or Scribus, will also get very confused if the name of the font they are configured to substitute to actually refers to another physical font on the user's hard drive. It will help everyone if Original Versions and Modified Versions can easily be distinguished from one another and from other derivatives. The substitution mechanism itself is outside the scope of the license. Users can always manually change a font reference in a document or set up some kind of substitution at a higher level but at the lower level the fonts themselves have to respect the Reserved Font Name(s) requirement to prevent ambiguity. If a substitution is currently active the user should be aware of it. 2.9 Am I not 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 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. 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 contributors and those who redistribute the fonts. Some additional information about using the OFL is included at the end of this FAQ. 5.3 Does this license restrict the rights of the Copyright Holder(s)? 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. Only the Copyright Holder(s) can do this. 5.4 Is the OFL a contract or a license? The OFL is a license and 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. 5.5 How about translating the license and the FAQ into other languages? SIL certainly recognises the need for people who are not familiar with English to be able to understand the OFL and this FAQ better in their own language. Making the license very clear and readable is a key goal of the OFL. If you are an experienced translator, you are very welcome to help by translating the OFL and its 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. We give permission to publish unofficial translations into other languages provided that they comply with the following guidelines: - put the fo[2!!/xЕb@,p+h]n٢=N=O֑GW^KωrxKk 4yg.q";(ބ] 8;kno<( OVd_1Ecҟ݉I75X'm5Fgu$<,nT!Z^ybskѭTlRsF`Ԥrvz $"B{?[ ?@kpN2H=7U"ei-p7֮ǰ.\bno!8nH L,sFx :5Tds$vq FsIR 7ԨhR#|j(a{R0y*?"f8^j9yRhHQcQ2~; 9B, :fO5 <럭1ş 1s"ߞp:SyaT?XV%$^})}XY GP=n$֎Vhi$ҬѓץdKݙQB*!=d/8Slc~K**$:\,hj'jʹ@ I=/1n9 `nҵ䑮d$gj𵗘9A#;Ҹ8@^Ԃ<8 MÎ yT˓LDU(▊k0^w=zPt?JLdցץF(^4ubKMH@ =IIRg jC׭(䟥&8^zQ9iN@JpCA'<F CHNJAր(F6 y\zmzQE'Oj8֘푁JgR=s a'{ЀN{#6>MyWAޑd'of|קk} χo|;MYmZmJA!n?#Zx+ky[Xۛ[XJy"fPV9ed[iŷ!}嵜s\ֆ+΀s!x-~k%7i'T$[XvI)']W|-$^,GCy) YIQsyow~.:2]m ٜ󟻏֔1P$# 4--+ #/+y<,20{gQM\Oŝolaӵ8d{{>&jfik u4,QۧYYAH"\U?eΊ$iH%:FmлF }-/Xx֚{MH#ҜV7`|ȮR4gg'5}Z;6+{xok[y<|'1+b/BmCnZ碛*2*$qBlOL:(+sӏzvsbo=xG($)$Uk7$MDoԹrisO:ǎVmZ΂ULmek1Kg pI\O~M||GYxłj/<,W#~f5=SC1+Ͼ&|3UK{pheEG|$)VxdzZV2n`Gp2/zh ƺI,<~ͧ`=Gu]x4[1 f}T)sĈEm*{<|1D'I~~Z:E^dwc 0Rl}j9uMNݣhK 鐃OpՔ}9WcMGVdc'InKc#5,۳l,xea(A+ȸ5K*}sV#eUrcaW3:{m3~:*yzυk;Kb,\:jJhc(=RtW%Q"Hʰ&ɴĐyF?ii^2\:V Cubyo OFPq0]~O] ڠbfYai6?r*3I#(ZŔ7o]:l?հ-LR2$ ?M;VKe$sL)<ֿ|&M-92 ZZmq6Ql`?*kU^-E-[=#ZxĂ'BpVl[q|JI?K" 8J6Gtevn<栎u$4裊̲Pp1ӷw5MR\x4mPI튯=~Ҝr(n҃8N zu⎆}i|Pyօ DnwL`NhpԛEʌi|=\Tm*Ee#(BIғy֗^΀Ґ= 7Rh2.zQIs׮h[7zӃ @=zS qiۇNI7wI^0ɣq曜O9Et%s>>5_[jQBWK%iUHTlwlg[⟅=[ut::tk{DQmc