oldstandard (23dec20)

git-svn-id: svn://tug.org/texlive/trunk@57210 c570f23f-e606-0410-a88d-b1316a301751

25 files changed, 652 insertions, 3364 deletions

diff --git a/Master/texmf-dist/doc/fonts/oldstandard/FONTLOG-2.2.txt b/Master/texmf-dist/doc/fonts/oldstandard/FONTLOG.txt
index 8ea2eb65337..53fd7a5dc50 100644
--- a/Master/texmf-dist/doc/fonts/oldstandard/FONTLOG-2.2.txt
+++ b/Master/texmf-dist/doc/fonts/oldstandard/FONTLOG.txt
@@ -43,69 +43,128 @@ lettertype of the early 20th century.
 
 ChangeLog
 ---------
+
+2020 December 18 (Robert Alessi) Version 2.6
+
+    * Added 2nd pointer to Alexey Kryukov's archived webpage.
+
+    * Added and updated FONTLOG.txt (this file).
+
+    * New file: OldStandard.fontspec. Slanted shapes for regular and bold are
+      now available through the 'FakeSlant' feature of fontspec.
+
+    * Updated naming schemes in BoldItalic. Thanks to Jontxo Reig for
+      testing.
+
+2020 February 24 (Robert Alessi) Version 2.5
+
+    * Updated documentation and makefile.
+
+    * Better g caron.
+
+    * Added missing small capitals Ā, Ī and Ū.
+
+    * Added font table.
+
+    * Reset all hinting information and instructions.
+
+    * Removed duplicate c2sc and smcp rules.
+
+    * Added small capitals for all Greek accented letters.
+
+2019 July 26 (Robert Alessi) Version 2.4a
+
+    * Reshaped macron, acute, grave and j in BoldItalic.
+
+2019 July 25 (Robert Alessi) Version 2.4
+
+    * Added auto-generated BoldItalic.
+
+2019 July 24 (Robert Alessi) Version 2.3 (1.0 in the current git repo)
+
+    * Fixed missing direction in U+2023.
+
+    * fixed missing control points, wrong coordinates and directions
+      in OldStandardT-Italic.sfd.
+
+    * Added g caron.
+
+    * Added small capitals in Regular (French, German, Italian,
+      Spanish, Basic Russian and Arabic DMG).
+
+    * Make +ss06 work if beta is preceded by a vowel with an accute
+      accent taken from the Greek Extended Unicode block.
+
 2011 April 30 (Alexey Kryukov) Version 2.2
 
-    * Latin Extended Additional (again, except Vietnamese and medievalist additions)
-      for Bold and Italic.
+    * Latin Extended Additional (again, except Vietnamese and
+      medievalist additions) for Bold and Italic.
 
-    * More punctuation characters, including New Testament critical signs.
+    * More punctuation characters, including New Testament critical
+      signs.
 
-    * New implementation for the 'frac' feature: it is now possible to build
-      any arbitrary fractions rather than just those available in Unicode in the
-      precomposed form.
+    * New implementation for the 'frac' feature: it is now possible to
+      build any arbitrary fractions rather than just those available
+      in Unicode in the precomposed form.
 
-    * SIL's Graphite rendering technologie is now supported. The features available
-      are mostly the same as for OpenType, but there are some additions (in
-      particular it is possible to render a Greek text with accents above capitals).
-      The manual has also been changed to reflect the new functionality.
+    * SIL's Graphite rendering technologie is now supported. The
+      features available are mostly the same as for OpenType, but
+      there are some additions (in particular it is possible to render
+      a Greek text with accents above capitals).  The manual has also
+      been changed to reflect the new functionality.
 
-    * Cosmetic glyph changes (foots/arms in Cyrillic 'Ka', 'Zhe', 'Ya' in
-      particular).
+    * Cosmetic glyph changes (foots/arms in Cyrillic 'Ka', 'Zhe', 'Ya'
+      in particular).
 
-    * Added human-readable stylistic set names (US English only) and style
-      (sub-family) names in a few additional languages.
+    * Added human-readable stylistic set names (US English only) and
+      style (sub-family) names in a few additional languages.
 
-    * The fonts are now available also in the WOFF format to simplify embedding
-      into web pages.
+    * The fonts are now available also in the WOFF format to simplify
+      embedding into web pages.
 
 2009 November 18 (Alexey Kryukov) Version 2.1 (not released)
 
-    * The "Greek and Coptic" Unicode range is now fully covered, except Coptic
-      letters. The epigraphic letters have been implemented in a simple sans-serif
-      style: I don't like "creativity" if it can result in producing urecognizable
-      glyphs.
-
-    * Regular and bold: New alternate glyphs for Cyrillic IE (U+0415/U+0435) and
-      Ukrainian IE (U+0404/U+0454), used by default for Church Slavonic. The intent
-      is to make Old Cyrillic YEST clearly distinguishable both from Latin E and
-      "wide" YEST.
-
-    * New glyphs for CYRILLIC SMALL LETTER MONOGRAPH UK (in all 3 styles).
-
-    * I have implemented a k-shaped kappa in all three styles, a script rho in
-      regular and bold and a rho with straignt tail in italic. These characters
-      (except the script rho) are kept unencoded and can be accessed via the 'mgrk'
-      feature tag. I don't think they would be very useful, but at least it is now
-      possible to use Old Standard for typesetting a copy of the Unicode Greek
-      codechart (I needed one for a book I was preparing).
-
-    * Multiple cosmetic glyph changes. In particular Latin capital "C", "E", "F",
-      "G", "L" and related glyphs have got heavier vertical serifs in the regular font.
-      Cedilla is redesigned (once again) in regular and bold. Shapes of some Greek
-      letters (including alternate beta and theta) have also been improved.
-
-    * I no longer use custom PUA mappings. I have preserved PUA codepoints for
-      a few standard glyphs (including capital accents) previously mapped there
-      by Adobe, as well as for additional accented Greek characters implemented
-      for compatibility with Ralph Hancock's fonts. Everything else has been moved
-      outside the encoding.
-
-    * Oops. I was wrong regarding "zhe with breve": this letter actually
-      should be formed with a standard (Latin) breve rather than a Cyrillic
-      telephone receiver-like accent. BTW I think rhis letter should be
-      available in the font: since I already support historical Romanian
-      characters, the modern Moldavian Cyrillic alphabet should be supported
-      as well.
+    * The "Greek and Coptic" Unicode range is now fully covered,
+      except Coptic letters. The epigraphic letters have been
+      implemented in a simple sans-serif style: I don't like
+      "creativity" if it can result in producing urecognizable glyphs.
+
+    * Regular and bold: New alternate glyphs for Cyrillic IE
+      (U+0415/U+0435) and Ukrainian IE (U+0404/U+0454), used by
+      default for Church Slavonic. The intent is to make Old Cyrillic
+      YEST clearly distinguishable both from Latin E and "wide" YEST.
+
+    * New glyphs for CYRILLIC SMALL LETTER MONOGRAPH UK (in all 3
+      styles).
+
+    * I have implemented a k-shaped kappa in all three styles, a
+      script rho in regular and bold and a rho with straignt tail in
+      italic. These characters (except the script rho) are kept
+      unencoded and can be accessed via the 'mgrk' feature tag. I
+      don't think they would be very useful, but at least it is now
+      possible to use Old Standard for typesetting a copy of the
+      Unicode Greek codechart (I needed one for a book I was
+      preparing).
+
+    * Multiple cosmetic glyph changes. In particular Latin capital
+      "C", "E", "F", "G", "L" and related glyphs have got heavier
+      vertical serifs in the regular font.  Cedilla is redesigned
+      (once again) in regular and bold. Shapes of some Greek letters
+      (including alternate beta and theta) have also been improved.
+
+    * I no longer use custom PUA mappings. I have preserved PUA
+      codepoints for a few standard glyphs (including capital accents)
+      previously mapped there by Adobe, as well as for additional
+      accented Greek characters implemented for compatibility with
+      Ralph Hancock's fonts. Everything else has been moved outside
+      the encoding.
+
+    * Oops. I was wrong regarding "zhe with breve": this letter
+      actually should be formed with a standard (Latin) breve rather
+      than a Cyrillic telephone receiver-like accent. BTW I think rhis
+      letter should be available in the font: since I already support
+      historical Romanian characters, the modern Moldavian Cyrillic
+      alphabet should be supported as well.
 
     * The regular font now includes most accented characters from the
       Latin Extended Additional range (but not Vietnamese).
@@ -120,58 +179,61 @@ ChangeLog
     * Implemented Roman numerals and ancient Roman epigraphic letters
       (including Claudian letters).
 
-    * Switched to lookup-based representation of the OpenType data
-      in the source files to conform the new FontForge's file format;
+    * Switched to lookup-based representation of the OpenType data in
+      the source files to conform the new FontForge's file format;
 
-    * Now both cubic and quadratic versions of the font outlines are stored
-      in the same source files (one file for each style), as FontForge's
-      new approach to multilayered fonts allows this;
+    * Now both cubic and quadratic versions of the font outlines are
+      stored in the same source files (one file for each style), as
+      FontForge's new approach to multilayered fonts allows this;
 
     * Switched to OFL version 1.1;
 
     * FontForge now can generate reasonably good TTF instructions (it
-      could not when OldStandard v. 1.0 was released). So the TTF fonts
-      are now automatically instructed with FontForge. I still include
-      the old instructions for the regular version (prepared with
-      Peter Baker's xgridfit utility) into the source package, but they
-      are no longer used in the font itself. This certainly makes some
-      glyphs look worse, but improves the overall performance of the font
-      (especially in the antialiased mode);
+      could not when OldStandard v. 1.0 was released). So the TTF
+      fonts are now automatically instructed with FontForge. I still
+      include the old instructions for the regular version (prepared
+      with Peter Baker's xgridfit utility) into the source package,
+      but they are no longer used in the font itself. This certainly
+      makes some glyphs look worse, but improves the overall
+      performance of the font (especially in the antialiased mode);
 
-    * Danish Aringacute redesigned (now has the acute at the top of the ring
-      and a specially designed, reduced in size, diacritic for the capital
-      glyph);
+    * Danish Aringacute redesigned (now has the acute at the top of
+      the ring and a specially designed, reduced in size, diacritic
+      for the capital glyph);
 
-    * Redesigned cedilla and all combinations with this accent in the upright
-      font;
+    * Redesigned cedilla and all combinations with this accent in the
+      upright font;
 
     * More contour cleanup;
 
     * Added accented combinations with "W" for Welsh;
 
-    * Added several new math characters to the regular font. The intent was
-      to fully cover the TeX OMS encoding, but this task is still far from
-      being reached;
+    * Added several new math characters to the regular font. The
+      intent was to fully cover the TeX OMS encoding, but this task is
+      still far from being reached;
 
-    * There is now a dedicated Unicode codepoint for capital insular "G"
-      (U+A77D), so move the corresponding glyph to that location;
+    * There is now a dedicated Unicode codepoint for capital insular
+      "G" (U+A77D), so move the corresponding glyph to that location;
 
-    * Corrected the shape of Greek symbol phi (U+03D5). It is still not
-      recommended to use this glyph instead of the normal (looped) form;
+    * Corrected the shape of Greek symbol phi (U+03D5). It is still
+      not recommended to use this glyph instead of the normal (looped)
+      form;
 
-    * Several new characters have been added, including the Latin letter EZH
-      (U+01B7/U+0292) and capital Es Zett for German (U+1E9E). There are
-      some new combining marks as well;
+    * Several new characters have been added, including the Latin
+      letter EZH (U+01B7/U+0292) and capital Es Zett for German
+      (U+1E9E). There are some new combining marks as well;
 
-    * I used to consider the breve accent should always take the typically
-      Cyrillic form when used after Cyrillic letters. However this assumption
-      seems to be wrong: the specific form of the diacritic is actually
-      an attribute of just three letters, i. e. "short i" (Russian etc.),
-      "Short u" (Byelorussian) and "zhe with breve" (Moldavian).
+    * I used to consider the breve accent should always take the
+      typically Cyrillic form when used after Cyrillic
+      letters. However this assumption seems to be wrong: the specific
+      form of the diacritic is actually an attribute of just three
+      letters, i. e. "short i" (Russian etc.), "Short u"
+      (Byelorussian) and "zhe with breve" (Moldavian).
 
 2007 July 14 (Alexey Kryukov) Version 1.1 (not released)
 
-    * Added Latin letters OPEN E and OPEN O, requested by an African user;
+    * Added Latin letters OPEN E and OPEN O, requested by an African
+      user;
 
     * New glyph for ampersand in the upright font;
 
@@ -190,32 +252,32 @@ ChangeLog
 2006 December 12 (Alexey Kryukov) Version 0.9
 
     * Added a few more Latin Extended-B characters, yogh and wynn in
-      particular (thanks to Peter Baker for the valuable information on the
-      design of the letter yogh he provided). I also have implemented
-      uppercase and lowercase versions of the insular "g". Thus Old
-      Standard is now suitable for typesetting texts in Old and Middle
-      English.
+      particular (thanks to Peter Baker for the valuable information
+      on the design of the letter yogh he provided). I also have
+      implemented uppercase and lowercase versions of the insular
+      "g". Thus Old Standard is now suitable for typesetting texts in
+      Old and Middle English.
 
-    * Added Hebrew aleph and a few Fraktur characters, useful for critical
-      apparatus, especially in Bible/New Testament editions.
+    * Added Hebrew aleph and a few Fraktur characters, useful for
+      critical apparatus, especially in Bible/New Testament editions.
 
     * Implemented a full set of standard f-ligatures, present in most
       OpenType fonts.
 
     * Andrew Panov has convinced me to implement a set of mathematical
       glyphs, designed in the style of traditional Russian math
-      typesetting. These glyphs are currently available only in the regular
-      version of the font.
+      typesetting. These glyphs are currently available only in the
+      regular version of the font.
 
     * A PDF manual, explaining various features of the font, is now
       available.
 
     * Greek sampi (both uppercase and lowercase) has been redesigned.
 
-    * Implemented Greek lunate epsilon and reversed lunate epsilon (the
-      design doesn't match the remaining Greek letters though). Thus all
-      Unicode slots intended for "alternate" and mathematical Greek glyphs
-      are now covered.
+    * Implemented Greek lunate epsilon and reversed lunate epsilon
+      (the design doesn't match the remaining Greek letters
+      though). Thus all Unicode slots intended for "alternate" and
+      mathematical Greek glyphs are now covered.
 
     * A few improvements in the TTF instructions for the regular font
       (drop-out control has been enabled).
@@ -224,26 +286,28 @@ ChangeLog
 
 2006 October 01 (Alexey Kryukov) Version 0.8
 
-    * Implemented a set of TrueType instructions (hints) for the regular
-      font (italics are still unhinted). I would like to thank Peter Baker
-      for his excellent (and extremely well documented) xgridfit program
-      (http://xgridfit.sourceforge.net), which provides a good Open Source
-      solution for gridfitting, or "hinting," TrueType fonts.
+    * Implemented a set of TrueType instructions (hints) for the
+      regular font (italics are still unhinted). I would like to thank
+      Peter Baker for his excellent (and extremely well documented)
+      xgridfit program (http://xgridfit.sourceforge.net), which
+      provides a good Open Source solution for gridfitting, or
+      "hinting," TrueType fonts.
 
-    * The TrueType version of the regular font now has a separate source
-      file (OldStandard.ttf.sfd) with quadratic splines.
+    * The TrueType version of the regular font now has a separate
+      source file (OldStandard.ttf.sfd) with quadratic splines.
 
-    * Changed the naming convention for the TrueType version: the font name
-      now has a "TT" suffix, so that both TTF and OTF versions can be
-      installed on the same system simultaneously.
+    * Changed the naming convention for the TrueType version: the font
+      name now has a "TT" suffix, so that both TTF and OTF versions
+      can be installed on the same system simultaneously.
 
     * Added a few Latin Extended-B characters, useful mainly for
-      germanists, in particular "b" with bar, "o" with ogonek and hwair.
-      Also I have corrected shapes of lowercase eth and thorn. Thus Old
-      Standard now includes all characters necessary for representing Old
-      Icelandic texts and Gothic transliteration. Still more characters
-      (the most important of them being uppercase and lowercase yogh) are
-      needed for a proper support of Old/Middle English.
+      germanists, in particular "b" with bar, "o" with ogonek and
+      hwair.  Also I have corrected shapes of lowercase eth and
+      thorn. Thus Old Standard now includes all characters necessary
+      for representing Old Icelandic texts and Gothic
+      transliteration. Still more characters (the most important of
+      them being uppercase and lowercase yogh) are needed for a proper
+      support of Old/Middle English.
 
     * As usual, a few minor bugs have been corrected.
 
@@ -262,23 +326,24 @@ ChangeLog
     * Added Greek glyphs, including those in the U+1F00--U+1FFF "Greek
       Extended" Unicode range.
 
-    * Ukrainian and Serbian Cyrillic glyphs were redesigned in order to
-      bring them into a better correspondance with real examples of
+    * Ukrainian and Serbian Cyrillic glyphs were redesigned in order
+      to bring them into a better correspondance with real examples of
       the early 20th century printing.
 
     * The standard mathematical operation signs were redesigned and
-      significantly enlarged, so that now their implementation contradicts
-      to the contemporary standards, but better corresponds to the European
-      tradition of math typesetting.
+      significantly enlarged, so that now their implementation
+      contradicts to the contemporary standards, but better
+      corresponds to the European tradition of math typesetting.
 
-    * Several additional math characters, needed to provide a full coverage
-      for the Mac Roman encoding, have been added.
+    * Several additional math characters, needed to provide a full
+      coverage for the Mac Roman encoding, have been added.
 
     * Ancient Greek metrical characters (U+23D1--U+23D9) have been
       implemented.
 
-    * A TTF version is released in addition to OpenType-CFF fonts. It has
-      no hinting at all, so don't complain for bad screen rendering!
+    * A TTF version is released in addition to OpenType-CFF fonts. It
+      has no hinting at all, so don't complain for bad screen
+      rendering!
 
 2006 Feb 14 (Alexey Kryukov) Version 0.2
 
@@ -299,3 +364,8 @@ For more information please visit the Fonts page on Thessalonica's
 website: http://www.thessalonica.org.ru/en/fonts.html.
 
 Or send an email to <alexios at thessalonica dot org dot ru>.
+
+N: Robert Alessi
+E: alessi@robertalessi.net
+W: http://www.robertalessi.net
+D: Current maintainer of Old Standard
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/OFL-FAQ.txt b/Master/texmf-dist/doc/fonts/oldstandard/OFL-FAQ.txt
index e744366483a..24854178ec7 100644
--- a/Master/texmf-dist/doc/fonts/oldstandard/OFL-FAQ.txt
+++ b/Master/texmf-dist/doc/fonts/oldstandard/OFL-FAQ.txt
@@ -1,225 +1,435 @@
 OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL)
-Version 1.1 - 26 February 2007
+Version 1.1-update5 - April 2017
+The OFL FAQ is copyright (c) 2005-2017 SIL International.
 (See http://scripts.sil.org/OFL for updates)
 
 
-1  ABOUT USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
+CONTENTS OF THIS FAQ
+1  USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
+2  USING OFL FONTS FOR WEB PAGES AND ONLINE WEB FONT SERVICES
+3  MODIFYING OFL-LICENSED FONTS
+4  LICENSING YOUR ORIGINAL FONTS UNDER THE OFL
+5  CHOOSING RESERVED FONT NAMES
+6  ABOUT THE FONTLOG
+7  MAKING CONTRIBUTIONS TO OFL PROJECTS
+8  ABOUT THE LICENSE ITSELF
+9  ABOUT SIL INTERNATIONAL
+APPENDIX A - FONTLOG EXAMPLE
 
-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  USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
 
-1.2  Can I make web pages using these fonts?
-Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended.
+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?
+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.
 
-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, rename Modified Versions, do not abuse the Author(s)' name(s) and do not sublicense).
+1.1.1  Does that restrict the license or distribution of that artwork?
+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).
 
-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.1.2  Is any kind of acknowledgement required?
+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.
 
-1.5  I want to distribute the fonts with my program. Does this mean my program also has to be free 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.2  Can the fonts be included with Free/Libre and Open Source Software collections such as GNU/Linux and BSD distributions and repositories?
+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 section 5.9 about rebuilding from source.)
 
-1.6  Can I include the fonts on a CD of freeware or commercial fonts?
+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?
+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.4  Can I sell a software package that includes these fonts?
+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: word processors, design and publishing applications, training and educational software, games and entertainment software, mobile device applications, etc.
+
+1.5  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.6  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 honour and respect their contribution!
+
+1.7  What about sharing OFL fonts with friends on a CD, DVD or USB stick?
+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.
+
+1.8  Can I host the fonts on a web site for others to use?
+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 web fonts in Section 2.
+
+1.9  Can I host the fonts on a server for use over our internal network?
+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.
+
+1.10  Does the full OFL license text always need to accompany the font?
+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 http://scripts.sil.org/OFL, 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.
+
+1.11  What do you mean by 'embedding'? How does that differ from other means of distribution?
+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.
+
+1.12  So can I embed OFL fonts in my document?
+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.
+
+1.13  Does embedding alter the license of the document itself?
+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 OFL does not make the resulting artwork subject to the OFL.
+
+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)?
+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.
+
+1.15  What about distributing fonts with a document? Within a compressed folder structure? Is it distribution, bundling or embedding?
+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.
+
+1.16  What about ebooks shipping with open fonts?
+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.
+
+1.17  Can Font Software released under the OFL be subject to URL-based access restrictions methods or DRM (Digital Rights Management) 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, 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.
+
+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?
+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.
+
+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?
+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 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.
+
+1.20 I'm writing a small app for mobile platforms, do I need to include the whole package? 
+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.
+
+1.21 What about including OFL fonts by default in my firmware or dedicated operating system? 
+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.
+
+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?
+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 1.4 for details and examples about selling bundles).
+
+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?
+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.
+
+1.24  Can services that provide or distribute OFL fonts restrict my use of them?
+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.
+
+
+2  USING OFL FONTS FOR WEBPAGES AND ONLINE WEB FONT SERVICES
+
+NOTE: This section often refers to a separate paper on 'Web Fonts & RFNs'. This is available at http://scripts.sil.org/OFL_web_fonts_and_RFNs
+
+2.1  Can I make webpages using these fonts?
+Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended. Your three best options are: 
+- referring directly in your stylesheet to open fonts which may be available on the user's system
+- providing links to download the full package of the font - either from your own website or from elsewhere - so users can install it themselves
+- using @font-face to distribute the font directly to browsers. This is recommended and explicitly allowed by the licensing model because it is distribution. The font file itself is distributed with other components of the webpage. It is not embedded in the webpage but referenced through a web address which will cause the browser to retrieve and use the corresponding font to render the webpage (see 1.11 and 1.15 for details related to embedding fonts into documents). As you take advantage of the @font-face cross-platform standard, be aware that web fonts are often tuned for a web environment and not intended for installation and use outside a browser. The reasons in favour of using web fonts are to allow design of dynamic text elements instead of static graphics, to make it easier for content to be localized and translated, indexed and searched, and all this with cross-platform open standards without depending on restricted extensions or plugins. You should check the CSS cascade (the order in which fonts are being called or delivered to your users) when testing.
+
+2.2  Can I make and use WOFF (Web Open Font Format) versions of OFL fonts?
+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 format, however, it is possible to create a WOFF version that is not considered modification, and so would not require a name change. 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.
+
+If the original font data or metadata is changed, or the WOFF-specific metadata is incomplete, the font must be considered a Modified Version, the OFL restrictions would apply and the name of the font must be changed: any RFNs cannot be used and copyright notices and licensing information must be included and cannot be deleted or modified. You must come up with a unique name - we recommend one corresponding to your domain or your particular web application. Be aware that only the original author(s) can use RFNs. This is to prevent collisions between a derivative tuned to your audience and the original upstream version and so to reduce confusion.
+
+Please note that most 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.
+
+2.3  What about other web font formats such as EOT/EOTLite/CWT/etc.?
+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 http://scripts.sil.org/OFL_web_fonts_and_RFNs 
+
+2.4  Can I make OFL fonts available through web font online services?
+Yes, you are welcome to include OFL fonts in online web font 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 1.17 for details related to URL-based access restrictions methods or DRM mechanisms).
+
+2.5  Some web font formats and services provide ways of "optimizing" the font for a particular website or web application; is that allowed? 
+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.
 
