summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/fonts/gentium-tug
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2013-07-05 19:18:18 +0000
committerKarl Berry <karl@freefriends.org>2013-07-05 19:18:18 +0000
commit56baa364aad0fa137689eba03eb3eaaacfe1673e (patch)
tree65610537cea5b7d4007ec1663ca5bab9a433c15c /Master/texmf-dist/doc/fonts/gentium-tug
parentd8a89cd2da7cf3b8bb2925b7bef0ea98443cdda5 (diff)
gentium-tug (4jul13)
git-svn-id: svn://tug.org/texlive/trunk@31103 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/fonts/gentium-tug')
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/ChangeLog184
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/FONTLOG.txt84
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/Gentium/FONTLOG.txt180
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/Gentium/GENTIUM-FAQ.txt205
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/Gentium/OFL-FAQ.txt369
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/Gentium/OFL.txt94
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/Gentium/QUOTES.txt73
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/Gentium/README.txt118
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/FONTLOG.txt153
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/GENTIUM-FAQ.txt249
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/OFL-FAQ.txt216
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/OFL.txt94
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/FONTLOG.txt205
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/GENTIUM-FAQ.txt205
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/OFL-FAQ.txt369
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/OFL.txt94
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/README.txt88
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/documentation/DOCUMENTATION.txt11
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/documentation/GentiumPlus-features.odtbin0 -> 46533 bytes
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/documentation/GentiumPlus-features.pdfbin0 -> 743398 bytes
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlusCompact/FONTLOG.txt206
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlusCompact/README.txt99
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlusCompact/feat_set_tuned.xml5
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/Makefile14
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/OFL-FAQ.txt369
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/OFL.txt95
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/README183
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/gentium.pdfbin0 -> 571845 bytes
-rw-r--r--Master/texmf-dist/doc/fonts/gentium-tug/gentium.tex540
29 files changed, 4502 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/ChangeLog b/Master/texmf-dist/doc/fonts/gentium-tug/ChangeLog
new file mode 100644
index 00000000000..21bbe9d2673
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/ChangeLog
@@ -0,0 +1,184 @@
+This file is part of the Gentium package for TeX.
+It is licensed under the Expat License, see doc//README for details.
+
+This file lists internal changes to the development. For the changes
+to the actual Gentium Plus PS fonts by release, see FONTLOG.txt.
+
+Each of the SIL fonts also has its own FONTLOG.txt. Please consult
+these FONTLOGs in their separate font project doc folders for a full
+record of changes, and for more information on the individual font
+projects.
+
+2013-05-17
+- Some changes in the test files. (Pavel)
+
+2013-04-30
+- More doc and distribution tweaks, resent to Victor. (Karl)
+
+2013-04-27
+- At the request of Victor Gaultney, changed the advance width of
+ the letters dcaron and lcaron back to the original value. Replaced
+ with some extra kerning pairs for the more common combinations. (Pavel)
+
+2013-03-20
+- Added license statement to more files, tweak docs. (Karl)
+
+2013-03-14
+- Updated Gentium Plus fonts. (Pavel)
+
+2013-03-10
+- Changed 'gentium' into 'gentium-tug' by request of SIL. (Mojca)
+
+2013-02-27
+- Added a script to create CTAN-friendly directory structure. (Mojca)
+
+2012-04-11
+- Added test files and samples for the differences between the
+ original TrueType and converted Type 1 fonts. (Pavel)
+
+2012-04-07
+- Corrected letters Tcedilla and Tcommaaccent in the extra kerning
+ pairs added to the Type 1 fonts. (Pavel)
+- Test file for LGR shows also the italic style. (Pavel)
+
+2012-03-30
+- Added more kerning pairs for accented letters to the Type 1
+ fonts. (Pavel)
+- Corrected the kern value for DV in GentiumPlus Regular in the
+ Type 1 fonts. The value was positive. (Pavel)
+
+2012-03-22
+- Added more kerning pairs for accented letters to the Type 1
+ fonts. (Pavel)
+
+2012-03-20
+- The scripts for the conversion of the fonts to Type1 can add
+ kerning pairs for accented Latin letters now. The original TTF
+ fonts have no such kerning pairs. More such kerning pairs should
+ be added. (Pavel)
+
+2012-03-14
+- Added several kerning pairs for small caps in the Type 1 version of
+ GentiumPlus (original TTFs have no kerning pairs for small caps).
+ They were added for these combinations: small cap + small cap
+ (currently without accents), capital letter + small cap and some
+ punctuation symbols preceeded or followed by small cap letter.
+ All these kerning pairs are created automatically and they are derived
+ from the respective kerning pairs for capital letters. (Pavel)
+
+2012-03-07
+- The Type 1 fonts have "TeX Users Group" as creator now. (Pavel)
+- Added license header to some files. (Pavel)
+
+2012-02-27
+- Added FamilyBlues and FamilyOtherBlues to Type 1 fonts. The fonts
+ can not be one family (t1lint complained), therefore two fonts
+ from GentiumPlus are one family and two fonts from GentiumBasic
+ are other family. (Pavel)
+- ForceBold set explicitly (true or false) for Type 1 fonts. (Pavel)
+- Added new targets "test" and "kerns" for the makefile building
+ Type 1 fonts. (Pavel)
+- Small clean-up of the Type 1 build scripts. (Pavel)
+
+2012-02-14
+- Update of the PDF/LaTeX documentation. (Pavel)
+
+2012-02-10
+- Added build scripts for Type 1 fonts to the subdirectory "type1" in
+ "source". The fonts are not reencoded to Adobe Standard Encoding (which
+ created many slots containing ".notdef"). (Pavel)
+
+2012-02-07
+- Update of the PDF/LaTeX documentation. (Pavel)
+
+2012-02-06
+- The build scripts for the conversion of the fonts to Type 1 remove
+ the lookups "mark" and "mkmk" after opening the TrueType font. This
+ eliminates really huge amount of error messages for GentiumPlus.
+ The scripts print messages about the current operation now. (Pavel)
+
+2012-02-05
+- Remove old scripts and refactor ruby sources. (Mojca)
+- Different formatting in map files, no functional changes; map files
+ for ot1, ts1, lgr, t2b, t2c, x2 may be removed in future (Mojca)
+- Fix dotlessj (uni0237) in some encodings;
+ fix scommaaccent & some greek letters in qx encoding. (Mojca)
+- Change L7X -> L7x in fd files. (Mojca)
+- Fix some typos in licenses, update README.
+
+2012-02-04
+- Improved the PDF/LaTeX documentation. (Pavel)
+- Some clean-up of Cyrillic encodings. (Pavel)
+- It's possible to set copyright text in the generated Type 1
+ fonts. (Pavel)
+
+2012-02-03
+- Added documentation in PDF with LaTeX source. Heavily based on the work
+ by Clea F. Rees. (Pavel)
+
+2012-01-31
+- Added TS1 encoding. (Pavel)
+- Improved test files for LGR Greek and Cyrillics. (Pavel)
+
+2012-01-30
+- Added the Expat license.
+
+2012-01-28
+- Added OT1 encoding. (Pavel)
+
+2012-01-24
+- Removed LIGKERN commands (and similar stuff) from the encoding
+ files for T2A, T2B, T2C, X2 and LGR (lig files are used instead).
+ (Pavel)
+- Add support for SmallCaps. (Mojca)
+
+2012-01-20
+- Simplified the file gentium.sty quite a lot, uses xkeyval now.
+
+2012-01-19
+- Added the possibility for afm2pl to use a lig file if present. (Pavel)
+- Added lig files for AGR, LGR, T2A, T2B, T2C and X2. (Pavel)
+- The fonts from the previous update copied to the main package. (Pavel)
+- Generated support for LGR. (Pavel)
+- Added simple test files for LGR and Czech. (Pavel)
+- Workaround for 'dcroat' and 'Idotaccent' for EC and T5 encodings. (Mojca)
+
+2012-01-16
+- Created first serious version of Type 1 fonts based on the script
+ by Clea F. Rees. Added kerning pairs for the combinations
+ accent + capital Greek letter. The letters dcaron and lcaron made
+ narrower than it the original fonts (for better results in Czech
+ and Slovak). The package still uses the old version of the
+ fonts. (Pavel)
+- Added LGR encoding (no support files generated). (Pavel)
+
+2012-01-13
+- Add gentium.sty for LaTeX and sample *.fd files (Pavel)
+- Write a script to generate ${enc}gentium.fd (Mojca)
+- Update ConTeXt support files to new names. (Mojca)
+- Add some test files. (Mojca & Pavel)
+
+2012-01-12
+- Try to create Type1 fonts with ttf2pt1 (just a temporary solution).
+ Observation: AFM font metrics are not compatible (often 1 point difference).
+- Generate tfm files from new ttf fonts. (Mojca)
+- Update map files with new names and split gentium.map into
+ gentium-truetype.map & gentium-type1.map. (Mojca)
+
+2011-10-17
+- Add t2a, t2b, t2c and x2 encoding files. (Pavel)
+
+2011-10-06
+- Replace Gen{R,I}102.ttf with Gentium-{R,I}.ttf (version 1.103)
+ GenA{R,I}102.ttf with GentiumAlt-{R,I}.ttf
+- Add GentiumPlus and GentiumPlusCompact (version 1.508)
+- TeX support files have not been updated yet.
+
+2010-10-09
+- Add GenAR102.ttf and GenAI102.ttf (requested by users)
+
+2010-07-07
+- Fix broken font files and some other typos in ConTeXt typescripts
+
+2008-11-13
+- First release of ConTeXt support files.
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/FONTLOG.txt b/Master/texmf-dist/doc/fonts/gentium-tug/FONTLOG.txt
new file mode 100644
index 00000000000..2f69b02c154
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/FONTLOG.txt
@@ -0,0 +1,84 @@
+The Gentium Plus PS fonts are Type 1 versions of the TrueType Gentium
+fonts released by SIL International. The conversion to Type 1
+necessarily introduces changes in the implementation of the shapes and
+the metrics. No changes to the shapes or advance widths have been made
+by humans, but a few human-made changes are in the kerning tables for
+the regular and italic; see below.
+
+The Gentium Plus PS fonts incorporate the name "Gentium" by permission
+of SIL given to the TeX Users Group (TUG). These fonts are
+semi-officially released and maintained under the auspices of TUG. For
+internal development changes, see the file ChangeLog.
+
+Each of the SIL fonts also has its own FONTLOG.txt. Please consult
+these FONTLOGs in their separate font project (Gentium*) subfolders here
+for a full record of changes, and for more information on the individual
+font projects.
+
+The home page for the Gentium Plus PS fonts and TeX support package:
+http://tug.org/gentium
+
+
+2 July 2013 (TeX development team, see below) Gentium Plus PS version 1.0
+- First public release.
+
+
+Basic information
+----------------
+The Type 1 regular and italic are derived from Gentium Plus,
+while the Type 1 bold and bold italic are derived from Gentium Basic.
+
+There are no intentional changes in the bold and bold italic beyond
+those made by the automatic conversion to Type 1.
+
+These are the changes in the regular and italic; we hope they will be
+incorporated in the original fonts in due time.
+
+- Some extra kerning pairs were added between accents and capital
+ Greek letters.
+
+- The advance width of dcaron and lcaron is much smaller than in the
+ original fonts. This improves the typesetting of Czech and Slovak.
+
+- There are additional kerning pairs for accented Latin letters, the
+ Czech/Slovak letters dcaron and lcaron, and for small caps. The
+ original fonts have no such kerning pairs. Manual corrections are
+ still needed in some cases, e.g., initial cap followed by small cap.
+
+- There was a positive kern between the letters D and V in the regular
+ style of Gentium Plus. The derived font has a negative kern.
+
+The conversion process, including these changes, is implemented in the
+Python and FontForge scripts included in the packages, e.g., ff-gentium.pe.
+
+
+Acknowledgements
+----------------
+(Here is where contributors can be acknowledged. If you make modifications be
+sure to add your name (N), email (E), web-address (W) and description (D).
+This list is sorted by last name in alphabetical order.)
+
+The full acknowledgements for the individual fonts can be found in the
+FONTLOGs for each separate font project.
+
+N: Karl Berry
+E: karl@freefriends.org
+W: http://freefriends.org/~karl
+D: Documentation, licensing, distribution, SIL <-> TUG contact, etc.
+
+N: Pavel Farar
+E: pavel.farar@centrum.cz
+D: Cyrillic support, conversion and generation scripts, etc.
+
+N: Mojca Miklavec
+E: mojca.miklavec.lists@gmail.com
+D: ConTeXt support, conversion and generation scripts, etc.
+
+N: Clea F. Rees
+W: http://cardiff.ac.uk/encap/contactsandpeople/profiles/rees-clea.html
+D: Original LaTeX support, documentation, conversion.
+
+N: Thomas A. Schmitz
+E: thomas.schmitz@uni-bonn.de
+W: http://www.philologie.uni-bonn.de/personal/schmitz
+D: Initial version of TeX support files, AGR encoding, ConTeXt support
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/FONTLOG.txt b/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/FONTLOG.txt
new file mode 100644
index 00000000000..fb5c617431d
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/FONTLOG.txt
@@ -0,0 +1,180 @@
+FONTLOG
+Gentium font family
+========================
+
+
+This file provides detailed information on the Gentium family of fonts. This
+information should be distributed along with the Gentium fonts and any
+derivative works.
+
+
+Basic Font Information
+----------------------
+
+Gentium ("belonging to the nations" in Latin) is a Unicode typeface family
+designed to enable the many diverse ethnic groups around the world who use
+the Latin script to produce readable, high-quality publications. The design
+is intended to be highly readable, reasonably compact, and visually
+attractive. Gentium has won a "Certificate of Excellence in Typeface Design"
+in two major international typeface design competitions: bukva:raz! (2001),
+TDC2003 (2003).
+
+Gentium provides glyphs for a wide range of Latin and Greek characters. The
+additional 'extended' Latin letters are designed to naturally harmonize with
+the traditional 26 ones. Diacritics are treated with careful thought and
+attention to their use. Gentium also supports both ancient and modern Greek,
+including a number of alternate forms. It currently supports the following
+ranges of Unicode 3.0 (completely unless noted):
+
+Range Description
+U+0020-U+007F Basic Latin
+U+00A0-U+00FF Latin-1 Supplement
+U+0100-U+017F Latin Extended-A
+U+0180-U+021F Latin Extended-B
+U+0222-U+0233 Latin Extended-B (continued)
+U+0250-U+02AD IPA Extensions
+U+02B0-U+02FF Spacing Modifier Letters
+U+0300-U+036F Combining Diacritical Marks
+U+0370-U+03D5 Greek (not including archaic or Coptic)
+U+1E00-U+1EFF Latin Extended Additional
+U+1F00-U+1FFF Greek Extended
+U+2000-U+203A General Punctuation (partial)
+U+2070-U+209F Superscripts and Subscripts
+U+20A0-U+20CF Currency Symbols (partial)
+U+2100-U+214F Letterlike Symbols (only a couple)
+
+Gentium Regular also includes some Cyrillic glyphs, but they are only early
+drafts. A future version will include a completely revised set, including
+italic, and will expand the support for Latin, Greek and Cyrillic to Unicode
+4.1.
+
+
+ChangeLog
+---------
+(This should list both major and minor changes, most recent first.)
+
+24th June 2011 (David Raymond) Gentium version 1.03
+- Changed licensing to the SIL Open Font License version 1.1
+
+28 Nov 2005 (Victor Gaultney) Gentium version 1.02
+- Changed licensing to the SIL Open Font License
+- Included FontLab source files
+- Fixed some duplicate PostScript glyphs names
+- Fixed italic angle
+
+19 Sep 2003 (Victor Gaultney) Gentium version 1.01
+- Maintenance release focused on changing internal font
+- Information to reflect the changeover to an SIL project
+- There is only one bug fix - the Greek mu PS name was changed to try and fix
+a display/printing problem. There is still no manual hinting
+
+16 Sep 2002 (Victor Gaultney) Gentium version 1.00
+- First public release
+- No manual hinting is included in this version. Some has been done - with
+good results - but is not yet complete enough.
+
+
+Information for Contributors
+----------------------------
+
+The main point of version 1.03 is to enable modification via the OFL 1.1 and to
+establish a means for people to contribute to the project. For information
+on what you're allowed to change or modify, consult the OFL and OFL-FAQ. The
+OFL-FAQ also gives a very general rationale regarding why you would want to
+contribute to the project.
+
+Anyone can make their own modified version of Gentium (using a different
+name), but SIL International will continue to maintain and develop the
+canonical version of the Gentium fonts. As the package maintainer, we warmly
+welcome contributions. Here are some things to keep in mind:
+
+Format: We are open to contributions in various formats, but if you want to
+maximise the chances of us including your work, please make it available to
+us (via email or a URL) as either a FontLab database (preferred) or a
+PostScript Type 1 (or OT-CFF) font.
+
+Source files: We're including FontLab databases used in developing
+the fonts. The current fonts, however, were not solely built from
+this FontLab database, so a simple "Generate Font" will not give you an
+identical result. These databases are provided not as canonical source but
+as an aid to anyone who might find it useful to have access to the
+PostScript-style curves before they were turned into TrueType ones. BTW -
+although only two databases are provided, they contain all the Alt glyphs.
+In the future we may be making our 'source' available in three formats:
+OpenType (TrueType), OT-CFF, and FontLab.
+
+Copyright attribution: If you submit something for inclusion in the main
+Gentium fonts, we will ask you to affirm that it is your original work, and
+ask you to assign the copyright of your work to SIL International. This is
+to ensure that future releases can be made under improved versions of the
+OFL without needing to track you down for further permission. This follows
+the same principle used by the FSF. Keep in mind that we are a
+not-for-profit organization committed to free/libre and open source
+software, and that any contributions incorporated in the fonts will always
+be available under the OFL or a similar license.
+
+Quality: Because we want to be able to guarantee a high level of quality for
+the primary Gentium fonts, we will review submissions carefully. Please
+don't be discouraged if we do not include a submission for this reason, or
+ask you to make specific revisions.
+
+What types of contributions are welcomed now (some more than others):
+- Old style figures
+- Small caps (although we would want such done for *all* caps, not just A-Z)
+- Specifications for smart Greek code (write us about this)
+- Coptic
+- Historic/Archaic Cyrillic
+- Glyphs used for ancient Greek text study (but not alphabetic ones, like
+the digamma)
+- Mathematical glyphs
+- OpenType code and glyphs for on-the-fly fraction creation
+- Additional scripts (Armenian, etc.?), and any needed OT/Graphite/AAT code
+- Other things that we may have once told you we didn't have time to do :-)
+
+What is not needed at this point:
+- Revisions to the basic letters or their spacing
+- Cyrillic revisions or additions. These are already in process
+- Other weights (Bold, Bold italic). We already have some work done on this
+- Alphabetic Ancient Greek glyphs (digamma, etc.). These are done and are
+waiting for the next release
+- Unicode 4.1 additions for Latin. We have these already in the pipeline
+- General Latin/Cyrillic OpenType/Graphite/AAT code - we already have this
+(see our Doulos SIL project)
+- Kerning - there is some in place
+- Hinting - although if you could offer to do some hinting, let us know :-)
+
+So why didn't we include some of this in this release? The only change for
+1.02 is the new licensing model. We thought that it was important to get a
+revised font out before we had completed the next big revision. We also
+didn't want to hold up release until we had everything neat and tidy :-)
+
+When submissions will be included: We hope to have a revised version of the
+Regular and Italic fonts (including full Cyrillic) completed by mid-2006. To
+do this we will need submissions early in the year. Other weights will
+follow after that.
+
+WARNINGS: The details of the source files and build procedures will be
+changing radically before the next release, so do not spend too much time
+working on systems that depend on the current FontLab database information.
+Also - the Cyrillic glyphs in the regular font are very early prototypes and
+will be changing completely. So don't bother to modify them!
+
+
+Acknowledgements
+----------------
+(Here is where contributors can be acknowledged. If you make modifications
+be sure to add your name (N), email (E), web-address (W) and description
+(D). This list is sorted by last name in alphabetical order.)
+
+N: Victor Gaultney
+E: victor_gaultney@sil.org
+W: http://www.sil.org/~gaultney/
+D: Original Designer of Latin, Greek and Cyrillic glyphs
+
+The Gentium project is maintained by SIL International.
+
+For more information please visit the Gentium page on SIL International's
+Computers and Writing systems website:
+http://scripts.sil.org/gentium
+
+Or send an email to <gentium AT sil DOT org>
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/GENTIUM-FAQ.txt b/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/GENTIUM-FAQ.txt
new file mode 100644
index 00000000000..7d93f53fb19
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/GENTIUM-FAQ.txt
@@ -0,0 +1,205 @@
+GENTIUM-FAQ
+Gentium Release 1.03
+========================
+
+Here are some answers to frequently asked questions about the Gentium fonts:
+
+
+General
+========
+
+How do you pronounce Gentium?
+
+ The preferred pronunciation is with a soft G as in 'general', not a
+ hard one as in 'gold': JEN-tee-oom.
+
+What is GentiumAlt?
+
+ It is a version of the font with redesigned diacritics (flatter
+ ones) to make it more suitable for use with stacking diacritics, and
+ for languages such as Vietnamese. The Greek glyphs also use the
+ Porsonic (single-curve) design for the circumflex. Since Gentium
+ does not currently include any 'smart' rendering routines, there is
+ no easy way to access these alternate diacritic shapes from within
+ the regular Gentium font. The encoding of the fonts are the same, so
+ the same text can be viewed with either one. There is also no
+ problem with having both font families installed at the same time.
+
+
+Licensing
+=========
+
+How is this version of Gentium different from version 1.02?
+
+ The only difference between version 1.02 and 1.03 is that Gentium is
+ now released under the SIL Open Font License 1.1. There has been no
+ change to metrics, glyphs or behavior.
+
+I want to use Gentium in my publication - can I?
+
+ Gentium is released under the SIL Open Font License, which permits use
+ for any publication, whether electronic or printed. For more answers
+ to use questions see the OFL-FAQ. The license, alongside information
+ specific to Gentium, is in the release package.
+
+I would like to bundle Gentium with my application - can I?
+
+ This is our most common question. The SIL Open Font License allows
+ bundling with applications, even commercial ones, with some restrictions.
+ See the OFL file.
+
+Can I use the font on my web site?
+
+ You can certainly create web pages that request that Gentium be used to
+ display them (if that font is available on the user's system). According
+ to the license, you are even allowed to place the font on your site for
+ people to download it. We would strongly recommend, however, that you
+ direct users to our site to download the font. This ensures that they
+ are always using the most recent version with bug fixes, etc. To make
+ this easier, we've simplified the URL for Gentium:
+ http://scripts.sil.org/gentium
+
+Is Gentium going to stay free?
+
+ There is no intention to ever charge users for using Gentium. The
+ current version is licensed under a free/open license and future
+ versions will be similar.
+
+
+Modification
+============
+
+I would like to modify Gentium to add a couple of characters I need. Can I?
+
+ Yes - that is allowed as long as you abide by the conditions of the
+ SIL Open Font License.
+
+So will you add glyphs upon request?
+
+ Gentium is no longer being updated. Gentium Plus has been significantly
+ updated and if further glyphs are requested, they could be added to
+ Gentium Plus.
+
+Can I send you work I've done to be incorporated into Gentium?
+
+ We are willing to incorporate your work into Gentium Plus. See the
+ Gentium Plus FONTLOG for information on becoming a contributor.
+
+
+Technical
+=========
+
+Can you help me get Gentium working on my system?
+
+ We cannot afford to offer individual technical support. The best
+ resource is this website, where we hope to offer some limited help.
+ However, we do want to hear of any problems you encounter, so that
+ we can add them to the list of bugs to fix in later releases.
+
+ Our contact address is <gentium AT sil DOT org>. Please understand
+ that we cannot guarantee a personal response.
+
+I can't find all the extended Latin letters in the font. How do I type them?
+
+ Gentium is Unicode-encoded, which means that the computer stores a
+ special, unique code for each letter in your document. Since most
+ keyboards do not have hundreds of keys, special software is needed
+ in order to type the hundreds of special characters supported by the
+ font.
+
+I can't find the 'o with right hook' in the font. Where is it?
+
+ Combinations of base letters with diacritics are often called
+ composite, or pre-composed glyphs. Gentium has hundreds of these
+ (the ones that are included in Unicode). There are, however, many
+ common combinations that are not represented by a single composite.
+ It is possible to enter these into a document, but only as
+ individual components. So 'o with right hook' would be entered as
+ 'o', then 'right hook'. Although this may not look very good in some
+ cases, we're not able to anticipate every possible combination.
+ Gentium Plus includes 'smart font' support for technologies such as
+ OpenType and SIL's Graphite. This improves diacritic positioning.
+
+Some diacritics are not aligning well with base glyphs, and if I type more
+than one diacritic, they run into each other. Why is that?
+
+ Gentium currently has no 'smart font' code for automatic diacritic
+ positioning. You may wish to use Gentium Plus which does include
+ 'smart font' support.
+
+How do I type the Greek letters?
+
+ You need a Unicode-compatible keyboarding system, which is not
+ included in the distribution package.
+
+I'm having problems making PDFs -- why won't my document distill?
+
+ Gentium is a large font, with lots of glyphs. As a result, some
+ printers can balk at PDFs that have the complete font embedded. The
+ easiest way to avoid this is to have Acrobat/Distiller subset the
+ font. This is generally a good idea anyway (with any font) and can
+ reduce the size of your files.
+
+
+Future
+======
+
+Now that SIL International has taken over Gentium, who will be the next
+designer?
+
+ Victor Gaultney will remain as primary designer, but other designers
+ from the SIL Non-Roman Script Initiative have joined the project team,
+ including Annie Olsen and Iska Routamaa. Other members of the NRSI team
+ will also add their expertise in technical matters.
+
+Do you plan to include other typographic enhancements (small caps, old style
+figures, etc.)?
+
+ Gentium Plus now has support for small caps. From a design point of view,
+ it would be great to have other enhancements, and we haven't ruled them
+ out. But there are other needs of much higher priority (such as Bold).
+ If you think you could contribute some of your time and effort to these
+ enhancements, see the Gentium Plus FONTLOG file for information on
+ becoming a contributor.
+
+What about bold?
+
+ Gentium Basic and Gentium Book Basic are now available in all four weights
+ (Regular, Italic, Bold and Bold-Italic). The 'Basic' fonts only cover
+ basic Latin glyphs. We are now working on completing these weights for
+ Gentium Plus. Be patient, though, as Gentium has lots of glyphs!
+
+Sans-serif?
+
+ There is a definite need for a sans-serif font that shares some of
+ Gentium's strengths -- high readability, economy of space, etc. It
+ would also be great if that font also harmonized well with Gentium.
+ We don't currently have any plans for a companion face, although one
+ of our other projects - Andika - may be useful. Andika is a sans-serif
+ font designed specifically for use in literacy programs around the
+ world. Andika Basic (Regular) is already available and a version of
+ Andika with a more complete repertoire will be available in a few months.
+
+Will you be extending Gentium to cover other scripts, and Hebrew in
+particular?
+
+ It is very unlikely that we would do this, as there are so many
+ pressing needs in Latin, Greek and Cyrillic scripts. But you could
+ contribute to the project.
+
+When will Cyrillic be completed?
+
+ Gentium Plus now has Cyrillic support.
+
+I need a couple of ancient Greek glyphs, such as the digamma. When will
+those be ready?
+
+ These are now available in Gentium Plus.
+
+Will there be a Type 1 version? What about OpenType?
+
+ Gentium Plus has OpenType and Graphite support. We do not plan to
+ produce Type 1. Included in the developer package of Gentium Plus
+ is a version in OT-CFF format, but it is provided as a source for
+ glyph outlines, not as a user-installable font, and includes no
+ smart font code. \ No newline at end of file
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/OFL-FAQ.txt b/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/OFL-FAQ.txt
new file mode 100644
index 00000000000..edb55c6107c
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/OFL-FAQ.txt
@@ -0,0 +1,369 @@
+OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL)
+Version 1.1-update2 - 23 August 2010
+(See http://scripts.sil.org/OFL for updates)
+
+
+CONTENTS OF THIS FAQ
+1 USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
+2 USING OFL FONTS FOR WEB PAGES AND ONLINE WEBFONT 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 USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
+
+1.1 Can I use the fonts for a book or other print publication?
+Yes. You can mention the font and author in the book's colophon if you wish, but that is not required.
+
+1.2 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 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 and include them in distribution CD/DVDs and online repositories. (Also see section 5.9 about rebuilding from source.)
+
+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.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 webfonts 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: use your common sense and 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 consists 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).
+
+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 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? 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.
+
+
+2 USING OFL FONTS FOR WEBPAGES AND ONLINE WEBFONT SERVICES
+
+2.1 Can I make webpages using these fonts?
+Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended. Your three best options:
+- 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 webfonts are often tuned for a web environment and not intended for installation and use outside a browser. The reasons in favour of using webfonts 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 webfont 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.
+
+2.4 Can I make OFL fonts available through webfont online services?
+Yes, you are welcome to include OFL fonts in online webfont 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 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. Be aware 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).
+
+2.6 Some webfont formats and services provide ways of "optimising" the font for a particular website or web application; is that allowed?
+Yes, it is permitted, but remember that these optimised 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 optimisation 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 used by your users. It may also introduce degradation of quality in the rendering or specific bugs on the various platforms compared to the original font. In other words, remember that one person's optimised font may be another person's missing feature. Various advanced typographic features are also available through CSS and may provide the desired effects without the need to modify the font.
+
+
+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.
+
+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.
+
+3.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?
+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.
+
+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.
+
+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.
+
+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.
+
+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. Please refer to the appropriate trademark laws.
+
+
+4 LICENSING YOUR ORIGINAL FONTS UNDER THE OFL
+
+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.
+
+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:
+
+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. Include this file in your release package.
+
+4.2.2 Put your copyright and the OFL text with Reserved Font Names 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). Depending on the format of your fonts and sources, you can use template human-readable headers or machine-readable metadata.
+
+4.2.3 Write an initial FONTLOG.txt for your font and include it in the release package.
+
+4.2.4 Include the relevant practical documentation on the license by including the OFL-FAQ.txt in your package.
+
+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.
+
+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), Kernest (http://kernest.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.
+
+4.5 Why should I use the OFL for my fonts?
+- to meet needs for fonts that can be modified to support minority 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 and Graphite 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 webfont online services
+- to attract attention for your commercial fonts
+- to make money through webfont 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
+
+
+5 CHOOSING RESERVED FONT NAMES
+
+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.
+
+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.
+
+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.
+
+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.
+
+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. 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.
+
+5.6 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.
+
+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).
+
+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.
+
+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 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 exiting RFNs but only add your own.
+
+
+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 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!
+
+6.2 Is the FONTLOG required?
+It is not a requirement of the license, but we strongly recommend you have one.
+
+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.
+
+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:
+
+- 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, svk, 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.
+
+
+8 ABOUT THE LICENSE ITSELF
+
+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.
+
+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. Only the Copyright Holder(s) can do this.
+
+8.3 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.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-2010 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.
+
+8.5 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.
+
+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.
+
+SIL gives permission to publish unofficial translations into other languages provided that they comply with the following guidelines:
+
+- Put the following disclaimer in both English and the target language stating clearly that the translation is unofficial:
+
+"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.
+
+If you start such a unofficial translation effort of the OFL and OFL-FAQ please let us know.
+
+
+9 ABOUT SIL INTERNATIONAL
+
+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.
+
+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 (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
+
+This file provides detailed information on the GlobalFontFamily Font Software. This information should be distributed along with the GlobalFontFamily fonts and any derivative works.
+
+Basic Font Information
+
+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...
+
+ChangeLog
+
+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 renowed educational institution with a strong design department...
+-----
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/OFL.txt b/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/OFL.txt
new file mode 100644
index 00000000000..5938f20e4f5
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/OFL.txt
@@ -0,0 +1,94 @@
+Copyright (c) 2003-2011 SIL International (http://www.sil.org/),
+with Reserved Font Names "Gentium" and "SIL".
+
+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
+-----------------------------------------------------------
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded,
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/QUOTES.txt b/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/QUOTES.txt
new file mode 100644
index 00000000000..9e95fd20cd8
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/QUOTES.txt
@@ -0,0 +1,73 @@
+QUOTES
+Gentium Release 1.03
+========================
+
+
+Read some of the comments sent to us by various grateful Gentium users:
+
+
+'Purpose: to build a free multilingual font to bring better typography to
+thousands of languages around the globe. I can think of no higher calling.'
+
+'...an interesting blend of economical use of space, a serious tone of voice
+and a modern informal dress code.'
+
+'Thank you for this fantastic font set -- fantastic both in its purpose and
+in its appearance and usability!'
+
+'Finally I can include Greek characters in my English papers without looking
+typographically schizophrenic!'
+
+'Thank you so much for sharing this amazing work. I do love the vision you
+have for "written word empowering". This is ethical science at its best.'
+
+'Our language restoration project thanks you.'
+
+'distinctive, elegant and readable'
+
+'a very warm look'
+
+'great consistency and legibility'
+
+'lotion for the eyes'
+
+'Your typeface Gentium is a "friendly" font to me. It's easy to read and its
+lines and visual connections flow gently.'
+
+'I needed a nice serif font with haceks and other diacriticals... and was
+very happy to find your Gentium. Thank you for making this available to us
+poorer academic perfectionists!'
+
+'Your font is definitely the most complete and good-looking I've found for
+my uses in Classical Greek.'
+
+'...the various letters in the Extended-Latin and IPA ranges look "native"
+to the font.'
+
+'...diacritic Nirvana...'
+
+'Thank you very much for this excellent font. It is the most readable I have
+ever seen.'
+
+'Officina Gentium: The workshop of the world.'
+
+'May I congratulate you on what seems to be an outstanding effort matched
+only by your generosity.'
+
+'I will be using this font regularly and will be recommending it strongly to
+others. This is a very beautiful typeface. What you have done is a most
+generous gift to the world.'
+
+'Many thanks. I have an esthetic dislike of "Times" fonts and a scholar's
+budget. Now I have Gentium and I'm pleased as punch.'
+
+'I appreciate your project, that of making a font suitable for many
+languages, including smaller ones.'
+
+'I am not sure where in the world I will end up, so I need something all
+inclusive. Thanks so much!'
+
+'Thanks for such a beautiful and mind-bogglingly useful typeface!'
+
+...
+
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/README.txt b/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/README.txt
new file mode 100644
index 00000000000..60ca7609ebd
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/Gentium/README.txt
@@ -0,0 +1,118 @@
+README
+Gentium Release 1.03
+24 June 2011
+====================
+
+Thank you for your interest in the Gentium fonts.
+We hope you find them useful!
+
+Gentium ("belonging to the nations" in Latin) is a Unicode typeface family
+designed to enable the many diverse ethnic groups around the world who use
+the Latin script to produce readable, high-quality publications. It supports
+a wide range of Latin-based alphabets and includes glyphs that correspond to
+all the Latin ranges of Unicode.
+
+The design is intended to be highly readable, reasonably compact, and
+visually attractive. The additional 'extended' Latin letters are designed to
+naturally harmonize with the traditional 26 ones. Diacritics are treated
+with careful thought and attention to their use. Gentium also supports both
+ancient and modern Greek, including a number of alternate forms. It has won
+a "Certificate of Excellence in Typeface Design" in two major international
+typeface design competitions: bukva:raz! (2001) and TDC2003 (2003).
+
+Gentium provides glyphs for a wide range of Latin and Greek characters.
+It currently supports the following ranges of Unicode 3.0 (completely unless
+noted):
+
+Range Description
+---------------------------
+U+0020-U+007F Basic Latin
+U+00A0-U+00FF Latin-1 Supplement
+U+0100-U+017F Latin Extended-A
+U+0180-U+021F Latin Extended-B
+U+0222-U+0233 Latin Extended-B (continued)
+U+0250-U+02AD IPA Extensions
+U+02B0-U+02FF Spacing Modifier Letters
+U+0300-U+036F Combining Diacritical Marks
+U+0370-U+03D5 Greek (not including archaic or Coptic)
+U+1E00-U+1EFF Latin Extended Additional
+U+1F00-U+1FFF Greek Extended
+U+2000-U+203A General Punctuation (partial)
+U+2070-U+209F Superscripts and Subscripts
+U+20A0-U+20CF Currency Symbols (partial)
+U+2100-U+214F Letterlike Symbols (only a couple)
+
+Gentium Regular also includes some Cyrillic glyphs, but they are only early
+drafts. A future version will include a completely revised set, and will
+expand the support for Latin, Greek and Cyrillic to cover Unicode 4.1. It
+will also include support for OpenType and Graphite smart font
+technologies.
+
+Gentium is released under the SIL Open Font License.
+Gentium is a trademark of SIL International.
+
+See the OFL and OFL-FAQ for details of the SIL Open Font License.
+See the FONTLOG for information on this and previous releases.
+See the QUOTES file to read the feedback received from Gentium users.
+See the GENTIUM-FAQ file for frequently asked questions and their answers
+ (such as why there are two families of fonts included).
+
+
+TIPS
+====
+
+We cannot afford to offer technical support at no cost. The font has, however,
+been through some testing on various platforms to be sure it works in most
+situations. In particular, it has been tested and shown to work on Windows
+2000, Windows XP and Ubuntu.
+
+If you do find a problem, please do report it to <gentium AT sil DOT org>.
+We can't guarantee any direct response, but will try to fix reported bugs in
+future versions. Make sure you read through the Gentium FAQ.
+
+Many problems can be solved, or at least explained, through an understanding
+of the encoding and use of the fonts. Here are some basic hints:
+
+Encoding:
+The fonts are encoded according to Unicode, so your application must support
+Unicode text in order to access letters other than the standard alphabet.
+Most Windows applications provide basic Unicode support. You will, however,
+need some way of entering Unicode text into your document.
+
+Keyboarding:
+Gentium does not include any keyboarding helps or utilities. It uses the
+built-in keyboards of the operating system. You will need to install the
+appropriate keyboard and input method for the characters of the language you
+wish to use. If you want to enter characters that are not supported by any
+system keyboard, depending on your platform Keyman (www.tavultesoft.com), KMFL
+(kmfl.sf.net), XKB (http://www.x.org/wiki/XKB) or Ukelele
+(scripts.sil.org/ukelele) can be helpful.
+
+Another method of entering some symbols is provided by a few applications
+as Adobe InDesign, LibreOffice or gucharmap. They can display a glyph palette
+that shows all the glyphs (symbols) in a font and allow you to enter them by
+clicking on the glyph you want.
+
+Rendering:
+Gentium also currently lacks any special font programming that can
+substitute one glyph for another or position glyphs in a 'smart' way, such
+as in OpenType, Apple Advanced Typography or SIL's Graphite. For example,
+although Gentium includes an 'ffl' ligature, there are no special routines
+in the font that will automatically substitute 'f'+'f'+'l' with 'ffl', but
+an individual application might provide that feature.
+
+
+INSTALLATION AND CONFIGURATION
+==============================
+
+For installation tips - including using packages (installers) - please refer
+to the documentation on http://scripts.sil.org/DecompressUtil
+
+CONTACT
+========
+For more information please visit the Gentium page on SIL International's
+Computers and Writing systems website:
+http://scripts.sil.org/gentium
+
+Or send an email to <gentium AT sil DOT org>
+
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/FONTLOG.txt b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/FONTLOG.txt
new file mode 100644
index 00000000000..b470a5b5af2
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/FONTLOG.txt
@@ -0,0 +1,153 @@
+FONTLOG
+Gentium Basic and Gentium Book Basic v1.1
+==========================================================
+
+
+This file provides detailed information on the Gentium Basic and Gentium Book Basic font families. This information should be distributed along with the Gentium Basic and Gentium Book Basic fonts and any derivative works.
+
+
+Basic Font Information
+----------------------
+
+Gentium ("belonging to the nations" in Latin) is a Unicode typeface family designed to enable the many diverse ethnic groups around the world who use the Latin script to produce readable, high-quality publications. The design is intended to be highly readable, reasonably compact, and visually attractive. Gentium has won a "Certificate of Excellence in Typeface Design" in two major international typeface design competitions: bukva:raz! (2001), TDC2003 (2003).
+
+The Gentium Basic and Gentium Book Basic font famililes are based on the original design, but with additional weights. The "Book" family is slightly heavier. Both families come with a complete regular, bold, italic and bold italic set of fonts.
+
+The supported character set, however, is much smaller than for the main Gentium fonts. These "Basic" fonts support only the Basic Latin and Latin-1 Supplement Unicode ranges, plus a selection of the more commonly used extended Latin characters, with miscellaneous diacritical marks, symbols and punctuation. For a complete list of supported characters see the list at the end of this document.
+
+In particular, these fonts do not support:
+
+- Full extended Latin IPA
+- Complete support for Central European languages
+- Greek
+- Cyrillic
+
+A much more complete character set will be supported in a future version of the complete Gentium fonts. These "Basic" fonts are intended as a way to provide additional weights for basic font users without waiting until the complete Gentium character set is finished. So please don't request additional glyphs or characters to be supported in the Basic fonts - such support will become available in the main Gentium family in the future.
+
+There are also some other limitations of the Basic fonts:
+
+- They are not completely metric-compatible with the full Gentium family
+ (some glyphs may have different widths, although changes have been minimal)
+- There is no kerning
+- There are no "Alt" versions, or ones with low-profile diacritics
+- The default stacking style for some diacritic combinations does not match Vietnamese-style conventions (although this is available through a OpenType/Graphite feature)
+- No support for TypeTuner
+
+There are, however, some wonderful new features that are still missing from the main Gentium family:
+
+- Bold!
+- Bold Italic!
+- The slightly-heavier Book family!
+- OpenType and Graphite smart code for diacritic placement!
+- A few useful OpenType and Graphite features
+- Support for a few more recent additions to Unicode and the SIL PUA (http://scripts.sil.org/UnicodePUA)
+- Character assignments are updated to conform to Unicode 5.1
+
+In particular, the Basic fonts support a subset of the smart font features that the Doulos SIL font supports. Those features are:
+
+- Capital Eng alternates
+- Literacy alternates
+- Capital Y-hook alternate
+- Capital N-left-hook alternate
+- Modifier apostrophe alternate
+- Modifier colon alternate
+- Open o alternate
+- Vietnamese-style diacritics
+
+More detail on the features can be seen in the Doulos SIL Technical Documentation (http://scripts.sil.org/DoulosSIL_Technical).
+
+
+Known Problems
+--------------
+
+We know of the following problems. Please report any other problems you encounter.
+
+- logicalnot (U+00AC) appears distorted in Bold Italic and Book Italic.
+- Opening the fonts with FontLab 5.0.x, then closing them, crashes FontLab. We are working to get this bug fixed in the next version of FontLab. A workaround is to open the font, save as a .vfb file, close (which still causes a crash). Then restart FontLab and open the .vfb file.
+
+
+ChangeLog
+---------
+(This should list both major and minor changes, most recent first.)
+
+4 Apr 2008 (Victor Gaultney) Gentium Basic/Gentium Book Basic version 1.1
+- Final release
+
+12 Nov 2007 (Victor Gaultney) Gentium Basic/Gentium Book Basic version 1.1b1
+- trimmed character set down to Basic
+- added additional weights
+- no FontLab source files
+
+28 Nov 2005 (Victor Gaultney) Gentium version 1.02
+- Changed licensing to the SIL Open Font License
+- Included FontLab source files
+- Fixed some duplicate PostScript glyphs names
+- Fixed italic angle
+
+19 Sep 2003 (Victor Gaultney) Gentium version 1.01
+- Maintenance release focused on changing internal font
+- Information to reflect the changeover to an SIL project
+- There is only one bug fix - the Greek mu PS name was changed to try and fix a display/printing problem. There is still no manual hinting
+
+16 Sep 2002 (Victor Gaultney) Gentium version 1.00
+- First public release
+- No manual hinting is included in this version. Some has been done - with good results - but is not yet complete enough.
+
+
+Information for Developers/Contributors
+---------------------------------------
+
+The source release contains FontLab source files for the eight fonts, but those files do not include the OpenType and Graphite code, as those are inserted after the fonts are generated from FontLab. The files are included as a source for the PostScript-style cubic curves. You are welcome, however, to open the font files themselves to gain access to the smart font code, although most editors will not let you edit that code directly. We will provide a richer set of sources for the full Gentium fonts at a later time.
+
+SIL will remain as maintainers of this font project, but we do not intend any further major releases. Our primary efforts will be going into the full Gentium package. Any contributions should be directed toward that project.
+
+
+Acknowledgements
+----------------
+(Here is where contributors can be acknowledged. If you make modifications be sure to add your name (N), email (E), web-address (W) and description (D). This list is sorted by last name in alphabetical order.)
+
+N: Victor Gaultney
+E: victor_gaultney@sil.org
+W: http://www.sil.org/~gaultney/
+D: Original Designer
+
+N: Annie Olsen
+E: nrsi@sil.org
+W: http://scripts.sil.org/
+D: Contributed some extended Latin glyphs
+
+N: SIL font engineers
+E: nrsi@sil.org
+W: http://scripts.sil.org/
+D: OpenType code and build support
+
+The Gentium project, and the Gentium Basic and Gentium Book Basic fonts, are maintained by SIL International.
+
+For more information please visit the Gentium page on SIL International's Computers and Writing systems website:
+http://scripts.sil.org/gentium
+
+Or send an email to <gentium AT sil DOT org>
+
+
+Character Range Coverage
+------------------------
+
+C0 Controls and Basic Latin (U+0020..U+007E)
+C1 Controls and Latin-1 Supplement (U+00A0..U+00FF)
+Latin Extended-A (U+0100..U+0103, U+0106..U+010E, U+011A..U+0121, U+0124..U+0125, U+0128..U+012D, U+0130..U+0133, U+0139..U+013A, U+0141..U+0144, U+0147..U+0148, U+014A..U+0155, U+0158..U+015D, U+0160..U+0161, U+0164, U+0168..U+0171, U+00174..U+017E)
+Latin Extended-B (U+0181, U+0186, U+0189..U+018A, U+018E, U+0190, U+0192, U+0197..U+019A, U+019D, U+019F..U+01A1, U+01A9..U+01AA, U+01AF..U+01B0, U+01B3..U+01B4, U+01B7, U+01CD..U+01E3, U+01E6..U+01E9, U+01EE..U+01EF, U+01F4..U+01F5, U+01F8..U+01FF, U+021E..U+021F, U+0226..U+0233, U+0237, U+023D, U+0241..U+0242, U+0244..U+0245, U+024A..U+024B)
+IPA Extensions (U+0251, U+0253..U+0254, U+0256..U+0257, U+0259, U+025B, U+0263, U+0268..U+0269, U+026B, U+0272, U+0275, U+0283, U+0289..U+028A, U+028C, U+0292, U+0294, U+02A0)
+Spacing Modifier Letters (U+02BC, U+02C0, U+02C6..U+02C7, U+02C9..U+02CB, U+02CD, U+02D7..U+02DD)
+Combining Diacritical Marks (U+0300..U+0304,U+0306..U+030C, U+031B, U+0323, U+0327..U+0328, U+0331, U+033F, U+035F)
+Greek and Coptic (U+03A0, U+03A9, U+03C0)
+Latin Extended Additional (U+1E02..U+1E0F, U+1E14..U+1E17, U+1E1C..U+1E27, U+1E2E..U+1E3B, U+1E3E..U+1E49, U+1E4C..U+1E6F, U+1E78..U+1E99, U+1EA0..U+1EF9)
+General Punctuation (U+2011, U+2013..U+2014, U+2018..U+201A, U+201C..U+201E, U+2020..U+2022, U+2026, U+2030, U+2039..U+203A, U+2044)
+Currency Symbols (U+20AC)
+Letterlike Symbols (U+2122..U+2123, U+2126)
+Mathematical Operators (U+2202, U+2205..U+2206, U+220F, U+2211..U+2212, U+2219..U+221A, U+221E, U+222B, U+2248, U+2260, U+2264..U+2265)
+Geometric Shapes (U+25CA, U+25CC)
+Latin Extended-C (U+2C60..U+2C62)
+Modifier Tone Letters (U+A700..U+A71A)
+Latin Extended-D (U+A789..U+A78C)
+Alphabetic Presentation Forms (U+FB01..U+FB02)
+SIL PUA (U+F130..U+F131, U+F195, U+F197, U+F1C8, U+F1E9..U+F1EA, U+F20E..U+F20F, U+F211..U+F212, U+F218..U+F219, U+F21D..U+F21F, U+F242, U+F26A)
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/GENTIUM-FAQ.txt b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/GENTIUM-FAQ.txt
new file mode 100644
index 00000000000..f525a5a0a6e
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/GENTIUM-FAQ.txt
@@ -0,0 +1,249 @@
+GENTIUM-FAQ
+Gentium Basic Release 1.1
+4 April 2008
+========================
+
+Here are some answers to frequently asked questions about the Gentium fonts:
+
+
+General
+========
+
+How do you pronounce Gentium?
+
+ The preferred pronunciation is with a soft G as in 'general', not a
+ hard one as in 'gold': JEN-tee-oom.
+
+What is GentiumAlt?
+
+ It is a version of the font with redesigned diacritics (flatter
+ ones) to make it more suitable for use with stacking diacritics, and
+ for languages such as Vietnamese. The Greek glyphs also use the
+ Porsonic (single-curve) design for the circumflex. Since the main
+ Gentium fonts do not currently include any 'smart' rendering routines,
+ there is no easy way to access these alternate diacritic shapes from
+ within the regular Gentium font. The encoding of the fonts are the same,
+ so the same text can be viewed with either one. There is also no
+ problem with having both font families installed at the same time.
+
+
+Licensing
+=========
+
+I want to use Gentium in my publication - can I?
+
+ Gentium is released under the SIL Open Font License, which permits use
+ for any publication, whether electronic or printed. For more answers
+ to use questions see the OFL-FAQ. The license, alongside information
+ specific to Gentium, is in the release package.
+
+I would like to bundle Gentium with my application - can I?
+
+ This is our most common question. The SIL Open Font License allows
+ bundling with applications, even commercial ones, with some restrictions.
+ See the OFL file.
+
+Can I use the font on my web site?
+
+ You can certainly create web pages that request that Gentium be used to
+ display them (if that font is available on the user's system). According
+ to the license, you are even allowed to place the font on your site for
+ people to download it. We would strongly recommend, however, that you
+ direct users to our site to download the font. This ensures that they
+ are always using the most recent version with bug fixes, etc. To make
+ this easier, we've simplified the URL for Gentium:
+ http://scripts.sil.org/gentium
+
+Is Gentium going to stay free?
+
+ There is no intention to ever charge users for using Gentium. The
+ current version is licensed under a free/open license and future
+ versions will be similar.
+
+
+Modification
+============
+
+I would like to modify Gentium to add a couple of characters I need. Can I?
+
+ Yes - that is allowed as long as you abide by the conditions of the
+ SIL Open Font License.
+
+So will you add glyphs upon request?
+
+ If you have a special symbol that you need (say, for a particular
+ transcription system), the best means of doing so will be to ensure
+ that the symbol makes it into the Unicode Standard. It is impossible
+ for us to add every glyph that every person desires, but we do place
+ a high priority on adding pretty much anything that falls in certain
+ Unicode ranges (extended Latin, Greek, Cyrillic). You can send us your
+ requests, but please understand that we are unlikely to add symbols
+ where the user base is very small, unless they have been accepted
+ into Unicode.
+
+Can I send you work I've done to be incorporated into Gentium?
+
+ Yes! See the FONTLOG for information on becoming a contributor.
+
+
+Technical
+=========
+
+Can you help me get Gentium working on my system?
+
+ We cannot afford to offer individual technical support. The best
+ resource is this website, where we hope to offer some limited help.
+ However, we do want to hear of any problems you encounter, so that
+ we can add them to the list of bugs to fix in later releases.
+
+ Our contact address is <gentium AT sil DOT org>. Please understand
+ that we cannot guarantee a personal response.
+
+I can't find all the extended Latin letters in the font. How do I type them?
+
+ Gentium is Unicode-encoded, which means that the computer stores a
+ special, unique code for each letter in your document. Since most
+ keyboards do not have hundreds of keys, special software is needed
+ in order to type the hundreds of special characters supported by the
+ font.
+
+I can't find the 'o with right hook' in the font. Where is it?
+
+ Combinations of base letters with diacritics are often called
+ composite, or pre-composed glyphs. Gentium has hundreds of these
+ (the ones that are included in Unicode). There are, however, many
+ common combinations that are not represented by a single composite.
+ It is possible to enter these into a document, but only as
+ individual components. So 'o with right hook' would be entered as
+ 'o', then 'right hook'. Although this may not look very good in some
+ cases, we're not able to anticipate every possible combination.
+ Future versions of Gentium will include 'smart font' support for
+ technologies such as OpenType and SIL's Graphite. This will make
+ diacritic positioning much better. The Gentium Basic fonts do,
+ however, include limited support for both OpenType and Graphite,
+ and demonstrate the type of support that will eventually be provided.
+
+Some diacritics are not aligning well with base glyphs, and if I type more
+than one diacritic, they run into each other. Why is that?
+
+ Gentium currently has no 'smart font' code for automatic diacritic
+ positioning, but the Gentium Basic fonts do, and similar support will
+ appear in the main fonts in the near future.
+
+How do I type the Greek letters?
+
+ You need a Unicode-compatible keyboarding system, which is not
+ included in the distribution package.
+
+I'm having problems making PDFs -- why won't my document distill?
+
+ Gentium is a large font, with lots of glyphs. As a result, some
+ printers can balk at PDFs that have the complete font embedded. The
+ easiest way to avoid this is to have Acrobat/Distiller subset the
+ font. This is generally a good idea anyway (with any font) and can
+ reduce the size of your files.
+
+
+Basic
+=====
+
+How are the Basic fonts (Gentium Basic, Gentium Book Basic) different
+from Gentium?
+
+ These font families are based on the original Gentium design, but with
+ additional weights. Both families come with a complete regular, bold,
+ italic and bold italic set of fonts. The supported character set,
+ however, is much smaller than for the main Gentium fonts. These
+ 'Basic' fonts support only the Basic Latin and Latin-1 Supplement
+ Unicode ranges, plus a selection of the more commonly used extended
+ Latin characters, with miscellaneous diacritical marks, symbols and
+ punctuation. In particular, these fonts do not support full extended
+ Latin IPA, complete support for Central European languages, Greek and
+ Cyrillic.
+
+What is the Book weight?
+
+ It is a complete second font family that is slightly heavier overall,
+ and more useful for some purposes. The main Gentium family will
+ eventually have a complete matching Book weight, along with matching
+ italics.
+
+Why is the line spacing greater for the Basic fonts?
+
+ In some environments, stacked diacritics in Gentium could display as
+ 'chopped-off'. Gentium Basic has slightly wider default line spacing
+ in order to avoid this problem. Most applications do, however, let you
+ set the line spacing explicitly, so you can have the lines spaced
+ precisely as you wish.
+
+Will you be accepting requests for additions to the Basic character set?
+
+ No. We are now focusing our development efforts on the main Gentium
+ fonts, which already provide richer character set support.
+
+Is there an Alt version of the Basic fonts?
+
+ No, although you may notice that capitals and some tall lowercase
+ letters do use 'low-profile' versions.
+
+
+Future
+======
+
+Now that SIL International has taken over Gentium, who will be the next
+designer?
+
+ Victor Gaultney will remain as primary designer, but Annie Olsen, a
+ fellow type designer from the SIL Non-Roman Script Initiative, has
+ joined the project team. She is a former calligraphy teacher, and is
+ well suited for the task. Other members of the NRSI team will also
+ add their expertise in technical matters.
+
+Do you plan to include other typographic enhancements (small caps, old style
+figures, etc.)?
+
+ Those would be nice, wouldn't they? From a design point of view,
+ it would be great to have these refinements, and we haven't ruled
+ them out. But there are other needs that are much higher priority
+ (Bold, Cyrillic, etc.). If you think you could contribute some of
+ your time and effort to these enhancements, see the FONTLOG file for
+ information on becoming a contributor.
+
+What about bold?
+
+ The Gentium Basic fonts include Bold and Bold Italic versions. The
+ main Gentium fonts will also include them in the future.
+
+Sans-serif?
+
+ There is a definite need for a sans-serif font that shares some of
+ Gentiums strengths -- high readability, economy of space, etc. It
+ would also be great if that font also harmonized well with Gentium.
+ We don't currently have any plans for a companion face, although one
+ of our other projects - Andika - may be useful. Andika is a sans-serif
+ font designed specifically for use in literacy programs around the
+ world, and is available from our web site.
+
+Will you be extending Gentium to cover other scripts, and Hebrew in
+particular?
+
+ It is very unlikely that we would do this, as there are so many
+ pressing needs in Latin, Greek and Cyrillic scripts. But you could
+ contribute to the project.
+
+When will Cyrillic be completed?
+
+ As soon as we can get it done, but it is still a few months away.
+
+I need a couple of ancient Greek glyphs, such as the digamma. When will
+those be ready?
+
+ These have already been designed and will be in the next main release.
+
+Will there be a Type 1 version? What about OpenType?
+
+ The next generation of Gentium will have OpenType, Graphite and AAT
+ support. We do not plan to produce Type 1 versions at this time, but
+ please write us if this is important (and tell us why). We are, however,
+ considering releasing a version in OT-CFF format, but it will not go
+ through the same careful testing as the standard OT/Graphite/AAT version. \ No newline at end of file
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/OFL-FAQ.txt b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/OFL-FAQ.txt
new file mode 100644
index 00000000000..6785a19cdff
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/OFL-FAQ.txt
@@ -0,0 +1,216 @@
+OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL)
+Version 1.1 - 1 February 2007
+(See http://scripts.sil.org/OFL for updates)
+
+
+1 ABOUT USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
+
+1.1 Can I use the fonts in any publication, even embedded in the file?
+Yes. You may use them like most other fonts, but unlike some fonts you may include an embedded subset of the fonts in your document. Such use does not require you to include this license or other files (listed in OFL condition 2), nor does it require any type of acknowledgement within the publication. Some mention of the font name within the publication information (such as in a colophon) is usually appreciated. If you wish to include the complete font as a separate file, you should distribute the full font package, including all existing acknowledgements, and comply with the OFL conditions. Of course, referencing or embedding an OFL font in any document does not change the license of the document itself. The requirement for fonts to remain under the OFL does not apply to any document created using the fonts and their derivatives. Similarly, creating any kind of graphic using a font under OFL does not make the resulting artwork subject to the OFL.
+
+1.2 Can I make web pages using these fonts?
+Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended.
+
+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.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 agreggated with software under FLOSS (Free/Libre and Open Source Software) licenses. Since fonts are much more useful aggregated to than merged with existing software, possible incompatibility with existing software licenses is not a problem. You can also repackage the fonts and the accompanying components in a .rpm or .deb package and include them in distro CD/DVDs and online repositories.
+
+1.5 I want to distribute the fonts with my program. Does this mean my program also has to be free and open source software?
+No. Only the portions based on the font software are required to be released under the OFL. The intent of the license is to allow aggregation or bundling with software under restricted licensing as well.
+
+1.6 Can I include the fonts on a CD of freeware or commercial fonts?
+Yes, as long some other font or software is also on the disk, so the OFL font is not sold by itself.
+
+1.7 Can I sell a software package that includes these fonts?
+Yes, you can do this with both the Original Version and a Modified Version. Examples of bundling made possible by the OFL would include: word processors, design and publishing applications, training and educational software, edutainment software, etc.
+
+1.8 Why won't the OFL let me sell the fonts alone?
+The intent is to keep people from making money by simply redistributing the fonts. The only people who ought to profit directly from the fonts should be the original authors, and those authors have kindly given up potential direct income to distribute their fonts under the OFL. Please honor and respect their contribution!
+
+1.9 I've come across a font released under the OFL. How can I easily get more information about the Original Version? How can I know where it stands compared to the Original Version or other Modified Versions?
+Consult the copyright statement in the license for ways to contact the original authors. Consult the FONTLOG for information on how the font differs from the Original Version, and get in touch with the various contributors via the information in the acknowledgment section. Please consider using the Original Versions of the fonts whenever possible.
+
+1.10 What do you mean in condition 4? Can you provide examples of abusive promotion / endorsement / advertisement vs. normal acknowledgement?
+The intent is that the goodwill and reputation of the author(s) should not be used in a way that makes it sound like the original author(s) endorse or approve of a specific Modified Version or software bundle. For example, it would not be right to advertise a word processor by naming the author(s) in a listing of software features, or to promote a Modified Version on a web site by saying "designed by ...". However, it would be appropriate to acknowledge the author(s) if your software package has a list of people who deserve thanks. We realize that this can seem to be a gray area, but the standard used to judge an acknowledgement is that if the acknowledgement benefits the author(s) it is allowed, but if it primarily benefits other parties, or could reflect poorly on the author(s), then it is not.
+
+
+2 ABOUT MODIFYING OFL LICENSED FONTS
+
+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.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?
+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.
+
+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.
+
+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.
+
+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.
+
+2.8 What do you mean by "primary name as presented to the user"? Are you are referring to the font menu name?
+Yes, the requirement to change the visible name used to differentiate the font from others applies to the font menu name and other mechanisms to specify a font in a document. It would be fine, for example, to keep a text reference to the original fonts in the description field, in your modified source file or in documentation provided alongside your derivative as long as no one could be confused that your modified source is the original. But you cannot use the Reserved Font Names in any way to identify the font to the user (unless the Copyright Holder(s) allow(s) it through a separate agreement, see section 2.7). Users who install derivatives ("Modified Versions") on their systems should not see any of the original names ("Reserved Font Names") in their font menus, for example. Again, this is to ensure that users are not confused and do not mistake a font for another and so expect features only another derivative or the Original Version can actually offer. Ultimately, creating name conflicts will cause many problems for the users as well as for the designer of both the Original and Modified versions, so please think ahead and find a good name for your own derivative. Font substitution systems like fontconfig, or application-level font fallback configuration within OpenOffice.org or Scribus, will also get very confused if the name of the font they are configured to substitute to actually refers to another physical font on the user's hard drive. It will help everyone if Original Versions and Modified Versions can easily be distinguished from one another and from other derivatives. The substitution mechanism itself is outside the scope of the license. Users can always manually change a font reference in a document or set up some kind of substitution at a higher level but at the lower level the fonts themselves have to respect the Reserved Font Name(s) requirement to prevent ambiguity. If a substitution is currently active the user should be aware of it.
+
+2.9 Am I not allowed to use any part of the Reserved Font Names?
+You may not use the words of the font names, but you would be allowed to use parts of words, as long as you do not use any word from the Reserved Font Names entirely. We do not recommend using parts of words because of potential confusion, but it is allowed. For example, if "Foobar" was a Reserved Font Name, you would be allowed to use "Foo" or "bar", although we would not recommend it. Such an unfortunate choice would confuse the users of your fonts as well as make it harder for other designers to contribute.
+
+2.10 So what should I, as an author, identify as Reserved Font Names?
+Original authors are encouraged to name their fonts using clear, distinct names, and only declare the unique parts of the name as Reserved Font Names. For example, the author of a font called "Foobar Sans" would declare "Foobar" as a Reserved Font Name, but not "Sans", as that is a common typographical term, and may be a useful word to use in a derivative font name. Reserved Font Names should also be single words. A font called "Flowing River" should have Reserved Font Names "Flowing" and "River", not "Flowing River".
+
+2.11 Do I, as an author, have to identify and Reserved Font Names?
+No, but we strongly encourage you to do so. This is to avoid confusion between your work and Modified versions. You may, however, give certain trusted parties the right to use any of your Reserved Font Names through separate written agreements. For example, even if "Foobar" is a RFN, you could write up an agreement to give company "XYZ" the right to distribute a modified version with a name that includes "Foobar". This allows for freedom without confusion.
+
+2.12 Are any names (such as the main font name) reserved by default?
+No. That is a change to the license as of version 1.1. If you want any names to be Reserved Font Names, they must be specified after the copyright statement.
+
+2.13 What is this FONTLOG thing exactly?
+It has three purposes: 1) to provide basic information on the font to users and other developers, 2) to document changes that have been made to the font or accompanying files, either by the original authors or others, and 3) to provide a place to acknowledge the authors and other contributors. Please use it! See below for details on how changes should be noted.
+
+2.14 Am I required to update the FONTLOG?
+No, but users, designers and other developers might get very frustrated at you if you don't! People need to know how derivative fonts differ from the originals, and how to take advantage of the changes, or build on them.
+
+
+3 ABOUT THE FONTLOG
+
+The FONTLOG can take a variety of formats, but should include these four sections:
+
+3.1 FONTLOG for <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.
+
+3.2 Basic Font Information
+(Here is where you would describe the purpose and brief specifications for the font project, and where users can find more detailed documentation. It can also include references to how changes can be contributed back to the Original Version. You may also wish to include a short guide to the design, or a reference to such a document.)
+
+3.3 ChangeLog
+(This should list both major and minor changes, most recent first. Here are some examples:)
+
+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>"
+
+1 Jan 2005 (Joe Smith) <FontFamilyName> Version 1.0
+- Initial release of font "<FontFamilyName>"
+
+3.4 Acknowledgements
+(Here is where contributors can be acknowledged.
+
+If you make modifications be sure to add your name (N), email (E), web-address (W) and description (D). This list is sorted by last name in alphabetical order.)
+
+N: Jane Doe
+E: jane@university.edu
+W: http://art.university.edu/projects/fonts
+D: Contributor - Armenian glyphs and code
+
+N: Fred Foobar
+E: fred@foobar.org
+W: http://foobar.org
+D: Contributor - misc Graphite fixes
+
+N: Pat Johnson
+E: pat@fontstudio.org
+W: http://pat.fontstudio.org
+D: Designer - Greek & Cyrillic glyphs based on Roman design
+
+N: Tom Parker
+E: tom@company.com
+W: http://www.company.com/tom/projects/fonts
+D: Engineer - original smart font code
+
+N: Joe Smith
+E: joe@fontstudio.org
+W: http://joe.fontstudio.org
+D: Designer - original Roman glyphs
+
+(Original authors can also include information here about their organization.)
+
+
+4 ABOUT MAKING CONTRIBUTIONS
+
+4.1 Why should I contribute my changes back to the original authors?
+It would benefit many people if you contributed back to what you've received. Providing your contributions and improvements to the fonts and other components (data files, source code, build scripts, documentation, etc.) could be a tremendous help and would encourage others to contribute as well and 'give back', which means you will have an opportunity to benefit from other people's contributions as well. Sometimes maintaining your own separate version takes more effort than merging back with the original. Be aware that any contributions, however, must be either your own original creation or work that you own, and you may be asked to affirm that clearly when you contribute.
+
+4.2 I've made some very nice improvements to the font, will you consider adopting them and putting them into future Original Versions?
+Most authors would be very happy to receive such contributions. Keep in mind that it is unlikely that they would want to incorporate major changes that would require additional work on their end. Any contributions would likely need to be made for all the fonts in a family and match the overall design and style. Authors are encouraged to include a guide to the design with the fonts. It would also help to have contributions submitted as patches or clearly marked changes (the use of smart source revision control systems like subversion, svk or bzr is a good idea). Examples of useful contributions are bug fixes, additional glyphs, stylistic alternates (and the smart font code to access them) or improved hinting.
+
+4.3 How can I financially support the development of OFL fonts?
+It is likely that most authors of OFL fonts would accept financial contributions - contact them for instructions on how to do this. Such contributions would support future development. You can also pay for others to enhance the fonts and contribute the results back to the original authors for inclusion in the Original Version.
+
+
+5 ABOUT THE LICENSE
+
+5.1 I see that this is version 1.1 of the license. Will there be later changes?
+Version 1.1 is the first minor revision of the OFL. We are confident that version 1.1 will meet most needs, but are open to future improvements. Any revisions would be for future font releases, and previously existing licenses would remain in effect. No retroactive changes are possible, although the Copyright Holder(s) can re-release the font under a revised OFL. All versions will be available on our web site: http://scripts.sil.org/OFL.
+
+5.2 Can I use the SIL Open Font License for my own fonts?
+Yes! We heartily encourage anyone to use the OFL to distribute their own original fonts. It is a carefully constructed license that allows great freedom along with enough artistic integrity protection for the work of the authors as well as clear rules for other contributors and those who redistribute the fonts. Some additional information about using the OFL is included at the end of this FAQ.
+
+5.3 Does this license restrict the rights of the Copyright Holder(s)?
+No. The Copyright Holder(s) still retains all the rights to their creation; they are only releasing a portion of it for use in a specific way. For example, the Copyright Holder(s) may choose to release a 'basic' version of their font under the OFL, but sell a restricted 'enhanced' version. Only the Copyright Holder(s) can do this.
+
+5.4 Is the OFL a contract or a license?
+The OFL is a license and not a contract and so does not require you to sign it to have legal validity. By using, modifying and redistributing components under the OFL you indicate that you accept the license.
+
+5.5 How about translating the license and the FAQ into other languages?
+SIL certainly recognises the need for people who are not familiar with English to be able to understand the OFL and this FAQ better in their own language. Making the license very clear and readable is a key goal of the OFL.
+
+If you are an experienced translator, you are very welcome to help 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 translations ambiguities could be abused and create problems.
+
+We give permission to publish unofficial translations into other languages provided that they comply with the following guidelines:
+
+- put the following disclaimer in both English and the target language stating clearly that the translation is unofficial:
+
+"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.
+
+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."
+"
+
+- 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.
+
+
+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.
+
+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.
+
+6.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
+
+
+7 ABOUT USING THE OFL FOR YOUR ORIGINAL FONTS
+
+If you want to release your fonts under the OFL, you only need to do the following:
+
+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.
+
+
+That's all. If you have any more questions please get in touch with us.
+
+
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/OFL.txt b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/OFL.txt
new file mode 100644
index 00000000000..c258eea2f95
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumBasic/OFL.txt
@@ -0,0 +1,94 @@
+Copyright (c) 2003-2008 SIL International (http://www.sil.org/),
+with Reserved Font Names "Gentium" and "SIL".
+
+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 - 1 February 2007
+-----------------------------------------------------------
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded,
+redistributed and/or sold with any software provided that the font
+names of derivative works are changed. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/FONTLOG.txt b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/FONTLOG.txt
new file mode 100644
index 00000000000..73fd9a928bd
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/FONTLOG.txt
@@ -0,0 +1,205 @@
+FONTLOG
+Gentium Plus font family
+========================
+
+
+This file provides detailed information on the Gentium Plus family of fonts.
+This information should be distributed along with the Gentium Plus fonts and
+any derivative works.
+
+
+Basic Font Information
+----------------------
+
+Gentium ("belonging to the nations" in Latin) is a Unicode typeface family
+designed to enable the many diverse ethnic groups around the world who use
+the Latin script to produce readable, high-quality publications. The
+design is intended to be highly readable, reasonably compact, and visually
+attractive. Gentium has won a "Certificate of Excellence in Typeface
+Design" in two major international typeface design competitions:
+bukva:raz! (2001), TDC2003 (2003).
+
+The Gentium Plus font family is based on the original design. It currently
+comes with regular and italic face only, although additional weights are in
+development.
+
+The goal for this product is to provide a single Unicode-based font family
+that contains a comprehensive inventory of glyphs needed for almost any
+Roman- or Cyrillic-based writing system, whether used for phonetic or
+orthographic needs, and provide a matching Greek face. In addition, there
+is provision for other characters and symbols useful to linguists. This
+font makes use of state-of-the-art font technologies to support complex
+typographic issues, such as the need to position arbitrary combinations
+of base glyphs and diacritics optimally.
+
+Two fonts from this typeface family are included in this release:
+
+ * Gentium Plus Regular
+ * Gentium Plus Italic
+
+Work is ongoing to provide bold and bold-italic weights, as well as a
+complete book-weight family.
+
+For detailed documentation see the contents of the 'documentation' folder.
+
+
+A Note Regarding the Open Font License and TypeTuner
+----------------------------------------------------
+
+The OFL prohibits the use of Reserved Font Names "Gentium" and "SIL" in
+the name of any font that is derived from the Original Version of Gentium
+Plus. However, SIL International (the Copyright Holder) grants through
+this separate written agreement the right to use the Reserved Font Names
+in any Modified Version of this font created by using TypeTuner as long
+as the feature information contained in the Original Version is used,
+unmodified, as the source for TypeTuner feature information, and
+"Gentium Plus" is not the resulting font family name.
+
+TypeTuner-produced fonts created in this manner are still bound by the
+terms of the OFL. Specifically, the use of Reserved Font Names is
+prohibited when making derivatives of a TypeTuner-produced font. Anyone
+making a derivative of a TypeTuner font will need to find a different
+name. For example a TypeTuner-produced font may be named
+"Gentium Plus Literacy SomeFarAwayPlace" but a derivative of that font made
+with other tools would not be allowed to use the "Gentium" and "SIL"
+Reserved Font Names and would have to be named something like "Nations Serif".
+
+
+ChangeLog
+---------
+(This should list both major and minor changes, most recent first.)
+
+1 August 2012 (SIL NRSI team) Gentium Plus version 1.510
+- Changed Graphite feature identifiers from integers to 4-character
+ alphanumeric tags (no other changes)
+
+12 September 2011 (SIL NRSI team) Gentium Plus version 1.508
+- Removed the VDMX table
+- Changed version number (using ttfsetver)
+
+25 Aug 2011 (SIL NRSI team) Gentium Plus version 1.506
+- Double-encoded the SIL PUA characters which were added to Unicode 5.2 and 6.0
+ (using ttfremap)
+- Corrected problem with coverage tables (using ttfsortcover)
+- Changed version number (using ttfsetver)
+- Added device metric tables
+- Added an empty dsig table
+
+16 Nov 2010 (SIL NRSI team) Gentium Plus version 1.504
+- Added codepage bits for 1251 (Cyrillic), 1257 (Windows Baltic), 1258
+ (Vietnamese)
+
+1 Nov 2010 (SIL NRSI team) Gentium Plus version 1.502
+- Regular and Italic weights only
+- New OpenType and Graphite support
+- Converted kerning to OpenType (but not Graphite)
+- New extended Cyrillic script support, inc. Serbian alternates
+- Character set and features up to same level as Charis SIL 4.106
+- Support for more historic Greek characters and alternate seriffed beta
+- No separate GentiumAlt fonts (replaced by font features)
+- Added WOFF versions and examples
+
+28 Nov 2005 (Victor Gaultney) Gentium version 1.02
+- Changed licensing to the SIL Open Font License
+- Included FontLab source files
+- Fixed some duplicate PostScript glyph names
+- Fixed italic angle
+
+19 Sep 2003 (Victor Gaultney) Gentium version 1.01
+- Maintenance release focused on changing internal font
+- Information to reflect the changeover to an SIL project
+- There is only one bug fix - the Greek mu PS name was changed to try and fix
+a display/printing problem. There is still no manual hinting.
+
+16 Sep 2002 (Victor Gaultney) Gentium version 1.00
+- First public release
+- No manual hinting is included in this version. Some has been done - with
+good results - but is not yet complete enough.
+
+
+Information for Developers/Contributors
+---------------------------------------
+
+The release of Gentium Plus version 1.502 (and any subsequent versions) under
+the OFL license provides a means for people to modify the fonts to meet their
+needs and contribute to the project. For information on what you're allowed to
+change or modify, consult the OFL and OFL-FAQ.
+
+Anyone can make their own modified version of Gentium Plus (using a different
+name), but SIL International will continue to maintain and develop the
+canonical version of the Gentium Plus fonts. As the package maintainer, we
+welcome contributions. Here are some things to keep in mind:
+
+Format: We are open to contributions in various formats, but if you want to
+maximise the chances of us including your work, please make it available to
+us (via email or a URL) as either a FontLab database (preferred) or a
+PostScript Type 1 (or OT-CFF) font.
+
+Source files: The primary source files for the fonts are the fonts themselves.
+They contain all the important data in the fonts and can be studied and
+modified using open font tools such as FontForge and TTX. The developer
+release contains additional source files that might be useful. See the file
+source/SOURCES.txt in that release archive for further information.
+
+Copyright attribution: If you submit something for inclusion in the main
+Gentium Plus fonts, we will ask you to affirm that it is your original work,
+and ask you to assign the copyright of your work to SIL International. This
+is to ensure that future releases can be made under improved versions of the
+OFL without needing to track you down for further permission. This follows
+the same principle used by the FSF. Keep in mind that we are a
+not-for-profit organization committed to free/libre and open source
+software, and that any contributions incorporated in the fonts will always
+be available under the OFL or a similar license.
+
+Quality: Because we want to be able to guarantee a high level of quality for
+the primary Gentium Plus fonts, we will review submissions carefully. Please
+don't be discouraged if we do not include a submission for this reason, or
+ask you to make specific revisions.
+
+Types of contributions: If you wish to make a contribution - a set of
+additional glyphs, scripts, code, etc. - please contact us before you do any
+work to see if it is a contribution we currently need. Every addition adds
+to the complexity of the project and needs to be carefully planned. This
+also avoids two people working on the same type of addition at the same time.
+
+Linux packages: Please contact the upstream maintainer of the various
+packages - nicolas_spalinger@sil.org - if you want to help package or
+maintain a package.
+
+When submissions will be included: We plan to revise the fonts when major
+updates are needed (eg new versions of Unicode). If you wish to make
+submissions, contact us on the timing.
+
+
+Acknowledgements
+----------------
+(Here is where contributors can be acknowledged. If you make modifications be
+sure to add your name (N), email (E), web-address (W) and description (D).
+This list is sorted by last name in alphabetical order.)
+
+N: Victor Gaultney
+E: victor_gaultney@sil.org
+W: http://www.sil.org/~gaultney/
+D: Original Designer
+
+N: Annie Olsen
+E: fonts@sil.org
+W: http://scripts.sil.org/
+D: Contributed some extended Latin glyphs
+
+N: Iska Routamaa
+E: fonts@sil.org
+W: http://scripts.sil.org/
+D: Contributed some extended Latin glyphs and extensive work on the italic face
+
+N: SIL font engineers
+E: fonts@sil.org
+W: http://scripts.sil.org/
+D: Graphite, OpenType, and TypeTuner code, and build support
+
+The Gentium and Gentium Plus fonts are maintained by SIL International.
+
+For more information please visit the Gentium page on SIL International's
+Computers and Writing systems website: http://scripts.sil.org/gentium
+
+Or send an email to gentium@sil.org
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/GENTIUM-FAQ.txt b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/GENTIUM-FAQ.txt
new file mode 100644
index 00000000000..9f836fa306d
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/GENTIUM-FAQ.txt
@@ -0,0 +1,205 @@
+GENTIUM-FAQ
+Gentium Plus
+========================
+
+Here are some answers to frequently asked questions about the Gentium Plus
+fonts:
+
+
+General
+========
+
+How do you pronounce Gentium?
+
+ The preferred pronunciation is with a soft G as in 'general', not a
+ hard one as in 'gold': JEN-tee-oom.
+
+
+Licensing
+=========
+
+I want to use Gentium Plus in my publication - can I?
+
+ Gentium Plus is released under the SIL Open Font License, which permits
+ use for any publication, whether electronic or printed. For more answers
+ to use questions see the OFL-FAQ. The license, alongside information
+ specific to Gentium Plus, is in the release package.
+
+I would like to bundle Gentium Plus with my application - can I?
+
+ This is our most common question. The SIL Open Font License allows
+ bundling with applications, even commercial closed source ones, with
+ some restrictions. See the OFL.txt file and the OFL-FAQ.
+
+Can I use the font on my web site?
+
+ You can certainly create web pages that request that Gentium Plus be
+ used to display them (both if that font is already available on the
+ user's system or if it is delivered via @font-face). According to the
+ license, you are also allowed to place the font on your site for people
+ to download it. We would strongly recommend, however, that you direct
+ users to our site to download the font. This ensures that they are
+ always using the most recent version with bug fixes, etc. To make this
+ easier, there is a simple URL for Gentium: http://scripts.sil.org/Gentium
+ There is further important discussion of webfont issues in the OFL-FAQ.
+
+Is Gentium Plus going to stay unrestricted and available at no cost?
+
+ There is no intention to ever charge users for using Gentium and its
+ variants. The current version is licensed under a free/open license and
+ future versions will be similarly unencumbered.
+
+
+Modification
+============
+
+I would like to modify Gentium Plus to add a couple of characters I need.
+Can I?
+
+ Yes - that is allowed as long as you abide by the conditions of the
+ SIL Open Font License.
+
+So will you add glyphs upon request?
+
+ If you have a special symbol that you need (say, for a particular
+ transcription system), the best means of doing so will be to ensure
+ that the symbol makes it into the Unicode Standard. It is impossible
+ for us to add every glyph that every person desires, but we do place
+ a high priority on adding pretty much anything that falls in certain
+ Unicode ranges (extended Latin, Greek, Cyrillic). You can send us your
+ requests, but please understand that we are unlikely to add symbols
+ where the user base is very small, unless they have been accepted
+ into Unicode.
+
+Can I send you work I've done to be incorporated into Gentium Plus?
+
+ Yes. See the FONTLOG for information on becoming a contributor.
+
+
+Technical
+=========
+
+Can you help me get Gentium Plus working on my system?
+
+ We cannot afford to offer individual technical support. The best
+ resource is this website, where we hope to offer some limited help.
+ However, we do want to hear of any problems you encounter, so that
+ we can add them to the list of bugs to fix in later releases.
+ Our contact address is gentium@sil.org. Please understand
+ that we cannot guarantee a personal response.
+
+I can't find all the extended Latin letters in the font. How do I type them?
+
+ Gentium Plus is Unicode-encoded, which means that the computer stores a
+ special, unique code for each letter in your document. Since most
+ keyboards do not have hundreds of keys, special software is needed
+ in order to type the hundreds of special characters supported by the
+ font. See the README.txt file for more information.
+
+I can't find the 'o with right hook' in the font. Where is it?
+
+ Combinations of base letters with diacritics are often called
+ composite, or pre-composed glyphs. Gentium Plus has hundreds of these
+ (the ones that are included in Unicode). There are, however, many
+ common combinations that are not represented by a single composite.
+ It is possible to enter these into a document, but only as
+ individual components. So 'o with right hook' would be entered as
+ 'o', then 'right hook'. Although this may not look very good in some
+ cases, we're not able to anticipate every possible combination.
+ Gentium Plus includes 'smart font' support for both OpenType and
+ Graphite.
+
+Some diacritics are not aligning well with base glyphs, and if I type more
+than one diacritic, they run into each other. Why is that?
+
+ The smart diacritic positioning in Gentium Plus relies on either
+ OpenType or Graphite. The application you are using must support
+ one of these technologies in order to see appropriate diacritic
+ positioning.
+
+How do I type the Greek letters?
+
+ You need a Unicode-compatible keyboarding system, which is not
+ included in the release.
+
+I'm having problems making PDFs -- why won't my document distill?
+
+ Gentium Plus is a large font, with lots of glyphs. As a result,
+ some older printers, PDF distillers and readers can balk at PDFs
+ that have the complete font embedded. The easiest way to avoid
+ this is to have the PDF distiller subset the font. This is
+ generally a good idea anyway (with any font) and can reduce the
+ size of your files.
+
+
+Plus
+=====
+
+How are the Gentium Plus fonts different from Gentium?
+
+ This font is based on the original Gentium design, but with an expanded
+ character and glyph repertoire. It currently comes with regular and
+ italic faces. It comes with near-complete support for Latin, Cyrillic
+ and Greek. It also contains 'smart font' support for OpenType and Graphite
+ technologies. This allows for correct diacritic placement over all base
+ characters, whether they are tall, short, wide, narrow, with or without
+ descenders. It also provides for a large variety of alternates glyphs.
+ These are described on the Gentium website.
+
+Why is the line spacing greater for the Plus fonts?
+
+ In some environments, stacked diacritics in Gentium could display as
+ 'chopped-off'. Gentium Plus has slightly wider default line spacing
+ in order to avoid this problem. Most applications do, however, let you
+ set the line spacing explicitly, so you can have the lines spaced
+ precisely as you wish.
+
+Is there an Alt version of the Basic fonts?
+
+ No, although you may notice that capitals and some tall lowercase
+ letters do use 'low-profile' versions. Gentium Plus also includes
+ OpenType and Graphite features to turn low-profile diacritics on
+ and off.
+
+
+Future
+======
+
+What are your future plans for Gentium Plus?
+
+ Our next major effort is completing bold and bold italic weights
+ of Gentium Plus alongside a new Gentium Book Plus family. These new
+ weights are currently available for Gentium Basic/Gentium Book Basic.
+
+Do you plan to include other typographic enhancements (old style
+figures, etc.)?
+
+ Those would be nice, wouldn't they? From a design point of view,
+ it would be great to have these refinements, and we haven't ruled
+ them out. But there are other needs that are much higher priority
+ (such as bold). If you think you could contribute some of your time
+ and effort to these enhancements, see the FONTLOG.txt file for
+ information on becoming a contributor.
+
+Sans-serif?
+
+ There is a definite need for a sans-serif font that shares some of
+ Gentium's strengths -- high readability, economy of space, etc. It
+ would also be great if that font also harmonized well with Gentium.
+ We don't currently have any plans for a companion face, although one
+ of our other projects - Andika - may be useful. Andika is a sans-serif
+ font designed specifically for use in literacy programs around the
+ world, and is available from our web site.
+
+Will you be extending Gentium to cover other scripts, and Hebrew in
+particular?
+
+ It is very unlikely that we would do this, as there are so many
+ pressing needs in Latin, Greek and Cyrillic scripts.
+
+Will there be a Type 1 version? What about OpenType?
+
+ Gentium Plus includes OpenType and Graphite support. We do not plan
+ to produce Type 1 versions at this time, but please write us if this
+ is important (and tell us why). We already provide the PostScript
+ bézier curves in the 'designsource' files in the developer release.
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/OFL-FAQ.txt b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/OFL-FAQ.txt
new file mode 100644
index 00000000000..edb55c6107c
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/OFL-FAQ.txt
@@ -0,0 +1,369 @@
+OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL)
+Version 1.1-update2 - 23 August 2010
+(See http://scripts.sil.org/OFL for updates)
+
+
+CONTENTS OF THIS FAQ
+1 USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
+2 USING OFL FONTS FOR WEB PAGES AND ONLINE WEBFONT 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 USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
+
+1.1 Can I use the fonts for a book or other print publication?
+Yes. You can mention the font and author in the book's colophon if you wish, but that is not required.
+
+1.2 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 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 and include them in distribution CD/DVDs and online repositories. (Also see section 5.9 about rebuilding from source.)
+
+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.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 webfonts 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: use your common sense and 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 consists 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).
+
+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 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? 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.
+
+
+2 USING OFL FONTS FOR WEBPAGES AND ONLINE WEBFONT SERVICES
+
+2.1 Can I make webpages using these fonts?
+Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended. Your three best options:
+- 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 webfonts are often tuned for a web environment and not intended for installation and use outside a browser. The reasons in favour of using webfonts 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 webfont 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.
+
+2.4 Can I make OFL fonts available through webfont online services?
+Yes, you are welcome to include OFL fonts in online webfont 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 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. Be aware 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).
+
+2.6 Some webfont formats and services provide ways of "optimising" the font for a particular website or web application; is that allowed?
+Yes, it is permitted, but remember that these optimised 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 optimisation 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 used by your users. It may also introduce degradation of quality in the rendering or specific bugs on the various platforms compared to the original font. In other words, remember that one person's optimised font may be another person's missing feature. Various advanced typographic features are also available through CSS and may provide the desired effects without the need to modify the font.
+
+
+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.
+
+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.
+
+3.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?
+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.
+
+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.
+
+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.
+
+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.
+
+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. Please refer to the appropriate trademark laws.
+
+
+4 LICENSING YOUR ORIGINAL FONTS UNDER THE OFL
+
+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.
+
+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:
+
+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. Include this file in your release package.
+
+4.2.2 Put your copyright and the OFL text with Reserved Font Names 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). Depending on the format of your fonts and sources, you can use template human-readable headers or machine-readable metadata.
+
+4.2.3 Write an initial FONTLOG.txt for your font and include it in the release package.
+
+4.2.4 Include the relevant practical documentation on the license by including the OFL-FAQ.txt in your package.
+
+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.
+
+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), Kernest (http://kernest.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.
+
+4.5 Why should I use the OFL for my fonts?
+- to meet needs for fonts that can be modified to support minority 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 and Graphite 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 webfont online services
+- to attract attention for your commercial fonts
+- to make money through webfont 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
+
+
+5 CHOOSING RESERVED FONT NAMES
+
+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.
+
+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.
+
+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.
+
+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.
+
+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. 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.
+
+5.6 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.
+
+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).
+
+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.
+
+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 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 exiting RFNs but only add your own.
+
+
+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 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!
+
+6.2 Is the FONTLOG required?
+It is not a requirement of the license, but we strongly recommend you have one.
+
+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.
+
+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:
+
+- 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, svk, 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.
+
+
+8 ABOUT THE LICENSE ITSELF
+
+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.
+
+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. Only the Copyright Holder(s) can do this.
+
+8.3 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.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-2010 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.
+
+8.5 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.
+
+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.
+
+SIL gives permission to publish unofficial translations into other languages provided that they comply with the following guidelines:
+
+- Put the following disclaimer in both English and the target language stating clearly that the translation is unofficial:
+
+"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.
+
+If you start such a unofficial translation effort of the OFL and OFL-FAQ please let us know.
+
+
+9 ABOUT SIL INTERNATIONAL
+
+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.
+
+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 (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
+
+This file provides detailed information on the GlobalFontFamily Font Software. This information should be distributed along with the GlobalFontFamily fonts and any derivative works.
+
+Basic Font Information
+
+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...
+
+ChangeLog
+
+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 renowed educational institution with a strong design department...
+-----
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/OFL.txt b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/OFL.txt
new file mode 100644
index 00000000000..a85aedb9e58
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/OFL.txt
@@ -0,0 +1,94 @@
+Copyright (c) 2003-2012 SIL International (http://www.sil.org/),
+with Reserved Font Names "Gentium" and "SIL".
+
+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
+-----------------------------------------------------------
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded,
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/README.txt b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/README.txt
new file mode 100644
index 00000000000..a3c52129c12
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/README.txt
@@ -0,0 +1,88 @@
+README
+Gentium Plus
+========================
+
+Thank you for your interest in the Gentium Plus fonts.
+We hope you find them useful!
+
+Gentium Plus supports a wide range of Latin, Greek and Cyrillic
+characters. Documentation for the fonts is available on Gentium website
+(http://scripts.sil.org/Gentium), including details on what ranges are
+supported.
+
+Gentium Plus is released under the SIL Open Font License.
+
+See the OFL and OFL-FAQ for details of the SIL Open Font License.
+See the FONTLOG for information on this and previous releases.
+See the GENTIUM-FAQ for answers to common questions about the Gentium fonts
+See the website (http://scripts.sil.org/Gentium) for further documentation.
+See the SIL Unicode Roman FAQ (http://scripts.sil.org/ComplexRomanFontFAQ)
+for frequently asked questions and their answers regarding SIL's Roman fonts.
+
+
+TIPS
+====
+
+As this font is distributed at no cost, we are unable to provide a
+commercial level of personal technical support. The font has, however,
+been through some testing on various platforms to be sure it works in most
+situations. In particular, it has been tested and shown to work on Windows
+XP, Windows Vista and Windows 7. Graphite capabilities have been tested
+on Graphite-supported platforms.
+
+If you do find a problem, please do report it to fonts@sil.org.
+We can't guarantee any direct response, but will try to fix reported bugs in
+future versions. Make sure you read through the
+SIL Unicode Roman FAQ (http://scripts.sil.org/ComplexRomanFontFAQ).
+
+Many problems can be solved, or at least explained, through an understanding
+of the encoding and use of the fonts. Here are some basic hints:
+
+Encoding:
+The fonts are encoded according to Unicode, so your application must support
+Unicode text in order to access letters other than the standard alphabet.
+Most Windows applications provide basic Unicode support. You will, however,
+need some way of entering Unicode text into your document.
+
+Keyboarding:
+This font does not include any keyboarding helps or utilities. It uses the
+built-in keyboards of the operating system. You will need to install the
+appropriate keyboard and input method for the characters of the language you
+wish to use. If you want to enter characters that are not supported by any
+system keyboard, the Keyman program (www.tavultesoft.com) can be helpful
+on Windows systems. Also available for Windows is MSKLC
+(http://www.microsoft.com/globaldev/tools/msklc.mspx).
+For Linux systems such as Ubuntu, KMFL (http://kmfl.sourceforge.net/)
+is available. Ukelele (http://scripts.sil.org/ukelele) is available for
+Mac OS X versions 10.2 and later.
+
+For other platforms, KMFL (http://kmfl.sourceforge.net/),
+XKB (http://www.x.org/wiki/XKB) or Ukelele (http://scripts.sil.org/ukelele)
+can be helpful.
+
+If you want to enter characters that are not supported by any system
+keyboard, and to access the full Unicode range, we suggest you use
+gucharmap, kcharselect on Ubuntu or similar software.
+
+Another method of entering some symbols is provided by a few applications such
+as Adobe InDesign or OpenOffice.org. They can display a glyph palette or input
+dialog that shows all the glyphs (symbols) in a font and allow you to enter
+them by clicking on the glyph you want.
+
+Rendering:
+This font is designed to work with Graphite or Opentype advanced font
+technologies. To take advantage of the advanced typographic
+capabilities of this font, you must be using applications that provide an
+adequate level of support for Graphite or OpenType. See "Applications
+that provide an adequate level of support for SIL Unicode Roman fonts"
+(http://scripts.sil.org/Complex_AdLvSup).
+
+
+CONTACT
+========
+For more information please visit the Gentium page on SIL International's
+Computers and Writing systems website:
+http://scripts.sil.org/Gentium
+
+Or send an email to gentium@sil.org
+
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/documentation/DOCUMENTATION.txt b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/documentation/DOCUMENTATION.txt
new file mode 100644
index 00000000000..c3f51bd51c0
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/documentation/DOCUMENTATION.txt
@@ -0,0 +1,11 @@
+DOCUMENTATION
+Gentium Plus
+========================
+
+
+This file describes the documentation files included with the Gentium Plus font family. This information should be distributed along with the Gentium Plus fonts and any derivative works.
+
+Primary documentation for the Gentium Plus font family is on the Gentium website (http://scripts.sil.org/Gentium).
+
+The GentiumPlus-features.pdf file illustrates the use of OpenType and Graphite features.
+The GentiumPlus-features.odt file illustrates the use of OpenType and Graphite features (source file for the pdf).
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/documentation/GentiumPlus-features.odt b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/documentation/GentiumPlus-features.odt
new file mode 100644
index 00000000000..b28fca1d8e1
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/documentation/GentiumPlus-features.odt
Binary files differ
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/documentation/GentiumPlus-features.pdf b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/documentation/GentiumPlus-features.pdf
new file mode 100644
index 00000000000..fdfcd3c878a
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlus/documentation/GentiumPlus-features.pdf
Binary files differ
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlusCompact/FONTLOG.txt b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlusCompact/FONTLOG.txt
new file mode 100644
index 00000000000..881f3eca863
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlusCompact/FONTLOG.txt
@@ -0,0 +1,206 @@
+FONTLOG
+Gentium Plus font family
+========================
+
+
+This file provides detailed information on the Gentium Plus family of fonts.
+This information should be distributed along with the Gentium Plus fonts and
+any derivative works.
+
+
+Basic Font Information
+----------------------
+
+Gentium ("belonging to the nations" in Latin) is a Unicode typeface family
+designed to enable the many diverse ethnic groups around the world who use
+the Latin script to produce readable, high-quality publications. The
+design is intended to be highly readable, reasonably compact, and visually
+attractive. Gentium has won a "Certificate of Excellence in Typeface
+Design" in two major international typeface design competitions:
+bukva:raz! (2001), TDC2003 (2003).
+
+The Gentium Plus font family is based on the original design. It currently
+comes with regular and italic face only, although additional weights are in
+development.
+
+The goal for this product is to provide a single Unicode-based font family
+that contains a comprehensive inventory of glyphs needed for almost any
+Roman- or Cyrillic-based writing system, whether used for phonetic or
+orthographic needs, and provide a matching Greek face. In addition, there
+is provision for other characters and symbols useful to linguists. This
+font makes use of state-of-the-art font technologies to support complex
+typographic issues, such as the need to position arbitrary combinations
+of base glyphs and diacritics optimally.
+
+Two fonts from this typeface family are included in this release:
+
+ * Gentium Plus Regular
+ * Gentium Plus Italic
+
+Work is ongoing to provide bold and bold-italic weights, as well as a
+complete book-weight family.
+
+For detailed documentation see the contents of the 'documentation' folder.
+
+
+A Note Regarding the Open Font License and TypeTuner
+----------------------------------------------------
+
+The OFL prohibits the use of Reserved Font Names "Gentium" and "SIL" in
+the name of any font that is derived from the Original Version of Gentium
+Plus. However, SIL International (the Copyright Holder) grants through
+this separate written agreement the right to use the Reserved Font Names
+in any Modified Version of this font created by using TypeTuner as long
+as the feature information contained in the Original Version is used,
+unmodified, as the source for TypeTuner feature information, and
+"Gentium Plus" is not the resulting font family name.
+
+TypeTuner-produced fonts created in this manner are still bound by the
+terms of the OFL. Specifically, the use of Reserved Font Names is
+prohibited when making derivatives of a TypeTuner-produced font. Anyone
+making a derivative of a TypeTuner font will need to find a different
+name. For example a TypeTuner-produced font may be named
+"Gentium Plus Literacy SomeFarAwayPlace" but a derivative of that font made
+with other tools would not be allowed to use the "Gentium" and "SIL"
+Reserved Font Names and would have to be named something like "Nations Serif".
+
+
+ChangeLog
+---------
+(This should list both major and minor changes, most recent first.)
+
+05 Oct 2011 (SIL TypeTuner) Tuned version of Gentium Plus version 1.508
+- Tuned and delivered by SIL TypeTuner
+(http://scripts.sil.org/ttw/fonts2go.cgi).
+- See included xml file for details of feature changes.
+
+12 September 2011 (SIL NRSI team) Gentium Plus version 1.508
+- Removed the VDMX table
+- Changed version number (using ttfsetver)
+
+25 Aug 2011 (SIL NRSI team) Gentium Plus version 1.506
+- Double-encoded the SIL PUA characters which were added to Unicode 5.2 and 6.0
+ (using ttfremap)
+- Corrected problem with coverage tables (using ttfsortcover)
+- Changed version number (using ttfsetver)
+- Added device metric tables
+- Added an empty dsig table
+
+16 Nov 2010 (SIL NRSI team) Gentium Plus version 1.504
+- Added codepage bits for 1251 (Cyrillic), 1257 (Windows Baltic), 1258
+ (Vietnamese)
+
+1 Nov 2010 (SIL NRSI team) Gentium Plus version 1.502
+- Regular and Italic weights only
+- New OpenType and Graphite support
+- Converted kerning to OpenType (but not Graphite)
+- New extended Cyrillic script support, inc. Serbian alternates
+- Character set and features up to same level as Charis SIL 4.106
+- Support for more historic Greek characters and alternate seriffed beta
+- No separate GentiumAlt fonts (replaced by font features)
+- Added WOFF versions and examples
+
+28 Nov 2005 (Victor Gaultney) Gentium version 1.02
+- Changed licensing to the SIL Open Font License
+- Included FontLab source files
+- Fixed some duplicate PostScript glyph names
+- Fixed italic angle
+
+19 Sep 2003 (Victor Gaultney) Gentium version 1.01
+- Maintenance release focused on changing internal font
+- Information to reflect the changeover to an SIL project
+- There is only one bug fix - the Greek mu PS name was changed to try and fix
+a display/printing problem. There is still no manual hinting.
+
+16 Sep 2002 (Victor Gaultney) Gentium version 1.00
+- First public release
+- No manual hinting is included in this version. Some has been done - with
+good results - but is not yet complete enough.
+
+
+Information for Developers/Contributors
+---------------------------------------
+
+The release of Gentium Plus version 1.502 (and any subsequent versions) under
+the OFL license provides a means for people to modify the fonts to meet their
+needs and contribute to the project. For information on what you're allowed to
+change or modify, consult the OFL and OFL-FAQ.
+
+Anyone can make their own modified version of Gentium Plus (using a different
+name), but SIL International will continue to maintain and develop the
+canonical version of the Gentium Plus fonts. As the package maintainer, we
+welcome contributions. Here are some things to keep in mind:
+
+Format: We are open to contributions in various formats, but if you want to
+maximise the chances of us including your work, please make it available to
+us (via email or a URL) as either a FontLab database (preferred) or a
+PostScript Type 1 (or OT-CFF) font.
+
+Source files: The primary source files for the fonts are the fonts themselves.
+They contain all the important data in the fonts and can be studied and
+modified using open font tools such as FontForge and TTX. The developer
+release contains additional source files that might be useful. See the file
+source/SOURCES.txt in that release archive for further information.
+
+Copyright attribution: If you submit something for inclusion in the main
+Gentium Plus fonts, we will ask you to affirm that it is your original work,
+and ask you to assign the copyright of your work to SIL International. This
+is to ensure that future releases can be made under improved versions of the
+OFL without needing to track you down for further permission. This follows
+the same principle used by the FSF. Keep in mind that we are a
+not-for-profit organization committed to free/libre and open source
+software, and that any contributions incorporated in the fonts will always
+be available under the OFL or a similar license.
+
+Quality: Because we want to be able to guarantee a high level of quality for
+the primary Gentium Plus fonts, we will review submissions carefully. Please
+don't be discouraged if we do not include a submission for this reason, or
+ask you to make specific revisions.
+
+Types of contributions: If you wish to make a contribution - a set of
+additional glyphs, scripts, code, etc. - please contact us before you do any
+work to see if it is a contribution we currently need. Every addition adds
+to the complexity of the project and needs to be carefully planned. This
+also avoids two people working on the same type of addition at the same time.
+
+Linux packages: Please contact the upstream maintainer of the various
+packages - nicolas_spalinger@sil.org - if you want to help package or
+maintain a package.
+
+When submissions will be included: We plan to revise the fonts when major
+updates are needed (eg new versions of Unicode). If you wish to make
+submissions, contact us on the timing.
+
+
+Acknowledgements
+----------------
+(Here is where contributors can be acknowledged. If you make modifications be
+sure to add your name (N), email (E), web-address (W) and description (D).
+This list is sorted by last name in alphabetical order.)
+
+N: Victor Gaultney
+E: victor_gaultney@sil.org
+W: http://www.sil.org/~gaultney/
+D: Original Designer
+
+N: Annie Olsen
+E: fonts@sil.org
+W: http://scripts.sil.org/
+D: Contributed some extended Latin glyphs
+
+N: Iska Routamaa
+E: fonts@sil.org
+W: http://scripts.sil.org/
+D: Contributed some extended Latin glyphs and extensive work on the italic face
+
+N: SIL font engineers
+E: fonts@sil.org
+W: http://scripts.sil.org/
+D: Graphite, OpenType, and TypeTuner code, and build support
+
+The Gentium and Gentium Plus fonts are maintained by SIL International.
+
+For more information please visit the Gentium page on SIL International's
+Computers and Writing systems website: http://scripts.sil.org/gentium
+
+Or send an email to gentium@sil.org
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlusCompact/README.txt b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlusCompact/README.txt
new file mode 100644
index 00000000000..e21ec732363
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlusCompact/README.txt
@@ -0,0 +1,99 @@
+README
+Gentium Plus v1.508
+========================
+
+Thank you for your interest in the Gentium Plus fonts.
+We hope you find them useful!
+
+Gentium Plus supports a wide range of Latin, Greek and Cyrillic
+characters. Documentation for the fonts is available on Gentium website
+(http://scripts.sil.org/Gentium), including details on what ranges are
+supported.
+
+Gentium Plus is released under the SIL Open Font License.
+
+See the OFL and OFL-FAQ for details of the SIL Open Font License.
+See the FONTLOG for information on this and previous releases.
+See the GENTIUM-FAQ for answers to common questions about the Gentium fonts
+See the website (http://scripts.sil.org/Gentium) for further documentation.
+See the SIL Unicode Roman FAQ (http://scripts.sil.org/ComplexRomanFontFAQ)
+for frequently asked questions and their answers regarding SIL's Roman fonts.
+
+TYPETUNER
+05 Oct 2011
+=========
+
+This package contains a TypeTuned version of the Gentium Plus font.
+
+The TypeTuner settings file used to generate the enclosed font
+is included in the package as GentiumPlus-feat_set_tuned.xml.
+By inspecting this file with a text editor you can determine
+which alternate behaviors have been enabled.
+
+
+TIPS
+====
+
+As this font is distributed at no cost, we are unable to provide a
+commercial level of personal technical support. The font has, however,
+been through some testing on various platforms to be sure it works in most
+situations. In particular, it has been tested and shown to work on Windows
+XP, Windows Vista and Windows 7. Graphite capabilities have been tested
+on Graphite-supported platforms.
+
+If you do find a problem, please do report it to fonts@sil.org.
+We can't guarantee any direct response, but will try to fix reported bugs in
+future versions. Make sure you read through the
+SIL Unicode Roman FAQ (http://scripts.sil.org/ComplexRomanFontFAQ).
+
+Many problems can be solved, or at least explained, through an understanding
+of the encoding and use of the fonts. Here are some basic hints:
+
+Encoding:
+The fonts are encoded according to Unicode, so your application must support
+Unicode text in order to access letters other than the standard alphabet.
+Most Windows applications provide basic Unicode support. You will, however,
+need some way of entering Unicode text into your document.
+
+Keyboarding:
+This font does not include any keyboarding helps or utilities. It uses the
+built-in keyboards of the operating system. You will need to install the
+appropriate keyboard and input method for the characters of the language you
+wish to use. If you want to enter characters that are not supported by any
+system keyboard, the Keyman program (www.tavultesoft.com) can be helpful
+on Windows systems. Also available for Windows is MSKLC
+(http://www.microsoft.com/globaldev/tools/msklc.mspx).
+For Linux systems such as Ubuntu, KMFL (http://kmfl.sourceforge.net/)
+is available. Ukelele (http://scripts.sil.org/ukelele) is available for
+Mac OS X versions 10.2 and later.
+
+For other platforms, KMFL (http://kmfl.sourceforge.net/),
+XKB (http://www.x.org/wiki/XKB) or Ukelele (http://scripts.sil.org/ukelele)
+can be helpful.
+
+If you want to enter characters that are not supported by any system
+keyboard, and to access the full Unicode range, we suggest you use
+gucharmap, kcharselect on Ubuntu or similar software.
+
+Another method of entering some symbols is provided by a few applications such
+as Adobe InDesign or OpenOffice.org. They can display a glyph palette or input
+dialog that shows all the glyphs (symbols) in a font and allow you to enter
+them by clicking on the glyph you want.
+
+Rendering:
+This font is designed to work with Graphite or Opentype advanced font
+technologies. To take advantage of the advanced typographic
+capabilities of this font, you must be using applications that provide an
+adequate level of support for Graphite or OpenType. See "Applications
+that provide an adequate level of support for SIL Unicode Roman fonts"
+(http://scripts.sil.org/Complex_AdLvSup).
+
+
+CONTACT
+========
+For more information please visit the Gentium page on SIL International's
+Computers and Writing systems website:
+http://scripts.sil.org/Gentium
+
+Or send an email to gentium@sil.org
+
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlusCompact/feat_set_tuned.xml b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlusCompact/feat_set_tuned.xml
new file mode 100644
index 00000000000..f06594eb954
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/GentiumPlusCompact/feat_set_tuned.xml
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE features_set SYSTEM "feat_set.dtd">
+<features_set version="1.0">
+ <feature name="Line spacing" value="Tight"/>
+</features_set>
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/Makefile b/Master/texmf-dist/doc/fonts/gentium-tug/Makefile
new file mode 100644
index 00000000000..856f44f7b14
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/Makefile
@@ -0,0 +1,14 @@
+# This file is part of the Gentium package for TeX.
+# It is licensed under the Expat License, see doc//README for details.
+
+env = TEXMFHOME=../../..
+gentium.pdf: gentium.tex
+ $(env) pdflatex '\nonstopmode\pdfmapfile{+gentium-type1.map}\input $<'
+# read the map file for running out of the development tree,
+# without having the package installed, necessarily.
+
+dist:
+ cd ../../../source/fonts/gentium-tug \
+ && ./make-zip-4CTAN.sh -l
+clean:
+ rm -f *.aux *.log *.out *.toc
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/OFL-FAQ.txt b/Master/texmf-dist/doc/fonts/gentium-tug/OFL-FAQ.txt
new file mode 100644
index 00000000000..edb55c6107c
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/OFL-FAQ.txt
@@ -0,0 +1,369 @@
+OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL)
+Version 1.1-update2 - 23 August 2010
+(See http://scripts.sil.org/OFL for updates)
+
+
+CONTENTS OF THIS FAQ
+1 USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
+2 USING OFL FONTS FOR WEB PAGES AND ONLINE WEBFONT 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 USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
+
+1.1 Can I use the fonts for a book or other print publication?
+Yes. You can mention the font and author in the book's colophon if you wish, but that is not required.
+
+1.2 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 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 and include them in distribution CD/DVDs and online repositories. (Also see section 5.9 about rebuilding from source.)
+
+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.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 webfonts 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: use your common sense and 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 consists 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).
+
+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 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? 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.
+
+
+2 USING OFL FONTS FOR WEBPAGES AND ONLINE WEBFONT SERVICES
+
+2.1 Can I make webpages using these fonts?
+Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended. Your three best options:
+- 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 webfonts are often tuned for a web environment and not intended for installation and use outside a browser. The reasons in favour of using webfonts 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 webfont 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.
+
+2.4 Can I make OFL fonts available through webfont online services?
+Yes, you are welcome to include OFL fonts in online webfont 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 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. Be aware 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).
+
+2.6 Some webfont formats and services provide ways of "optimising" the font for a particular website or web application; is that allowed?
+Yes, it is permitted, but remember that these optimised 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 optimisation 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 used by your users. It may also introduce degradation of quality in the rendering or specific bugs on the various platforms compared to the original font. In other words, remember that one person's optimised font may be another person's missing feature. Various advanced typographic features are also available through CSS and may provide the desired effects without the need to modify the font.
+
+
+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.
+
+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.
+
+3.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?
+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.
+
+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.
+
+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.
+
+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.
+
+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. Please refer to the appropriate trademark laws.
+
+
+4 LICENSING YOUR ORIGINAL FONTS UNDER THE OFL
+
+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.
+
+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:
+
+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. Include this file in your release package.
+
+4.2.2 Put your copyright and the OFL text with Reserved Font Names 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). Depending on the format of your fonts and sources, you can use template human-readable headers or machine-readable metadata.
+
+4.2.3 Write an initial FONTLOG.txt for your font and include it in the release package.
+
+4.2.4 Include the relevant practical documentation on the license by including the OFL-FAQ.txt in your package.
+
+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.
+
+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), Kernest (http://kernest.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.
+
+4.5 Why should I use the OFL for my fonts?
+- to meet needs for fonts that can be modified to support minority 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 and Graphite 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 webfont online services
+- to attract attention for your commercial fonts
+- to make money through webfont 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
+
+
+5 CHOOSING RESERVED FONT NAMES
+
+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.
+
+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.
+
+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.
+
+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.
+
+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. 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.
+
+5.6 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.
+
+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).
+
+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.
+
+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 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 exiting RFNs but only add your own.
+
+
+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 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!
+
+6.2 Is the FONTLOG required?
+It is not a requirement of the license, but we strongly recommend you have one.
+
+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.
+
+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:
+
+- 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, svk, 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.
+
+
+8 ABOUT THE LICENSE ITSELF
+
+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.
+
+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. Only the Copyright Holder(s) can do this.
+
+8.3 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.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-2010 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.
+
+8.5 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.
+
+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.
+
+SIL gives permission to publish unofficial translations into other languages provided that they comply with the following guidelines:
+
+- Put the following disclaimer in both English and the target language stating clearly that the translation is unofficial:
+
+"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.
+
+If you start such a unofficial translation effort of the OFL and OFL-FAQ please let us know.
+
+
+9 ABOUT SIL INTERNATIONAL
+
+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.
+
+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 (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
+
+This file provides detailed information on the GlobalFontFamily Font Software. This information should be distributed along with the GlobalFontFamily fonts and any derivative works.
+
+Basic Font Information
+
+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...
+
+ChangeLog
+
+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 renowed educational institution with a strong design department...
+-----
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/OFL.txt b/Master/texmf-dist/doc/fonts/gentium-tug/OFL.txt
new file mode 100644
index 00000000000..1a3a84b58f2
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/OFL.txt
@@ -0,0 +1,95 @@
+Copyright (c) 2013 TeX Users Group (http://www.tug.org/)
+Copyright (c) 2003-2011 SIL International (http://www.sil.org/),
+with Reserved Font Names "Gentium" and "SIL".
+
+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
+-----------------------------------------------------------
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded,
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/README b/Master/texmf-dist/doc/fonts/gentium-tug/README
new file mode 100644
index 00000000000..366dc9e5e3e
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/README
@@ -0,0 +1,183 @@
+The home page for the original SIL Gentium font family is
+http://scripts.sil.org/Gentium.
+
+The home page for this TeX package, gentium-tug, is http://tug.org/gentium.
+This TeX package consists of:
+
+1. The original (unaltered) GentiumPlus, GentiumBook, and other
+Gentium-family fonts in TrueType format, as developed by SIL and
+released under the OFL (see OFL.txt and OFL-FAQ.txt).
+
+2. Converted fonts in PostScript Type 1 format, released under the same
+terms. These incorporate the name "Gentium" by permission of SIL given
+to the TeX Users Group.
+
+3. ConTeXt, LaTeX and other supporting files under the Expat license,
+text given below (also at http://directory.fsf.org/wiki/License:Expat).
+
+4. Documentation: the TeX-specific documentation is in
+gentium.{tex,pdf}. We have also included the original documentation,
+fontlogs, and other files from the SIL distribution, entirely unaltered,
+in the Gentium*/ subdirectories here.
+
+The contributors are listed in the FONTLOG.txt files.
+
+
+ENCODINGS:
+=========
+The package provides font files needed for both Unicode XeTeX and LuaTeX
+as well as 8-bit engines such as pdfTeX and TeX (->dvips).
+
+For 8-bit engines the following encodings are available:
+- Latin:
+ ot1 OT1 - default encoding in TeX
+ ec T1 - for most European languages
+ texnansi LY1 - for most Western European languages
+ l7x L7x - for Baltic languages
+ qx QX - for Polish
+ t5 T5 - for Vietnamese
+ ts1 TS1 - TeX symbols (for LaTeX)
+
+- Greek:
+ agr (only supported in ConTeXt)
+ lgr (only supported in LaTeX)
+
+- Cyrillic:
+ t2a T2A
+ t2b T2B
+ t2c T2C
+ x2 X2
+
+
+FILES:
+=====
+See the FONTLOG for high-level descriptions of what comes from what.
+
+/doc/fonts/gentium
+ /Gentium - OFL and other files from SIL
+ /GentiumBasic
+ /GentiumPlus
+ /GentiumPlusCompact
+ ChangeLog - internal ChangeLog for development of TeX packaging
+ FONTLOG.txt - ChangeLog for font releases
+ gentium.tex - package documentation
+ gentium.pdf
+ OFL.txt - font licence
+ OFL-FAQ.txt - FAQ about font licence
+ README - this file
+/fonts
+ /afm/public/gentium - Adobe Font Metrics (only needed for generating new tfm files)
+ GentiumPlus-R.afm
+ GentiumPlus-I.afm
+ GenBasB.afm
+ GenBasBI.afm
+ /enc/dvips/gentium - encoding files
+ gentium-{ts1,agr,lgr}.enc
+ gentium-{ot1,ec,texnansi,qx,t5,l7x,t2a,t2b,t2c,x2}{,-sc}.enc
+ gentium-{ec,t5}-ttf{,-sc}.enc - to get around a bug in pdfTeX (dcroat & Idotaccent)
+ /map
+ /dvips/gentium
+ gentium-type1.map - for TeX and LaTeX
+ /pdftex/gentium
+ gentium-{ec,texnansi,qx,t5,l7x,agr,t2a}.map - for ConTeXt MKII
+ gentium-{ot1,ts1,lgr,t2b,t2c,x2}.map - (not used anywhere; might be removed)
+ gentium-truetype.map - for pdfTeX and pdfLaTeX
+ /tfm/public/gentium
+ {ts1,agr,lgr}-gentiumplus-{regular,italic}.tfm
+ {ot1,ec,texnansi,qx,t5,l7x,t2a,t2b,t2c,x2}-gentiumplus-{regular,italic}{,-sc}.tfm
+ {ot1,ec,texnansi,qx,t5,l7x,ts1}-gentiumbasic-{bold,bolditalic}.tfm
+ /truetype/public/gentium - fonts from SIL
+ Gentium-R.ttf
+ Gentium-I.ttf
+ GentiumAlt-R.ttf
+ GentiumAlt-I.ttf
+
+ GenBasR.ttf
+ GenBasI.ttf
+ GenBasB.ttf
+ GenBasBI.ttf
+
+ GenBkBasR.ttf
+ GenBkBasI.ttf
+ GenBkBasB.ttf
+ GenBkBasBI.ttf
+
+ GentiumPlus-R.ttf
+ GentiumPlus-I.ttf
+ GentiumPlusCompact-R.ttf
+ GentiumPlusCompact-I.ttf
+ /type1/public/gentium - fonts, converted from TrueType by TUG
+ GentiumPlus-R.pfb
+ GentiumPlus-I.pfb
+ GenBasB.pfb
+ GenBasBI.pfb
+
+/source/fonts/gentium
+ /lig
+ gentium-{agr,lgr,t2a,t2b,t2c,x2}.lig - additional ligatures used to generate tfm files
+ /type1 - scripts for TrueType -> Type1 conversion
+ ff-gentium.pe
+ generate-extra-kerns.sh
+ greekcorrection.py
+ kerncorrection.py
+ Makefile
+ generate-support-files.rb - ruby script to generate different files
+ gentium.rb - ruby library with support classes and functions
+/tex
+ /context/third/gentium - support files for ConTeXt
+ type-gentium.tex
+ /latex/gentium - support files for LaTeX
+ gentium.sty
+ {ot1,t1,ly1,qx,t5,l7x,ts1,lgr,t2a,t2b,t2c,x2}gentium.fd
+
+
+TODO:
+====
+- check that there are no f-ligatures in the encodings X2, LGR
+ and possibly AGR
+
+- Add kerning pairs for Cyrillic.
+
+- Add more kerning pairs for accented Latin letters. Currently, there
+ are kerning pairs mostly for the combination of one accented letter
+ and a letter without accent. There are just several kerning pairs
+ for the combination of two accented letters, mostly useful for Czech
+ and Slovak.
+
+- Look at the letter Lcaron if the accent should be moved to the left
+ (reported to SIL).
+
+- The combination of two commas seems not to give quotedblbase in T1.
+ Check it and correct using lig file if needed.
+
+- when/if bold variants of Gentium are released,
+ either remove Gentium Basic or create a complete set.
+
+
+
+EXPAT LICENSE:
+=============
+This file is part of the Gentium package for TeX.
+The package contains font files licensed under the SIL Open Font License,
+while the rest are under the Expat License.
+
+Copyright (c) 2008-2013 TeX Users Group
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be included
+in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/gentium.pdf b/Master/texmf-dist/doc/fonts/gentium-tug/gentium.pdf
new file mode 100644
index 00000000000..77f41ad2894
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/gentium.pdf
Binary files differ
diff --git a/Master/texmf-dist/doc/fonts/gentium-tug/gentium.tex b/Master/texmf-dist/doc/fonts/gentium-tug/gentium.tex
new file mode 100644
index 00000000000..791e11c6dc8
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/gentium-tug/gentium.tex
@@ -0,0 +1,540 @@
+% !TEX TS-program = pdflatex
+% !TEX encoding = UTF-8 Unicode
+
+% This file is part of the Gentium package for TeX.
+% It is licensed under the Expat License, see doc//README for details.
+
+\documentclass[11pt, welsh, british]{article}
+\usepackage{babel}
+\usepackage[utf8x]{inputenc}
+\usepackage[T1]{fontenc}
+\usepackage{gentium}
+\renewcommand{\ttdefault}{lmvtt}
+\usepackage{fancyhdr,lastpage,fancyref}
+\usepackage{array,longtable,verbatim}
+\usepackage{booktabs}
+\usepackage{multirow}
+\usepackage{url}
+ \urlstyle{tt}
+\usepackage[breaklinks,colorlinks,
+ linkcolor=black,citecolor=black,urlcolor=black]
+ {hyperref}
+%\usepackage{microtype}
+\usepackage[a4paper,headheight=14pt,scale=0.8]{geometry}
+ % use 14pt for 11pt text, 15pt for 12pt text
+
+\title{Gentium for \TeX}
+\author{Mojca Miklavec \and Pavel Farář \and Thomas A. Schmitz}
+\newcommand*{\dyddiad}{\today}
+\newcommand*{\ofname}{of}
+\date{\dyddiad}
+\pagestyle{fancy}
+ \fancyhf[lh]{\itshape gentium}
+ \fancyhf[rh]{\itshape\dyddiad}
+ \fancyhf[ch]{}
+ \fancyhf[lf]{}
+ \fancyhf[rf]{}
+ \fancyhf[cf]{\itshape --- \thepage~\ofname~\pageref{LastPage} ---}
+
+\usepackage{textcomp}
+
+\def\ConTeXt{Con{\TeX}t}
+\def\ConTeXtMKII{Con{\TeX}t {\sc MkII}}
+\def\ConTeXtMKIV{Con{\TeX}t {\sc MkIV}}
+\def\XeTeX{Xe{\TeX}} % TODO: improve the first "e"--reversed and lowered
+\def\pdfTeX{pdf{\TeX}}
+\def\pdfLaTeX{pdf{\LaTeX}}
+\def\TeXLive{\TeX~Live}
+\def\MiKTeX{MiK\TeX}
+\def\MacTeX{Mac\TeX}
+
+\begin{document}
+\maketitle
+\thispagestyle{empty}
+\pdfinfo{%
+ /Creator (TeX)
+ /Producer (pdfTeX)
+ /Author (Pavel Farář, Mojca Miklavec, Clea F.\ Rees)
+ /Title (Gentium for TeX)
+ /Subject (TeX)
+ /Keywords (TeX,LaTeX,font,fonts,tex,latex,gentium,GentiumPlus,GentiumBasic,Gentium,SIL,sil)}
+\pdfcatalog{%
+ /URL ()
+ /PageMode /UseOutlines}
+ % other values: /UseNone, /UseOutlines, /UseThumbs, /FullScreen
+ %[openaction <actionspec>]
+% \pagestyle{empty}
+ % if you want this, you probably want to comment out \maketitle as well...?
+\setlength{\parindent}{0pt}
+\setlength{\parskip}{0.5em}
+
+
+\newcommand*{\sil}{\textsc{sil}}
+\newcommand*{\pkgname}[1]{\textsf{#1}}
+\newcommand*{\fname}[1]{\textsf{#1}}
+
+\begin{abstract}
+ \hspace*{-\parindent}This document outlines the
+ \TeX/\LaTeX/\ConTeXt\ support provided by this
+ package for the Gentium font collection released by \sil.
+\end{abstract}
+
+\tableofcontents
+
+
+\section{Introduction}
+
+This document explains how to use the \TeX/\LaTeX/\ConTeXt\ support in
+the present package for the Gentium font collection developed by \sil.
+This package includes fonts in PostScript Type~1 format converted from
+the original TrueType files released by \sil\ (using the FontForge
+routines found in this package). These Type~1 fonts use the name
+`Gentium' by permission of \sil\ to the \TeX\ Users Group. Therefore
+the name of this \TeX\ package, by request of \sil, is
+\pkgname{gentium-tug}. Its home page is \url{http://tug.org/gentium}.
+
+Further information about the fonts themselves can be found in the
+included documentation and at \url{http://scripts.sil.org/gentium}. The
+fonts are released under the \textsc{sil} Open Font License. For
+details, see \url{ofl.txt} and \url{ofl-faq.txt}. (In the event of
+releasing modified versions of the fonts, either TrueType or Type~1,
+it's required to use a name that doesn't include ``Gentium'', per the
+\textsc{ofl}.)
+
+This \TeX/\LaTeX/\ConTeXt\ support package consists of metrics, map
+files, style files, documentation, and so on. These files are released
+under the Expat license. The text for both licenses is included at the
+end of this document, and in files in the distribution.
+
+If you have the package installed and just want to know how to use
+Gentium in your \TeX\ documents, feel free to skip to
+section~\ref{sec:latex-package} (\LaTeX\ usage) or
+section~\ref{sec:context-package} (\ConTeXt\ usage).
+
+Please report any problems (contact info on the web page). If you can
+also send a fix, so much the better.
+
+
+\section{Gentium collection background}
+
+This package uses the original fonts GentiumPlus to make the regular and
+italic styles and GentiumBasic to make the bold and bold italic styles,
+and combines them into one \TeX-world family.
+
+GentiumPlus is a serif family designed to support a wide range of Latin,
+Greek and Cyrillic characters. It currently includes just the regular
+and italic style, as well as smallcaps.
+
+GentiumBasic has just the Latin characters and it even lacks some Latin
+characters found in GentiumPlus. Therefore, the bold and bold italic
+styles of this package support fewer languages than the regular and
+italic styles (e.g.\ Czech and Slovak are not fully
+supported). Moreover, GentiumBasic has no smallcaps and no kerning
+pairs. When and if \sil\ releases bold and bold italic GentiumPlus
+fonts, we will switch to those, of course.
+
+This package does not use the Berry fontname scheme, but longer names
+similar to those of Latin Modern, etc. One disadvantage of this choice
+is that you cannot use the additional font selection commands provided
+by the package \pkgname{nfssext-cfr}.
+
+
+\section{Installation}
+
+If you are using a reasonably recent \MiKTeX\ or \TeXLive\ or distro
+installation it should be enough to install the \pkgname{gentium-tug}
+package (if it's not already present).
+
+Otherwise, or if you want to install the font manually, you will in
+general need to perform these steps:
+\begin{enumerate}
+\item choose whether to install the font system-wide or in a personal
+ directory;
+\item move or copy the package files to the appropriate location;
+\item refresh the \TeX\ database;
+\item incorporate the included map file fragments for the different
+ engines.
+\end{enumerate}
+
+However, that's all that it make sense to say here. It's beyond the
+scope of this Gentium documentation to explain all the myriad ways in
+which \TeX-world map files can be installed and used; there are
+differences between \TeXLive\ and \MiKTeX, too.
+
+Instead, we refer you to an explanation of the system-wide installation,
+with information for both \MiKTeX\ and \TeXLive, at
+\url{http://tug.org/fonts/fontinstall.html}. A corresponding
+explanation for personal installation is at
+\url{http://tug.org/fonts/fontinstall-personal.html}.
+
+Those pages describe using \path{testfont.tex} for a basic test of the
+font; a tfm file name to use with that is \url{ec-gentiumplus-regular}.
+
+To further test your installation and that the package works on your
+system, run \LaTeX\ on this \path{gentium.tex} source file. (You'll
+need some commonly-available \LaTeX\ packages too, or comment them at.)
+The console output and/or log should tell you whether any fonts were not
+found. You can also compare your output with the original
+\path{gentium.pdf}.
+
+
+\section{Gentium \TeX\ support packages}\label{sec:support}
+
+In short, for \LaTeX\ it suffices to include \verb|\usepackage{gentium}|
+in your document preamble, and for \ConTeXtMKIV,
+\verb|\setupbodyfont[gentium]|. Details follow.
+
+The only prerequisite is that the \LaTeX\ package (\path{gentium.sty})
+requires \pkgname{xkeyval}, which you almost certainly already have.
+
+
+\subsection{Encodings}\label{sec:encs}
+
+The package supports not only the most common Latin encodings such as
+\textsc{ot1}, TeXnANSI/\textsc{ly1}, Cork/\textsc{ec}/\textsc{t1} and
+Text Companion/\textsc{ts1} encodings, but also (in regular and italic)
+other Latin, Greek and Cyrillic encodings. Most characters in the text
+encodings and some of those in the Text Companion encoding are
+available, including the~\texteuro. You can see the available encodings
+in table~\ref{encodings}. The Greek encoding LGR is supported only in
+\LaTeX, AGR only in \ConTeXt.
+
+\begin{table}[h]
+\centering
+ \begin{tabular}{lll}
+ \toprule
+ script & available encodings & styles \\
+ \midrule
+ Latin & OT1, T1, LY1, L7x, QX, T5, TS1 & regular, italic, bold,
+ bold italic \\
+ Cyrillic & T2A, T2B, T2C, X2 & regular, italic\\
+ Greek & LGR (\LaTeX), AGR (\ConTeXt) & regular, italic \\
+ \bottomrule
+ \end{tabular}
+ \caption{Available encodings in \pkgname{gentium-tug}.}
+ \label{encodings}
+\end{table}
+
+The regular and italic styles support all these Latin, Greek and Cyrillic
+encodings. They support also small caps for the Latin and Cyrillic encodings,
+but there are no small caps for Greek.
+
+The bold and bold italic styles support only the Latin encodings and they
+have no small caps.
+
+Cork/T1 encoding lacks visible space, cwm (compound work mark),
+SS and the character for composing permille sign.
+
+Missing characters in bold styles for Latin encodings:
+
+T1: Aogonek / aogonek, Eogonek / eogonek, Lcaron / lcaron,
+ Scedilla / scedilla, uni021A (Tcommaaccent) / uni021B (tcommaaccent),
+ dcaron, tcaron
+
+L7x: Rcommaaccent, Gcommaaccent, Kcommaaccent, Lcommaaccent, Ncommaaccent,
+ Aogonek, Eogonek, Iogonek, Uogonek
+
+QX: Aogonek, Eogonek, Iogonek, uni021A (Tcommaaccent)
+
+
+\subsection{\LaTeX}
+\label{sec:latex-package}
+
+To use Gentium fonts in a \LaTeX\ document, add
+\verb|\usepackage{gentium}| to your document preamble. This will set
+the default serif/roman family to \fname{gentium}.
+
+If you want to use Gentium together with another font (sans or
+typewriter) with a different x-height, you should consider using the
+option \verb|scaled|. This scales Gentium font and if you choose the
+right scaling factor, you will get the same x-height of both fonts.
+Here is an example of this option:
+\begin{verbatim}
+\usepackage[scaled=0.9]{gentium}
+\end{verbatim}
+
+
+\subsection{\ConTeXt}
+\label{sec:context-package}
+
+In \ConTeXtMKIV, to switch to the Gentium typeface you only need:
+\begin{verbatim}
+\setupbodyfont[gentium]
+\end{verbatim}
+
+In \ConTeXtMKII, before doing that you need either (for \pdfTeX):
+\begin{verbatim}
+\usetypescriptfile[type-gentium]
+\usetypescript[gentium][ec] % or whatever encoding
+\end{verbatim}
+or (for \XeTeX):
+\begin{verbatim}
+\usetypescriptfile[type-gentium]
+\usetypescript[gentium]
+\end{verbatim}
+
+
+\subsection{Changes in the Type~1 fonts vs.\ the TrueType originals}
+
+The shapes of all characters in the Type~1 fonts are the same as in the
+original TrueType fonts, except for the unavoidable changes are induced
+by the format conversion (that is, the spline representations are
+necessarily different).
+
+However, a few small changes---hopefully improvements---were made to the
+metrics of the GentiumPlus family (that is, regular and italic; bold and
+bold italic are untouched). The Type~1 fonts are used to generate the
+\TeX\ font metric files (tfm), so these changes propagate to the 8-bit
+engines like \pdfTeX.
+
+The first change concerns Greek. 8-bit Greek encodings (LGR and AGR) do
+not use precomposed accented capital letters. These letters are composed
+as a sequence of two glyphs: accent + capital letter. The problem is
+that this sequence does not look like the precomposed letter---there is
+often big space between the accent and the letter. Therefore, there are
+some extra kerning pairs between accents and capital Greek
+letters. These kerning pairs are created automatically (the script is
+included in the sources) and the goal is to have the same relative
+position between the accent and the letter as in the precomposed
+letter. Thanks to these extra kerning pairs you should get better
+results for 8-bit engines. These changes are irrelevant for Unicode
+engines---they use the precomposed letters.
+
+The second change is in the letters dcaron (ď) and lcaron
+(ľ) that are used in the Czech and Slovak languages. (There was
+no need to change tcaron (ť) and Lcaron (Ľ) with the same
+accent.) There is no change of their shapes, and their advance widths
+are also untouched---the change is to add several kerning pairs with
+quite big negative values. Without these changes there was often a large
+space between dcaron or lcaron and the following letter, so the changes
+make the words containing these letters much more compact. You get these
+changes automatically if you use 8-bit engines. If you use Unicode
+engines with the original TrueType fonts, you get the original
+metrics. However, you can tell the Unicode engines to use the Type~1
+fonts (which append \verb|PS| to the family name) like this:
+\begin{verbatim}
+\usepackage{fontspec}
+\setmainfont{GentiumPlusPS}
+\end{verbatim}
+Then you get the additional kern pairs for dcaron and lcaron. The
+unfortunately disadvantage is that you cannot use small caps.
+
+The last (similar) change is that additional kerning pairs were added to
+the Type~1 fonts for accented Latin letters and small caps. The original
+TrueType fonts have no such kerning pairs. As with the Czech/Slovak
+changes, you get these changes automatically if you use 8-bit
+engines. If you use Unicode engines with the original TrueType fonts,
+you get the original metrics, but you can override as above (but since
+you cannot use small caps with that method, the kerning pairs for small
+caps become irrelevant).
+
+
+\section{Known bugs}
+
+There are problems in older versions of \pdfTeX\ with small caps when
+using TrueType fonts. Especially the Latin encoding \textsc{t5} and all
+Cyrillic encodings are unusable. You can use the Type~1 version of the
+fonts or at least \pdfTeX\ version 1.40.13 to avoid these problems.
+
+The Gentium fonts are a work in progress and as such they still miss
+some features like kerning pairs for some letters. Currently, there are
+no kerning pairs in the GentiumBasic family at all and the GentiumPlus
+family has kerning pairs just for Latin letters without accents and for
+Greek letters; there are no kerning pairs for small caps, accented Latin
+letters or Cyrillic letters. The Type~1 fonts in this package have some
+additional kerning pairs for accented Latin letters and for small
+caps. Kerning pairs for Cyrillic are under consideration.
+
+
+\section{License}
+
+The fonts in this page, both the \sil\ originals and the derived Type~1
+versions, are released under \textsc{ofl}. The \TeX\ support files
+are licensed under the Expat License. Here are the full license texts.
+
+
+\subsection{SIL Open Font License}
+
+Copyright (c) 2003-2011 SIL International (http://www.sil.org/),
+with Reserved Font Names ``Gentium'' and ``SIL''.
+
+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
+
+
+% TODO: Try to have the similar look as the text version
+%-----------------------------------------------------------
+SIL OPEN FONT LICENSE Version 1.1 --- 26 February 2007
+%-----------------------------------------------------------
+
+
+PREAMBLE
+
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded,
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+
+DEFINITIONS
+
+``Font Software'' refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+``Reserved Font Name'' refers to any names specified as such after the
+copyright statement(s).
+
+``Original Version'' refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+``Modified Version'' refers to any derivative made by adding to, deleting,
+or substituting---in part or in whole---any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+``Author'' refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+
+PERMISSION \& CONDITIONS
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+
+TERMINATION
+
+This license becomes null and void if any of the above conditions are
+not met.
+
+
+DISCLAIMER
+
+\textsc{The font software is provided ``as is'', without warranty of any kind,
+express or implied, including but not limited to any warranties of
+merchantability, fitness for a particular purpose and noninfringement
+of copyright, patent, trademark, or other right. In no event shall the
+copyright holder be liable for any claim, damages or other liability,
+including any general, special, indirect, incidental, or consequential
+damages, whether in an action of contract, tort or otherwise, arising
+from, out of the use or inability to use the font software or from
+other dealings in the font software.}
+
+
+\subsection{Expat License}
+
+Copyright (c) 2008-2013 TeX Users Group
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+``Software''), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be included
+in all copies or substantial portions of the Software.
+
+\textsc{The software is provided ``as is'', without warranty of any kind,
+express or implied, including but not limited to the warranties of
+merchantability, fitness for a particular purpose and noninfringement.
+In no event shall the authors or copyright holders be liable for any
+claim, damages or other liability, whether in an action of contract,
+tort or otherwise, arising from, out of or in connection with the
+software or the use or other dealings in the software.}
+
+
+
+% OT1 is the same for regular and italic style (like TeX Gyre, unlike
+% Computer Modern)---this might go to the bugs section.
+
+% Cyrillic encodings use some letters with tail instead of with descender.
+
+
+% TODO
+
+% Show the available encodings in a better way (probably something
+% similar to README), probably use small caps. Look at Clea's tables
+% if they are better than what I wrote.
+
+% Improve the LaTeX logo in Gentium (not so much related to this
+% documentation).
+
+% Search for gentiumplus and vgx---the latter shouldn't be present.
+
+% Scale the monospaced font to match the x-height.
+
+% Change the license and other information in the header.
+
+
+% NOTES TO CLEA
+
+% Current (unlike Clea's) LY1 doesn't contain Wcircumflex and others.
+% Look at it!
+% \textsc{ly1} is
+% necessary for access to Wcircumflex (Ŵ), wcircumflex (ŵ),
+% Ycircumflex (Ŷ) and ycircumflex (ŷ) as pre-composed
+% glyphs.
+
+% Look what's different from Clea's package.
+
+
+% Some Clea's texts that might be used:
+
+% The final option controls whether Latin Modern is used for sans and
+% typewriter text. Because Computer Modern does not support the
+% TeXnANSI/\textsc{ly1} encoding, you will likely get strange results
+% unless you redefine \path{\sfdefault} and \path{\ttdefault}. Latin
+% Modern is used because it is close to the default Computer Modern fonts
+% and is widely available. If you would prefer that the package not
+% redefine the default sans and typewriter families, use \verb|lm=false|
+% when loading \pkgname{gentiumplus}. To explicitly request the default
+% behaviour, which does redefine these families, use \verb|lm| or
+% \verb|lm=true|.
+
+% Loading \path{gentium.sty} does not affect the setup for
+% mathematics.
+
+\end{document}