CINXE.COM

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title>Guidelines for Writing System Support: Technical Details: Glyph Design</title> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <meta name="keywords" content="UNESCO,Guidelines,WSI,WSIs,writing system,writing systems,glyph,design,font,typeface"> <link rel="stylesheet" href="/cms/assets/misc/css/default.css" type="text/css"> <link rel="stylesheet" href="/cms/sites/nrsi/themes/default/_css/default.css" type="text/css"> <style type="text/css">  </style>   <script async src="https://www.googletagmanager.com/gtag/js?id=G-FVXRGR2Q9V"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'G-FVXRGR2Q9V'); </script> <title>Guidelines for Writing System Support: Technical Details: Glyph Design</title> </head> <body style="padding:0; margin:0"> <style> .archive_notice { /* box-shadow: black 0pt 4pt 20px -8px inset; */ display: block; background-color: orange; font-size: 12pt; font-style: normal; font-weight: lighter; line-height: 100%; padding: 5pt; text-align: center; width: auto; } form { display: none } .webform::before { content: "Forms are disabled on this static version of the site."; display: block; width: fit-content; } </style> <div class="archive_notice"> This is an archive of the original scripts.sil.org site, preserved as a historical reference. Some of the content is outdated. Please consult our other sites for more current information: <a href="https://software.sil.org">software.sil.org</a>, <a href="https://scriptsource.org">ScriptSource</a>, <a href="https://silnrsi.github.io/FDBP/">FDBP</a>, and <a href="https://silnrsi.github.io/silfontdev/">silfontdev</a> </div> <table width="100%" height="100%" border="0" cellspacing="0" cellpadding="0"> <tr> <td style="background: #0068a6; padding-left:20; padding-top:10; white-space:nowrap;" width="110" valign="top"> <p><a href="http://www.sil.org/">  <img src="/cms/sites/nrsi/themes/default/_media/SIL_Logo_TM_Blue_2014.png" width="85" height="95" border="0" alt=""> </a><br><br></p> <p class="Cat1"><a class="Cat1" href="/cms/scripts/page.php%3Fid%3Dhome%26site_id%3Dnrsi.html">Home</a></p> <p class="Cat1"><a class="Cat1" href="/cms/scripts/page.php%3Fid%3Dcontactus%26site_id%3Dnrsi.html">Contact Us</a></p> <p class="Cat1"><a class="Cat1" href="/cms/scripts/page.php%3Fid%3Dgeneral%26site_id%3Dnrsi.html">General</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Dbabel%26site_id%3Dnrsi.html">Initiative B@bel</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Dwsi_guidelines%26site_id%3Dnrsi.html">WSI Guidelines</a></p> <p class="Cat1"><a class="Cat1" href="/cms/scripts/page.php%3Fid%3Dencoding%26site_id%3Dnrsi.html">Encoding</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Dencodingprinciples%26site_id%3Dnrsi.html">Principles</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Dunicode%26site_id%3Dnrsi.html">Unicode</a></p> <p class="Cat3"><a class="Cat3" href="/cms/scripts/page.php%3Fid%3Dunicodetraining%26site_id%3Dnrsi.html">Training</a></p> <p class="Cat3"><a class="Cat3" href="/cms/scripts/page.php%3Fid%3Dunicodetutorials%26site_id%3Dnrsi.html">Tutorials</a></p> <p class="Cat3"><a class="Cat3" href="/cms/scripts/page.php%3Fid%3Dunicodepua%26site_id%3Dnrsi.html">PUA</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Dconversion%26site_id%3Dnrsi.html">Conversion</a></p> <p class="Cat3"><a class="Cat3" href="/cms/scripts/page.php%3Fid%3Dencconvres%26site_id%3Dnrsi.html">Resources</a></p> <p class="Cat3"><a class="Cat3" href="/cms/scripts/page.php%3Fid%3Dconversionutilities%26site_id%3Dnrsi.html">Utilities</a></p> <p class="Cat4"><a class="Cat4" href="/cms/scripts/page.php%3Fid%3Dteckit%26site_id%3Dnrsi.html">TECkit</a></p> <p class="Cat3"><a class="Cat3" href="/cms/scripts/page.php%3Fid%3Dconversionmaps%26site_id%3Dnrsi.html">Maps</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Dencodingresources%26site_id%3Dnrsi.html">Resources</a></p> <p class="Cat1"><a class="Cat1" href="/cms/scripts/page.php%3Fid%3Dinput%26site_id%3Dnrsi.html">Input</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Dinputprinciples%26site_id%3Dnrsi.html">Principles</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Dinpututilities%26site_id%3Dnrsi.html">Utilities</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Dinputtutorials%26site_id%3Dnrsi.html">Tutorials</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Dinputresources%26site_id%3Dnrsi.html">Resources</a></p> <p class="Cat1"><a class="Cat1" href="/cms/scripts/page.php%3Fid%3Dtypedesign%26site_id%3Dnrsi.html">Type Design</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Dtypedesignprinciples%26site_id%3Dnrsi.html">Principles</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Dfontdesigntools%26site_id%3Dnrsi.html">Design Tools</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Dfontformats%26site_id%3Dnrsi.html">Formats</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Dtypedesignresources%26site_id%3Dnrsi.html">Resources</a></p> <p class="Cat3"><a class="Cat3" href="/cms/scripts/page.php%3Fid%3Dfontdownloads%26site_id%3Dnrsi.html">Font Downloads</a></p> <p class="Cat3"><a class="Cat3" href="/cms/scripts/page.php%3Fid%3Dfontdownloadsgentium%26site_id%3Dnrsi.html">Gentium</a></p> <p class="Cat3"><a class="Cat3" href="/cms/scripts/page.php%3Fid%3Dfontdownloadsdoulos%26site_id%3Dnrsi.html">Doulos</a></p> <p class="Cat3"><a class="Cat3" href="/cms/scripts/page.php%3Fid%3Dfontdownloadsipa%26site_id%3Dnrsi.html">IPA</a></p> <p class="Cat1"><a class="Cat1" href="/cms/scripts/page.php%3Fid%3Drendering%26site_id%3Dnrsi.html">Rendering</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Drenderingprinciples%26site_id%3Dnrsi.html">Principles</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Drenderingtechnologies%26site_id%3Dnrsi.html">Technologies</a></p> <p class="Cat3"><a class="Cat3" href="/cms/scripts/page.php%3Fid%3Drenderingopentype%26site_id%3Dnrsi.html">OpenType</a></p> <p class="Cat3"><a class="Cat3" href="/cms/scripts/page.php%3Fid%3Drenderinggraphite%26site_id%3Dnrsi.html">Graphite</a></p> <p class="Cat2"><a class="Cat2" href="/cms/scripts/page.php%3Fid%3Drenderingresources%26site_id%3Dnrsi.html">Resources</a></p> <p class="Cat3"><a class="Cat3" href="/cms/scripts/page.php%3Fid%3Dfontfaq%26site_id%3Dnrsi.html">Font FAQ</a></p> <p class="Cat1"><a class="Cat1" href="/cms/scripts/page.php%3Fid%3Dlinks%26site_id%3Dnrsi.html">Links</a></p> <p class="Cat1"><a class="Cat1" href="/cms/scripts/page.php%3Fid%3Dglossary%26site_id%3Dnrsi.html">Glossary</a></p> <br> </td> <td valign="top" style="padding:0" xwidth="650"> <div style="background: #6699CC url(/cms/sites/nrsi/themes/default/_media/home_banner_gradient.gif) no-repeat right; padding:0 0 0 25; height:36px; margin:0; color:#FFFFFF;"> <p style="font-family:Times New Roman; font-size:25px; color:#FFFFFF; padding:10 0 0 0; margin:0 0 0 0">Computers & Writing Systems</p> </div> <div style="padding:0 0 0 0; background-color:#000000; color:#FFFFFF"> <table width='100%'> <tr> <td style="padding: 0 0 0 25px"><a class="GlobalNavLink" href="http://www.sil.org/">SIL HOME</a> | <a class="GlobalNavLink" href="https://software.sil.org/products/">SIL SOFTWARE</a> | <a class="GlobalNavLink" href="/support.html">SUPPORT</a> | <a class="GlobalNavLink" href="https://www.givedirect.org/donate/?cid=13536">DONATE</a> | <a class="GlobalNavLink" href="/privacy-policy.html">PRIVACY POLICY</a> </td> <td align='right' width='20%'> <script async src="https://cse.google.com/cse.js?cx=0760bf09a6bff4b0c"></script><style>.gsc-control-cse {padding: 0.6em; min-width: 10em; width: 18em; max-width: 20em} form.gsc-search-box {display: unset;}</style><div class="gcse-search"></div> </td> </tr> </table> </div> <div style="padding:0 25 25 25"> <p class='CategoryPath'>You are here: <a class='CategoryPath' href='/cms/scripts/page.php%3Fid%3Dgeneral%26site_id%3Dnrsi.html'>General</a> > <a class='CategoryPath' href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines%26site_id%3Dnrsi.html'>WSI Guidelines</a><br> Short URL: <a href='/wsi_guidelines_sec_8.html'>https://scripts.sil.org/WSI_Guidelines_Sec_8</a></p>   <h1>Guidelines for Writing System Support: Technical Details: Glyph Design </h1> <p> <span class='author_date_hits'>Victor Gaultney, 2003-09-05</span></p><div class='Sidebar'><p><span class='Runin'>UNESCO project Initiative B@bel</span></p> <p>A complete index of all SIL's contributions to UNESCO‘s project Initiative B@bel can be found <a href='/cms/scripts/page.php%3Fid%3Dbabel%26site_id%3Dnrsi.html'>here</a>.</p> </div><p></p> <div class='Sidebar'><p><span class='Runin'>Guidelines Table of Contents</span></p> <p><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_1%26site_id%3Dnrsi.html'>Section 1: Components of a Writing System Implementation</a></p> <p><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_2%26site_id%3Dnrsi.html'>Section 2: The Process of WSI Development</a></p> <p><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_3%26site_id%3Dnrsi.html'>Section 3: Roles and Actors</a></p> <p><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_4%26site_id%3Dnrsi.html'>Section 4: Keys to Success</a></p> <p><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_5_1%26site_id%3Dnrsi.html'>Section 5: Technical Details: Characters, Codepoints, Glyphs</a></p> <ul class='dListUnordered'> <li><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_5_1%26site_id%3Dnrsi.html'>Part 1: Characters</a></li> <li><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_5_2%26site_id%3Dnrsi.html'>Part 2: Codepoints and Glyphs</a></li> <li><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_5_3%26site_id%3Dnrsi.html'>Part 3: Keystrokes and Codepoints</a></li> <li><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_5_4%26site_id%3Dnrsi.html'>Part 4: Further Reading</a></li> </ul> <p><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_6_1%26site_id%3Dnrsi.html'>Section 6: Technical Details: Encoding and Unicode</a></p> <ul class='dListUnordered'> <li><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_6_1%26site_id%3Dnrsi.html'>Part 1: An Introduction to Encodings</a></li> <li><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_6_2%26site_id%3Dnrsi.html'>Part 2: An Introduction to Unicode</a></li> <li><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_6_3%26site_id%3Dnrsi.html'>Part 3: Adding New Characters and Scripts to Unicode</a></li> </ul> <p><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_7%26site_id%3Dnrsi.html'>Section 7: Technical Details: Data Entry and Editing</a></p> <p><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_8%26site_id%3Dnrsi.html'>Section 8: Technical Details: Glyph Design</a></p> <p><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_9_1%26site_id%3Dnrsi.html'>Section 9: Technical Details: Smart Rendering</a></p> <ul class='dListUnordered'> <li><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_9_1%26site_id%3Dnrsi.html'>Part 1: The Rendering Process</a></li> <li><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_9_2%26site_id%3Dnrsi.html'>Part 2: Glyph Processing — Dumb Fonts</a></li> <li><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_9_3%26site_id%3Dnrsi.html'>Part 3: Glyph Processing — Smart Fonts</a></li> <li><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_9_4%26site_id%3Dnrsi.html'>Part 4: User Interaction</a></li> </ul> <p><a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_glossary%26site_id%3Dnrsi.html'>Glossary</a></p> </div><p></p> <p class='TOCTitle'>Contents</p> <div class='TOC'> <ol> <li class='TOC2'><a href='#b6837f31'>8.1   Basic font requirements</a></li> <li class='TOC2'><a href='#7c7f1a06'>8.2   The need for quality</a></li> <li class='TOC2'><a href='#d023f347'>8.3   Sources for fonts</a> <ol> <li class='TOC3'><a href='#1c10e6a1'>8.3.1   Commercial companies</a></li> <li class='TOC3'><a href='#e212d93f'>8.3.2   Public and not-for-profit</a></li> <li class='TOC3'><a href='#5c37dd26'>8.3.3   Freeware/shareware</a></li> <li class='TOC3'><a href='#39ad1f44'>8.3.4   Intellectual property and copyright issues</a></li> </ol> </li> <li class='TOC2'><a href='#eac5e6c4'>8.4   Process of font development</a> <ol> <li class='TOC3'><a href='#8dc5ac03'>8.4.1   Initial research and planning</a></li> <li class='TOC3'><a href='#2fe8a2ef'>8.4.2   Glyph design procedures</a></li> <li class='TOC3'><a href='#e8453776'>8.4.3   Testing</a></li> </ol> </li> <li class='TOC2'><a href='#36b46512'>8.5   Conclusion</a></li> <li class='TOC2'><a href='#0b4eb81d'>8.6   Sources for information</a> <ol> <li class='TOC3'><a href='#9e76e408'>8.6.1   Tools</a></li> <li class='TOC3'><a href='#217187dc'>8.6.2   Web sites</a></li> <li class='TOC3'><a href='#8e6d2c79'>8.6.3   Publications</a></li> </ol> </li> <li class='TOC2'><a href='#988a35df'>8.7  References</a></li> </ol> </div> <p></p> <p></p> <p>The most basic computing need for a given writing system is a font. Without one, a WSI cannot exist, and the quality and accuracy of the letters is commonly how WSIs are judged. This section addresses the need for quality fonts and how they can be obtained, developed and improved. Specifics about “smart” fonts and their behavior are covered in <a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_9_1%26site_id%3Dnrsi.html'>Section 9</a>. A general glossary of font terminology can be found on the <a href='https://www.microsoft.com/typography/glossary/content.htm' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> Microsoft Typography web site</a>. </p> <a name='b6837f31'></a> <h2>8.1   Basic font requirements</h2> <p>The purpose of a font is to correctly display text in a language using the appropriate writing system. At a minimum, this requires the font to be complete and accurate for the language(s) covered by the font. Technically, this means that a font must:</p> <ul class='dListUnordered'> <li><span class='Em'>Contain all necessary glyphs for the writing system</span>. For example, many African writing systems use the letter <img src='/cms/sites/nrsi/media/eng_9x13.png' height='13' width='9'> to signify the sound ‘ng’ as in the English word ‘sing’. It is not enough to have the letters ‘n’ and ‘g’ in the font and display them in place of the <img src='/cms/sites/nrsi/media/eng_9x13.png' height='13' width='9'>, the special symbol needs to be present in the font.</li> <li><span class='Em'>Display glyphs accurately</span>. Each glyph needs to be the right shape according to the requirements of the writing system. Although two languages may share the same basic system, each may have particular preferences over how certain glyphs are shaped. The font needs to accommodate these cultural preferences, which can include different preferences in spacing. For example, Thai is normally written without word breaks, whereas some minority languages that use the Thai script prefer that word spaces be used. There can also be differences in how much space is preferred between words and even letters. Finally, diacritics and other marks must be oriented correctly relative to the base glyphs.</li> <li><span class='Em'>Support a useful encoding</span>. The font needs to be encoded according to some agreed standard, whether that be a proprietary encoding for a particular application, or an international standard such as Unicode. If a glyph is not accessible to the application, then it is as if the glyph did not exist at all. The choice of which standard to support is closely related to the individual WSI, although Unicode should be the default choice in most situations.</li> </ul> <a name='7c7f1a06'></a> <h2>8.2   The need for quality</h2> <p>WSIs are typically created by programmers or linguists, not typeface designers. Even though the computational complexity required to make a WSI work may be impressive, most WSIs suffer from fonts that are poor in quality, and may result in documents that are difficult or unpleasant to read. This is because most of the typeface design is done by those untrained in the task.</p> <p>Typeface design is a subtle art, and the details of how lettershapes are shaped and interact are complex. So it is very valuable to consult experienced designers in the development of a WSI, and integrate their recommendations into the implementation. </p> <p>It is a mistake to assume that language communities with little experience in technology will be satisfied with anything that only somewhat resembles their script. On the contrary, these readers are often more sophisticated and exacting than their counterparts who use the Latin script. For example, in Asia, there is a long history of writing, literacy and literature in many beautiful, indigenous scripts. Because of this strong manuscript tradition, the expectation is that fonts ought to closely follow traditional shapes. Yes, there is openness to modern interpretations, and a recognition of technical limitations, but satisfaction is usually linked with how faithfully the design echoes the tradition.</p> <p>The history of Bengali typefaces illustrates this phenomenon. Bengali type has been available since 1778, and the printed history of the script is full of attempts to recreate the characteristic shapes with new technology. By the mid-20th century, the major font foundries, Monotype and Linotype, had systems that could typeset books and newspapers successfully. But both, and the Linotype in particular, had to make significant compromises in the rendering of the script due to technical limitations. Nevertheless, the general Bengali population seemed satisfied with the result. When new technology became available in the late 1970s, Linotype developed a new typeface that recreated the traditional style and forms that hearkened back to the manuscript tradition. Despite predictions that no one would accept it—they seemed satisfied with what they had—it became very successful and is now considered to be the definitive design for Bengali fonts. Nothing else is generally accepted for text material.<span class='footnote_ref'><a href='#footnote_1' name='_ftnref_1'>1</a></span></p> <p>WSI development needs to take into account the need for typefaces that accurately reflect the writing style and acknowledge the written history of the script. Because of the complex tools and subtle design sense required to create fonts, it is a specialized craft. Rarely do those who develop keyboards, encoding systems and other programmatic WSI components have the skills and training necessary, and so they must look elsewhere for fonts.</p> <a name='d023f347'></a> <h2>8.3   Sources for fonts</h2> <p><span class='Em'>So where can quality typefaces be found?</span> Traditional foundries as well as individual developers have designed good fonts for non-Latin writing systems. Generally, those companies with a long tradition of quality design offer the best fonts, but charge accordingly for them. Free fonts can be found all over the internet, but most lack in completeness and overall quality. There are exceptions to both of these, so it is worth investigating a variety of sources.</p> <a name='1c10e6a1'></a> <h3>8.3.1   Commercial companies</h3> <p>Most commercial font vendors are not multi-faceted corporations, but are smaller companies focused solely on font development. As such, they rely on sales of their typefaces as their primary income source. Hence, their products can be expensive, and incorporation of their fonts in other WSIs requires payment of significant licensing fees. Their fonts are usually of good quality, though, and have high acceptance within language communities. Some of these companies are:</p> <p></p> <ul class='dListUnordered'> <li><a href='http://www.monotype.com/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>Monotype</span></a>, <a href='http://www.linotype.com/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>Linotype</span></a>, <a href='http://www.adobe.com/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>Adobe</span></a>. These traditional font foundries have a long history of design excellence. Monotype, in particular, has a library of non-Latin fonts that is second to none in design quality, and often serves as the standard by which others are judged. Adobe is the youngest of this group, and has relatively few non-Latin fonts, but is a quality foundry. All three are open to licensing their fonts to others for inclusion in WSIs.</li> <li><a href='http://developer.apple.com/fonts/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>Apple</span></a>, <a href='http://www.microsoft.com/typography/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>Microsoft</span></a>. Though not recognized as font foundries in their own right, they both do significant font development. Most of their designs are licensed from Linotype or Monotype, but they do use local font providers, and work with the foundries to add extra features, such as additional glyphs or smart font programming to make the fonts work in their operating systems. Although these companies will not license their fonts to others, many of the fonts are shipped as standard components of their software. This means that WSI developers may be able to create solutions that assume that certain fonts will be present. Although not ideal, this is one option for developers<span class='footnote_ref'><a href='#footnote_2' name='_ftnref_2'>2</a></span>.</li> <li><a href='http://www.linguistssoftware.com/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>Linguist’s Software</span></a>, <a href='http://www.xenotypetech.com/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>Xenotype</span></a>. These companies, and others like them, specialize in fonts and WSIs for less-common languages. They tend to fill in the gaps around traditional foundries, and provide an alternative to other commercial fonts. Linguist’s Software has an impressive list of available fonts, and their products tend to be very complete and tailored to academic users. Like Xenotype, though, the quality of their designs vary widely. They may, however, be the only commercially available font for a particular script.</li> </ul> <a name='e212d93f'></a> <h3>8.3.2   Public and not-for-profit</h3> <p>An alternative to commercial fonts are those developed by public and non-for-profit agencies. The goal of these groups is to enable technological advancement and literature production in both majority and minority writing systems. Their fonts are generally free for individual use, but may require modest licensing fees for inclusion in third-party WSIs. Font quality among these groups varies widely, but is often good. Because of their close association with language communities, these agencies tend to develop products that accurately reflect linguistic needs and preferences, and meet practical publishing needs. </p> <p>There are only a few instances where governments have specifically developed and distributed fonts, but government-sponsored agencies can have an active role. <a href='http://www.nectec.or.th/home/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> The National Electronics and Computer Technology Center (NECTEC)</a> in Thailand has led many of the computing efforts in that country, and has developed fonts that match the preferred style for text publishing.</p> <p>More work is done by NGOs. These organizations range in size from small to large, and those differences are reflected in how widely their fonts are known. Many NGO fonts are developed and deployed locally, usually by untrained designers, and are not known outside of the language communities. Larger groups, such as SIL International<span class='footnote_ref'><a href='#footnote_3' name='_ftnref_3'>3</a></span>, have a broader scope, have greater resources (including trained designers), and are able to take on major font development projects.</p> <a name='5c37dd26'></a> <h3>8.3.3   Freeware/shareware</h3> <p>Although most public and not-for-profit fonts are inexpensive or free, there is also a large and growing body of freeware and shareware fonts developed by individuals and distributed over the internet. Most of these are incomplete, inaccurate, of poor design quality, or do not function correctly, and are poor choices for inclusion in WSIs. </p> <p>A small subset of these fonts, however, may be suitable. Internet searches can be successful in finding freeware fonts, and may even bring up reviews or comments on specific fonts. There are also many guides to non-Western fonts; three of these are:</p> <p></p> <ul class='dListUnordered'> <li><a href='http://scriptsource.org/finding_software' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> Finding Software on ScriptSource</a> — a collection of links to fonts and software</li> <li><a href='http://www.alanwood.net/unicode/fonts.html' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> Alan Wood’s Unicode Resources</a></li> </ul> <a name='39ad1f44'></a> <h3>8.3.4   Intellectual property and copyright issues</h3> <p>One of the challenges of incorporating third-party fonts in WSIs relates to intellectual property and copyright issues. It is not always easy to determine the true source of a font design. Many fonts on the internet are simply illegal versions of commercial fonts. So it is important to look at the copyright notice within the fonts, and even ask the developer where the design originated.</p> <p>Fonts often need modification to work with a specific WSI or to meet the needs of a specific language community. It is important to know the licensing restrictions of any fonts that are modified. Many commercial and some public groups prohibit any modification, however minor. Others give their fonts very broad, open-source-style licensing.</p> <p>The related paper “Intellectual Property Concerns in the Development of Complex Script and Language Resources” gives much more detail on these issues and discusses the unique nature of fonts as both works of art and pieces of computer software.</p> <a name='eac5e6c4'></a> <h2>8.4   Process of font development</h2> <p>Despite the wide variety of fonts available from commercial and non-commercial sources, there remain situations where a new font design is needed. No font may exist, or those that are available may be inappropriate because of style or quality. There also may be licensing restrictions that hinder the use or modification of a particular font. </p> <p>If significant funding is available, fonts can be commissioned from professional designers. Traditional foundries, such as Monotype, have a long history of this, but most recent commissions go to individuals or small foundries such as <a href='http://www.tiro.com/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> Tiro Typeworks</a>, who are known for a specific area of expertise. Internet mailing lists, such as <a href='http://gmunch.home.pipeline.com/typo-L/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> TYPO-L</a> and <a href='http://type-design.p90.net/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> Type-Design</a> can also be a means to find designers interested in work, and professional associations such as <a href='http://www.atypi.org/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> ATypI</a> can help.</p> <p>The font development process, whether done by a foundry or by an individual, is similar to the WSI development process outlined in <a href='/cms/scripts/page.php%3Fid%3Dwsi_guidelines_sec_2%26site_id%3Dnrsi.html'>Section 2</a>. </p> <a name='8dc5ac03'></a> <h3>8.4.1   Initial research and planning</h3> <p>Careful planning is important to a font project’s success. Because the designer is often someone without an intimate knowledge of the writing system, they need reliable information from others about letter shapes, style and behavior. The basic steps are to:</p> <p><span class='Em'>Determine detailed needs</span>. A font project needs a clear specification of all the glyphs needed and how they are to be encoded. This description will likely change as more information is discovered, but some initial listing is useful. The designer will also need to know how the glyphs are to interact with one another: how diacritics relate to base characters, common and uncommon letter combinations, etc. An orthography description, if available, can be very helpful.</p> <p><span class='Em'>Identify key script experts</span>. The most important source for script information is the language community itself and the script experts within. These should be people whom the community recognizes as authoritative with regard to the written language—scribes, teachers, leaders, artists. Ongoing interaction with these experts can ensure that the font accurately reflects the writing system and meets the needs of the community.</p> <p><span class='Em'>Gather other sources and references</span>. It is not enough to simply talk with script experts. Samples of the writing system are needed. There should be a variety of these—handwritten samples, school primers, existing books—and the script experts should give their opinion on which are the most ‘correct’. The internet can also be a source of information, but is often misleading or wrong. Published books and academic research are often more reliable and can provide useful historical background. Finally, electronic versions of authentic text material (folktales, etc.), if they exist, can be useful in testing.</p> <p><span class='Em'>Make style decisions</span>. Most language communities would love to have more than a single style of font for their use. This raises priority questions and requires some additional investigation. <span class='Em'>What will be the primary use of the font—long document publishing, literacy primers, signage, on-screen reading (such as on the internet)?</span> The use should be reflected in the style of the font. Tradition is also important. <span class='Em'>Is an ‘italic’ version needed for a script with no history of slanted forms?</span> The answer is sometimes yes and sometimes no. For example, the Ethiopic script traditionally has a single style of letterform, a bold letter with calligraphic elements. <span class='Em'>Is it appropriate to create an italic version? And is an even bolder form even conceivable?</span> There is no tradition of this, but the availability of the Bold and Italic buttons in word processing applications encourages users to desire these modern variants.</p> <div class='mediacontainer'> <img src='/cms/sites/nrsi/media/Eth_Se_173x55.png' height='55' width='173'> </div> <br clear='left'> <br> <p></p> <a name='2fe8a2ef'></a> <h3>8.4.2   Glyph design procedures</h3> <p>Once planning is complete, and key style decisions are made, the design of glyphs can begin. Designers vary in their preferred design process. Some draw their glyphs directly on screen, while others prefer to draw shapes on paper and then bring them into the computer. In order to give a complete picture of what could be involved in the design process, the latter situation is described here. This is, again, only an example of the process and is not a definitive method.</p> <p><span class='Em'>Drawing</span>. After study of the writing system, and the intended use for the font, the designer draws tentative lettershapes on paper, with a height of typically 2-5 cm. The lettershapes may be drawn as complete words, as an alphabet sample, or as seemingly random combinations of letters. The main goal is not to create final, perfect forms, but to experiment with stroke weights, terminal designs, initial spacing and general proportions.</p> <p><span class='Em'>Scanning</span>. Once these initial shapes have been drawn, they are scanned into the computer, preferably at a resolution of approximately 300-400 pixels in height. Any scanning software would work for this, as long as the scanned image can be cropped and imported into the font design package. Detailed instructions on how prepare, scan and import images into the Macromedia Fontographer font design program can be found in <a href='http://www.sil.org/~gaultney/Hints/scan.html' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>Scanning Tips</span></a>.</p> <p><span class='Em'>Initial digital outlines</span>. Digital fonts are typically described not in terms of pixels, but as mathematical curves that define the outline of the glyph. So the scanned images are used only as a guideline for the preparation of the outlines. Once the scanned images are imported into the font design application, the designer can begin to draw initial outlines of a few key glyphs, based generally on the drawn and scanned shapes. These are tentative, and will likely be changed throughout the next step.</p> <p><span class='Em'>Refining parameters</span>. After the basic shapes have been drawn, the designer can create draft fonts in order to test glyph size, weight, etc., and then revise the draft shapes repeatedly until they look generally correct. At the end of this process, there should be specific parameters determined for the font—letter height, stroke widths, length of serifs, amount of contrast, and other numeric guidelines.</p> <p><span class='Em'>Completing the glyph set</span>. The next step is to design the remaining glyphs, based upon the style and parameters of the initial key glyphs. </p> <p><span class='Em'>Adjusting spacing</span>. Good spacing can improve a mediocre typeface, but bad spacing can ruin a beautiful one. Great care must be taken to ensure that letters are spaced properly. This includes kerning for pairs of letters that, because of their design, would run into one another or leave large gaps of whitespace between them. The goal is to create a flowing, uninterrupted line of text with even texture. This is important for readability, especially for beginning readers.</p> <p><span class='Em'>Hinting</span>. Legibility of letters on computer screens, or on low-resolution printing devices, is heavily dependent on ‘hints’ contained in the font<span class='footnote_ref'><a href='#footnote_4' name='_ftnref_4'>4</a></span>. These are special computer instructions that specify how the mathematical outlines are turned into pixels. Hinting is a highly technical task, and most independent designers avoid it due to the time and expertise it requires. Modern font development applications include auto-hinting routines that can improve a font’s appearance on screen, but the results are not as good as manual hinting. For more discussion on hinting strategies, see <a href='/cms/scripts/page.php%3Fid%3Dnotesonhintingwithfl%26site_id%3Dnrsi.html'><span class='Em'>Notes on Hinting with FontLab</span></a>.</p> <p><span class='Em'>Packaging and distribution</span>. This involves packaging the font and any related documentation and instructions for the user or for those who are building the font into a larger WSI or software application.</p> <a name='e8453776'></a> <h3>8.4.3   Testing</h3> <p>Although testing is usually done throughout the whole font design process, it also needs to be done once the font is generally completed, with all glyphs designed and spaced. There are four kinds of testing:</p> <p></p> <ul class='dListUnordered'> <li><span class='Em'>technical</span>—to see if it works with other WSI components and in the appropriate software environments</li> <li><span class='Em'>internal designer</span>—the kind done by the designer during the design process</li> <li><span class='Em'>external designer</span>—review by another designer or colleague to inspect the glyphs for design problems</li> <li><span class='Em'>script expert</span>—review done by experts in the writing system in order to ensure accuracy and general satisfaction throughout the language community</li> </ul> <a name='36b46512'></a> <h2>8.5   Conclusion</h2> <p>Fonts are critical WSI components. Font design, however, is a complicated task, and requires artistic as well as analytical skills. Most WSI developers do not have the expertise to design their own fonts, and need to look to other sources. There are many companies and individuals who will license fonts and even prepare new designs on commission. Despite this, it is sometimes necessary for a WSI developer to take on the task.</p> <a name='0b4eb81d'></a> <h2>8.6   Sources for information</h2> <p>The following are sources for information on fonts and typeface design.</p> <a name='9e76e408'></a> <h3>8.6.1   Tools</h3> <p>Many of these tools come from FontLab Ltd., a company that has become the main font tool provider for the font design industry.</p> <p><a href='http://www.fontmaster.nl/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>DTL Fontmaster</span></a>—specialized, but expensive tools for design and font production</p> <p><a href='http://www.high-logic.com/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>Font Creator</span></a>—a little known, and limited, TrueType font editor</p> <p><a href='http://www.fontlab.com' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>FontLab</span></a>—the font design tool that has become the industry standard</p> <p><a href='http://www.macromedia.com/software/fontographer/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>Fontographer</span></a>—this was the main design tool, but has not been updated in many years and is rapidly becoming obsolete</p> <p><a href='http://www.fontlab.com/html/scanfont.html' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>Scanfont</span></a>—a tool for scanning drawn glyphs and importing them into FontLab</p> <p><a href='http://www.fontlab.com/html/transtype.html' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>TransType</span></a>—a font converter</p> <p><a href='http://www.fontlab.com/html/typetool.html' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>TypeTool</span></a>—a lightweight, and cheaper, version of FontLab</p> <p>Microsoft and Apple also provide font development tools on their Web sites. See <a href='#websites'>section 8.6.2</a>.</p> <p>A large number of copyleft, FLOSS and open source tools are listed in <a href='/cms/scripts/page.php%3Fid%3Dfloss%26site_id%3Dnrsi.html'>Resources for Writing Systems Implementation using Copyleft and FLOSS (Free/Libre and Open Source Software)</a>.</p> <a name='websites'></a> <a name='217187dc'></a> <h3>8.6.2   Web sites</h3> <p><a href='http://www.adobe.com/type/topics/main.html' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>Adobe Type Topics</span></a>—a variety of information on Adobe fonts and general type issues</p> <p><a href='http://developer.apple.com/fonts/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>Apple Fonts/Tools</span></a>—technical information and tools from Apple Computer</p> <p><a href='http://www.microsoft.com/typography/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>Microsoft Typography</span></a>—excellent site about the technical aspects of type design and Microsoft’s tools</p> <p><a href='http://www.truetype.demon.co.uk/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> <span class='Em'>TrueType Typography</span></a>—general information about the TrueType font format</p> <a name='8e6d2c79'></a> <h3>8.6.3   Publications</h3> <p>Bringhurst, Robert, <span class='Em'>The elements of typographic style</span>. (2nd ed), Point Roberts: WA, Hartley & Marks, 1996. This is a general reference to use of fonts and type, but can be useful to anyone studying design.</p> <p>Moye, Stephen, <span class='Em'>Fontographer: type by design</span>. MIS Press, 1995. Though out of print, this book is a useful guide to type design processes. It is specifically for Fontographer, but can be applicable to other tools.</p> <p>Tracy, Walter, <span class='Em'>Letters of credit: a view of type design</span>. London: Gordon Fraser, 1986. This is the best book on the foundational concepts behind type design, and gives particularly good advice on spacing Latin fonts.</p> <p>The <a href='http://www.typebooks.org/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> TypeBooks</a> web site is a good source for books and reviews.</p> <a name='988a35df'></a> <h2>8.7  References</h2> <p>[ROS1999] Fiona Ross, <span class='bib_title'>The Printed Bengali Character and its Evolution.</span>London: Curzon Press, 1999.</p> <div class='Note'><p class='Note_heading'>Copyright notice</p><p>(c) Copyright 2003 UNESCO and SIL International Inc.</p> </div> <br><hr clear='all'><p>Note: the opinions expressed in submitted contributions below do not necessarily reflect the opinions of our website.</p><hr> <hr align='left' class='footnote_rule'><table> <tr> <td class='footnote_number' align='top'><a href='#_ftnref_1' name='footnote_1'>1</a></td> <td class=footnote_text>See [ROS1999]</td> </tr> <tr> <td class='footnote_number' align='top'><a href='#_ftnref_2' name='footnote_2'>2</a></td> <td class=footnote_text>It should be noted, though, that these companies do not allow their fonts to be modified in any way, or distributed outside the operating system.</td> </tr> <tr> <td class='footnote_number' align='top'><a href='#_ftnref_3' name='footnote_3'>3</a></td> <td class=footnote_text><a href='http://www.sil.org/' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> http://www.sil.org/</a> and <a href='/'>https://scripts.sil.org/</a></td> </tr> <tr> <td class='footnote_number' align='top'><a href='#_ftnref_4' name='footnote_4'>4</a></td> <td class=footnote_text>A general description of hinting can be found at <a href='http://www.microsoft.com/typography/hinting/hinting.htm' target='_blank'><img src='/cms/assets/icons/offsite_link.png'> http://www.microsoft.com/typography/hinting/hinting.htm</a></td> </tr> </table> <hr> <p><small>© 2003-2024 <a href='http://www.sil.org/' target='_blank'>SIL International</a>, all rights reserved, unless otherwise noted elsewhere on this page.<br> Provided by SIL's Writing Systems Technology team (formerly known as NRSI). Read our <a href="/privacy-policy.html">Privacy Policy</a>. <a href='/support.html'>Contact us here.</a></small></p> </div> </td> </table> </body> </html>