-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!
+2.6  Is subsetting a web font considered modification?
+Yes. Removing any parts of the font when delivering a web font 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 2.8 and http://scripts.sil.org/OFL_web_fonts_and_RFNs
 
-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.
+2.7  Are there any situations in which a modified web font could use RFNs?
+Yes. If a web font is optimized only in ways that preserve Functional Equivalence (see 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 web font service or provider to sign a separate agreement with the author(s) that allows the use of RFNs for Modified Versions.
 
-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.
+2.8  How do you know if an optimization to a web font preserves Functional Equivalence?
+Functional Equivalence is described in full in the 'Web fonts and RFNs' paper at http://scripts.sil.org/OFL_web_fonts_and_RFNs, in general, an optimized font is deemed to be Functionally Equivalent (FE) to the Original Version if it:
 
+- 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 web page, will display properly. 
+- 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.
+- Presents text with no obvious degradation in visual quality. The lettershapes should be equally (or more) readable, within limits of the rendering platform.
+- 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.
 
-2  ABOUT MODIFYING OFL LICENSED FONTS
+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.
 
-2.1  Can I change the fonts? Are there any limitations to what things I can and cannot change?
-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 add additional information into it that covers your contribution.
+2.9  Isn't use of web fonts another form of embedding?
+No. Unlike embedded fonts in a PDF, web fonts 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 web fonts used by a document may be identified and downloaded for desktop use demonstrates that they are philosophically and technically separate from the web pages that specify them. See http://scripts.sil.org/OFL_web_fonts_and_RFNs
 
-2.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?
+2.10  So would it be better to not use RFNs at all if you want your font to be distributed by a web fonts service?
+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 web font services. If that web font 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.
+
+2.11  What should an agreement for the use of RFNs say? Are there any examples?
+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 web font services to clearly state when they have established such agreements, so that the public understands clearly that their service is operating appropriately.
+
+See the separate paper on 'Web Fonts & RFNs' for in-depth discussion of issues related to the use of RFNs for web fonts. This is available at http://scripts.sil.org/OFL_web_fonts_and_RFNs
+
+
+3  MODIFYING OFL-LICENSED FONTS
+
+3.1  Can I change the fonts? Are there any limitations to what things I can and cannot change?
+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.)
+
+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?
 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.
 
-2.3  Can I charge people for my additional work? In other words, if I add a bunch of special glyphs and/or OpenType/Graphite code, can I sell the enhanced font?
+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?
 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.
 
-2.4  Can I pay someone to enhance the fonts for my use and distribution?
-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 benefitted from the contributions of others.
+3.4  Can I pay someone to enhance the fonts for my use and distribution?
+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.
 
-2.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?
-No. If you redistribute a Modified Version of the font it must be under the OFL. You may not restrict it in any way. 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 benefitted from the contributions of others.
+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?
+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.
 
-2.6  Do I have to make any derivative fonts (including source files, build scripts, documentation, etc.) publicly available?
-No, but please do share your improvements with others. You may find that you receive more than what you gave in return.
+3.6  Do I have to make any derivative fonts (including extended source files, build scripts, documentation, etc.) publicly available?
+No, but please consider sharing your improvements with others. You may find that you receive in return more than what you gave.
 
-2.7  Why can't I use the Reserved Font Name(s) in my derivative font names? I'd like people to know where the design came from.
-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 Name(s) 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. 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.
+3.7  If a trademark is claimed in the OFL font, does that trademark need to remain in modified fonts?
+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.
 
-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.
+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? 
+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.
 
-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".
+4  LICENSING YOUR ORIGINAL FONTS UNDER THE OFL
 
-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.
+4.1  Can I use the SIL OFL for my own fonts?
+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.
 
-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).
+4.2  What do I have to do to apply the OFL to my font?
+If you want to release your fonts under the OFL, we recommend you do the following:
 
-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.
+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.
 
-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.
+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 web site 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.
 
+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).
 
-3  ABOUT THE FONTLOG
+4.2.4  Include the relevant practical documentation on the license by adding the current OFL-FAQ.txt file in your package.
 
-The FONTLOG can take a variety of formats, but should include these four sections:
+4.2.5  If you wish you can use the OFL graphics (http://scripts.sil.org/OFL_logo) on your website. 
 
-3.1  FONTLOG for <FontFamilyName>
-This file provides detailed information on the <FontFamilyName> font software. This information should be distributed along with the <FontFamilyName> fonts and any derivative works.
+4.3  Will you make my font OFL for me?
+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. 
 
-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.)
+4.4  Will you distribute my OFL font for me?
+No, although if the font is of sufficient quality and general interest we may include a link to it on our partial list of OFL fonts on the OFL web site. You may wish to consider other open font catalogs or hosting services, such as the Unifont Font Guide (http://unifont.org/fontguide), The League of Movable Type (http://theleagueofmovabletype.com) or the Open Font Library (http://openfontlibrary.org/), which despite the name has no direct relationship to the OFL or SIL. 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. 
 
-3.3  ChangeLog
-(This should list both major and minor changes, most recent first. Here are some examples:)
+4.5  Why should I use the OFL for my fonts?
+- to meet needs for fonts that can be modified to support lesser-known languages
+- to provide a legal and clear way for people to respect your work but still use it (and reduce piracy)
+- to involve others in your font project
+- to enable your fonts to be expanded with new weights and improved writing system/language support
+- to allow more technical font developers to add features to your design (such as OpenType, Graphite or AAT support)
+- to renew the life of an old font lying on your hard drive with no business model
+- to allow your font to be included in Libre Software operating systems like Ubuntu
+- to give your font world status and wide, unrestricted distribution
+- to educate students about quality typeface and font design
+- to expand your test base and get more useful feedback 
+- to extend your reach to new markets when users see your metadata and go to your website
+- to get your font more easily into one of the web font online services
+- to attract attention for your commercial fonts
+- to make money through web font services
+- to make money by bundling fonts with applications
+- to make money adjusting and extending existing open fonts
+- to get a better chance that foundations/NGOs/charities/companies who commission fonts will pick you 
+- to be part of a sharing design and development community 
+- to give back and contribute to a growing body of font sources
 
-7 February 2007 (Pat Johnson) <NewFontFamilyName> Version 1.3
-- Added Greek and Cyrillic glyphs
-- Released as "<NewFontFamilyName>"
 
-7 March 2006 (Fred Foobar) <NewFontFamilyName> Version 1.2
-- Tweaked contextual behaviours
-- Released as "<NewFontFamilyName>"
+5  CHOOSING RESERVED FONT NAMES
 
-1 Feb 2005 (Jane Doe) <NewFontFamilyName> 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 "<NewFontFamilyName>"
+5.1  What are Reserved Font Names?
+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.
 
-1 Jan 2005 (Joe Smith) <FontFamilyName> Version 1.0
-- Initial release of font "<FontFamilyName>"
+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.
+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.
 
-3.4  Acknowledgements
-(Here is where contributors can be acknowledged. 
+5.3  What do you mean by "primary name as presented to the user"? Are you referring to the font menu name?
+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. 
 
-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.)
+5.4  Am I not allowed to use any part of the Reserved Font Names?
+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.
 
-N: Jane Doe
-E: jane@university.edu
-W: http://art.university.edu/projects/fonts
-D: Contributor - Armenian glyphs and code
+5.5  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 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.
 
-N: Fred Foobar
-E: fred@foobar.org
-W: http://foobar.org
-D: Contributor - misc Graphite fixes
+5.6  Do I, as an author, have to identify any Reserved Font Names?
+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 web fonts see section 2.
 
-N: Pat Johnson
-E: pat@fontstudio.org
-W: http://pat.fontstudio.org
-D: Designer - Greek & Cyrillic glyphs based on Roman design
+5.7  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).
 
-N: Tom Parker
-E: tom@company.com
-W: http://www.company.com/tom/projects/fonts
-D: Engineer - original smart font code
+5.8  Is there any situation in which I can use Reserved Font Names for a Modified Version?
+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 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. 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.
+
+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?
+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 own 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.
+
+5.10  Can I add other Reserved Font Names when making a derivative font?
+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.
 
-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.)
+6  ABOUT THE FONTLOG
 
+6.1  What is this FONTLOG thing exactly?
+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!
 
-4  ABOUT MAKING CONTRIBUTIONS
+6.2  Is the FONTLOG required?
+It is not a requirement of the license, but we strongly recommend you have one.
 
-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.
+6.3  Am I required to update the FONTLOG when making Modified Versions?
+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, such as the FONTLOG support in FontForge.
 
-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.
+6.4  What should the FONTLOG look like?
+It is typically a separate text file (FONTLOG.txt), but can take other formats. It commonly includes these four sections:
 
-4.3  How can I financially support the development of OFL fonts?
+- brief header describing the FONTLOG itself and name of the font family
+- Basic Font Information - description of the font family, purpose and breadth
+- ChangeLog - chronological listing of changes
+- Acknowledgements - list of authors and contributors with contact information
+
+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.
+
+
+7  MAKING CONTRIBUTIONS TO OFL PROJECTS
+
+7.1  Can I contribute work to OFL projects?
+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.
+
+7.2  Why should I contribute my changes back to the original authors?
+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.
+
+7.3  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, 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.
+
+7.4  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
+8  ABOUT THE LICENSE ITSELF
 
-5.1  I see that this is version 1.1 of the license. Will there be later changes?
+8.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.
+8.2  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 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.
+
+8.3  Is the OFL a contract or a license?
+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.
 
-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.
+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?
+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-2017 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.
 
-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.
+8.5  Can I quote from the OFL FAQ?
+Yes, SIL gives permission to quote from the OFL FAQ (OFL-FAQ.txt), in whole or in part, provided that the quoted text is:
 
-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.
+- unmodified,
+- used to help explain the intent of the OFL, rather than cause misunderstanding, and
+- accompanied with the following attribution: "From the OFL FAQ (OFL-FAQ.txt), copyright (c) 2005-2017 SIL International. Used by permission. http://scripts.sil.org/OFL-FAQ_web".
 
-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.
+8.6  Can I translate 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 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.
 
-We give permission to publish unofficial translations into other languages provided that they comply with the following guidelines:
+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.
 
-- put the following disclaimer in both English and the target language stating clearly that the translation is unofficial:
+SIL gives permission to publish unofficial translations into other languages provided that they comply with the following guidelines:
 
-"This is an unofficial translation of the SIL Open Font License into $language. 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.
+- Put the following disclaimer in both English and the target language stating clearly that the translation is unofficial:
 
-However, we recognize that this unofficial translation will help users and designers not familiar with English to understand the SIL OFL better and make it easier to use and release font families under this collaborative font design model. We encourage designers who consider releasing their creation under the OFL to read the FAQ in their own language if it is available.
- 
-Please go to http://scripts.sil.org/OFL for the official version of the license and the accompanying FAQ."
+"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 http://scripts.sil.org/OFL for the official version of the license and the accompanying OFL-FAQ."
 
-- 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.  
+- 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 a unofficial translation effort of the OFL and its accompanying FAQ please let us know, thank you.
+If you start such a unofficial translation effort of the OFL and OFL-FAQ please let us know.
 
+8.7 Does the OFL have an explicit expiration term?
+No, the implicit intent of the OFL is that the permissions granted are perpetual and irrevocable. 
 
-6  ABOUT SIL INTERNATIONAL
 
-6.1  Who is SIL International and what does it do?
-SIL International is a worldwide faith-based education and development organization (NGO) that studies, documents, and assists in developing the world's lesser-known languages through literacy, linguistics, translation, and other academic disciplines. 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.
+9  ABOUT SIL INTERNATIONAL
 
-6.2  What does this have to do with font licensing?
-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 FLOSS community.
+9.1  Who is SIL International and what do they do?
+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.
 
-6.3  How can I contact SIL?
+9.2  What does this have to do with font licensing?
+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.
+
+9.3  How can I contact SIL?
 Our main web site is: http://www.sil.org/
 Our site about complex scripts is: http://scripts.sil.org/
-Information about this license (including contact email information) is at: http://scripts.sil.org/OFL
+Information about this license (and contact information) is at: http://scripts.sil.org/OFL
+
+
+APPENDIX A - FONTLOG EXAMPLE
+
+Here is an example of the recommended format for a FONTLOG, although other formats are allowed.
 
+-----
+FONTLOG for the GlobalFontFamily fonts
 
-7  ABOUT USING THE OFL FOR YOUR ORIGINAL 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.
 
-If you want to release your fonts under the OFL, you only need to do the following:
+Basic Font Information
 
-7.1  Put your copyright and reserved font names information in the beginning of the main OFL file.
-7.2  Put your copyright and the OFL references in your various font files (such as in the copyright, license and description fields) and in your other components (build scripts, glyph databases, documentation, rendering samples, etc).
-7.3  Write an initial FONTLOG for your font and include it in the release package.
-7.4  Include the OFL in your release package.
-7.5  We also highly recommend you include the relevant practical documentation on the license by putting the OFL-FAQ in your package.
-7.6  If you wish, you can use the OFL Graphics on your web page.
+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...
 
-That's all. If you have any more questions please get in touch with us.
+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 trunk version)
+- 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: 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
 
+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...
+-----
 
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/OFL.txt b/Master/texmf-dist/doc/fonts/oldstandard/OFL.txt
index 0465ff4d116..db85e267e7e 100644
--- a/Master/texmf-dist/doc/fonts/oldstandard/OFL.txt
+++ b/Master/texmf-dist/doc/fonts/oldstandard/OFL.txt
@@ -1,11 +1,12 @@
-Copyright (c) 2006-2008, Alexey Kryukov 
-(<http://www.thessalonica.org.ru|alexios@thessalonica.org.ru>).
-All rights reserved.
+Copyright (c) 2006-2011 Alexey Kryukov (<amkryukov@gmail.com>),
+without Reserved Font Names.
 
-This Font Software is licensed under the SIL Open Font License, Version 1.1.
-This license is copied below, and is also available with a FAQ at:
-http://scripts.sil.org/OFL
+Copyright (c) 2019-2020, Robert Alessi (<alessi@robertalessi.net>),
+without Reserved Font Names.
 
+This Font Software is licensed under the SIL Open Font License,
+Version 1.1.  This license is copied below, and is also available with
+a FAQ at: http://scripts.sil.org/OFL
 
 -----------------------------------------------------------
 SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/OldStandard.fontspec b/Master/texmf-dist/doc/fonts/oldstandard/OldStandard.fontspec
new file mode 100644
index 00000000000..95ae5d4ddbd
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/oldstandard/OldStandard.fontspec
@@ -0,0 +1,13 @@
+\defaultfontfeatures[Old Standard]
+        {
+	Extension           = .otf,
+	UprightFont         = OldStandard-Regular,
+	ItalicFont          = OldStandard-Italic,
+	BoldFont            = OldStandard-Bold,
+	BoldItalicFont      = OldStandard-BoldItalic,
+	SlantedFont         = OldStandard-Regular,
+	SlantedFeatures     = {FakeSlant=0.25},
+	BoldSlantedFont     = OldStandard-Bold,
+	BoldSlantedFeatures = {FakeSlant=0.25}
+        }
+
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/README b/Master/texmf-dist/doc/fonts/oldstandard/README
index 0f24068a685..051559e8a3b 100644
--- a/Master/texmf-dist/doc/fonts/oldstandard/README
+++ b/Master/texmf-dist/doc/fonts/oldstandard/README
@@ -1,5 +1,5 @@
-This is the README for the OldStandard package, version 2.5,
-release 2020-05-30.
+This is the README for the OldStandard package, version 2.6,
+release 2020-12-23.
 
 This package provides the Old Standard family of fonts
 designed by Alexey Kryukov and revised by Robert Alessi, 
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/README.md b/Master/texmf-dist/doc/fonts/oldstandard/README.md
new file mode 100644
index 00000000000..436ce26b082
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/oldstandard/README.md
@@ -0,0 +1,78 @@
+Old Standard
+============
+
+License
+-------
+Copyright (c) 2006-2011 Alexey Kryukov (<amkryukov@gmail.com>),
+without Reserved Font Names.
+
+Copyright (c) 2019-2020, Robert Alessi (<alessi@robertalessi.net>),
+without Reserved Font Names.
+
+Please send error reports and suggestions for improvements to Robert
+Alessi:
+
+  * email: <alessi@roberalessi.net>
+  * website: <http://git.robertalessi.net/oldstandard/about>
+  * development: <http://git.robertalessi.net/oldstandard>
+  * comments, feature requests, bug reports: <https://gitlab.com/ralessi/oldstandard/issues>
+
+
+This Font Software is licensed under the SIL Open Font License,
+Version 1.1.  This license is available with a FAQ at:
+<http://scripts.sil.org/OFL>
+
+History
+-------
+This font is just the same as Alexey Kryukov's beautiful *Old
+Standard*.[^1] In comparison to the previous releases of *Old
+Standard*, it includes new letters and some corrections:
+
+1. Small capitals for Roman, Greek and Cyrillic letters, in all three
+   styles, Regular, Italic and Bold have been added. Small capitals,
+   which were missing from *Old Standard*, were already in use a
+   century ago in fine books which used font faces very similar to
+   *Old Standard*. Typical use cases of small capitals were headers,
+   current headings and in some books proper names.
+2. *For the time being*, a bold italic shape has been
+   auto-generated. Of course, auto-generating shapes is not a
+   satisfactory solution. However, it is better than using the font
+   loader to emulate bold shapes. A real bold italic shape is planned
+   in the versions of *Old Standard* to come.
+3. The letter G with caron above, that is: Ǧ (`U+01E6`, uppercase) and
+   ǧ (`U+01E7`, lowercase) has been added. It is the only character
+   missing from *Old Standard* that is needed in some of the accepted
+   standards of romanization of classical Arabic.[^2]
+4. Additionally, this release corrects the `+ss06` feature provided by
+   *Old Standard*. This feature is supposed to distinguish between
+   regular and ‘curled’ beta (β/ϐ) and to print ‘curled’ beta
+   (`U+03D0`) in medial position. This feature worked in most cases
+   with the previous release of *Old Standard*. However, it failed if
+   the beta is preceded by a vowel with an acute accent taken from the
+   *Greek extended* Unicode block.
+
+### Why a new release of *Old Standard*?
+At the time of writing, *Old Standard* was last updated six years
+ago. Being unable himself to contact the author, the writer, while in
+need to have new letters included in *Old Standard* and some issues
+addressed, took the decision to make a new release of *Old Standard*,
+while maintaining the hope that the author will one day resume the
+development of this typeface.
+
+### Reference web page (archived on Sept. 26, 2019)
+[http://thessalonica.org.ru/en/oldstandard.html](https://web.archive.org/web/20190926123235/http://thessalonica.org.ru/en/oldstandard.html)
+
+Documentation
+-------------
+Please refer to Alexey Kryukov's documentation which is can be found
+here:
+<http://mirrors.ctan.org/fonts/oldstandard/doc/oldstand-manual.pdf>
+(CTAN) or here:
+[http://thessalonica.org.ru/en/fonts-download.html](https://web.archive.org/web/20190924110631/http://thessalonica.org.ru/en/fonts-download.html) (Alexey
+Kryukov's web page).
+
+[^1]: See <https://github.com/akryukov/oldstand>
+
+[^2]: See for references the [current documentation of the arabluatex
+     package](http://mirrors.ctan.org/macros/luatex/latex/arabluatex/arabluatex.pdf),
+     sect. “Transliteration”.
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/didot-de.png b/Master/texmf-dist/doc/fonts/oldstandard/didot-de.png
deleted file mode 100644
index da117512683..00000000000
--- a/Master/texmf-dist/doc/fonts/oldstandard/didot-de.png
+++ /dev/null
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/didot-fr.png b/Master/texmf-dist/doc/fonts/oldstandard/didot-fr.png
deleted file mode 100644
index a39b0085a9c..00000000000
--- a/Master/texmf-dist/doc/fonts/oldstandard/didot-fr.png
+++ /dev/null
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/fonttable.pdf b/Master/texmf-dist/doc/fonts/oldstandard/fonttable.pdf
index 68477b96354..76daaf8834d 100644
--- a/Master/texmf-dist/doc/fonts/oldstandard/fonttable.pdf
+++ b/Master/texmf-dist/doc/fonts/oldstandard/fonttable.pdf
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/fonttable.tex b/Master/texmf-dist/doc/fonts/oldstandard/fonttable.tex
index f1b2814c8a2..5e90225f7b9 100644
--- a/Master/texmf-dist/doc/fonts/oldstandard/fonttable.tex
+++ b/Master/texmf-dist/doc/fonts/oldstandard/fonttable.tex
@@ -1,3 +1,6 @@
+% arara: lualatex
+% arara: lualatex
+% arara: lualatex
 \documentclass[12pt]{article}
 \usepackage{fontspec}
 
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/gendocs.sh b/Master/texmf-dist/doc/fonts/oldstandard/gendocs.sh
deleted file mode 100644
index 9cb47268bcb..00000000000
--- a/Master/texmf-dist/doc/fonts/oldstandard/gendocs.sh
+++ /dev/null
@@ -1,12 +0,0 @@
-#!/bin/bash
-
-ZIP="zip -DrX"
-PACK_NAME=oldstand-manual
-VERSION="2.0"
-
-rm -f *.toc *.aux *.out
-xelatex $PACK_NAME.tex
-xelatex $PACK_NAME.tex
-rm -f *.zip
-
-$ZIP $PACK_NAME.src.zip gendocs.sh $PACK_NAME.tex *.png
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/greek-contextual.png b/Master/texmf-dist/doc/fonts/oldstandard/greek-contextual.png
deleted file mode 100644
index 249e7808ec8..00000000000
--- a/Master/texmf-dist/doc/fonts/oldstandard/greek-contextual.png
+++ /dev/null
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/oldstand-manual.pdf b/Master/texmf-dist/doc/fonts/oldstandard/oldstand-manual.pdf
deleted file mode 100644
index 47a77947757..00000000000
--- a/Master/texmf-dist/doc/fonts/oldstandard/oldstand-manual.pdf
+++ /dev/null
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/oldstand-manual.tex b/Master/texmf-dist/doc/fonts/oldstandard/oldstand-manual.tex
deleted file mode 100644
index b9d9e05953a..00000000000
--- a/Master/texmf-dist/doc/fonts/oldstandard/oldstand-manual.tex
+++ /dev/null
@@ -1,3064 +0,0 @@
-\documentclass[12pt,a4paper,openany]{book}
-
-\usepackage{OldStandard}
-
-\usepackage{xunicode}
-%\usepackage{xltxtra}
-\defaultfontfeatures{Mapping=tex-text}
-\usepackage{polyglossia}
-\setdefaultlanguage{english}
-\setotherlanguage[variant=ancient]{greek}
-\setotherlanguage{russian}
-
-
-\hoffset=-1in
-\voffset=-1in
-\oddsidemargin=30mm
-\evensidemargin=20mm
-\textwidth=160mm
-\textheight=240mm
-
-\catcode"2019=12
-\lccode"2019="2019
-
-\usepackage{array}
-\usepackage{longtable}
-\newcolumntype{B}[1]{>{\large\bfseries}c{#1}}
-\newcolumntype{T}[1]{>{\ttfamily}l{#1}}
-\usepackage[colorlinks=true]{hyperref}
-
-\usepackage{float}
-\restylefloat{table}
-
-\providecommand{\XeTeX}{X\kern-.125em\lower.5ex\hbox{Ǝ}\kern-.1667em\TeX}
-\providecommand{\XeLaTeX}{X\kern-.125em\lower.5ex\hbox{Ǝ}\kern-.125em\LaTeX}
-\providecommand{\LuaTeX}{Lua\kern-.125em\TeX}
-
-\newcommand{\ie}{i.\,e.}
-\newcommand{\eg}{e.\,g.}
-\renewcommand{\omit}[1]{}
-
-\makeatletter
-\renewcommand\tableofcontents{%
-\chapter*{\contentsname}%
-\thispagestyle{empty}
-\markboth{Table of contents}{Table of contents}
-\@starttoc{toc}%
-}
-\makeatother
-\sloppy
-
-\begin{document}
-
-\pagestyle{empty}
-
-\vspace*{\stretch{0.4}}
-
-\begin{center}
-
-{\fontsize{48}{56}\selectfont OLD STANDARD}
-
-\bigskip
-
-{\huge A Unicode Font\\ for Classical and Medieval Studies
-
-}
-
-\bigskip
-
-\rule{\textwidth}{0.5pt}
-
-\bigskip
-
-{\Large\itshape User’s manual\\
-Version 2.3
-}
-
-\bigskip
-
-\rule{\textwidth}{0.5pt}
-
-\vspace{\stretch{1}}
-
-{\Large Alexey Kryukov }
-
-\vspace*{3ex}
-{\large Edited for CTAN by Bob Tennent}
-
-\vspace{\stretch{0.6}}
-
-\end{center}
-
-\clearpage
-
-\vspace*{\stretch{1}}
-
-This manual is set in Old Standard with Latin Modern fonts used for missing 
-styles (\eg, typewriter fonts).
-
-\vspace{\stretch{0.1}}
-
-Copyright © 2006--2011 Alexey Kryukov.
-
-Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2
-or any later version published by the Free Software Foundation;
-with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
-A copy of the license is included in the section entitled “GNU
-Free Documentation License”.
-
-\vspace{\stretch{0.2}}
-
-\clearpage
-
-\setcounter{page}{1}
-
-\tableofcontents
-
-\pagestyle{headings}
-
-\chapter{About Old Standard}
-\thispagestyle{empty}
-
-Anybody who has ever thumbed through any old books printed in the late
-19\textsuperscript{th} or early 20\textsuperscript{th} century may have
-noted a specific typeface style most commonly used at that time: basically,
-a variation of the modern (classicist) antiqua, but with less contrast and greater
-legibility. This group of typefaces also had an accompanying style of italics
-with some specific shapes: \textit{k} with the upper leg terminating with a
-rounded ball, open bowl on \textit{g} (again, with a rounded ball at its end),
-curved bowl on \textit{y} and so on. Maybe you were wondering, why is it so
-difficult to find a digital typeface of similar style, despite the vast
-number of computer fonts currently available. In general, the Modern style
-was almost completely abandoned in the middle 20\textsuperscript{th}
-century, as it no longer corresponded to the tastes of the time; moreover,
-contemporary typographers often consider this lettertype obsolete and
-out-of-fashion due to its “unnaturality”.
-
-Nevertheless, the classicist style in general, and its modification used in
-the early 20\textsuperscript{th} century in particular, has at least one
-advantage: it is still very suitable for typesetting scientific papers,
-especially on social and humanitarian sciences, as its specific features
-are closely associated in people’s eyes with old books they learned on.
-However, it would be even more important to stress the fact that book
-printing in many non-Western languages first appeared or was greatly
-improved in the 19\textsuperscript{th} century, and thus many classical
-typefaces for non-Latin scripts (the most beautiful examples of Greek and
-Cyrillic lettertypes in particular) were designed to be harmonizable with
-the Modern faces~— the standard Roman printing style of the time.
-
-That’s why the Modern style should be considered an extremely good choice
-for typesetting multilingual texts, and so I am really surprised that 
-nobody has yet attempted to implement a multilingual typeface on this basis.
-Instead, multilingual typesetting is usually done with Times-styled fonts,
-which eliminate specific features of each script instead of stressing them.
-This is the main reason why I designed Old Standard, a
-multilingual font which attempts to revive the most common printing style
-of the early 20\textsuperscript{th} century. Old Standard has two main
-purposes: it is intended to be used as a specialized font for philologists
-(mainly classicists and slavists) and also as a general-purpose font for
-typesetting various editions in languages that use Greek or Cyrillic
-script. For this reason Old Standard provides glyphs for a wide range of
-Latin, Greek and Cyrillic characters.
-
-\section{Origin and Design}
-
-Old Standard was first intended as a digital version of
-\textit{Обыкновенная} (Standard) typeface found in the following font
-catalogues printed in the Soviet Union: 
-
-\begin{figure}
-
-\centerline{\XeTeXpicfile "stand-su.png" width 160mm}
-
-\caption{The regular version of the Russian “Standard” typeface from the
-1966 font catalogue}
-
-\label{fig:stand-su}
-
-\end{figure}
-
-\begin{otherlanguage}{russian}
-
-\begin{itemize}
-
-\item Каталог ручных и машинных шрифтов. М.: Книга, 1966.
-
-\item Каталог ручных шрифтов и наборных украшений. Харьков: Прапор, 1973.
-
-\end{itemize}
-
-\end{otherlanguage}
-That’s where the name originates from: I have only added “Old” to
-stress the difference from \textit{Обыкновенная Новая} (“New Standard”)~—
-another, a bit similar and yet quite different typeface, much more
-popular in the Soviet typography. Currently there is a good digital version
-of New Standard, available from \href{http://www.paratype.ru}{Paratype},
-so I was not planning to reproduce it.
-
-Later, however, I realized that the \textit{Обыкновенная} typeface, as it
-was used in Soviet printing of the second half of the
-20\textsuperscript{th} century, is not an independent family, but rather a
-bunch of various sets inherited from pre-1917 Russian typography. So I had
-to improve the initial design basing mainly on various Russian and German
-editions of the late 19\textsuperscript{th} and early
-20\textsuperscript{th} centuries, mainly manuals of ancient languages and
-editions of classical (Greek and Latin) authors, where I could find good
-examples of Latin, Greek, and, in the case of Russian books, also Cyrillic
-letters, used alongside. I have also bought the following font catalogue,
-which, unlike later Soviet catalogues, contains examples of several
-“Standard” typefaces, so that I could compare the letterforms and select
-those I considered the most elegant:
-\foreignlanguage{russian}{Государственный трест ВСНХ «Полиграф». Образцы
-шрифтов. М., 1927}.
-
-Thus the current version of Old Standard doesn’t reproduce any particular
-typeface, but rather attempts to revive the general style of the early
-20\textsuperscript{th} century typography (mostly Russian and German).
-Nevertheless, I have decided to keep the initial name: of course, it
-doesn’t look very original, but seems to be a good choice for a lettertype
-that was once so common that no special name was associated with it
-(typefaces of this style are usually called just “Standard” or “Modern” in
-old font catalogues).
-
-\section{Greek font design}
-
-The Greek characters in Old Standard require a separate note. The upright
-letters follow the style first introduced by the famous French typecutter
-Firmin Didot and then widely used in various editions both in Greece itself
-and many other European countries. It would be no exaggeration to state that
-most Greek editions printed in continental Europe for more than
-100 years were set with Didot faces. So it is no wonder that digital versions
-of this design have already been created by several type foundries. However
-almost all these fonts either cover just the Greek script and provide no
-support for Latin (not to say Cyrillic) characters, or combine Didot's Greek
-design with a stylistically incompatible (usually Times-styled) Latin face.
-Most of them (even some hightly overpriced commercial products) also 
-don't meet my quality standards.
-
-\begin{figure}[htb]
-
-\centerline{\XeTeXpicfile "didot-fr.png" width 160mm}
-
-\caption{An excerpt from a French edition typeset with a Didot face. The 
-example is taken from: Les hanrangues de Démosthène. Text grec publié 
-d’après les travaux les plus récents de la philologie avec un commentaire 
-critique et explicatif, une introduction générale et des notices sur chaque 
-discours par Henri Weil. Deuxieme édition entèrement revue et corrigée. 
-Paris, 1881.}
-
-\hypertarget{fig:didot-fr}{}\label{fig:didot-fr}
-
-\end{figure}
-
-A notable exception is
-\href{http://www.greekfontsociety.org/pages/en\_typefaces.html}{GFS Didot},
-now available for free from the \href{http://www.greekfontsociety.gr/}{Greek
-Font Society}. Unlike many others, the designers of this font did care about
-a matching Latin face, but, surprisingly, their choice has nothing to do
-with the classicist style: instead, they implemented their font as an
-accompanying Greek family for Adobe Palatino. For this reason the proportions
-and metrics of GFS Didot are quite different from those of original Greek
-Didot; in particular ascenders and descenders are significantly shorter.
-The Unicode version now comes with its own Latin alphabet, but, again, it
-is based mostly on the Palatino design, although some glyph features are
-adapted to the geometrical shapes of Greek capitals. The resulting font
-may be very elegant, but, again, it is not suitable to reproduce the authentic
-look of old editions, and essentally should have not been called Didot
-due to a different style of its Latin part.
-
-\begin{figure}[htb]
-
-\centerline{\XeTeXpicfile "didot-de.png" width 160mm}
-
-\caption{A modification of the Didot style, used in German editions. The
-example is taken from: Herodoti Historiae. Recensuit Henricus Stein. Tomus
-II. Berolini, 1871. P.~318.}
-
-\hypertarget{fig:didot-de}{}\label{fig:didot-de}
-
-\end{figure}
-
-It should also be noted that the historic Didot style had several variations;
-in particular its \hyperlink{fig:didot-de}{German version} (popular also in
-Russia) is slightly different from the \hyperlink{fig:didot-fr}{font used in 
-French editions of the same time}. Old Standard seems to be the only digital
-typeface that follows mostly the German and Russian understanding of the
-Didot style, although for some characters (\eg, Greek circumflex) I have 
-preferred French forms, considering them more elegant.
-
-\begin{figure}[htb]
-
-\centerline{\XeTeXpicfile "teubner.png" width 160mm}
-
-\caption{An example of the Teubner Greek font, taken from: Herodotus für
-den Schulgebrauch erklärt. Von Dr. K.~Abicht, Direktor des Gymnasiums zu
-Ols. Vierter Band. Buch~VIII. Dritte verbesserte Auflage. Leipzig, 1882.
-S.~192.}
-
-\hypertarget{fig:teubner}{}\label{fig:teubner}
-
-\end{figure}
-
-Designing an italic style for a Greek typeface represents a separate
-problem. Most modern implementations of Greek Didot are accompanied with
-italic versions obtained by applying a slant to the upright glyphs. I have
-chosen a different solution: instead of creating a slanted version of
-the Didot family (completely unknown to traditional typography), I have
-based my italics on various cursive Greek fonts actually used in the German
-typography of the early 20\textsuperscript{th} century. The most elegant of
-those fonts was the face used by the famous Teubner publishing house in
-Leipzig for their editions of classical authors.
-
-Surprisingly, until recently nobody has attempted to implement a digital version
-of the \hyperlink{fig:teubner}{Teubner Greek font}, and this is a pity,
-because Teubner editions are still considered a model of fine Greek
-printing in Germany, Russia and, I think, many other European countries,
-exactly like the Loeb classical library in the Anglo-American world. It
-should be noted here that the actual Teubner typeface is sometimes
-confused with another cursive Greek font, also called “λιπσιακό” in Greece,
-which does have some digital implementations, in particular Monotype Greek
-91 and the grml/grbl fonts which Claudio Beccari has designed to provide a
-matching italic font for his CB Greek package. Indeed, a similar font was
-sometimes used in Leipzig editions (mainly for headings), but it is quite
-different from the standard text face these editions are set with.
-
-I should admit however, that even Old Standard Italic doesn’t provide an
-authentic reproduction of the Teubner font. The problem is that the Greek
-letters used in Leipzig editions are a bit bolder than their accompanying
-Latin face, so that it was really difficult to bring them into a better
-correspondence with Latin and Cyrillic glyphs. That’s why I had to consider
-also some less elegant, but lighter Greek typefaces used by other printing
-houses in Germany at the same time. I hope however that the general style
-of the Teubner font is preserved, so that anybody who likes Leipzig
-editions of classical authors will like Old Standard as well.
-
-\omit{
-
-\chapter{Installation and Usage}
-\thispagestyle{empty}
-
-\section{Obtaining Old Standard}
-
-If you are reading this document, then you probably have already downloaded
-Old Standard. You may check if you have the most recent version by visiting
-the following page at the Thessalonica web site: 
-
-\href{http://www.thessalonica.org.ru/en/fonts.html}
-{\texttt{http://www.thessalonica.org.ru/en/fonts.html}}
-
-This page contains information about all font projects I am currently
-developing and download links.
-
-\section{Which format to prefer?}
-
-The Old Standard font family is currently available in two formats, so that
-before downloading fonts you should consider with which software you are
-planning to use them:
-
-\begin{description}
-
-\item[\XeTeXpicfile "truetype.png"] TrueType fonts, or, more precisely,
-\hyperlink{OT}{OpenType} fonts with TrueType outlines;
-
-\item[\XeTeXpicfile "opentype.png"] \hyperlink{OT}{OpenType} fonts with
-PostScript outlines (also called OpenType-CFF).
-
-\end{description}
-
-Note that fonts in those two formats have different file extensions:
-\texttt{*.ttf} for TrueType, \texttt{*.otf} for OpenType-CFF
-(this is the convention most font developers currently follow).
-There also used to be a small difference in Windows icons: while \texttt{*.otf}
-files appear in a folder or on a disk with a dog-eared page icon
-showing a slanted letter “O” (for OpenType), an old icon with two overlapping
-“T’s” has been used for TrueType fonts. It is worth pointing out, that the
-icon was misleading, since the TrueType version of the Old Standard
-family beginning from the very first releases supported the same set of
-advanced \hyperlink{OT}{OpenType} features as its OpenType-CFF counterpart
-(see \autoref{i18n} for information on how to take advantage of those
-features).
-
-The reason for displaying the old icon is that Windows checks the presense of
-a digital signature in a TrueType font, considering (quite illogically)
-this would allow to distinguish “old” TrueType fonts from “modern” OpenType
-fonts with TrueType outlines. This is not a problem by itself, but it
-has recently been reported that Microsoft Word 2010 (the first version
-with optional OpenType features support) has adopted the same approach
-and doesn't allow to access optional features in a TrueType font which
-is not digitally signed. So now my TTF fonts contain a dummy digital signature
-(which seems sufficient to fool both Windows Explorer and Word), and thus
-appear with the same “O” icon as the OTF versions.
-
-The two formats are different in many aspects, which are important
-from a developer's point of view, but almost not noticeable for an ordinary
-user. In particular, OpenType-CFF fonts use PostScript oputlines, based
-on third-order (cubic) Beziér curves, while in TrueType fonts second-order
-(quadratic) splines are used. There is also a significant difference in
-hinting (grid-fitting) area: TrueType hints theoretically allow to
-achieve much better quality of screen rendering, but quality hinting is a
-very difficult and time-consuming process.
-
-Note that it is possible to install both TrueType and OpenType-CFF versions
-alongside: in order to prevent name clashes a “TT” suffix is appended to
-font name/family name fields in TrueType fonts. Thus you can compare both
-versions and decide which one better fits your needs. In the older versions
-of this manual I recommended installing TrueType versions, since this
-format used to be better supported in many applications on various
-platforms. However most of the problems with OpenType-CFF fonts have been
-fixed in recent software releases. In particular:
-
-\begin{itemize}
-
-\item In most Windows programs (except Adobe's desktop publishing applications)
-\textit{kerning}\footnote{Kerning is the adjustment of space between pairs
-of letters, especially by placing two characters closer together than
-normal. Kerning makes certain combinations of letters, such as WA, MW,
-TA or VA, look better. Kerning data is specific for each particular font
-and for this reason is normally specified in the font file; carefully
-designed fonts normally have a large number of kerning pairs.} worked
-only for the first 256 characters in the font. Of course this means that
-you couldn't get kerning working neither for Greek nor for Cyrillic
-letters. This issue seems to no longer exist in Windows Vista/7;
-
-\item older version of OpenOffice.org didn't embed OpenType-CFF fonts into PDF
-files. Moreover, under Unix-like systems OpenOffice.org could not access
-such fonts at all, so that using TTF versions was the only option. This
-is fixed in OpenOffice.org 3.2 (and LibreOffice).
-
-\end{itemize}
-
-Thus selecting one of two formats is now essentially a matter of taste.
-Since Old Standard has been drawn in cubic splines (and then converted to
-quadratic for the TTF version), and since it still has only autogenerated
-TrueType hints, the OpenType-CFF format may theoretically give you even
-a better screen rendering quality. However note that only the
-TTF version currently supports the \hyperlink{Graphite}{Graphite}
-rendering technologie (this is a limitation of the technologie itself),
-and this might be a reason to still prefer TrueType fonts for
-OpenOffice.org/LibreOffice users.
-
-\section{Source Package}
-
-You also can download the FontForge sources of the Old Standard font family.
-Of course this package may be useful for you only if you have the 
-\href{http://fontforge.sourceforge.net}{FontForge} font editor, as well
-as some other font editing utilities, and know how to use them.
-Note that downloading the source package may make a sense for you only
-if you are going to apply some modifications to the original files, i.~e.
-to prepare your own version of the fonts. Please consult the 
-\hyperlink{license}{Terms of Use} section of this document to see which
-license conditions should be met when distributing such derivative works.
-
-Sometimes I am getting e-mails from packagers of Linux distributions
-asking if they could build Old Standard from sources just like they used to
-do for application executables. Well, I can't prohibit this (as the fonts
-are available under a free license and even the name itself is not reserved,
-as explained \hyperlink{license}{below}) but \textbf{I strongly discourage
-doing so}. The reason is that, despite the common name, font sources aren't
-very much like application sources, and similarly TTF or OTF fonts have very
-few common with compiled programs. When an application is built from sources,
-the resulting files are usually suitable only for a particular platform or
-system and cannot be used in other environments. Fonts represent just an
-opposite case: font sources are specific for a particular font editing
-application, while the output files are suitable for various platforms and
-can be easily disassembled/opened/edited. 
-
-This means rebuilding fonts from sources will not give you any productivity 
-improvements, but you can easily lose some functionality (e. g. because 
-your FontForge version doesn't work exactly like one I used to build the
-original font files). That's why I can recommend this approach only of you
-know what are you doing and your intent is to apply some real changes/
-improvements to the font sources.
-
-\section{System Requirements}
-
-\subsection{Windows}
-
-Old Standard is a large Unicode font.
-
-For Windows, you need at least Windows 95 (or at least Windows 2000 for the
-PostScript-flavored OpenType fonts) and a word processor that can handle
-Unicode-based documents, such as Microsoft Word 97 and above,
-\href{http://www.openoffice.org}{OpenOffice.org} 1.0 and above,
-or \href{http://www.libreoffice.org}{LibreOffice}, which has
-splitted from the OpenOffice.org project in 2010 and has now superseded
-it in most Linux distributions.
-
-You will also need a way to enter the Unicode characters that are not
-directly accessible from standard keyboards. Remember that you can browse
-the contents of any font and copy characters to the clipboard by using the
-Character Map utility that comes with Windows. Character Map does not
-support Unicode values beyond the Basic Multilingual Plane; an excellent
-alternative is Andrew West’s
-\href{http://www.babelstone.co.uk/Software/BabelMap.html}{BabelMap}
-(free). Some applications also provide their own mechanisms for entering
-characters, such as Insert→Symbol in MS Word or Insert→Special Character
-in OpenOffice.org/LibreOffice. In Microsoft Office applications you can also enter 
-a Unicode character by typing its hexadecimal number followed by
-\texttt{ALT-x}.
-
-Of course inputting Unicode characters via a character table or accessing
-them directly by their hexadecimal codes has some significant
-disadvantages: first, it is relatively slow and so may be used only for
-characters which you need relatively rare, and second, it may be
-recommended only for experienced users, since Unicode includes a lot of
-similar characters, which, however, are intended for different purposes, so
-that sometimes it is difficult to make the correct choice without
-consulting the documentation. So normally you will need a special keyboard
-utility allowing to input characters needed for the language of your
-choice. Some custom keyboard layouts for such languages as Classical Greek
-are provided by my \href{http://www.thessalonica.org.ru}{Thessalonica}
-package. Alternatively, you may use
-\href{http://www.tavultesoft.com/keyman/}{Tavultesoft Keyman}~— the
-leading keyboard mapping utility, providing an extensive range of features.
-There is a large number of keyboard layouts already designed for
-Tavultesoft Keyman, so you probably just have to check
-\href{http://www.tavultesoft.com/keyman/downloads/keyboards/}{the list of
-available keyboard} to select one or more which are suitable for your
-needs.
-
-\subsection{Linux and X11 Windowing Environment}
-
-Most Unix-like systems now use the same basic framework, called X Window
-System (commonly X or X11) to build graphical user interfaces. This means
-that all issues related with font installation and usage are basically the
-same, no matter, if you use Linux, BSD, Solaris or some other system. In
-order to be able to handle TrueType or OpenType fonts your system should
-have the \href{http://freetype.sourceforge.net}{freetype} library installed
-and enabled; this is normally done by default in all modern distributions.
-As under Windows, you will need a Unicode-aware word processor. Presumable
-you will do most of your work in OpenOffice.org or LibreOffice; other, less powerful word
-processors, like AbiWord or KWord, support Unicode as well.
-
-As under Windows, you may input Unicode characters using either a character
-map utility (both the most full-featured X11-based desktop environments,
-KDE and Gnome, include such utilities, comparable with the Windows
-Character Map), or a special keyboard driver. Again, you can try
-\href{http://www.thessalonica.org.ru}{Thessalonica} for OpenOffice.org.
-Another good choice is \href{href://kmfl.sourceforge.net}{kmfl}~— a
-keyboarding input method which aims to bring Tavultesoft Keyman
-functionality to *nix operating systems. KMFL is being jointly developed by
-\href{http://www.sil.org}{SIL International} and
-\href{http://www.tavultesoft.com}{Tavultesoft}. Note that KMFL is not
-available by default in some popular Linux distributions, so that
-you may have to compile, install and configure it yourself. This task
-is a bit difficult for an average user, but the result surely worth
-efforts.
-
-\section{Installation Instructions}
-
-\subsection{Windows}
-
-Font installation under Windows is simple. You can install Old Standard as
-you would any TrueType or OpenType-CFF font by placing the font files to
-the Windows \texttt{fonts} folder. To do that:
-
-\begin{enumerate}
-
-\item Go to the Windows Control Panel and open the “Fonts” applet;
-
-\item On the File menu, select “Install New Font\ldots”;
-
-\item Switch to the drive and directory that contain the fonts you want to
-add;
-
-\item To select more than one font to add, press and hold down the CTRL
-key, click the fonts you want, then click on OK.
-
-\end{enumerate}
-
-You may need to restart some applications before they can access the fonts
-you have just installed.
-
-\subsection{Linux and X11}
-
-Currently there are no prepackaged RPM or DEB files for Old Standard, but,
-of course, you can always install the fonts manually, which is actually not
-so complex task with modern Linux distributions. A tricky part is related
-with the fact that there are actually two engines responsible for font
-installation and handling in X11 environment:
-\href{http://www.fontconfig.org}{fontconfig} and an older X11 engine. Since
-fontconfig is used by almost all recent applications (including those
-based on GTK2 and QT4), in most cases it is sufficient to install fonts
-via fontconfig (this is the only option in case of OpenType-CFF fonts). On
-most distributions you can do that just by placing the font files to your
-\texttt{~/.fonts} directory. After that you may need to run
-
-\texttt{\$ fc-cache}
-
-\noindent from your command line to update your fontconfig configuration.
-You can also use a graphical font installation tool provided by KDE (the
-most powerful graphical desktop environment for X11), but be aware that
-this tool actually does just the things described above, i.~e. copies the
-fonts to the appropriate directory and runs \texttt{fc-cache}.
-
-However, if you want to make TrueType fonts accessible to some older X11
-applications, then additional steps are required:
-
-\begin{enumerate}
-
-\item Find the place in your directory tree where your X stores TTF fonts.
-The usual place is \texttt{/usr/X11R6/lib/X11/fonts/truetype} and the
-subdirectories therein;
-
-\item create under that location a subdirectory for the fonts you are going
-to install, for example:
-
-\texttt{\$ mkdir /usr/X11R6/lib/X11/fonts/truetype/oldstand}.
-
-You should become root to do that. Then copy the *.ttf files there:
-
-\texttt{\$ cp *.ttf /usr/X11R6/lib/X11/fonts/oldstand/};
-
-\item switch to the directory where you have just copied the font files and
-run the following commands:
-
-\texttt{\$ ttmkfdir > fonts.scale}
-\texttt{\$ mkfontdir}
-
-\item Now the hardest part: we have to inform your X server about the path
-where the recently installed fonts are placed. This can be done by
-two ways:
-
-\begin{enumerate}
-
-\item in most distributions fonts are managed directly by the X11 system.
-In this case the information about font paths is stored in the main X11
-server configuration file, which is located under \texttt{/etc/X11} and
-may be called \texttt{xorg.conf}, \texttt{XF66Config} or
-\texttt{XF86Config-4} depending from your distribution and the version of
-the X11 server it uses. So open that file in your favorite text editor,
-and add the following line to the “Files” section:
-
-\texttt{FontPath "/usr/X11R6/lib/X11/fonts/oldstand/"};
-
-\item some Linux distributions (\href{http://www.altlinux.ru}{Alt Linux} in
-particular) handle fonts using a special X Font Server (xfs). You can
-easily determine if your distribution belongs to this second group, as in
-this case the only “FontPath” element in your \texttt{xorg.conf} or
-\texttt{XF86Config} will look as follows:
-
-\texttt{FontPath "unix/:-1"}
-
-If you have noticed such a line in your main X11 configuration file, you
-should keep it untouched and instead edit the \texttt{/etc/X11/xfs/config}
-file and add the new font path there.
-
-\end{enumerate}
-
-\item Finally, if everything is done correctly, the fonts will be
-accessible for X11 applications when you restart your X Server. However,
-you can also activate your new fonts immediately. Again, this can be done
-by two ways:
-
-\begin{enumerate}
-
-\item if your system doesn’t use xfs, then you should execute the following
-commands:
-
-\texttt{\$ xset fp+ /usr/X11R6/lib/X11/fonts/oldstand/}
-
-\texttt{\$ xset rehash}
-
-\item otherwise you have to restart your X Font Server. Usually this
-can be done by executing
-
-\texttt{\$ service xfs restart}
-
-\end{enumerate}
-
-\end{enumerate}
-
-\subsection{OpenOffice.org}
-
-Under MS Windows OpenOffice.org/LibreOffice just uses system-wide installed
-fonts, but Unix versions have their own font administration utility,
-inherited from the dark times when no suitable engine that would be able
-to properly handle scalable fonts existed at the X11 level. Normally
-OpenOffice.org/LibreOffice can automatically detect X11 fonts and add
-them to its configuration (so no additional steps are required), but
-sometimes it fails to find them. In this case you should let
-OpenOffice.org/LibreOffice know about your new fonts using the \texttt{spadmin}
-utility. You can either run this tool manually from your OpenOffice.org
-directory, or select the “OpenOffice.org printer administration” GUI menu
-item in KDE or Gnome (you should close any open OpenOffice.org/LibreOffice 
-instances before you can do this). When the \texttt{spadmin} window appears, 
-do the following:
-
-\begin{figure}[htb]
-
-\centerline{\XeTeXpicfile "spadmin.png" width 160mm}
-
-\caption{The OpenOffice.org printer administration utility: main window}
-
-\hypertarget{fig:spadmin}{}\label{fig:spadmin}
-
-\end{figure}
-
-\begin{enumerate}
-
-\item click on the “Fonts...” button;
-
-\item click on "Add...;
-
-\item look for the directory where the fonts are installed\\ (e.~g.
-\texttt{/usr/share/fonts/truetype/oldstand/}), as \autoref{fig:spadmin-add}
-shows;
-
-\begin{figure}[htb]
-
-\centerline{\XeTeXpicfile "spadmin-add.png" width 140mm}
-
-\caption{Adding new fonts to OpenOffice.org via spadmin}
-
-\hypertarget{fig:spadmin-add}{}\label{fig:spadmin-add}
-
-\end{figure}
-
-\item Click on “Select all”;
-
-\item Click on OK.
-
-\end{enumerate}
-
-When you restart OpenOffice.org/LibreOffice, the fonts should be available to its
-applications.
-
-\subsection{{\TeX} systems}
-
-Adding new fonts to a \TeX{} installation is always difficult for an
-average user, as in order to use a font with \TeX{} typesetting system one
-has to generate many additional files, \TeX{} font metrics files (TFM) in
-particular. Yet I still haven’t provided a \TeX{} support package for Old
-Standard, mainly because Old Standard currently has only three shapes
-(regular, italic and bold), and thus such a package would have very limited
-functionality from the \TeX{} point of view. However, you can easily use
-Old Standard (as well as any other TrueType or OpenType-CFF font) in your
-\TeX{} documents without any additional steps if you install
-\href{http://scripts.sil.org/xetex}{\XeTeX}~— a Unicode enabled version of
-the \TeX{} compiler. In particular this manual was set with \XeLaTeX{}
-using the TrueType versions of the fonts. 
-
-\XeTeX{} has many other advantages over traditional \TeX{} compilers, as it
-combines the full Unicode support with a very good support of advanced
-\hyperlink{OT}{OpenType} features. In particular, this manual (including
-all examples demonstrating smart font rendering features available in Old
-Standard) was typeset with \XeTeX.
-
-}
-
-\section{Terms of use}
-\hypertarget{license}{}
-
-The current version of Old Standard is distributed under the
-\href{http://scripts.sil.org/OFL}{SIL Open Font License} (OFL) v.~1.1. I 
-selected OFL for my typeface because it is the only license developed
-specially for fonts that meets the standards of the FLOSS (Free/Libre and
-Open Source Software) community, in particular the Debian Free Software
-Guidelines. Both the text of the license itself and the OFL FAQ are
-included in the fonts package, so I don’t reproduce them here. Basically
-licensing under OFL means that you can freely use, copy, modify and
-distribute the fonts, as long as the terms of the license are not violated.
-In particular you are not allowed to remove the original copyright notices
-from the font software and to change licensing conditions (\ie, distribute
-either original or modified versions under a different license). One additional
-significant restriction is that you can’t sell the fonts alone (however
-OFL allows you to bundle and sell them together with any other software, either
-free or commercial).
-
-A large part of OFL is devoted to so-called Reserved Font Names which can't
-be used in derivative works without a written permission of the original
-author. However there are no Reserved Font Names specified for Old Standard.
-This is because I think I can't prohibit anybody from using such common
-words as “Old” or “Standard” in their font names. In fact I even encourage
-you to base names of your modified versions on the original one, so that 
-the user can easily determine where the main design comes from. For example,
-if you have modified Old Standard in order to get Serbian Cyrillic glyphs
-displayed by default instead of Russian ones, it might be logical to call
-your version “Old Standard Serbian”. It is still desired however that you
-don't take the original name as is, but add some suffix specific for your
-version.
-
-Note that this manual is \emph{not} covered by SIL OFL, but distributed under the
-\href{http://gnu.mirror.fr/licenses/fdl.html}{GNU Free Documentation
-license}. See \autoref{FDL} for more information.
-
-\section{Acknowledgments}
-
-I would like to thank:
-
-\begin{itemize}
-
-\item George Williams for his excellent
-\href{http://fontforge.sourceforge.net}{FontForge} program, and
-especially for his responsiveness in fixing bugs and adding new features.
-Without his assistance this package would never be released!
-
-\item Peter Baker for his \href{http://xgridfit.sourceforge.net}{xgridfit}
-utility, which provides a good Open Source solution for adding TrueType
-instructions to a font, and also for valuable information on the design of
-the Middle English letter yogh he provided;
-
-\item Tavmjong Bah (Tav), who kindly granted me his Perl scripts (originally
-written for his \href{http://tavmjong.free.fr/FONTS/}{Arev fonts}) used to
-convert separate kerning pairs defined in a FontForge source file into
-kerning classes;
-
-\item \href{http://canopus.iacp.dvo.ru/~panov/}{Andrew Panov} for valuable
-remarks on the design of mathematical characters and scanned images he
-provided.
-
-\end{itemize}
-
-\chapter{Multilingual Support, Unicode and OpenType}
-\hypertarget{i18n}{}\label{i18n}
-\thispagestyle{empty}
-
-\section{Unicode coverage}
-
-\subsection{General principles}
-
-Since Old Standard is a multilingual font family, I will always do my best
-to extend the range of supported characters, thus providing support for
-more languages. Nevertheless, I would like to protect my typeface from some
-problems shared by many similar free font projects. The developers of those
-fonts are often attempting to cover the widest possible number of scripts
-and Unicode blocks, even if the Unicode
-\href{http://www.unicode.org/charts}{code charts} is the only source of
-their knowledge about the design of a specific character. Of course, the
-resulting glyphs do not always look really acceptable for actual typesetting.
-Moreover, due to the lack of time and resources the designers are often
-unable to keep all glyphs at the same quality level: for example, we often
-can see autogenerated accented characters with mispositioned diacritics. In
-particular, there are so many fonts that are claimed to support the
-extended Greek range, but actually are not suitable for typesetting
-classical Greek\ldots{} Another common problem is that only the regular
-version of each particular font is really actively developed, while all
-additional weights and shapes fall far behind it (\eg, support much fewer
-Unicode characters).
-
-That’s why I have formulated for myself several principles which I am
-always trying to follow when designing additional glyphs:
-
-\begin{itemize}
-
-\item I shall never add any new characters just for completeness, \ie, to
-get a specific Unicode range fully covered. Before drawing a new glyph I
-must ensure that I really understand its intended purpose and the
-principles of its design.
-
-\item Because Old Standard is supposed to reproduce the actual printing style
-of the early 20\textsuperscript{th} century, I shall avoid implementing new
-characters based just on general considerations. Ideally, all glyphs
-should be based on real examples taken from some old editions. Of course,
-exceptions to this rule are sometimes necessary, as many characters were
-first introduced only in 20\textsuperscript{th} century, or even never
-existed in traditional typography before they were adopted by the Unicode
-standard.
-
-\item I shall try to develop all font styles (currently regular,
-italic and bold) simultaneously, \ie, if a specific character is added 
-to the regular font, it should also be designed for italics and bold. 
-Exceptions are allowed for glyphs that don't have dedicated codepoints
-and are supposed to be accessible via smart font features, as well as for those 
-characters that have no corresponding italic or slanted style (this is the case 
-for many mathematical symbols).
-
-\end{itemize}
-
-\subsection{Character repertoire}
-
-Currently the following Unicode ranges are fully or partially covered by
-Old Standard:
-
-\begin{description}
-
-\item[Basic Latin (0000–007F)] Fully supported.
-
-\item[Latin 1 Supplement (0080–00FF)] Fully supported.
-
-\item[Latin Extended-A (0100–017F)] Fully supported.
-
-\item[Latin Extended-B (0180–024F)] Old Standard implements two groups of
-characters from this block, namely several letters needed for various Old
-Germanic languages and Croatian accented characters and digraphs.
-
-\item[IPA Extensions (0250–02AF)] From this range Old Standard currently
-implements a few characters which can be used in other contexts, except IPA.
-One such example is \texttt{U+0280} LATIN LETTER SMALL CAPITAL R, needed for the
-transliteration of Old Norse runic inscriptions.
-
-\item[Spacing Modifier Letters (02B0–02FF)] Old Standard implements spacing
-versions of some combining diacritical marks, available in the next block.
-
-\item[Combining Diacritical Marks (0300–036F)] Most standard accents,
-commonly used in various European languages, are supported.
-
-\item[Greek and Coptic (0370–03FF)] Fully covered, except Coptic
-letters.
-
-\item[Cyrillic (0400–04FF)] Old Standard implements all modern Slavic
-(i.~e. Russian, Uk\-rai\-nian, Byelorussian, Serbian and Macedonian)
-characters, as well as historical characters and extensions for Old
-Slavonic.
-
-\item[Phonetic Extensions (1D00–1D7F)] Only one character (\texttt{U+1D79} LATIN
-SMALL LETTER INSULAR G) is implemented. Note that the uppercase version 
-of this letterform is now encoded in Latin Extended-D range.
-
-\item[Latin Extended Additional (1E00–1EFF)] This range is coveref except
-Vietnamese acented characters and medievalist additions.
-
-\item[Greek Extended (1F00–1FFF)] Fully supported.
-
-\item[General Punctuation (2000–206F)] Fully supported, except invisible
-control characters.
-
-\item[Superscripts and Subscripts (2070–209F)] Subscript and superscript
-forms of digits and math operators (but not letters), available in this
-block, are covered.
-
-\item[Currency Symbols (20A0–20CF)] The EURO SIGN \texttt{U+20AC}.
-
-\item[Letterlike Symbols (2100–214F)] In this block Old Standard implements
-a few characters, belonging to the following two categories: first, a few
-standard symbols, present in most Western or Cyrillic fonts (in particular
-NUMERO SIGN \texttt{U+2116}, TRADE MARK SIGN \texttt{U+2122} and OHM SIGN \texttt{U+2126}), and second,
-some characters which may be useful for textual criticism (such as Fraktur ℭ
-and ℌ).
-
-\item[Number Forms (2150–218F)] Fully covered.
-
-\item[Mathematical Operators (2200–22FF)] This block is far from being
-finished, and yet it already includes (I hope) all symbols which are most
-commonly used in mathematical typesetting.
-
-\item[Miscellaneous Technical (2300–23FF)] In this block Old Standard
-implements angle brackets \texttt{U+2329} and \texttt{U+232A} (these characters should
-probably be avoided: use “mathematical” angle brackets at \texttt{U+27E8/U+27E9}
-instead) and ancient metrical symbols (23D1—23D9).
-
-\item[Geometric Shapes (25A0–25FF)] Old Standard implements only a few of
-these symbols, for compatibility with legacy fonts and charsets.
-
-\item[Miscellaneous Mathematical Symbols-A (27C0–27EF)] Old Standard
-implements mathematical angle, square and double angle brackets (useful
-also for critical text editions).
-
-\item[Supplemental Mathematical Operators (2A00–2AFF)] In this block I have
-implemented only a few characters, in particular alternate “less than” and
-“greater than” symbols with a slanted bar, which actually where preferred
-forms in the traditional European typesetting before the arrive of modern
-standards.
-
-\item[Cyrillic Extended-A (2DE0–2DFF)] Fully covered.
-
-\item[Supplemental Punctuation (2E00–2E7F)] Old Standard implements New
-Testament editorial symbols, Ancient Greek textual symbols and half brackets.
-
-\item[CJK Symbols and Punctuation (3000–303F)] Again, Old Standard includes
-angle and square brackets at \texttt{U+3008/U+3009} and \texttt{U+301A/U+301B}
-correspondingly, as some people have used to use them for textual
-criticism. Nevertheless “mathematical” versions of those characters (see
-above) should probably be preferred for their purposes.
-
-\item[Cyrillic Extended-B (A640–A69F)] Old Standard implements letters and
-signs for Old Cyrillic (but not letters for old Abkhasian orthography).
-
-\item[Latin Extended-D (A720–A7FF)] LATIN CAPITAL LETTER INSULAR G (\texttt{U+A77D})
-and Ancient Roman epigraphic letters.
-
-\item[Private Use Area] This block includes a few additional accented Greek
-letters and some glyphs traditionally mapped to PUA codepoints in Adobe
-fonts (I find this practice reasonable, even if Adobe itself now has dropped
-it). It is not recommended to use those glyphs directly: instead, you should
-access them by applying various smart font features (see \autoref{OT}
-for more information), if your application allows
-this.
-
-\item[Alphabetic Presentation Forms (FB00–FB4F)] In this block the standard
-Latin f-ligatures are available.
-
-\item[Math Alphanumeric Symbols (1D400–1D7FF)] Old Standard includes a few
-Fraktur letters, useful for critical editions of ancient/biblical texts.
-This block is far from being complete (and I am not planning to implement
-the whole alphabet anyway); however, it already includes all characters
-which appear in the Nestle---Aland New Testament.
-
-\end{description}
-
-\subsection{TODO}
-
-As you can see, lots of characters are still waiting to be implemented.
-Since Old Standard is oriented mainly to historians and philologists, I am
-especially interested in adding those characters which might be useful for
-textual studies and studying various ancient languages. Here are some
-priorities:
-
-\begin{itemize}
-
-\item Some characters useful for medievalists are still missing from the
-Latin Extended-B range;
-
-\item some IPA characters (at least those needed for English phonetic
-transcription);
-
-\item a large group of medievalist additions has been adopted in Unicode~5.1.
-Of course it would be nice to implement them in Old Standard.
-
-\end{itemize}
-
-\subsection{How you can help}
-
-If you would like to get a specific character available in Old Standard,
-then probably the best help you can offer is to provide some high
-resolution (normally 600dpi) scans showing you character used in an old
-book, where the rest of text is set with a Modern typeface (this condition
-is especially important for additional Latin letters). If it is impossible
-to find such examples (e.~g. because your character had not yet been
-introduced at the time when Modern typefaces were popular), then at least 
-provide a clear description on how it should be designed (or point me to a
-such description). Also remember that, except the upright character, I will
-have to implement also an italic version, and the design of italic glyphs
-may often require additional notes.
-
-Of course you can also design the desired character(s) yourself and then
-contribute them to Old Standard. Such contributions are always very
-welcome, but be aware that I will review the submissions carefully in order
-to be able to guarantee a high level of quality for the fonts. Please
-don’t be discouraged if I do not include a submission for this reason, or
-ask you to make some specific revisions.
-
-\section{Smart Font Capabilities and Language Support}
-
-This section is intended to demonstrate, how Old Standard can be used for
-typesetting texts in various languages. This assumes discussing two types
-of issues: “smart” font rendering features intended to provide a better
-support for each particular language and some glyph design peculiarities.
-Old Standard currently supports two “smart” font technologies: OpenType
-and Graphite. Since the OpenType technologie is much more widespread,
-this section deals mostly with OpenType rendering. It starts from a special
-paragraph which describes the advantages of the OpenType technologie and
-discusses the level of OpenType support in various applications. Then the
-manual proceeds to various language-specific details (again, focusing
-mainly on OpenType features), sorting them by scripts: Latin, Greek and
-Cyrillic. The Graphite rendering mode is described in a
-\hyperlink{Graphite}{separate paragraph}.
-
-\subsection{What is OpenType?}
-\hypertarget{OT}{}\label{OT}
-
-OpenType is a smart font rendering technology, that allows proper
-typographic treatment of complex scripts and advanced typographic effects
-for simpler scripts. This is achieved by applying various
-\textit{features}, or \textit{tags}, described in the OpenType
-specification. Some of those features are supposed to be enabled by
-default, while others are considered optional. In order to get advantage of
-all those advanced typographic features, you need two basic components: a
-“smart” font including certain extra tables, where the features applicable
-to this font are specified, and an OpenType-aware application. Not all
-applications currently support OpenType, although their number is growing.
-So before relying on any smart features provided by Old Standard or another
-typeface you should carefully examine which of those features are expected
-to work in your application, and which are not.
-
-The most popular OpenType rendering engine for Windows platform is the
-\textit{Uniscribe} library, developed by Microsoft. This library is used
-not only by own Microsoft software, but also by many other Windows
-applications, for example, the Windows versions of
-\href{http://www.openoffice.org}{OpenOffice.org} and
-\href{http://www.libreoffice.org}{LibreOffice}. Initially Uniscribe
-supported only complex scripts (like Arabic or Devanagari), but the most
-recent versions, supplied with Microsoft Windows XP SP2 and Microsoft
-Office 2003 (note that MS Office uses its own version of Uniscribe rather
-than the system library) also perform some processing for Latin, Greek and
-Cyrillic. The Uniscribe support for Western scripts is still limited:
-Microsoft Word 2003 performs only \hyperlink{mark}{accent positioning} and
-\hyperlink{ccmp}{character composition/decomposition}. On the other hand,
-the supported features are actually the most important ones, and they are
-really sufficient for proper text rendering, although without additional
-typographic niceties.
-
-Adobe’s applications (such as InDesign) use another shaping engine, called
-\textit{CoolType}, which provides access to many optional features offered 
-by OpenType, such as small caps, stylistic sets and various types of ligatures. 
-Old Standard currently supports some of those optional features, such as 
-stylistic sets. To tell the truth, this functionality is very important from
-the point of view of a fine typography, but in most cases almost useless for 
-a linguist. However beginning from the CS3 version Adobe Creativity Suite
-applications are said to support a wider range of OT features, including 
-mark positioning and glyph composition/decomposition, which makes them much 
-more suitable for typesetting linguistic texts when previously.
-
-In the Unix world, there are at least two free OpenType rendering
-libraries. One such library is \textit{Pango}, used in applications based
-on the GTK2 toolkit. This library currently has nearly the same
-capabilities as MS Uniscribe (although still there are some glitches).
-Another, even more powerful rendering engine is
-\href{http://icu.sourceforge.net}{\textit{ICU}}, used by \XeTeX. ICU
-properly handles virtually all features provided by Old Standard, even those 
-not supported by most other rendering engines (language-dependent substitutions 
-for example). Unix versions of \href{http://www.openoffice.org}{OpenOffice.org}
-and \href{http://www.libreoffice.org}{LibreOffice} also use ICU, but,
-unfortunately, this is not very useful for our purposes, as they enable
-complex text processing only for complex scripts.
-
-I know very little about Mac, but I have to mention that many applications for
-this platform also have a very good level of OpenType support. One such
-application is \href{http://www.redlers.com}{Mellel}, the leading word
-processor for Mac OS X, designed to serve scholars, creative and technical
-writing and multilingual word processing.
-
-\subsection{Latin Script}
-
-\subsubsection{Standard Ligatures}
-
-Old Standard currently includes 5 standard f-ligatures (namely \textit{ff,
-fi, fl, ffi} and \textit{ffl}) present in most OpenType fonts and also
-\textit{fj} and \textit{ffj} ligatures which are required for proper
-typesetting in Nordic languages. All these ligatures are accessible via the
-\texttt{liga} feature, enabled by default in most applications which
-support it (such as Adobe InDesign). Two language-dependent exceptions have
-been made from this rule, according to the common convention usually
-applied to OpenType fonts:
-
-\begin{itemize}
-
-\item Turkish, Azerbaijani and Crimean Tatar alphabets have two distinct
-versions of the letter \textit{i}, one dotted and the other dotless. For
-this reason the \textit{fi} and \textit{ffi} ligatures are not applied for
-those language systems to avoid the confusion which would be possible
-otherwise.
-
-\item No ligatures are enabled by default for German, since this language
-has very complex rules of ligature processing. You still can get them if
-you enable the \texttt{dlig} feature tag in addition to \texttt{liga}.
-
-\end{itemize}
-
-Note that the exceptions described above will work as expected only if your
-application can perform OpenType processing depending from the current
-language.
-
-\subsubsection{Combining Mark Positioning}
-\hypertarget{mark}{}
-
-One of the most attractive possibilities offered by OpenType is smart
-diacritic positioning: if you type a letter followed by a diacritic from
-the Unicode “Combining Diacritics” range, the diacritic will be placed
-exactly above or below the letter. To achieve this effect, an OpenType
-font should support the \texttt{mark} feature tag. This feature allows to
-add \textit{anchor points} both to base letters and diacritics, so that,
-when an accent mark is typed after a base character, the glyphs are
-positioned by such a way that their anchor points are coincident. Another
-type of anchor points, specified by the \texttt{mkmk} feature, is used to
-position two marks with respect to each other, so that an additional
-diacritic can be stacked properly above the first. 
-
-Old Standard provides proper \texttt{mark} and \texttt{mkmk} anchor points
-for most Latin letters and combining marks, so that you can type them in
-almost any combination and the result will be visually identical with the
-corresponding precomposed accented characters (in case they are available
-in the font). Most OpenType renderers (except older versions of Adobe’s 
-Cooltype library) support the corresponding feature tags, and so you can
-safely use these features in most OpenType-aware applications (MS Word 2003
-for example).
-
-\subsubsection{Unicode Composition and Decomposition}
-\hypertarget{ccmp}{}
-
-Another important OpenType feature is \texttt{ccmp}. This feature allows
-to decompose a character into two glyphs or, on the contrary, to compose
-two characters into a single glyph for better glyph processing. Often such
-substitutions correspond to canonical (de)compositions specified in the
-Unicode character database, but this is not a required condition. So if we
-would like to replace a specific glyph or a group of glyphs with another
-glyph or a group of glyphs, such replacement can almost always be
-implemented via \texttt{ccmp}: the only important limitation here is that
-this feature is not supposed to (an often just cannot) be turned off, and
-thus it should not be used for optional typographic refinements, such as
-Latin ligatures.
-
-Old Standard uses \texttt{ccmp} mainly to compose accented glyphs from an
-accent and a base character in those cases where a simple accent positioning
-would not produce the desired result. For example, the Czech alphabet has
-some accented characters (\textit{ď}, \textit{ľ}, \textit{ť}) where the
-accent is identified with the haček (caron), but actually looks like an
-apostrophe. So when you type \textit{d}, \textit{l} or \textit{t} followed
-by combining haček, Old Standard just substitutes the corresponding Czech
-character for you.
-
-There are also some situations where \texttt{mark} and \texttt{ccmp} should
-be used together to produce a better result. For example, before you can
-place an accent above letters like \textit{i} or \textit{j} you have to
-replace the base letter with a dotless variant first, and this can be done
-only with \texttt{ccmp}. For this reason all OpenType renderers which
-support accent positioning support also this feature (Word 2003 does).
-
-\subsubsection{Stylistic Sets}
-
-Stylistic sets are used to enable a group of stylistic variant glyphs,
-designed to harmonize visually, and make them automatically substituted
-instead of the default forms. OpenType allows to specify up to 20 stylistic
-sets, marking them \texttt{ss01}, \texttt{ss02}\ldots{} \texttt{ss20}. The
-following stylistic sets, currently available in Old Standard, are relevant
-for the Latin script:
-
-\begin{description}
-
-\item[ss01] This set allows to automatically substitute small and capital
-\textit{s} and \textit{t} with commaaccent (\texttt{U+0218}, \texttt{U+0219},
-\texttt{U+021A}, \texttt{U+021B}) instead of the corresponding letters with
-cedilla (\texttt{U+015E}, \texttt{U+015F}, \texttt{U+0162},
-\texttt{U+0163}), as required by Romanian typographic rules. The same substitution
-can be done automatically for Romanian and Moldavian languages, if only
-your application supports the \texttt{local} feature tag; otherwise you can
-use \texttt{ss01} instead. Of course this is important only if the glyph
-variants with commaaccent are not typed directly (which is also possible,
-as now those letterforms have separate Unicode codepoints).
-
-\begin{table}[h!]
-\centering\LARGE
-\begin{tabular}[c]{ccc}
-
-\fontspec[Script=Latin,Color=696969,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-raţiune şi conştiinţă & ⇒ &
-\fontspec[Script=Latin,Language=Romanian,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-raţiune şi conştiinţă \\
-\fontspec[Script=Latin,Color=696969,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-\itshape raţiune şi conştiinţă & ⇒ &\itshape 
-\fontspec[Script=Latin,Language=Romanian,
-          ItalicFont= *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-raţiune şi conştiinţă \\
-
-\end{tabular}
-\end{table}
-
-\item[ss02] By enabling this feature tag you can get all occurrences of
-small and capital Latin \textit{g} automatically replaced with “insular”
-forms, sometimes preferred for typesetting Old English:
-
-\begin{table}[h!]
-\centering\LARGE
-\begin{tabular}[c]{ccc}
-
-\fontspec[Script=Latin,Color=696969,]{OldStandard-Regular}
-Gosfregð & ⇒ &
-\fontspec[Script=Latin,RawFeature=+ss02]{OldStandard-Regular}
-Gosfregð \\
-\fontspec[Script=Latin,Color=696969,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-\itshape Gosfregð & ⇒ &\itshape 
-\fontspec[Script=Latin,RawFeature=+ss02,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-Gosfregð \\
-
-\end{tabular}
-\end{table}
-
-This stylistic set is preserved for backwards compatibility: I no longer 
-recommend using it, as both capital and small insular \textit{g} now 
-have dedicated Unicode codepoints, and it is probably better to type them
-directly.
-
-\end{description}
-
-\subsubsection{Sample Text Fragments in Old and Classical Languages}
-
-\paragraph{Classical Latin}
-
-Of course classical Latin is supported. Just an example:
-
-\begin{quote}
-\large
-\fontspec[Script=Latin,Language=Latin,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-          ]{OldStandard}
-Gallia est omnis divīsa in partes tres, quārum unam incŏlunt Belgae, aliam
-Aquitāni, tertiam qui ipsōrum lingua Celtae, nostra Galli appellantur. Hi
-omnes lingua, institūtis, legĭbus inter se diffĕrunt. Gallos ab Aquitānis
-Garumna flumen, a Belgis Matrŏna et Sequăna divĭdit. Horum omnium
-fortissimi sunt Belgae, propterea quod a cultu atque humanitāte provinciae
-longissime absunt, minimeque ad eos mercatōres saepe commeant atque ea, quae
-ad effeminandos anĭmos pertĭnent, important, proximique sunt Germānis, qui
-trans Rhenum incŏlunt, quibuscum continenter bellum gerunt. Qua de causa
-Helvetii quoque relĭquos Gallos virtūte praecēdunt, quod fere cotidiānis
-proeliis cum Germānis contendunt, cum aut suis finĭbus eos prohĭbent aut
-ipsi in eōrum finĭbus bellum gerunt.
-
-\smallskip
-
-\itshape
-Gallia est omnis divīsa in partes tres, quārum unam incŏlunt Belgae, aliam
-Aquitāni, tertiam qui ipsōrum lingua Celtae, nostra Galli appellantur. Hi
-omnes lingua, institūtis, legĭbus inter se diffĕrunt. Gallos ab Aquitānis
-Garumna flumen, a Belgis Matrŏna et Sequăna divĭdit. Horum omnium
-fortissimi sunt Belgae, propterea quod a cultu atque humanitāte provinciae
-longissime absunt, minimeque ad eos mercatōres saepe commeant atque ea, quae
-ad effeminandos anĭmos pertĭnent, important, proximique sunt Germānis, qui
-trans Rhenum incŏlunt, quibuscum continenter bellum gerunt. Qua de causa
-Helvetii quoque relĭquos Gallos virtūte praecēdunt, quod fere cotidiānis
-proeliis cum Germānis contendunt, cum aut suis finĭbus eos prohĭbent aut
-ipsi in eōrum finĭbus bellum gerunt.
-
-\end{quote}
-
-\paragraph{Old English}
-
-The following text (a writ from William the Conqueror to the citizens of
-London, 1066) demonstrates several specific characters used in Old English.
-Note the insular “G” automatically substituted instead of the regular Latin
-“G” by applying the stylistic set 02.
-
-\begin{quote}
-\large
-
-\fontspec[Script=Latin,Language=English,RawFeature=+ss02,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-Will(el)m kyng gret Will(el)m bisceop and Gosfregð portirēfan and ealle þā
-burhwaru binnan Londone, Frencisce and Englisce, frēond\-līce. And ic kȳðe ēow
-þæt ic wylle þæt get bēon eallre þǣra laga weorðe þē gyt wǣran on Eadwerdes
-dæge kynges. And ic wylle þæt ǣlc cyld bēo his fæder yrfnume æfter his
-fæder dæge. And ic nelle geþolian þæt ǣnig man ēow ǣnig wrang bēode. God
-ēow gehealde!
-
-\smallskip
-
-\itshape
-Will(el)m kyng gret Will(el)m bisceop and Gosfregð portirēfan and ealle þā
-burhwaru binnan Londone, Frencisce and Englisce, frēond\-līce. And ic kȳðe ēow
-þæt ic wylle þæt get bēon eallre þǣra laga weorðe þē gyt wǣran on Eadwerdes
-dæge kynges. And ic wylle þæt ǣlc cyld bēo his fæder yrfnume æfter his
-fæder dæge. And ic nelle geþolian þæt ǣnig man ēow ǣnig wrang bēode. God
-ēow gehealde!
-
-\end{quote}
-
-\paragraph{Middle English}
-
-No special typographic features are required for typesetting Middle
-English, so the following example just demonstrates some characters,
-specific for this language, in particular the \textit{ȝ} (yogh):
-
-\begin{quote}
-\large
-
-\fontspec[Script=Latin,Language=English,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-Our Lord, which ich shal douten, is my liȝtyng and my helpe. Our Lord is
-defendour of my lif; for what þyng shal ich drede? To þat noiand comen
-neȝe vp me, þat hij etand my flesshes: Myn enemys, þat trubleden me, ben
-made sike, and hij fellen. Ȝif hij setten manaces oȝains me, myn hert ne
-shal nouȝt drede. Ȝyf myn enemy arere bataile oȝains me, y shal hopen in
-þat. Ich asked þe lif þat euer shal last of our Lord; ich shal bisechen
-þat, þat ich mai wonne in þe hous of our Lord alle þe daies of my lif; Þat
-ich se þe wille of our Lord and uisite his temple.
-
-\smallskip
-
-\itshape
-Our Lord, which ich shal douten, is my liȝtyng and my helpe. Our Lord is
-defendour of my lif; for what þyng shal ich drede? To þat noiand comen
-neȝe vp me, þat hij etand my flesshes: Myn enemys, þat trubleden me, ben
-made sike, and hij fellen. Ȝif hij setten manaces oȝains me, myn hert ne
-shal nouȝt drede. Ȝyf myn enemy arere bataile oȝains me, y shal hopen in
-þat. Ich asked þe lif þat euer shal last of our Lord; ich shal bisechen
-þat, þat ich mai wonne in þe hous of our Lord alle þe daies of my lif; Þat
-ich se þe wille of our Lord and uisite his temple.
-
-\end{quote}
-
-\paragraph{Gothic Transliteration}
-
-Two additional letters are used in Gothic transliteration: \textit{þ}
-(þiuþ, thorn) and \textit{ƕ} (hwair). Both of them are available in Old
-Standard:
-
-\begin{quote}
-\large
-
-\fontspec[Script=Latin,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-Akei ik sunja izwis qiþa: batizo ist izwis ei ik galeiþau; unte jabai ik ni
-galeiþa, parakletus ni qimiþ at izwis; aþþan jabai gagga, sandja ina du
-izwis. Jah qimands is gasakiþ þo manaseþ bi frawaurht jah bi garaihtiþa
-jah bi staua; bi frawaurht raihtis, þata þatei ni galaubjand du mis; iþ bi
-garaihtiþa, þatei du attin meinamma gagga, jah ni þanaseiþs saiƕiþ mik;
-iþ bi staua, þatei sa reiks þis fairƕaus afdomiþs warþ.
-
-\smallskip
-
-\itshape
-Akei ik sunja izwis qiþa: batizo ist izwis ei ik galeiþau; unte jabai ik ni
-galeiþa, parakletus ni qimiþ at izwis; aþþan jabai gagga, sandja ina du
-izwis. Jah qimands is gasakiþ þo manaseþ bi frawaurht jah bi garaihtiþa
-jah bi staua; bi frawaurht raihtis, þata þatei ni galaubjand du mis; iþ bi
-garaihtiþa, þatei du attin meinamma gagga, jah ni þanaseiþs saiƕiþ mik;
-iþ bi staua, þatei sa reiks þis fairƕaus afdomiþs warþ.
-
-\end{quote}
- 
-\paragraph{Old Icelandic}
-
-A fragment of text in Old Icelandic. Note some specific letters used in
-that language, as well as the \textit{fj} ligature.
-
-\begin{quote}
-\large
-
-\fontspec[Script=Latin,Language=Icelandic,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-Kømr nú þessi fregn fyrir Hrólf konung ok kappa hans upp í kastalann, at
-maðr mikilúðligr sé kominn til hallarinnar ok hafi drepit einn hirðmann
-hans, ok vildu þeir láta drepa manninn. Hrólfr konungr spurðisk eptir,
-hvárt hirðmaðrinn hefði verit saklauss drepinn. „Því var næsta“, sǫgðu
-þeir. Kómusk þá fyrir Hrólf konung ǫll sannindi hér um. Hrólfr konungr
-sagði þat skyldu fjarri, at drepa skyldi manninn~— „hafi þit hér illan
-vanda upp tekit, at berja saklausa menn beinum; er mér í því óvirðing, en
-yðr stór skǫmm, at gøra slíkt. Hefi ek jafnan rœtt um þetta áðr, ok hafi
-þit at þessu engan gaum gefit, ok hygg ek at þessi maðr muni ekki alllítill
-fyrir sér, er þér hafið nú á leitat; ok kallið hann til mín, svá at ek viti
-hverr hann er“.
-
-\smallskip
-
-\itshape
-Kømr nú þessi fregn fyrir Hrólf konung ok kappa hans upp í kastalann, at
-maðr mikilúðligr sé kominn til hallarinnar ok hafi drepit einn hirðmann
-hans, ok vildu þeir láta drepa manninn. Hrólfr konungr spurðisk eptir,
-hvárt hirðmaðrinn hefði verit saklauss drepinn. „Því var næsta“, sǫgðu
-þeir. Kómusk þá fyrir Hrólf konung ǫll sannindi hér um. Hrólfr konungr
-sagði þat skyldu fjarri, at drepa skyldi manninn~— „hafi þit hér illan
-vanda upp tekit, at berja saklausa menn beinum; er mér í því óvirðing, en
-yðr stór skǫmm, at gøra slíkt. Hefi ek jafnan rœtt um þetta áðr, ok hafi
-þit at þessu engan gaum gefit, ok hygg ek at þessi maðr muni ekki alllítill
-fyrir sér, er þér hafið nú á leitat; ok kallið hann til mín, svá at ek viti
-hverr hann er“.
-
-\end{quote}
-
-A special note is required on the shape of the Icelandic letter \textit{þ}
-(thorn). In modern fonts this character’s design is almost always based on
-the lowercase \textit{p} with an ascender added. This design is also the
-only mentioned by Icelandic type designer Gunnlaugur SE Briem in his
-article \href{http://66.147.242.192/~operinan/2/2.11/index.htm}{Thorn and eth: how
-to get them right}. And yet this letterform doesn’t look characteristic for
-the traditional typography. Generally speaking, there were two styles of
-\textit{thorn} most commonly used in the late 19\textsuperscript{th} and
-early 20\textsuperscript{th} century printing:
-
-\begin{itemize}
-
-\item a glyph based on the lowercase \textit{p}, but with a double sided
-serif at the top of the ascender;
-
-\item a glyph with its top and bottom serifs positioned under an angle to
-the vertical stem and the bowl stretched upwards.
-
-\end{itemize}
-
-In both cases the upper element often doesn’t reach the full ascender
-height, which makes a significant advantage over the modern letterform
-where the glyph often looks unbalanced due to the fact that the ascender is
-significantly longer than the descender.
-
-I have preferred the second form for the upright font, as it looks more
-elegant and seems to be preferable for Old English and the Gothic
-transliteration. However, it is important to stress the fact, that it is
-also perfectly suitable for Norse languages. In particular it was actively
-used for this purpose in the German printing, as for example the “Sammlung
-kurzer Grammatiken Germanischer Dialekte” series, published in Halle a.S.
-in early 20\textsuperscript{th} century and now, thanks to the
-\href{http://www.ling.upenn.edu/~kurisuto/germanic/language\_resources.html}{Germanic
-Lexicon Project}, available on the web in the form high resolution scans, can
-demonstrate.
-
-In the same books, however, the italic thorn already has the contemporary
-style. So I have implemented this letterform too in the italic font
-(where, indeed, it looks more appropriate than in the regular version).
-
-\subsection{Greek Script}
-
-\subsubsection{Alternate Forms}
-
-In addition to the basic Greek alphabet the Unicode standard includes
-alternate forms for several letters, such as script \textit{theta}, stroked
-\textit{phi} and so on. These characters were included mainly for
-compatibility with legacy character sets (Symbol for example), and using
-them anywhere except mathematical contexts is strongly discouraged.
-Nevertheless, the fact these characters are encoded causes a great mess by
-itself, since it convinces font designers to think that any Greek typeface
-can and should include two basic forms for several Greek letters, and that
-some of these forms are always preferred for a Greek text, while others are
-intended only for mathematical usage. Of course this assumption is wrong:
-in fact all such letterforms are font-specific, so that normally only one
-of them is stylistically compatible with each particular typeface.
-
-That’s why, although OldStandard implements several alternate forms for
-Greek letters, only a few of them can be considered really useful. The most
-important of such exceptions is curly \textit{beta} \texttt{U+03D0}: this character,
-indeed, should be available in any correct Greek font, since according to
-the French typographic rules it is used instead of the regular
-\textit{beta} with descender as a medial and final form (the same rule was
-sometimes applied also in Greece itself). For this reason French
-classicists often type \texttt{U+03D0} directly in their documents, and particularly
-I see nothing wrong in this practice, although it is not recommended by
-Unicode. However, in a “smart” font it is also possible to implement
-a contextual substitution rule, allowing initial/medial forms to be
-automatically substituted at the correct places.
-
-In Old Standard v.~1.0 I used contextual alternates (the \texttt{calt}
-feature tag) for this purpose, but later I realized this feature is
-normally enabled by default in most applications which support it, and,
-since contextual forms are not very common in contemporary Greek publishing
-outside France, most classicists would probably be discouraged if they appear
-automatically in their texts. So now a stylistic set (\texttt{ss06}) 
-is used instead.
-
-\begin{figure}[htb]
-
-\centerline{\XeTeXpicfile "greek-contextual.png" width 160mm}
-
-\caption{Contextual forms of \textit{beta} and \textit{theta} in
-traditional Greek typesetting. This example has been taken from: Ὡρολόγιον
-τὸ μέγα, περιέχον ἁπάσαν τὴν ἀνήκουσαν αὐτῷ ἀκολουθίαν, κατὰ τὴν τάξιν τῆς
-ἀνατολικῆς τοῦ Χριστοῦ ἐκκλησίας, καὶ ἐξαιρέτως τῶν ὑποκειμένων αὐτῇ εὐαγῶν
-μοναστηρίων. Ἔκδοσις ἑβδόμη. Ἐν Βενετία, 1851. Σ.~32.}
-
-\label{fig:greek-contextual}
-
-\end{figure}
-
-\textit{Theta} is another letter, which can have two different forms, both
-of which are stylistically compatible with Didot faces. The Unicode
-code chart displays the closed \textit{theta}
-{\fontspec[Script=Greek,RawFeature=+mgrk,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-          ]{OldStandard}\textit{θ}} at \texttt{U+03B8}
-(thus making it the default letterform), while the open, or script variant
-form \textit{ϑ} is mapped to \texttt{U+03D1} and intended only for mathematical
-usage.  Most fonts currently follow this convention. Historically, however,
-selection of one or another form has been made depending from national
-typographic traditions. In particular, French and Greek publishers
-certainly preferred the closed letterform, although in some
-19\textsuperscript{th} century editions the open theta is used at the
-beginning of words, i.~e. a rule, similar to one of \textit{beta}, is
-applied (see \autoref{fig:greek-contextual} for example). On the other
-hand, in German and Russian typography the open \textit{theta} was normally
-used; this is also the only style of this letter found in the Teubner font
-and other cursive Greek typefaces of a German origin.
-
-Since my sources contained good examples of both open and closed
-\textit{theta} in Didot-styled Greek fonts, I have implemented them both,
-and have added a closed letterform even to the italic font for better
-compatibility with the regular version. However, since Old Standard mainly
-follows German typographic conventions, it seemed inappropriate to map this
-form to \texttt{U+03B8} and thus make it the only accessible glyph for the case
-advanced Open Type features are not supported by user’s application.
-Instead the following solution has been preferred: the open \textit{theta}
-is mapped both to \texttt{U+03B8} (GREEK SMALL LETTER THETA) and \texttt{U+03D1} (GREEK THETA
-SYMBOL), while the closed glyph may be automatically substituted instead
-of \texttt{U+03B8} in one of the following situations:
-
-\begin{itemize}
-
-\item in any postition, if the \texttt{ss05} (stylistic set 05) feature
-tag is applied. You can apply this substitution to an ordinary Greek text if
-you prefer the closed form of \textit{theta};
-
-\item applying the \texttt{mgrk} (Mathematical Greek) feature tag triggers the
-same substitution as well. This is supposed to be used in mathematical contexts
-in order to make the glyph mapping exactly corresponding to one defined by the
-Unicode standard;
-
-\item at the middle and the end of words, if the stylistic set 06 (the \texttt{ss06}
-feature tag) is active.
-
-\end{itemize}
-
-Thus enabling both \texttt{ss05} and \texttt{ss06} allows you to typeset your
-text in exact comformance with French typographic conventions (\textit{theta}
-is aways closed, the contextual substitution for \texttt{beta} is on). On the
-other hand, activating just \texttt{ss06} will turn on contextual forms both for
-\textit{beta} and \textit{theta}, as demonstrated below:
-
-\begin{table}[h!]
-\centering\LARGE
-\begin{tabular}[c]{ccc}
-
-\fontspec[Script=Greek,Color=696969,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-θαυμασθεὶς βάρβαρος & ⇒ &
-\fontspec[Script=Greek,RawFeature=+ss06,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-θαυμασθεὶς βάρβαρος \\
-\fontspec[Script=Greek,Color=696969,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-\itshape θαυμασθεὶς βάρβαρος & ⇒ & \itshape 
-\fontspec[Script=Greek,RawFeature=+ss06,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-θαυμασθεὶς βάρβαρος \\
-
-\end{tabular}
-\end{table}
-
-Note that the \texttt{U+03D1} character will always be displayed as a script theta,
-no matter, which feature tags you have applied.
-
-The following example shows a fragment of Greek text with contextual
-alternates (note the medial \textit{beta} and the closed \textit{theta}
-substituted in the appropriate places):
-
-\begin{quote}
-\large
-
-\fontspec[Script=Greek,RawFeature=+ss06,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-Κῦρος δὲ συγκαλέσας τοὺς στρατηγοὺς καὶ λοχαγοὺς τῶν Ἑλλήνων συνεβουλεύετό
-τε πῶς ἂν τὴν μάχην ποιοῖτο καὶ αὐτὸς παρῄνει θαρ\-ρύνων τοιάδε· «ὦ ἄνδρες
-Ἕλληνες, οὐκ ἀνθρώπων ἀπορῶν [βαρβά\-ρων] συμ\-μάχους ὑμᾶς ἄγω, ἀλλὰ νομίζων
-ἀμείνονας καὶ κρείττους πολλῶν βαρβάρων ὑμᾶς εἶναι, διὰ τοῦτο προσέλαβον.
-ὅπως οὖν ἔσεσθε ἄνδρες ἄξιοι τῆς ἐλευθερίας ἧς κέκτησθε καὶ ἧς ὑμᾶς ἐγὼ
-εὐδαιμονίζω. εὖ γὰρ ἴστε ὅτι τὴν ἐλευθερίαν ἑλοίμην ἂν ἀντὶ ὧν ἔχω πάντων
-καὶ ἄλλων πολλαπλασίων».
-
-\itshape
-Κῦρος δὲ συγκαλέσας τοὺς στρατηγοὺς καὶ λοχαγοὺς τῶν Ἑλλήνων συνεβουλεύετό
-τε πῶς ἂν τὴν μάχην ποιοῖτο καὶ αὐτὸς παρῄνει θαρ\-ρύνων τοιάδε· «ὦ ἄνδρες
-Ἕλληνες, οὐκ ἀνθρώπων ἀπορῶν [βαρβά\-ρων] συμ\-μάχους ὑμᾶς ἄγω, ἀλλὰ νομίζων
-ἀμείνονας καὶ κρείττους πολλῶν βαρβάρων ὑμᾶς εἶναι, διὰ τοῦτο προσέλαβον.
-ὅπως οὖν ἔσεσθε ἄνδρες ἄξιοι τῆς ἐλευθερίας ἧς κέκτησθε καὶ ἧς ὑμᾶς ἐγὼ
-εὐδαιμονίζω. εὖ γὰρ ἴστε ὅτι τὴν ἐλευθερίαν ἑλοίμην ἂν ἀντὶ ὧν ἔχω πάντων
-καὶ ἄλλων πολλαπλασίων».
-
-\end{quote}
-
-Except the script \textit{theta} to closed \textit{theta} substitution, the
-\texttt{mgrk} feature allows to change the appearance of some other glyphs.
-This includes \textit{kappa} in all font styles and \textit{rho} in italic
-(in regular and bold the default shape for this character is Unicode conforming).
-Note that the k-shaped glyph for \textit{kappa}, which can be activated by this way, 
-doesn't harmonize well with other Didot-styled letters (although I've done my
-best to make it aesthetically acceptable), so using it anywhere outside of
-math contexts is not recommended.
-
-Old Standard also implements stroked \textit{phi} (\texttt{U+03D5}), omega-like
-\textit{pi} (\texttt{U+03D6}) and lunate epsilon (\texttt{U+03F5}). There are
-no special “smart” font features to get those glyph substituted instead of
-default letterforms, so they can be accessed only by their Unicode codepoints.
-Again, there is no reason to do so when typesetting ordinary Greek texts,
-although the glyphs might be useful in mathematical contexts.
-
-The same statement would be true for the lunate \textit{sigma}, both small and
-capital: although it is sometimes reasonable to use this form e. g. for 
-typesetting papyrological texts (where word breaks and thus the usage of
-final sigmas are sometimes not obvious), it is probably impossible to 
-implement a lunate sigma fully conforming the Didot style. So I don't
-recommend using this letterform and have implemented it mainly in order
-to make existing documents which use this character (such as some texts 
-from the \href{http://www.tlg.uci.edu}{Thesaurus Linguae Graecae} corpus)
-readable.
-
-\subsubsection{Combining Mark Positioning}
-
-Unicode provides codepoints for all accented characters needed for the
-standard Greek orthography, and yet this set is often insufficient for
-classicists. The most common problem is combining a breathing and/or an
-accent with a macron or a breve mark. Also one often has to put a macron,
-a breve or a circumflex above \textit{epsilon} or \textit{omicron} when
-publishing epigraphical documents, although such combinations make no sense
-for literary Greek. For this reason some Unicode Greek fonts include a huge
-number of additional accented characters in the Unicode Private Use Area.
-The most important problem here is that each vendor uses its own
-arrangement of PUA slots, so that fonts are often incompatible with each
-other, especially because very few of them have more or less correct OT
-layouts allowing to access those glyphs without typing them directly.
-
-Old Standard uses a different approach: it has a carefully adjusted set of
-anchor points and \texttt{ccmp} rules, which allow to correctly position
-accent marks relatively to each other and combine breathings with accents
-to specially designed combinations, when necessary. Moreover, when you
-type a capital letter folowed by one or more accents, these accents are
-placed \textit{before} the letter, and the letter itself is shifted right
-to the necessary amount of space. Thus you can type any possible accented
-combination using combining marks, if only your application supports smart
-accent positioning (but this is not a problem at least with Microsoft Word
-2003 and above). Note that you should observe the following order of typing
-diacritics: first a macron or a breve, then a breathing and finally an
-accent. For example, combining marks were used to type the following
-fragment of the Mantinea inscription:
-
-\begin{quote}
-\large
-
-\fontspec[Script=Greek,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-ὀσ̱έοι ἂν χρε̄στε̄́ριον κακρίνε̄ || ε̄̓̀ γνο̄σίαι κακριθε̄́ε̄ το̄͂ν χρε̄μάτο̄ν, | πὲ τοῖς
-ϝοικιάται(ς) τᾶς θεο̄͂ ε̄̓͂ναι, κὰ ϝοικίας δάσασθαι τὰς ἂν ο̄̓͂δ᾽ ἐάσας. εἰ τοῖς
-ϝο̄φλε̄κόσι ἐπὶ τοῖδ’ ἐδικάσαμε[ν], | ἄ τε θεὸς κὰς οἰ δικασσταὶ,
-ἀπυσ̱εδομίν[ος] || το̄͂ν χρε̄μάτο̄ν τὸ λάχος, ἀπεχομίνος | κὰ το̄̓ρρέντερον γένος
-ε̄̓͂ναι | ἄματα πάντα ἀπὺ τοῖ ἰεροῖ, ἴλαον ε̄̓͂ναι.
-
-\smallskip
-
-\itshape
-ὀσ̱έοι ἂν χρε̄στε̄́ριον κακρίνε̄ || ε̄̓̀ γνο̄σίαι κακριθε̄́ε̄ το̄͂ν χρε̄μάτο̄ν, | πὲ τοῖς
-ϝοικιάται(ς) τᾶς θεο̄͂ ε̄̓͂ναι, κὰ ϝοικίας δάσασθαι τὰς ἂν ο̄̓͂δ᾽ ἐάσας. εἰ τοῖς
-ϝο̄φλε̄κόσι ἐπὶ τοῖδ’ ἐδικάσαμε[ν], | ἄ τε θεὸς κὰς οἰ δικασσταὶ,
-ἀπυσ̱εδομίν[ος] || το̄͂ν χρε̄μάτο̄ν τὸ λάχος, ἀπεχομίνος | κὰ το̄̓ρρέντερον γένος
-ε̄̓͂ναι | ἄματα πάντα ἀπὺ τοῖ ἰεροῖ, ἴλαον ε̄̓͂ναι.
-
-\end{quote}
-
-Old Standard includes also several precomposed accented Greek characters in
-the PUA, added for compatibility with
-\href{http://www.users.dircon.co.uk/~hancock/index.htm}{Ralph Hancock}’s
-fonts. However, you should use those characters with a caution and only if
-your application doesn’t support combining mark positioning.
-
-\subsubsection{Tilde-Shaped Circumflex vs. Lunate Circumflex}
-
-Greek circumflex (perispomeni) often becomes a matter of discussions. I
-know, that some (mostly English and American) classicists prefer porsonic
-(lunate) circumflex, similar to an inverted breve, mainly because this form is
-characteristic for most Greek fonts traditionally used in English and
-American typography. However, in fact the preferred design of this accent
-is a purely font specific question. For most typefaces of the continental
-European origin (such as Didot or Teubner) only the tilde-shaped form is
-acceptable, as inverted breve just cannot be harmonized with most letters.
-So, don’t ask me to implement a version with “porsonic” circumflex.
-
-\subsubsection{Iota Adscript vs. Iota Subscript}
-\hypertarget{isub}{}\label{isub}
-
-Combinations of Greek vowels with “mute” iota, defined in Unicode, is one
-more important group of glyphs, which may be designed by various ways,
-depending from the designer’s preferences. Most ancient Greek language
-manuals state that mute iota (called \textit{iota subscript}) is written
-below lowercase letters, but after capital vowels a regular small iota,
-written inline and so called \textit{iota adscript}, should be used
-instead.  Currently most Unicode Greek fonts follow this convention, and
-many classicists even suppose any over implementations of uppercase
-combinations with mute iota to be illegal.
-
-However, iota subscript below capital letters also may occur in some
-editions. In particular, this orthography is very common for liturgical
-books of the Greek Orthodox church. Particularly I prefer this typographic
-tradition, not only because it is inherited from fine Greek typography of
-the past centuries, but also for some technical reasons. The problem here
-is that, if a mute iota is designed as a regular iota and printed inline,
-it should behave as a separate character. This means that, when
-letterspacing for the surrounding text is changed, the distance between the
-iota and the preceding vowel should be scaled too. Of course this is
-impossible if both characters are implemented as a single glyph.
-
-That’s why in Old Standard mute iota is looks like a iota subscript in
-all accented combinations with capital vowels. Note that \textit{unaccented}
-capital vowels with mute iota represent a special case: unlike their
-accented counterparts, they are used in upper case only, i.~e. may occur
-only in a fully capitalized text. So for these glyphs (namely, Unicode
-characters \texttt{U+1FBC}, \texttt{U+1FCC}, \texttt{U+1FFC}) I have designed a special version of
-iota adscript, which looks like a \textit{capital} Iota, decreased in size.
-To my mind, this shape will better match to the design of surrounding
-capital glyphs.
-
-Such an implementation of capital vowels with mute iota has nothing wrong
-by itself, but, of course, it would be nice to allow replacing each of
-affected Unicode codepoints with a pair of glyphs: the vowel itself and a
-regular iota. Theoretically, this could be done by applying a smart font
-feature, but, unfortunately, I am not aware of any suitable OpenType
-feature, which:
-
-\begin{itemize}
-
-\item can be used for replacing a single glyph with two or more glyphs, as in
-our case;
-
-\item can be disabled if a user doesn’t like it.
-
-\end{itemize}
-
-Things are different for \hyperlink{Graphite}{Graphite}, since this
-technologie doesn't impose any limitations on the number and usage of
-features the designer would consider appropriate. That's why in Graphite-enabled
-applications Old Standard now uses the adscript design by default. This
-can be easily changed by applying another value to the appropriate
-feature. Unfortunately I can't implement the same behavior in a way
-compatible with OpenType, so all other applications will just use the
-default glyphs for capital vowels with the mute iota. If you absolutely
-don’t like the subscript design, at least you can always type regular
-iota as a separate character. 
-
-\subsection{Cyrillic Script}
-
-\subsubsection{Combining Mark Positioning}
-
-Smart combining mark positioning is often necessary for Cyrillic.
-Although the stress is usually not indicated in modern languages which use
-the Cyrillic script, accentuation is still mandatory for textbooks,
-dictionaries and books for children. This is especially important for
-Serbian, which has long and short vowels and four types of accent.
-Nevertheless, there are virtually no precomposed Cyrillic accented
-characters in Unicode, so that using combining marks remains the only
-option. So Old Standard provides all necessary anchor points allowing to
-place accents above Cyrillic vowels (see the following sections about
-Serbian and Old Slavonic for examples).
-
-\subsubsection{Serbian Alternate Forms}
-
-It is a well known fact, that, except several specific letters, Serbian
-Cyrillic alphabet also has different preferred shapes for some letters
-common for most languages which use the Cyrillic script. According to the
-most common opinion, four Serbian variant forms are specific for the
-italic style, while one can occur both in roman and italic styles, as
-\autoref{fig:serbian} demonstrates. This practice was adopted by many font
-designers, and Adobe even included Serbian variant forms into its Cyrillic
-specification, although they have not been accepted by Unicode.
-
-\begin{figure}
-
-\centerline{\XeTeXpicfile "serbian.png" width 80mm}
-
-\caption{Serbian and Macedonian variant forms. Russian norms on the left,
-Serbian and Macedonian norms on the right}
-\label{fig:serbian}
-
-\end{figure}
-
-However, after studying several examples of old Serbian printing (a small
-collection of such examples was previously available at the site of the
-faculty of Mathematics at the Belgrade university) I have an impression that
-the modern practice is not fully justified by the preceding tradition.
-
-As far as I can see, there are only two letters (namely Cyrillic \textit{п}
-and \textit{т}), which always have typically “Serbian” forms, clearly
-distinct from their Russian counterparts. However, the late
-19\textsuperscript{th} and early 20\textsuperscript{th} century editions,
-set with Modern typefaces, also show a significant difference from the
-contemporary “Serbian” style, as the horizontal bar (the most
-characteristic feature of “Serbian” \textit{п} and \textit{т}) is attached
-to the base glyph rather than positioned above it (like a diacritical
-mark). The \textit{т} also may look like a slanted upright glyph, but I
-have preferred to draw both \textit{п} and \textit{т} in the same
-“historical” style.
-
-It is especially important to stress that “Serbian” \textit{д} with a hook
-below seems to never occur in the traditional Serbian printing, although
-there was absolutely no problem to reproduce this form, if somebody
-considered it correct, as Latin italic \textit{g} has exactly the same
-shape in Modern typefaces of the early 20\textsuperscript{th} century. My
-own opinion is that the contemporary Serbian letterform first appeared as a
-result of uncritically reproducing the handwritten shape, erroneously
-considered typically Serbian (actually it is not, as the same style is
-preferred also in the Russian handwriting, which doesn’t mean this practice
-should necessarily be reflected in printing). On the other hand, I have an
-impression that the “Russian” italic \textit{д} (with an ascender) is also
-not so common in Serbian printing: often it is replaced with a slanted
-version of the upright letter. This glyph seemed a good compromise for me:
-based on the historical tradition and at the same time certainly acceptable
-for those Serbs who absolutely don’t like the Russian form.
-
-In Old Standard only three italic letters, listed above (\textit{д},
-\textit{п} and \textit{т}) form the default set of Serbian alternate forms,
-which are automatically enabled when you mark a text with Serbian language.
-Alternatively, if your application doesn’t support the \texttt{locl}
-feature tag (which is probably the case) you can achieve the same result by
-enabling the stylistic set 11. Here an example of a fully accentuated 
-Serbian text, which demonstrates both the combining mark positioning and
-the localized forms in the italic style:
-
-\begin{quote}
-\large
-
-\fontspec[Script=Cyrillic,Language=Serbian,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-На но̀ве̄мбарско̄м су̑нцу прѐврће̄ се пр̏љава̄ у̏троба на̏ше̄ ку̏ће̄. Чу̏дно сам ту̑жан.
-И док но̏сӣм с ма̑јко̄м си̑вӯ о̀тр̄ца̄нӯ сла̏марицу ту̑по за̀гледан у јѐдан мр̑твӣ
-о̏бла̄к над цр̑нӣм, ни̏скӣм кро̀во\-вима на̏ше̄г прѐдгра̄ђа~— са̀плиће̄м се о пра̏г. О̀на
-ми ка̑же̄: „Па̏зи“. О̏нда̄ бри̑жно: „Шта̏ ти је да̀нас?“ О̀на је ве̏лика гла̑дна̄ жѐна,
-си́во̄ст ѝзбӣја̄ ѝз ње̄. У̀опште, све̏ је да̀нас си̑во. И не̏бо, и на̏ша а̀влија, и
-шу́паљ, гра̀нат о̀рах сред ње̑, и о̀ве̄ на̏ше ства̑ри ко̀је̄, јѐдна по јѐдна, ѝзлазе̄
-на да̑н.
-
-\smallskip
-
-\itshape
-На но̀ве̄мбарско̄м су̑нцу прѐврће̄ се пр̏љава̄ у̏троба на̏ше̄ ку̏ће̄. Чу̏дно сам ту̑жан.
-И док но̏сӣм с ма̑јко̄м си̑вӯ о̀тр̄ца̄нӯ сла̏ма\-рицу ту̑по за̀гледан у јѐдан мр̑твӣ
-о̏бла̄к над цр̑нӣм, ни̏скӣм кро̀вовима на̏ше̄г прѐдгра̄ђа~— са̀плиће̄м се о пра̏г. О̀на
-ми ка̑же̄: „Па̏зи“. О̏нда̄ бри̑жно: „Шта̏ ти је да̀нас?“ О̀на је ве̏лика гла̑д\-на̄ жѐна,
-си́во̄ст ѝзбӣја̄ ѝз ње̄. У̀опште, све̏ је да̀нас си̑во. И не̏бо, и на̏ша а̀влија, и
-шу́паљ, гра̀нат о̀рах сред ње̑, и о̀ве̄ на̏ше ства̑ри ко̀је̄, јѐдна по јѐдна, ѝзлазе̄
-на да̑н.
-
-\end{quote}
-
-The case of the letter \textit{б} is basically the same as one of the
-\textit{д}. The only difference here is that the “script” form actually
-seems to be more common for Russian, than for Serbian printing, although in
-the Russian tradition it is applicable only for the italic style. At least
-it was used in the italic version of one particular “Standard” typeface of
-early 20\textsuperscript{th} century. That’s why I have implemented this
-letterform in Old Standard, although the italic version of the glyph is
-actually based on a Russian source, and the upright shape has been added
-just for completeness. These glyphs are not automatically applied for
-Serbian text by default, but you can enable the stylistic set 12 to get
-them substituted, as in the following example:
-
-\begin{table}[h!]
-\centering\LARGE
-
-\begin{tabular}[c]{ccc}
-
-\fontspec[Script=Cyrillic,Language=Serbian,Color=696969,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}мртви облак & ⇒ &
-\fontspec[Script=Cyrillic,Language=Serbian,RawFeature=+ss12,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}мртви облак \\
-\fontspec[Script=Cyrillic,Language=Serbian,Color=696969,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}\itshape мртви облак & ⇒ &\itshape 
-\fontspec[Script=Cyrillic,Language=Serbian,RawFeature=+ss12,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}мртви облак \\
-
-\end{tabular}
-\end{table}
-
-Finally, the case of “Serbian” \textit{г} is a bit special: here the
-specific shape is really justified by the peculiarities of the Serbian
-handwriting tradition, and yet the letterform normally used in pre-computer
-Serbian printing was typically Russian, i.~e. had no horizontal bar above.
-Particularly I think the modern “Serbian” variant has nothing wrong by
-itself, but, of course, it is difficult to implement it, if both
-\textit{п} and \textit{т} are designed in the historical style, so that
-there is no gap between the bar and the base glyph. Nevertheless I have
-attempted to implement a Serbian \textit{г} in the same style as \textit{п}
-and \textit{т}, basing on
-\href{http://cirilica.com/cirilica/Strane/Slova/Azbuka.html}{the
-recommendations by Nikola Kovanovich}, but this glyph is purely
-experimental, and thus currently it is not accessible via any OpenType
-features.
-
-\subsubsection{Old Slavonic and Church Slavonic}
-
-Until 2008, Unicode included only a subset of historical Cyrillic
-characters, which was not sufficient for typesetting any actual texts.
-Thus legacy encodings or PUA-based solutions were the only solution for 
-representing historical documents in old Slavic languages which used
-the Cyrillic script. In Unicode 5.1 the range of supported early 
-Cyrillic characters was greatly extended and now includes all letters
-and signs normally used in scientific publication and Orthodox liturgical 
-books (including even combining letters). Beginning from the version
-2.0 Old Standard fully supports historical Cyrillic, including Unicode
-5.1 extensions.
-
-However, except just having all necessary characters available in a font,
-typesetting Old Slavonic or Church Slavonic also requires some complex
-text rendering. So the following smart font features necessary for this
-purpose are implemented in Old Standard:
-
-\begin{description}
-
-\item[Combining mark positioning] Old Slavonic (and especially modern
-Church Slavonic) has a wide range of combining characters, such as accents,
-breathings, titlos and superscript letters. Basically the accentuation
-system is very similar to Greek one, but, unlike for Greek, there are no
-precomposed accented characters available in Unicode, so that using
-combining marks is the only option.
-
-\item[Enclosing combining marks] Church Slavonic inherited from Greek
-its numeric system, where numbers are denoted with letters. However, special
-enclosing marks, shown in the following table, have been invented to denote
-large numbers beginning from 10000:
-
-\begin{table}[h!]
-\centering
-\begin{tabular}[c]
-{|>{\fontspec[Script=Cyrillic,Language=Church Slavonic,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-             ]{OldStandard}}
-p{4em}|p{5.6em}|p{5.6em}|}
-\hline
-\textit{Notation}& \textit{Numerical meaning}& \textit{Old Slavonic name}\\
-\hline
- \Large\hfil{а҃⃝}\hfil & 10\,000 & тьма\\
-\hline
- \Large\hfil{а҃҈}\hfil & 100\,000 & легион\\
-\hline
- \Large\hfil{а҃҉}\hfil & 1\,000\,000 & леодр\\
-\hline
- \Large\hfil{а҃꙰ }\hfil & 10\,000\,000 & ворон\\
-\hline
- \Large\hfil{а҃꙱ }\hfil & 100\,000\,000 & колода\\
-\hline
-\end{tabular}
-\end{table}
-
-Old Standard implements two types of OT lookups to achieve proper positioning
-for this kind of marks: first, standard anchor points (the \texttt{mark}
-feature) used to attach a mark to a base character, and second, contextual
-positioning lookups allowing to increase the base character bearings and
-advance width when it is followed by enclosing marks. Unfortunately, this
-technique is not guaranteed to work in all OpenType-aware applications: in 
-particular at the time this manual was written contextual positioning did 
-not properly work in \XeTeX.
-
-\item[Historic letterforms] Although the modern Cyrillic script (so called
-“civil” style) is often used to typeset medieval texts, some of the modern
-letterforms are especially closely associated with the typographic reform under
-Peter the Great, and thus would look out of place in a historical context. 
-That's why Old Standard provides some stylistic alternates, specially intended
-for Old Russian and Old (Church) Slavonic:
-
-\begin{table}[h!]
-\centering\LARGE
-\begin{tabular}[c]{cccc}
-
-\fontspec[Script=Cyrillic,Color=696969,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-не вѣдыи бѹдѹщаго & 
-⇒ & 
-\fontspec[Script=Cyrillic,Language=Church Slavonic,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-не вѣдыи бѹдѹщаго &\\
-
-\fontspec[Script=Cyrillic,Color=696969,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-\itshape не вѣдыи бѹдѹщаго & 
-⇒ & 
-\fontspec[Script=Cyrillic,Language=Church Slavonic,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-\itshape не вѣдыи бѹдѹщаго &\\
-
-\end{tabular}
-\end{table}
-
-These alternates are enabled for Old Church Slavonic, if
-your application understands the \texttt{locl} feature tag and allows
-to mark a text with this language. Alternatively you can get the same
-substitutions by applying the stylistic set 14 (\texttt{ss14}).
-
-There is also an additional stylistic set (\texttt{ss15}) intended to handle
-the Cyrillic I vs. Cyrillic N problem. It is a well known fact that in the oldest
-Cyrillic manuscripts these two letters looked more like their Greek prototypes
-(\textit{Eta} and \textit{Nu}), and only in 15\textsuperscript{th} century
-the middle bar slope has aquired its modern form. However using an H-shaped
-Cyrillic I and N-shaped Cyrillic N by default (even for typesetting Old Slavonic)
-would probably be misleading in some context. So these substitutions (they are
-available only in regular and bold) are optional:
-
-\begin{table}[h!]
-\centering\LARGE
-\begin{tabular}[c]{cccc}
-
-\fontspec[Script=Cyrillic,Language=Church Slavonic,Color=696969,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-не вѣдыи бѹдѹщаго & 
-⇒ & 
-\fontspec[Script=Cyrillic,Language=Church Slavonic,RawFeature=+ss15,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-не вѣдыи бѹдѹщаго &\\
-
-\end{tabular}
-\end{table}
-
-\item[Contextual letterforms] Some Cyrillic letters have tall ascenders,
-while in medieval manuscripts the same letters normally did not extend above
-x-height, so that it was possible to put an accent or a combining letter
-above them. Old Standard includes special low forms for some of such letters
-(namely \textit{б} and \textit{ѣ}) and can automatically subsitute them
-when the letter is followed by an accent:
-
-\begin{table}[h!]
-\centering\LARGE
-\fontspec[Script=Cyrillic,Language=Church Slavonic,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-
-\begin{tabular}[c]{ccc}
-
-\fontspec[Script=Cyrillic,Language=Church Slavonic,Color=696969,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-прѣдъ богомъ & ⇒ & прѣⷣ҇ бⷢ҇омъ \\
-\fontspec[Script=Cyrillic,Language=Church Slavonic,Color=696969,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-\itshape прѣдъ богомъ & ⇒ &\itshape прѣⷣ҇ бⷢ҇омъ \\
-
-\end{tabular}
-\end{table}
-
-\end{description} 
-
-Finally an example of Old Slavonic text with combining marks and historic
-letters and letterforms:
-
-\begin{quote}
-\large
-
-\fontspec[Script=Cyrillic,Language=Church Slavonic,
-          ItalicFont = *-Italic,
-          UprightFont = *-Regular,
-         ]{OldStandard}
-А҆ ѡ҆ сеⷨ Иракліи и҆ною̀ притчею рекоша сеⷤ Феѡ҆́фиⷧ҇ мⷣрыи хронограⷴ написа.
-Є҆рміи же раⷥумѣвь на нь творѧщꙋся братію ѿиде, ꙁлато многѡ̀ вꙁемъ, и҆ и҆де 
-въ Є҆гѷпеⷮ҇ къ коленꙋ Хамову сн҃а Ноєва. иⷤ и҆ пріаша є҆́го с̾ честію. и҆ живе
-тѹ во̑ вѣлице чьсти, носѧ риꙁу ꙁлаⷮу и҆ мⷣрствꙋꙗ҆́ше па Є҆гѷпетскыⷯ влъхвоⷯ҇,
-влъх̾вѹѧ и҆ повѣда и҆мъ хотѧщаѧ̀ быти. бѣ̏ же и҆ хїтръ бесѣдаⷨ. и҆ кланѧхꙋсѧ
-є҆́му гл҃ще б҃ъ Є҆рміин ꙗ҆ко повѣдающа иⷨ хотѧщаѧ̀ быти и҆мъ и повѣдающа 
-иⷨ и҆мѣніє є҆гоⷤ и дателѧ богаⷮствѹ нарицахѹ ꙗ҆ко ꙁлат̾наго б҃а мнѧще.
-
-\smallskip\itshape
-
-А҆ ѡ҆ сеⷨ Иракліи и҆ною̀ притчею рекоша сеⷤ Феѡ҆́фиⷧ҇ мⷣрыи хронограⷴ написа.
-Є҆рміи же раⷥумѣвь на нь творѧщꙋся братію ѿиде, ꙁла\-то многѡ̀ вꙁемъ, и҆ и҆де 
-въ Є҆гѷпеⷮ҇ къ коленꙋ Хамову сн҃а Ноєва. иⷤ и҆ пріаша є҆́го с̾ честію. и҆ живе
-тѹ во̑ вѣлице чьсти, носѧ риꙁу ꙁлаⷮу и҆ мⷣрствꙋꙗ҆́ше па Є҆гѷпетскыⷯ влъхвоⷯ҇,
-влъх̾вѹѧ и҆ повѣда и҆мъ хотѧщаѧ̀ быти. бѣ̏ же и҆ хїтръ бесѣдаⷨ. и҆ кланѧхꙋсѧ
-є҆́му гл҃ще б҃ъ Є҆рміин ꙗ҆ко повѣдающа иⷨ хотѧщаѧ̀ быти и҆мъ и повѣдающа 
-иⷨ и҆мѣніє є҆гоⷤ и дателѧ богаⷮствѹ нарицахѹ ꙗ҆ко ꙁлат̾наго б҃а мнѧще.
-
-\end{quote}
-
-\omit{
-
-\subsection{Graphite Support}
-\hypertarget{Graphite}{}\label{Graphite}
-
-\href{http://scripts.sil.org/Graphite}{Graphite} is a rendering technologie
-developed by \href{http://www.sil.org}{SIL International}. It is similar
-to OpenType at some aspects, but doesn't prescribe a list of features with
-predefined meanings and their possible implementations, thus leaving more
-freedom to a font designer. Another advantage of Graphite is that it gives
-a better control on some subtle aspects of font behavior. However, this
-technologie isn't currently widely supported: except SIL's own
-\href{http://scripts.sil.org/WorldPadDownload}{WorldPad} editor (a
-Windows-only application which requires a .NET runtime), the Graphite
-support is now built into OpenOffice.org (beginning from the 3.2 version)
-and LibreOffice. There is also an open-source project to put Graphite
-support into Mozilla.
-
-This means the Graphite support in Old Standard would be mostly actual for
-OpenOffice.org/LibreOffice users. Since this office suite still lacks
-proper OpenType support for Wester scripts (its Windows version depends
-from Miscrosoft Uniscribe rendering engine), Graphite gives a nice
-possibility to get a consistent rendering both on Linux and Windows
-platforms. It also provides an optional features support (although for
-reasons discussed below I'd not recommend to actively use it at the
-present time).
-
-Note that it is currently not possible to add Graphite tables to
-OpenType-CFF fonts. So for now the technologie is only supported by
-the TrueType version of Old Standard.
-
-\subsubsection{Graphite Features in Old Standard}
-
-In Graphite fonts each feature is identified by a human-readable name
-(which may be localized, but Old Standard currently includes only US
-English names) and a unique ID. Those IDs are often numerical, but in
-Old Standard 4-letter codes, similar to OpenType feature tags, are used
-for this purpose. A Graphite feature normally has several states (or
-settings), which again have their own names and IDs. In the simplest case
-a feature is boolean, i.~e. supports just two two possible settings: 1
-(true) and 0 (false).
-
-The following table lists all Graphite features defined in Old Standard
-with their possible settings. It also tells which settings are available
-for each particular style (for example, there are no required Serbian
-forms in regular and bold). The last column shows the correspondences between
-OpenType and Graphite features. Note that some cells in this columns are
-left blank, and this means the given feature setting corresponds to the
-default font behavior, without any OpenType features applied. A dash (---)
-indicates there is no OpenType feature similar to this Graphite
-feature/setting pair.
-
-\begin{center}
-\setlength{\tabcolsep}{2.4pt}
-\begin{longtable}[c]{|>{\raggedright}p{11.2em}|T|>{\raggedright}p{8.4em}|p{2em}|c|c|c|T|}
-\hline
-\multicolumn{2}{|B|}{\rule{0pt}{14pt}Supported Features} & \multicolumn{2}{B|}{Feature Settings} &
-\multicolumn{3}{B|}{Font Styles} & \multicolumn{1}{B|}{OpenType}\\
-\cline{1-7}
-\multicolumn{1}{|B|}{\rule{0pt}{14pt}English Name} & \multicolumn{1}{B|}{ID} & \multicolumn{1}{B|}{Name} &
-\multicolumn{1}{B|}{ID} & \multicolumn{1}{B|}{Rg} & \multicolumn{1}{B|}{Bd} &
-\multicolumn{1}{B|}{It} & \multicolumn{1}{B|}{equiv.}\\
-\hline
-
-Diagonal Fractions & frac & False/True & 0/1  & + & + & + & frac\\
-\hline
-
-Vertical Position & vpos & Normal Vertical Position & 0 & + & + & + & \\
-\cline{3-8}
-
-& & Superiors & 1 & + & + & + & sups \\
-\cline{3-8}
-
-& & Inferiors & 2 & + & + & + & subs \\
-\hline
-
-Ligatures & liga & No Ligatures & 0 & + & + & + & \\
-\cline{3-8}
-
-& & Common Ligatures & 2 & + & + & + & liga\footnote{\texttt{dlig} for German.} \\
-\hline
-
-Diphthong Ligatures & dphl & False/True & 0/1 & + & + & + & dlig\\
-\hline
-
-French Spacing Rules\newline for Punctuation Marks & frsp & False/True & 0/1  & + & + & + & -\\
-\hline
-
-Localized Forms\newline for Romanian & rolc & No Localized Forms & 0 & + & + & + & \\
-\cline{3-8}
-
-& & Required\newline Localized Forms & 1 & + & + & + & locl; ss01 \\
-\hline
-
-Localized Forms\newline for Serbian & srlc & No Localized Forms & 0 & + & + & + & \\
-\cline{3-8}
-
-& & Required\newline Localized Forms & 1 & − & + & − & locl; ss11 \\
-\cline{3-8}
-
-& & Optional\newline Localized Forms & 2 & + & + & + & ss12 \\
-\hline
-
-Localized Forms\newline for Old Slavonic & oslc & No Localized Forms & 0 & + & + & + & \\
-\cline{3-8}
-
-& & Required\newline Localized Forms & 1 & + & + & + & locl; ss14 \\
-\cline{3-8}
-
-& & Optional\newline Localized Forms & 2 & + & − & + & ss15 \\
-\hline
-
-Greek Punctuation Marks & elpt & False/True & 0/1  & + & + & + & locl\\
-\hline
-
-Mathematical Greek & mgrk & False/True & 0/1  & + & + & + & mgrk\\
-\hline
-
-Greek Theta & elth & Script Form & 0 & + & + & + & \\
-\cline{3-8}
-
-& & Closed Form & 1 & + & + & + & ss05\\
-\hline
-
-Contextual Forms\newline for Greek & elct & False/True & 0/1 & + & + & + & ss06\\
-\hline
-
-Greek Accents & elmk & Before Capitals & 0 & + & + & + & \\
-\cline{3-8}
-
-& & Above Capitals & 1 & + & + & + & —\\
-\hline
-
-Greek Mute Iota\newline with Capitals & elis & Adscript & 0 & + & + & + & —\\
-\cline{3-8}
-
-& & Subscript & 1 & + & + & + & \\
-\hline
-
-Capitalized Greek & elcp & False/True & 0/1  & + & + & + & —\\
-\hline
-
-Language-Dependent Feature Modifications & fmod & Default & 0 & + & + & + & \\
-\cline{3-8}
-
-& & Dutch & 19 & + & + & + & —\\
-\cline{3-8}
-
-& & Turkish & 31 & + & + & + & —\\
-\hline
-
-\end{longtable}
-\end{center}
-
-Note that some OpenType features, supported by Old Standard, (such as
-\texttt{ccmp}, \texttt{mark} or \texttt{mkmk}) are not listed in this
-table. In fact my Graphite tables implement nearly the same functions
-as provided by those features, but the corresponding rules are considered
-mandatory and always executed, so there are no optional features to
-control them. On the other hand, you can see that most Graphite features
-have their OpenType equivalents. However, due to more flexible nature
-of the Graphite technologie it was possible to describe some additional
-features, which would be too difficult to implement in OpenType. These
-features are listed below.
-
-\begin{description}
-
-\item[French Spacing Rules] This feature adds extra space to some
-punctuation marks, as required by the French typographic rules. It will
-be on by default for a French text.
-
-\begin{table}[h!]
-\centering\LARGE
-\begin{tabular}[c]{>{\fontspec[Script=Latin,Color=696969]{Old Standard TT}}cc
->{\fontspec[
-	Renderer=Graphite,
-	ItalicFont=OldStandardTT-Italic,
-	RawFeature={French Spacing Rules for Punctuation Marks=True}]{Old Standard TT}}c}
-
-Il a dit: «Bonjour!» & ⇒ & Il a dit: «Bonjour!»\\
-\itshape Il a dit: «Bonjour!» & ⇒ &\itshape Il a dit: «Bonjour!»\\
-
-\end{tabular}
-\end{table}
-
-\item[Greek Accents] Setting this feature to the “Above Capitals” state
-causes Greek accents/breathings to be displayed above capital letters 
-instead of their default position before capitals. This convention would
-probably look a bit chocking for a modern classicist, but it was quite
-common in Greek 19\textsuperscript{th} century typography.
-
-\begin{table}[h!]
-\centering\LARGE
-
-\begin{tabular}[c]{>{\fontspec[Script=Greek,Color=696969]{Old Standard TT}}cc
->{\fontspec[
-	Renderer=Graphite,
-	ItalicFont=OldStandardTT-Italic,
-	RawFeature={Greek Accents=Above Capitals}]{Old Standard TT}}c}
-
-ᾨδὴ ἐν ᾍδη & ⇒ & ᾨδὴ ἐν ᾍδη \\
-
-\itshape ᾨδὴ ἐν ᾍδη & ⇒ &\itshape ᾨδὴ ἐν ᾍδη \\
-
-\end{tabular}
-\end{table}
-
-\item[Greek Mute Iota with Capitals] This feature allows to select the
-preferred style of the Greek mute iota in combination with capital
-letters. See \autoref{isub} for more information of this issue. Note 
-that the adscript style (i.~e. a normal lowercase iota) is used
-by default if the Graphite rendering is enabled, while in applications
-which don't support Graphite the corresponding glyphs are always
-rendered with iota subscript.
-
-\begin{table}[h!]
-\centering\LARGE
-
-\begin{tabular}[c]{>{\fontspec[Script=Greek,Color=696969]{Old Standard TT}}cc
->{\fontspec[
-	Renderer=Graphite,
-	ItalicFont=OldStandardTT-Italic,
-	RawFeature={Greek Mute Iota with Capitals=Adscript}]{Old Standard TT}}c}
-
-ᾨδὴ ἐν ᾍδη & ⇒ & ᾨδὴ ἐν ᾍδη \\
-
-\itshape ᾨδὴ ἐν ᾍδη & ⇒ &\itshape ᾨδὴ ἐν ᾍδη \\
-
-\end{tabular}
-\end{table}
-
-\item[Capitalized Greek] This feature converts lowercase Greek letters
-to uppercase. The accents/breathings are removed, unless the “Greek
-Accents” feature is set to “Above Capitals”:
-
-\begin{table}[H]
-\centering\LARGE
-
-\begin{tabular}[c]{>{\fontspec[Script=Greek,Color=696969]{Old Standard TT}}cc
->{\fontspec[
-	Renderer=Graphite,
-	ItalicFont=OldStandardTT-Italic,
-	RawFeature={Capitalized Greek=True}]{Old Standard TT}}c}
-
-ἄυλος αὐλὸς & ⇒ & ἄυλος αὐλὸς \\
-
-\itshape ἄυλος αὐλὸς & ⇒ &\itshape ἄυλος αὐλὸς \\
-
-\end{tabular}
-\end{table}
-
-Ιn the later case the diacritical marks preserved, but placed at the top of
-the capitalized letters:
-
-\begin{table}[h!]
-\centering\LARGE
-
-\begin{tabular}[c]{>{\fontspec[Script=Greek,Color=696969]{Old Standard TT}}cc
->{\fontspec[
-	Renderer=Graphite,
-	ItalicFont=OldStandardTT-Italic,
-	RawFeature={
-		Capitalized Greek=True;
-		Greek Accents=Above Capitals}]{Old Standard TT}}c}
-
-ἄυλος αὐλὸς & ⇒ & ἄυλος αὐλὸς \\
-
-\itshape ἄυλος αὐλὸς & ⇒ &\itshape ἄυλος αὐλὸς \\
-
-\end{tabular}
-\end{table}
-
-\item[Language-Dependent Feature Modifications] This feature may modify
-the effect produced by some other features depending from its current
-setting. For example, in the Turkish mode fi-ligatures are disabled. In
-OpenType the same effect is achieved by associating a feature lookup
-with a specific combination of scripts/languages. It is not recommended
-to manually change settings of this feature: they are supposed to be
-activated by default depending from the language assigned to a text in
-your application.
-
-\end{description}
-
-\subsubsection{Using Graphite Features in OpenOffice.org/LibreOffice}
-
-\begin{figure}[htb]
-
-\centerline{\XeTeXpicfile "graphite-ooo-extension.png" width 104mm}
-
-\caption{The window of the Graphite Font Extension for OpenOffice.org,
-displaying the Graphite features of Old Standard.}
-
-\hypertarget{fig:graphite-ext}{}\label{fig:graphite-ext}
-
-\end{figure}
-
-OpenOffice.org 3.2 and above (or LibreOffice) automatically recognizes
-fonts which contain Graphite tables. For such fonts Graphite rendering
-is enabled by default. However, currently there is no special GUI
-allowing to select typographic features (either OpenType or Graphite).
-Instead, a special extended font name syntax has been developed: in
-order to activate an optional feature, its ID, followed by an equals
-sign and the ID of the desired setting, are appended directly to the
-font name string. An ampersand is used to separate different feature/settings
-pairs.
-
-For example, the following “font” should be used in order to get
-capitalized Greek text with accents and breathings placed
-above letters:
-
-\begin{verbatim}
-Old Standard TT:elmk=1&elcp=1
-\end{verbatim}
-
-Of course modifying the font name directly is very inconvenient, since
-it is difficult to remember short tags and numerical values used for
-feature/setting IDs in different fonts. Things may be simplified if you
-install Keith Stribley's \href{http://www.thanlwinsoft.org/GraphiteOOoExt/}
-{Graphite Font Extension}, which provides a \hyperlink{fig:graphite-ext}{dialog}
-to make feature selection easy.
-
-However, at the present time (as for March 2011) this extension should be
-used with a caution due to several problems related both with the extension
-itself and the Graphite renderer:
-
-\begin{itemize}
-
-\item the extension cannot determine which feature settings are supposed
-to be on for the current text language. For example, in Old Standard
-common ligatures are enabled by default but disabled for German.
-Thus you can't activate the standard Latin ligatures in a German text
-with the Graphite extension, since it will consider they are already on;
-
-\item the displayed list of features and their possible settings will
-always correspond to the regular font, even if the the selected text is
-formatted in bold or italic;
-
-\item the extension doesn't care about the order of applied features,
-and, unfortunately, this order may be significant, since applying multiple
-features at once may sometimes lead to incorrect rendering. However, this
-problems doesn't occur, if feature IDs are appended to the font name in
-the same order as they are defined in the font file.
-
-\end{itemize}
-
-If you have experienced any of the problems described above, then you
-have only two options available: either to avoid using optional features
-at all, or to access them by modifying the font name directly. Refer
-to the table above for the list of feature/setting IDs supported by
-Old Standard.
-
-It is also possible that the Graphite renderer will do wrong things
-for you, so that you want to avoid using it. Then you can either switch
-to the OpenType-CFF version of the font (which doesn't support Graphite),
-or to completely disable the Graphite engine for your OpenOffice.org
-installation. You can do this by modifying the \texttt{SAL\_DISABLE\_GRAPHITE}
-environment variable which is set in \texttt{\textasciitilde/.profile} on Linux and
-\texttt{HKCU/environment} in the Windows registry. Graphite Font Extension
-provides a GUI option to simplify this operation (however, it didn't work on
-my Ubuntu box).
-
-\subsubsection{Using Graphite Features in \XeTeX}
-
-Graphite Support has recently been added to \XeTeX, which means Graphite
-features are now accessible from \TeX{} documents. Moreover, it is possible
-to enable the Graphite font renderer with the \texttt{fontspec} package,
-which greatly simplifies selecting system-installed fonts in \LaTeX{}
-documents for users of Unicode-based \TeX{} compilers (\XeTeX{} and \LuaTeX).
-This functionality is relatively new, so you'll need at least \TeX{} Live 2010
-or Mik\TeX 2.9 for the recommendations below to work.
-
-You can activate the Graphite rendering mode for a particular font via the
-the \texttt{Renderer} option (its value should be set to \texttt{Graphite})
-in the argument list of a font selection command (such as \verb|\fontspec|,
-\verb|\newfontfamily| or \verb|\setmainfont|). Since there are no standard
-feature tags in Graphite, most of the \texttt{fontspec} feature selection
-interface is useless here: optional feature identifiers and their settings are
-just passed to the \texttt{RawFeature} option (which normally serves
-the last resort for accessing OpenType features which aren't supported otherwise).
-
-As the \texttt{fontspec} package author
-\href{http://tex.stackexchange.com/questions/4324/using-graphite-fonts-on-xelatex}{has
-explained}, both \texttt{<feature ID>=<setting ID>} and \texttt{<feature name>=<setting name>}
-combinations can be used to specify the desired optional feature settings.
-However in my tests the first syntax didn't work, probably because Old Standard
-unlike most other Graphite fonts doesn't use numerical feature identifiers. So
-for example in order to get capitalized Greek text with accents above vowels one
-should write something like the following (note that settings passed to
-\texttt{RawFeature} are separated with a semicolon:
-
-\begin{verbatim}
-\fontspec[
-    Renderer=Graphite,
-    RawFeature={
-        Capitalized Greek=True;
-        Greek Accents=Above Capitals}
-    ]{Old Standard TT}
-\end{verbatim}
-
-Of course this code is quite easy to understand, but it is surely not optimal
-in terms of conciseness.
-
-The Graphite support in \XeTeX{} and \texttt{fontspec} is not very much tested,
-and so various undesired effects may still occur. Here's a few problems I have
-noticed with their solutions:
-
-\begin{itemize}
-
-\item \texttt{fontspec} sometimes would complain that the current roman font does not
-support a particular script (say, Cyrillic or Greek). This error is reported because
-\texttt{fontspec} expects to find the information about supported scripts in
-the font's tables responsible for its “smart” rendering. Well, this makes some sense
-for OpenType, but Graphite essentially has no “script” concept at all (it allows
-to define language-specific some behavior, but doesn't group languages by their
-script). So there is just no desired data in Graphite tables, and this leads
-to an error. Fortunately the workaround is simple: it is sufficient to explicitly
-tell \texttt{fontspec} to use the desired font for a particular script by defining
-the appropriate font family. For example:
-
-\begin{verbatim}
-\newfontfamily\greekfont[
-	Renderer=Graphite
-	]{Old Standard TT}
-\end{verbatim}
-
-\item under certain conditions \XeTeX{} correctly loads additional font family
-members (e.~g. bold or italic) but apparently doesn't recognize them as Graphite
-fonts. The workaround is to explicitly specify all the additional styles in
-\texttt{fontspec} options, e.~g.:
-
-\begin{verbatim}
-\fontspec[
-    Renderer=Graphite,
-    ItalicFont={OldStandardTT-Italic},
-    BoldFont={OldStandardTT-Bold}
-    ]{Old Standard TT}
-\end{verbatim}
-
-\end{itemize}
-
-}
-
-\chapter{GNU Free Documentation License}
-\label{FDL}
-
-\begin{center}
-
-Version 1.2, November 2002
-
-Copyright \copyright{} 2000,2001,2002  Free Software Foundation, Inc.
- 
-\bigskip
- 
-51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
-  
-\bigskip
- 
-Everyone is permitted to copy and distribute verbatim copies of this
-license document, but changing it is not allowed.
-
-\end{center}
-
-\subsection*{Preamble}
-
-The purpose of this License is to make a manual, textbook, or other
-functional and useful document “free” in the sense of freedom: to assure
-everyone the effective freedom to copy and redistribute it, with or without
-modifying it, either commercially or noncommercially.  Secondarily, this
-License preserves for the author and publisher a way to get credit for
-their work, while not being considered responsible for modifications made
-by others.
-
-This License is a kind of “copyleft”, which means that derivative works of
-the document must themselves be free in the same sense.  It complements the
-GNU General Public License, which is a copyleft license designed for free
-software.
-
-We have designed this License in order to use it for manuals for free
-software, because free software needs free documentation: a free program
-should come with manuals providing the same freedoms that the software
-does.  But this License is not limited to software manuals; it can be used
-for any textual work, regardless of subject matter or whether it is
-published as a printed book.  We recommend this License principally for
-works whose purpose is instruction or reference.
-
-\section{Applicability and Definitions}
-\label{FDL:sec1}
-
-This License applies to any manual or other work, in any medium, that
-contains a notice placed by the copyright holder saying it can be
-distributed under the terms of this License.  Such a notice grants a
-world-wide, royalty-free license, unlimited in duration, to use that work
-under the conditions stated herein.  The “\textbf{Document}”, below,
-refers to any such manual or work.  Any member of the public is a licensee,
-and is addressed as “\textbf{you}”.  You accept the license if you copy,
-modify or distribute the work in a way requiring permission under copyright
-law.
-
-A “\textbf{Modified Version}” of the Document means any work containing the
-Document or a portion of it, either copied verbatim, or with modifications
-and/or translated into another language.
-
-A “\textbf{Secondary Section}” is a named appendix or a front-matter
-section of the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document’s overall subject (or
-to related matters) and contains nothing that could fall directly within
-that overall subject.  (Thus, if the Document is in part a textbook of
-mathematics, a Secondary Section may not explain any mathematics.)  The
-relationship could be a matter of historical connection with the subject or
-with related matters, or of legal, commercial, philosophical, ethical or
-political position regarding them.
-
-The “\textbf{Invariant Sections}” are certain Secondary Sections whose
-titles are designated, as being those of Invariant Sections, in the notice
-that says that the Document is released under this License.  If a section
-does not fit the above definition of Secondary then it is not allowed to be
-designated as Invariant.  The Document may contain zero Invariant Sections.
-If the Document does not identify any Invariant Sections then there are
-none.
-
-The “\textbf{Cover Texts}” are certain short passages of text that are
-listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says
-that the Document is released under this License.  A Front-Cover Text may
-be at most 5 words, and a Back-Cover Text may be at most 25 words.
-
-A “\textbf{Transparent}” copy of the Document means a machine-readable
-copy, represented in a format whose specification is available to the
-general public, that is suitable for revising the document
-straightforwardly with generic text editors or (for images composed of
-pixels) generic paint programs or (for drawings) some widely available
-drawing editor, and that is suitable for input to text formatters or for
-automatic translation to a variety of formats suitable for input to text
-formatters.  A copy made in an otherwise Transparent file format whose
-markup, or absence of markup, has been arranged to thwart or discourage
-subsequent modification by readers is not Transparent. An image format is
-not Transparent if used for any substantial amount of text. A copy that is
-not “Transparent” is called “\textbf{Opaque}”.
-
-Examples of suitable formats for Transparent copies include plain ASCII
-without markup, Texinfo input format, LaTeX input format, SGML or XML using
-a publicly available DTD, and standard-conforming simple HTML, PostScript
-or PDF designed for human modification.  Examples of transparent image
-formats include PNG, XCF and JPG.  Opaque formats include proprietary
-formats that can be read and edited only by proprietary word processors,
-SGML or XML for which the DTD and/or processing tools are not generally
-available, and the machine-generated HTML, PostScript or PDF produced by
-some word processors for output purposes only.
-
-The “\textbf{Title Page}” means, for a printed book, the title page itself,
-plus such following pages as are needed to hold, legibly, the material this
-License requires to appear in the title page. For works in formats which
-do not have any title page as such, “Title Page” means the text near the
-most prominent appearance of the work’s title, preceding the beginning of
-the body of the text.
-
-A section “\textbf{Entitled XYZ}” means a named subunit of the Document
-whose title either is precisely XYZ or contains XYZ in parentheses
-following text that translates XYZ in another language.  (Here XYZ stands
-for a specific section name mentioned below, such as
-“\textbf{Acknowledgements}”, “\textbf{Dedications}”,
-“\textbf{Endorsements}”, or “\textbf{History}”.) To “\textbf{Preserve the
-Title}” of such a section when you modify the Document means that it
-remains a section “Entitled XYZ” according to this definition.
-
-The Document may include Warranty Disclaimers next to the notice which
-states that this License applies to the Document.  These Warranty
-Disclaimers are considered to be included by reference in this
-License, but only as regards disclaiming warranties: any other
-implication that these Warranty Disclaimers may have is void and has
-no effect on the meaning of this License.
-
-\section{Verbatim Copying}
-\label{FDL:sec2}
-
-You may copy and distribute the Document in any medium, either commercially
-or noncommercially, provided that this License, the copyright notices, and
-the license notice saying this License applies to the Document are
-reproduced in all copies, and that you add no other conditions whatsoever
-to those of this License.  You may not use technical measures to obstruct
-or control the reading or further copying of the copies you make or
-distribute.  However, you may accept compensation in exchange for copies.
-If you distribute a large enough number of copies you must also follow the
-conditions in \autoref{FDL:sec3}.
-
-You may also lend copies, under the same conditions stated above, and
-you may publicly display copies.
-
-\section{Copying in Quantity}
-\label{FDL:sec3}
-
-If you publish printed copies (or copies in media that commonly have
-printed covers) of the Document, numbering more than 100, and the
-Document’s license notice requires Cover Texts, you must enclose the
-copies in covers that carry, clearly and legibly, all these Cover
-Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
-the back cover.  Both covers must also clearly and legibly identify
-you as the publisher of these copies.  The front cover must present
-the full title with all words of the title equally prominent and
-visible.  You may add other material on the covers in addition.
-Copying with changes limited to the covers, as long as they preserve
-the title of the Document and satisfy these conditions, can be treated
-as verbatim copying in other respects.
-
-If the required texts for either cover are too voluminous to fit
-legibly, you should put the first ones listed (as many as fit
-reasonably) on the actual cover, and continue the rest onto adjacent
-pages.
-
-If you publish or distribute Opaque copies of the Document numbering
-more than 100, you must either include a machine-readable Transparent
-copy along with each Opaque copy, or state in or with each Opaque copy
-a computer-network location from which the general network-using
-public has access to download using public-standard network protocols
-a complete Transparent copy of the Document, free of added material.
-If you use the latter option, you must take reasonably prudent steps,
-when you begin distribution of Opaque copies in quantity, to ensure
-that this Transparent copy will remain thus accessible at the stated
-location until at least one year after the last time you distribute an
-Opaque copy (directly or through your agents or retailers) of that
-edition to the public.
-
-It is requested, but not required, that you contact the authors of the
-Document well before redistributing any large number of copies, to give
-them a chance to provide you with an updated version of the Document.
-
-\section{Modifications}
-\label{FDL:sec4}
-
-You may copy and distribute a Modified Version of the Document under
-the conditions of sections 2 and 3 above, provided that you release
-the Modified Version under precisely this License, with the Modified
-Version filling the role of the Document, thus licensing distribution
-and modification of the Modified Version to whoever possesses a copy
-of it.  In addition, you must do these things in the Modified Version:
-
-\begin{itemize}
-
-\item[A.] Use in the Title Page (and on the covers, if any) a title
-distinct from that of the Document, and from those of previous versions
-(which should, if there were any, be listed in the History section of the
-Document).  You may use the same title as a previous version if the
-original publisher of that version gives permission.
- 
-\item[B.] List on the Title Page, as authors, one or more persons or
-entities responsible for authorship of the modifications in the Modified
-Version, together with at least five of the principal authors of the
-Document (all of its principal authors, if it has fewer than five), unless
-they release you from this requirement.
-
-\item[C.] State on the Title page the name of the publisher of the Modified
-Version, as the publisher.
-
-\item[D.] Preserve all the copyright notices of the Document.
-
-\item[E.] Add an appropriate copyright notice for your modifications
-adjacent to the other copyright notices.
-
-\item[F.] Include, immediately after the copyright notices, a license
-notice giving the public permission to use the Modified Version under the
-terms of this License, in the form shown in the Addendum below.
-
-\item[G.] Preserve in that license notice the full lists of Invariant
-Sections and required Cover Texts given in the Document’s license notice.
- 
-\item[H.] Include an unaltered copy of this License.
-   
-\item[I.] Preserve the section Entitled “History”, Preserve its Title, and
-add to it an item stating at least the title, year, new authors, and
-publisher of the Modified Version as given on the Title Page.  If there is
-no section Entitled “History” in the Document, create one stating the
-title, year, authors, and publisher of the Document as given on its Title
-Page, then add an item describing the Modified Version as stated in the
-previous sentence.
- 
-\item[J.] Preserve the network location, if any, given in the Document for
-public access to a Transparent copy of the Document, and likewise the
-network locations given in the Document for previous versions it was based
-on.  These may be placed in the “History” section.  You may omit a network
-location for a work that was published at least four years before the
-Document itself, or if the original publisher of the version it refers to
-gives permission.
- 
-\item[K.] For any section Entitled “Acknowledgements” or “Dedications”,
-Preserve the Title of the section, and preserve in the section all the
-substance and tone of each of the contributor acknowledgements and/or
-dedications given therein.
- 
-\item[L.] Preserve all the Invariant Sections of the Document, unaltered in
-their text and in their titles. Section numbers or the equivalent are not
-considered part of the section titles.
- 
-\item[M.] Delete any section Entitled “Endorsements”.  Such a section may
-not be included in the Modified Version.
- 
-\item[N.] Do not retitle any existing section to be Entitled
-“Endorsements” or to conflict in title with any Invariant Section.
- 
-\item[O.] Preserve any Warranty Disclaimers.
-
-\end{itemize}
-
-If the Modified Version includes new front-matter sections or appendices
-that qualify as Secondary Sections and contain no material copied from the
-Document, you may at your option designate some or all of these sections as
-invariant.  To do this, add their titles to the list of Invariant Sections
-in the Modified Version’s license notice.  These titles must be distinct
-from any other section titles.
-
-You may add a section Entitled “Endorsements”, provided it contains
-nothing but endorsements of your Modified Version by various parties~— for
-example, statements of peer review or that the text has been approved by an
-organization as the authoritative definition of a standard.
-
-You may add a passage of up to five words as a Front-Cover Text, and a
-passage of up to 25 words as a Back-Cover Text, to the end of the list of
-Cover Texts in the Modified Version.  Only one passage of Front-Cover Text
-and one of Back-Cover Text may be added by (or through arrangements made
-by) any one entity.  If the Document already includes a cover text for the
-same cover, previously added by you or by arrangement made by the same
-entity you are acting on behalf of, you may not add another; but you may
-replace the old one, on explicit permission from the previous publisher
-that added the old one.
-
-The author(s) and publisher(s) of the Document do not by this License give
-permission to use their names for publicity for or to assert or imply
-endorsement of any Modified Version.
-
-\section{Combining Documents}
-\label{FDL:sec5}
-
-You may combine the Document with other documents released under this
-License, under the terms defined in \autoref{FDL:sec4} above for modified
-versions, provided that you include in the combination all of the Invariant
-Sections of all of the original documents, unmodified, and list them all as
-Invariant Sections of your combined work in its license notice, and that
-you preserve all their Warranty Disclaimers.
-
-The combined work need only contain one copy of this License, and multiple
-identical Invariant Sections may be replaced with a single copy.  If there
-are multiple Invariant Sections with the same name but different contents,
-make the title of each such section unique by adding at the end of it, in
-parentheses, the name of the original author or publisher of that section
-if known, or else a unique number.  Make the same adjustment to the section
-titles in the list of Invariant Sections in the license notice of the
-combined work.
-
-In the combination, you must combine any sections Entitled “History” in the
-various original documents, forming one section Entitled “History”;
-likewise combine any sections Entitled “Acknowledgements”, and any sections
-Entitled “Dedications”.  You must delete all sections Entitled
-“Endorsements”.
-
-\section{Collection of Documents}
-\label{FDL:sec6}
-
-You may make a collection consisting of the Document and other documents
-released under this License, and replace the individual copies of this
-License in the various documents with a single copy that is included in
-the collection, provided that you follow the rules of this License for
-verbatim copying of each of the documents in all other respects.
-
-You may extract a single document from such a collection, and distribute
-it individually under this License, provided you insert a copy of this
-License into the extracted document, and follow this License in all
-other respects regarding verbatim copying of that document.
-
-\section{Aggregation with Independent Works}
-\label{FDL:sec7}
-
-A compilation of the Document or its derivatives with other separate and
-independent documents or works, in or on a volume of a storage or
-distribution medium, is called an “aggregate” if the copyright resulting
-from the compilation is not used to limit the legal rights of the
-compilation’s users beyond what the individual works permit.  When the
-Document is included in an aggregate, this License does not apply to the
-other works in the aggregate which are not themselves derivative works of
-the Document.
-
-If the Cover Text requirement of \autoref{FDL:sec3} is applicable to these
-copies of the Document, then if the Document is less than one half of the
-entire aggregate, the Document’s Cover Texts may be placed on covers that
-bracket the Document within the aggregate, or the electronic equivalent of
-covers if the Document is in electronic form.  Otherwise they must appear
-on printed covers that bracket the whole aggregate.
-
-\section{Translation}
-\label{FDL:sec8}
-
-Translation is considered a kind of modification, so you may distribute
-translations of the Document under the terms of \autoref{FDL:sec4}.
-Replacing Invariant Sections with translations requires special permission
-from their copyright holders, but you may include translations of some or
-all Invariant Sections in addition to the original versions of these
-Invariant Sections.  You may include a translation of this License, and all
-the license notices in the Document, and any Warranty Disclaimers,
-provided that you also include the original English version of this License
-and the original versions of those notices and disclaimers.  In case of a
-disagreement between the translation and the original version of this
-License or a notice or disclaimer, the original version will prevail.
-
-If a section in the Document is Entitled “Acknowledgements”, “Dedications”,
-or “History”, the requirement (\autoref{FDL:sec4}) to Preserve its Title
-(section~1) will typically require changing the actual title.
-
-\section{Termination}
-\label{FDL:sec9}
-
-You may not copy, modify, sublicense, or distribute the Document except
-as expressly provided for under this License.  Any other attempt to
-copy, modify, sublicense or distribute the Document is void, and will
-automatically terminate your rights under this License.  However,
-parties who have received copies, or rights, from you under this
-License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
-\section{Future Revisions of this License}
-\label{FDL:sec10}
-
-The Free Software Foundation may publish new, revised versions
-of the GNU Free Documentation License from time to time.  Such new
-versions will be similar in spirit to the present version, but may
-differ in detail to address new problems or concerns. See
-\href{http://www.gnu.org/copyleft/}{http://www.gnu.org/copyleft/}.
-
-Each version of the License is given a distinguishing version number.
-If the Document specifies that a particular numbered version of this
-License “or any later version” applies to it, you have the option of
-following the terms and conditions either of that specified version or
-of any later version that has been published (not as a draft) by the
-Free Software Foundation.  If the Document does not specify a version
-number of this License, you may choose any version ever published (not
-as a draft) by the Free Software Foundation.
-
-\section*{ADDENDUM: How to use this License for your documents}
-\phantomsection
-\addcontentsline{toc}{section}{ADDENDUM: How to use this License for 
-your documents}
-
-To use this License in a document you have written, include a copy of
-the License in the document and put the following copyright and
-license notices just after the title page:
-
-\bigskip
-
-\begin{quote}
-Copyright © YEAR YOUR NAME.
-Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2
-or any later version published by the Free Software Foundation;
-with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
-A copy of the license is included in the section entitled “GNU
-Free Documentation License”.
-\end{quote}
-
-\bigskip
-
-If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
-replace the “with \dots\ Texts.” line with this:
-
-\bigskip
-
-\begin{quote}
-with the Invariant Sections being LIST THEIR TITLES, with the
-Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
-\end{quote}
-
-\bigskip
-    
-If you have Invariant Sections without Cover Texts, or some other
-combination of the three, merge those two alternatives to suit the
-situation.
-
-If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of
-free software license, such as the GNU General Public License,
-to permit their use in free software.
-
-\end{document}
-
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/oldstandard-samples.pdf b/Master/texmf-dist/doc/fonts/oldstandard/oldstandard-samples.pdf
index fa49e7a5256..918196ba17d 100644
--- a/Master/texmf-dist/doc/fonts/oldstandard/oldstandard-samples.pdf
+++ b/Master/texmf-dist/doc/fonts/oldstandard/oldstandard-samples.pdf
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/oldstandard-samples.tex b/Master/texmf-dist/doc/fonts/oldstandard/oldstandard-samples.tex
index 86716f8b600..73caac482a1 100644
--- a/Master/texmf-dist/doc/fonts/oldstandard/oldstandard-samples.tex
+++ b/Master/texmf-dist/doc/fonts/oldstandard/oldstandard-samples.tex
@@ -45,6 +45,7 @@ X\textsu{0123456789}
 \section*{Cyrillic}
 
 {\ifxetex\else\ifluatex\else\fontencoding{T2A}\selectfont\fi\fi
+
 Съешь ещё этих мягких французских булок да
 выпей чаю!}
 
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/oldstandard.pdf b/Master/texmf-dist/doc/fonts/oldstandard/oldstandard.pdf
index a46d503d8f0..c2d3a3accc3 100644
--- a/Master/texmf-dist/doc/fonts/oldstandard/oldstandard.pdf
+++ b/Master/texmf-dist/doc/fonts/oldstandard/oldstandard.pdf
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/oldstandard.tex b/Master/texmf-dist/doc/fonts/oldstandard/oldstandard.tex
index c6b60267cef..6334d20861b 100644
--- a/Master/texmf-dist/doc/fonts/oldstandard/oldstandard.tex
+++ b/Master/texmf-dist/doc/fonts/oldstandard/oldstandard.tex
@@ -1,3 +1,7 @@
+% arara: lualatex: { shell: yes }
+% arara: biber
+% arara: lualatex: { shell: yes }
+% arara: lualatex: { shell: yes }
 \RequirePackage{filecontents}
 \begin{filecontents*}{\jobname.bib}
 @software{arabluatex,
@@ -27,27 +31,11 @@
 \end{filecontents*}
 \documentclass[letterpaper]{article}
 \usepackage{fontspec}
-\usepackage[english]{babel}
+\usepackage[greek.ancient,english]{babel}
 \babeltags{grc = greek}
 
 \babelfont{rm}{Old Standard}
 \babelfont[greek]{rm}[RawFeature={+ss05;+ss06}]{Old Standard}
-\defaultfontfeatures[NewComputerModern Mono]
-	{
-		Extension      = .otf ,
-		UprightFont    = NewCMMono10-Regular,
-		BoldFont       = NewCMMono10-Bold,
-		ItalicFont     = NewCMMono10-Italic,
-		BoldItalicFont = NewCMMono10-BoldOblique,
-	}
-\defaultfontfeatures[NewComputerModern Sans]
-	{
-		Extension      = .otf ,
-		UprightFont    = NewCMSans10-Regular,
-		BoldFont       = NewCMSans10-Bold,
-		ItalicFont     = NewCMSans10-Oblique,
-		BoldItalicFont = NewCMSans10-BoldOblique,
-	}
 \babelfont{sf}{NewComputerModern Sans}
 \babelfont{tt}{NewComputerModern Mono}
 
@@ -98,8 +86,8 @@
 
 \usepackage[toc]{multitoc}
 
-\edef\pkgver{2.5}
-\edef\pkgdate{2020/02/24}
+\edef\pkgver{2.6}
+\edef\pkgdate{2020/12/18}
 \title{\mdseries\tcbox[colframe=black, enhanced, tikznode, drop
   lifted shadow, colback=white, boxrule=.25mm]%
   {\textsc{Old Standard}\\
@@ -109,7 +97,7 @@
     \large v\pkgver -- \pkgdate}}
 
 \author{Robert Alessi \\
-\href{mailto:alessi@robertalessi.net?Subject=arabluatex package}%
+\href{mailto:alessi@robertalessi.net?Subject=OldStandard package}%
 {\texttt{alessi@robertalessi.net}}}
 \date{}
 
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/opentype.png b/Master/texmf-dist/doc/fonts/oldstandard/opentype.png
deleted file mode 100644
index ea138301406..00000000000
--- a/Master/texmf-dist/doc/fonts/oldstandard/opentype.png
+++ /dev/null
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/serbian.png b/Master/texmf-dist/doc/fonts/oldstandard/serbian.png
deleted file mode 100644
index 72c42a8d52f..00000000000
--- a/Master/texmf-dist/doc/fonts/oldstandard/serbian.png
+++ /dev/null
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/spadmin-add.png b/Master/texmf-dist/doc/fonts/oldstandard/spadmin-add.png
deleted file mode 100644
index f56d9b4d71b..00000000000
--- a/Master/texmf-dist/doc/fonts/oldstandard/spadmin-add.png
+++ /dev/null
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/spadmin.png b/Master/texmf-dist/doc/fonts/oldstandard/spadmin.png
deleted file mode 100644
index 04108eb6658..00000000000
--- a/Master/texmf-dist/doc/fonts/oldstandard/spadmin.png
+++ /dev/null
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/stand-su.png b/Master/texmf-dist/doc/fonts/oldstandard/stand-su.png
deleted file mode 100644
index de323919aa9..00000000000
--- a/Master/texmf-dist/doc/fonts/oldstandard/stand-su.png
+++ /dev/null
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/teubner.png b/Master/texmf-dist/doc/fonts/oldstandard/teubner.png
deleted file mode 100644
index ca0b86c481c..00000000000
--- a/Master/texmf-dist/doc/fonts/oldstandard/teubner.png
+++ /dev/null
diff --git a/Master/texmf-dist/doc/fonts/oldstandard/truetype.png b/Master/texmf-dist/doc/fonts/oldstandard/truetype.png
deleted file mode 100644
index e2540aeb1a3..00000000000
--- a/Master/texmf-dist/doc/fonts/oldstandard/truetype.png
+++ /dev/null