lexend (17nov19)

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

4 files changed, 765 insertions, 0 deletions

diff --git a/Master/texmf-dist/doc/fonts/lexend/LICENSE b/Master/texmf-dist/doc/fonts/lexend/LICENSE
new file mode 100644
index 00000000000..22443139013
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/lexend/LICENSE
@@ -0,0 +1,416 @@
+The LaTeX Project Public License
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
+
+LPPL Version 1.3c  2008-05-04
+
+Copyright 1999 2002-2008 LaTeX3 Project
+    Everyone is allowed to distribute verbatim copies of this
+    license document, but modification of it is not allowed.
+
+
+PREAMBLE
+========
+
+The LaTeX Project Public License (LPPL) is the primary license under
+which the LaTeX kernel and the base LaTeX packages are distributed.
+
+You may use this license for any work of which you hold the copyright
+and which you wish to distribute.  This license may be particularly
+suitable if your work is TeX-related (such as a LaTeX package), but 
+it is written in such a way that you can use it even if your work is 
+unrelated to TeX.
+
+The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
+below, gives instructions, examples, and recommendations for authors
+who are considering distributing their works under this license.
+
+This license gives conditions under which a work may be distributed
+and modified, as well as conditions under which modified versions of
+that work may be distributed.
+
+We, the LaTeX3 Project, believe that the conditions below give you
+the freedom to make and distribute modified versions of your work
+that conform with whatever technical specifications you wish while
+maintaining the availability, integrity, and reliability of
+that work.  If you do not see how to achieve your goal while
+meeting these conditions, then read the document `cfgguide.tex'
+and `modguide.tex' in the base LaTeX distribution for suggestions.
+
+
+DEFINITIONS
+===========
+
+In this license document the following terms are used:
+
+   `Work'
+    Any work being distributed under this License.
+    
+   `Derived Work'
+    Any work that under any applicable law is derived from the Work.
+
+   `Modification' 
+    Any procedure that produces a Derived Work under any applicable
+    law -- for example, the production of a file containing an
+    original file associated with the Work or a significant portion of
+    such a file, either verbatim or with modifications and/or
+    translated into another language.
+
+   `Modify'
+    To apply any procedure that produces a Derived Work under any
+    applicable law.
+    
+   `Distribution'
+    Making copies of the Work available from one person to another, in
+    whole or in part.  Distribution includes (but is not limited to)
+    making any electronic components of the Work accessible by
+    file transfer protocols such as FTP or HTTP or by shared file
+    systems such as Sun's Network File System (NFS).
+
+   `Compiled Work'
+    A version of the Work that has been processed into a form where it
+    is directly usable on a computer system.  This processing may
+    include using installation facilities provided by the Work,
+    transformations of the Work, copying of components of the Work, or
+    other activities.  Note that modification of any installation
+    facilities provided by the Work constitutes modification of the Work.
+
+   `Current Maintainer'
+    A person or persons nominated as such within the Work.  If there is
+    no such explicit nomination then it is the `Copyright Holder' under
+    any applicable law.
+
+   `Base Interpreter' 
+    A program or process that is normally needed for running or
+    interpreting a part or the whole of the Work.    
+
+    A Base Interpreter may depend on external components but these
+    are not considered part of the Base Interpreter provided that each
+    external component clearly identifies itself whenever it is used
+    interactively.  Unless explicitly specified when applying the
+    license to the Work, the only applicable Base Interpreter is a
+    `LaTeX-Format' or in the case of files belonging to the 
+    `LaTeX-format' a program implementing the `TeX language'.
+
+
+
+CONDITIONS ON DISTRIBUTION AND MODIFICATION
+===========================================
+
+1.  Activities other than distribution and/or modification of the Work
+are not covered by this license; they are outside its scope.  In
+particular, the act of running the Work is not restricted and no
+requirements are made concerning any offers of support for the Work.
+
+2.  You may distribute a complete, unmodified copy of the Work as you
+received it.  Distribution of only part of the Work is considered
+modification of the Work, and no right to distribute such a Derived
+Work may be assumed under the terms of this clause.
+
+3.  You may distribute a Compiled Work that has been generated from a
+complete, unmodified copy of the Work as distributed under Clause 2
+above, as long as that Compiled Work is distributed in such a way that
+the recipients may install the Compiled Work on their system exactly
+as it would have been installed if they generated a Compiled Work
+directly from the Work.
+
+4.  If you are the Current Maintainer of the Work, you may, without
+restriction, modify the Work, thus creating a Derived Work.  You may
+also distribute the Derived Work without restriction, including
+Compiled Works generated from the Derived Work.  Derived Works
+distributed in this manner by the Current Maintainer are considered to
+be updated versions of the Work.
+
+5.  If you are not the Current Maintainer of the Work, you may modify
+your copy of the Work, thus creating a Derived Work based on the Work,
+and compile this Derived Work, thus creating a Compiled Work based on
+the Derived Work.
+
+6.  If you are not the Current Maintainer of the Work, you may
+distribute a Derived Work provided the following conditions are met
+for every component of the Work unless that component clearly states
+in the copyright notice that it is exempt from that condition.  Only
+the Current Maintainer is allowed to add such statements of exemption 
+to a component of the Work. 
+
+  a. If a component of this Derived Work can be a direct replacement
+     for a component of the Work when that component is used with the
+     Base Interpreter, then, wherever this component of the Work
+     identifies itself to the user when used interactively with that
+     Base Interpreter, the replacement component of this Derived Work
+     clearly and unambiguously identifies itself as a modified version
+     of this component to the user when used interactively with that
+     Base Interpreter.
+     
+  b. Every component of the Derived Work contains prominent notices
+     detailing the nature of the changes to that component, or a
+     prominent reference to another file that is distributed as part
+     of the Derived Work and that contains a complete and accurate log
+     of the changes.
+  
+  c. No information in the Derived Work implies that any persons,
+     including (but not limited to) the authors of the original version
+     of the Work, provide any support, including (but not limited to)
+     the reporting and handling of errors, to recipients of the
+     Derived Work unless those persons have stated explicitly that
+     they do provide such support for the Derived Work.
+
+  d. You distribute at least one of the following with the Derived Work:
+
+       1. A complete, unmodified copy of the Work; 
+          if your distribution of a modified component is made by
+          offering access to copy the modified component from a
+          designated place, then offering equivalent access to copy
+          the Work from the same or some similar place meets this
+          condition, even though third parties are not compelled to
+          copy the Work along with the modified component;
+
+       2. Information that is sufficient to obtain a complete,
+          unmodified copy of the Work.
+
+7.  If you are not the Current Maintainer of the Work, you may
+distribute a Compiled Work generated from a Derived Work, as long as
+the Derived Work is distributed to all recipients of the Compiled
+Work, and as long as the conditions of Clause 6, above, are met with
+regard to the Derived Work.
+
+8.  The conditions above are not intended to prohibit, and hence do not
+apply to, the modification, by any method, of any component so that it
+becomes identical to an updated version of that component of the Work as
+it is distributed by the Current Maintainer under Clause 4, above.
+
+9.  Distribution of the Work or any Derived Work in an alternative
+format, where the Work or that Derived Work (in whole or in part) is
+then produced by applying some process to that format, does not relax or
+nullify any sections of this license as they pertain to the results of
+applying that process.
+     
+10. a. A Derived Work may be distributed under a different license
+       provided that license itself honors the conditions listed in
+       Clause 6 above, in regard to the Work, though it does not have
+       to honor the rest of the conditions in this license.
+      
+    b. If a Derived Work is distributed under a different license, that
+       Derived Work must provide sufficient documentation as part of
+       itself to allow each recipient of that Derived Work to honor the 
+       restrictions in Clause 6 above, concerning changes from the Work.
+
+11. This license places no restrictions on works that are unrelated to
+the Work, nor does this license place any restrictions on aggregating
+such works with the Work by any means.
+
+12.  Nothing in this license is intended to, or may be used to, prevent
+complete compliance by all parties with all applicable laws.
+
+
+NO WARRANTY
+===========
+
+There is no warranty for the Work.  Except when otherwise stated in
+writing, the Copyright Holder provides the Work `as is', without
+warranty of any kind, either expressed or implied, including, but not
+limited to, the implied warranties of merchantability and fitness for a
+particular purpose.  The entire risk as to the quality and performance
+of the Work is with you.  Should the Work prove defective, you assume
+the cost of all necessary servicing, repair, or correction.
+
+In no event unless required by applicable law or agreed to in writing
+will The Copyright Holder, or any author named in the components of the
+Work, or any other party who may distribute and/or modify the Work as
+permitted above, be liable to you for damages, including any general,
+special, incidental or consequential damages arising out of any use of
+the Work or out of inability to use the Work (including, but not limited
+to, loss of data, data being rendered inaccurate, or losses sustained by
+anyone as a result of any failure of the Work to operate with any other
+programs), even if the Copyright Holder or said author or said other
+party has been advised of the possibility of such damages.
+
+
+MAINTENANCE OF THE WORK
+=======================
+
+The Work has the status `author-maintained' if the Copyright Holder
+explicitly and prominently states near the primary copyright notice in
+the Work that the Work can only be maintained by the Copyright Holder
+or simply that it is `author-maintained'.
+
+The Work has the status `maintained' if there is a Current Maintainer
+who has indicated in the Work that they are willing to receive error
+reports for the Work (for example, by supplying a valid e-mail
+address). It is not required for the Current Maintainer to acknowledge
+or act upon these error reports.
+
+The Work changes from status `maintained' to `unmaintained' if there
+is no Current Maintainer, or the person stated to be Current
+Maintainer of the work cannot be reached through the indicated means
+of communication for a period of six months, and there are no other
+significant signs of active maintenance.
+
+You can become the Current Maintainer of the Work by agreement with
+any existing Current Maintainer to take over this role.
+
+If the Work is unmaintained, you can become the Current Maintainer of
+the Work through the following steps:
+
+ 1.  Make a reasonable attempt to trace the Current Maintainer (and
+     the Copyright Holder, if the two differ) through the means of
+     an Internet or similar search.
+
+ 2.  If this search is successful, then enquire whether the Work
+     is still maintained.
+
+  a. If it is being maintained, then ask the Current Maintainer
+     to update their communication data within one month.
+     
+  b. If the search is unsuccessful or no action to resume active
+     maintenance is taken by the Current Maintainer, then announce
+     within the pertinent community your intention to take over
+     maintenance.  (If the Work is a LaTeX work, this could be
+     done, for example, by posting to comp.text.tex.)
+
+ 3a. If the Current Maintainer is reachable and agrees to pass
+     maintenance of the Work to you, then this takes effect
+     immediately upon announcement.
+     
+  b. If the Current Maintainer is not reachable and the Copyright
+     Holder agrees that maintenance of the Work be passed to you,
+     then this takes effect immediately upon announcement.  
+    
+ 4.  If you make an `intention announcement' as described in 2b. above
+     and after three months your intention is challenged neither by
+     the Current Maintainer nor by the Copyright Holder nor by other
+     people, then you may arrange for the Work to be changed so as
+     to name you as the (new) Current Maintainer.
+     
+ 5.  If the previously unreachable Current Maintainer becomes
+     reachable once more within three months of a change completed
+     under the terms of 3b) or 4), then that Current Maintainer must
+     become or remain the Current Maintainer upon request provided
+     they then update their communication data within one month.
+
+A change in the Current Maintainer does not, of itself, alter the fact
+that the Work is distributed under the LPPL license.
+
+If you become the Current Maintainer of the Work, you should
+immediately provide, within the Work, a prominent and unambiguous
+statement of your status as Current Maintainer.  You should also
+announce your new status to the same pertinent community as
+in 2b) above.
+
+
+WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE
+======================================================
+
+This section contains important instructions, examples, and
+recommendations for authors who are considering distributing their
+works under this license.  These authors are addressed as `you' in
+this section.
+
+Choosing This License or Another License
+----------------------------------------
+
+If for any part of your work you want or need to use *distribution*
+conditions that differ significantly from those in this license, then
+do not refer to this license anywhere in your work but, instead,
+distribute your work under a different license.  You may use the text
+of this license as a model for your own license, but your license
+should not refer to the LPPL or otherwise give the impression that
+your work is distributed under the LPPL.
+
+The document `modguide.tex' in the base LaTeX distribution explains
+the motivation behind the conditions of this license.  It explains,
+for example, why distributing LaTeX under the GNU General Public
+License (GPL) was considered inappropriate.  Even if your work is
+unrelated to LaTeX, the discussion in `modguide.tex' may still be
+relevant, and authors intending to distribute their works under any
+license are encouraged to read it.
+
+A Recommendation on Modification Without Distribution
+-----------------------------------------------------
+
+It is wise never to modify a component of the Work, even for your own
+personal use, without also meeting the above conditions for
+distributing the modified component.  While you might intend that such
+modifications will never be distributed, often this will happen by
+accident -- you may forget that you have modified that component; or
+it may not occur to you when allowing others to access the modified
+version that you are thus distributing it and violating the conditions
+of this license in ways that could have legal implications and, worse,
+cause problems for the community.  It is therefore usually in your
+best interest to keep your copy of the Work identical with the public
+one.  Many works provide ways to control the behavior of that work
+without altering any of its licensed components.
+
+How to Use This License
+-----------------------
+
+To use this license, place in each of the components of your work both
+an explicit copyright notice including your name and the year the work
+was authored and/or last substantially modified.  Include also a
+statement that the distribution and/or modification of that
+component is constrained by the conditions in this license.
+
+Here is an example of such a notice and statement:
+
+  %% pig.dtx
+  %% Copyright 2005 M. Y. Name
+  %
+  % This work may be distributed and/or modified under the
+  % conditions of the LaTeX Project Public License, either version 1.3
+  % of this license or (at your option) any later version.
+  % The latest version of this license is in
+  %   http://www.latex-project.org/lppl.txt
+  % and version 1.3 or later is part of all distributions of LaTeX
+  % version 2005/12/01 or later.
+  %
+  % This work has the LPPL maintenance status `maintained'.
+  % 
+  % The Current Maintainer of this work is M. Y. Name.
+  %
+  % This work consists of the files pig.dtx and pig.ins
+  % and the derived file pig.sty.
+
+Given such a notice and statement in a file, the conditions
+given in this license document would apply, with the `Work' referring
+to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being
+generated from `pig.dtx' using `pig.ins'), the `Base Interpreter'
+referring to any `LaTeX-Format', and both `Copyright Holder' and
+`Current Maintainer' referring to the person `M. Y. Name'.
+
+If you do not want the Maintenance section of LPPL to apply to your
+Work, change `maintained' above into `author-maintained'.  
+However, we recommend that you use `maintained', as the Maintenance
+section was added in order to ensure that your Work remains useful to
+the community even when you can no longer maintain and support it
+yourself.
+
+Derived Works That Are Not Replacements
+---------------------------------------
+
+Several clauses of the LPPL specify means to provide reliability and
+stability for the user community. They therefore concern themselves
+with the case that a Derived Work is intended to be used as a
+(compatible or incompatible) replacement of the original Work. If
+this is not the case (e.g., if a few lines of code are reused for a
+completely different task), then clauses 6b and 6d shall not apply.
+
+
+Important Recommendations
+-------------------------
+
+ Defining What Constitutes the Work
+
+   The LPPL requires that distributions of the Work contain all the
+   files of the Work.  It is therefore important that you provide a
+   way for the licensee to determine which files constitute the Work.
+   This could, for example, be achieved by explicitly listing all the
+   files of the Work near the copyright notice of each file or by
+   using a line such as:
+
+    % This work consists of all files listed in manifest.txt.
+   
+   in that place.  In the absence of an unequivocal list it might be
+   impossible for the licensee to determine what is considered by you
+   to comprise the Work and, in such a case, the licensee would be
+   entitled to make reasonable conjectures as to which files comprise
+   the Work.
+
diff --git a/Master/texmf-dist/doc/fonts/lexend/README.md b/Master/texmf-dist/doc/fonts/lexend/README.md
new file mode 100644
index 00000000000..58f9e049f9c
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/lexend/README.md
@@ -0,0 +1,92 @@
+# latex-lexend
+
+The [Lexend fonts](https://www.lexend.com/) for XeLaTeX and LuaLaTeX through fontspec
+
+<!-- TOC depthFrom:2 depthTo:6 withLinks:1 updateOnSave:1 orderedList:0 -->
+
+- [Dowloading](#dowloading)
+- [Working with the Source Code](#working-with-the-source-code)
+	- [Cloning](#cloning)
+	- [Building](#building)
+		- [Prerequisites](#prerequisites)
+		- [Making the Package](#making-the-package)
+	- [Developing](#developing)
+- [License](#license)
+- [Random Quote](#random-quote)
+
+<!-- /TOC -->
+
+## Dowloading
+
+You can find this package on[CTAN](https://ctan.org/): https://ctan.org/pkg/lexend
+
+## Working with the Source Code
+
+### Cloning
+
+To clone this repo, be sure to clone it recursively:
+
+```sh
+git clone --recursive https://github.com/BrainStone/latex-lexend.git
+```
+
+For older git versions or if you forgot to clone it recursively, do it like this:
+
+```sh
+git clone https://github.com/BrainStone/latex-lexend.git
+cd latex-lexend
+git submodule update --init --recursive
+```
+
+### Building
+
+#### Prerequisites
+
+Before you try to build this package make sure you have the following installed:
+
+- `make`
+- `pandoc`
+- A working TeX environment with a working `latexmk` and `lualatex` command.
+- `git` (Yes, `git` is used to determine the version number automatically. So if you want it build properly, you need it, if you don't care about that, it's
+  not needed)
+
+#### Making the Package
+
+Now if you just want to build the package, run:
+
+```sh
+make
+```
+
+Removing the build directory after creating the package can be done with
+
+```sh
+make clean
+```
+
+### Developing
+
+If you wish to work on this package, be sure to clone it as described and also to run this command to set everything up:
+
+```sh
+make setupWorkspace
+```
+
+## License
+
+The licensing of this project is a bit uncommon, so let me explain:
+
+The source repository, the one you find under https://github.com/BrainStone/latex-lexend, however is licensed under the
+[GNU General Public License v3.0](https://www.gnu.org/licenses/gpl-3.0.html).
+
+The final package, the one you find on [CTAN](https://ctan.org/), is licensed under [The LaTeX Project Public License 1.3c](https://ctan.org/license/lppl1.3c).
+So use it like you would use most other packages on [CTAN](https://ctan.org/).
+
+Lastly, the font collection itself is licensed under the [SIL Open Font License 1.1](https://opensource.org/licenses/OFL-1.1). You can find the license file
+under https://github.com/ThomasJockin/lexend/blob/master/OFL.txt.
+
+## Random Quote
+
+> Hardware: The parts of a computer system that can be kicked.
+>
+> <cite>Jeff Pesis</cite>
diff --git a/Master/texmf-dist/doc/fonts/lexend/lexend.pdf b/Master/texmf-dist/doc/fonts/lexend/lexend.pdf
new file mode 100644
index 00000000000..73f622104d2
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/lexend/lexend.pdf
diff --git a/Master/texmf-dist/doc/fonts/lexend/lexend.tex b/Master/texmf-dist/doc/fonts/lexend/lexend.tex
new file mode 100644
index 00000000000..8f78d058a07
--- /dev/null
+++ b/Master/texmf-dist/doc/fonts/lexend/lexend.tex
@@ -0,0 +1,257 @@
+\documentclass[oneside,a4paper]{l3doc}
+
+% Packages
+\usepackage{lexend}
+
+\usepackage[english]{babel}
+\usepackage{blindtext}
+\usepackage{hologo}
+\usepackage{listings}
+\usepackage{pgffor}
+\usepackage{soul}
+\usepackage{xcolor}
+
+% Settings
+\setmonofont{DejaVu Sans Mono}
+
+\hypersetup{
+	hidelinks,
+	bookmarksnumbered,
+	bookmarksopen,
+	bookmarksdepth=3,
+	colorlinks=true,
+	allcolors=blue,
+	unicode
+}
+
+\urlstyle{rm}
+
+\definecolor{lightgray}{gray}{0.95}
+
+\lstset{breaklines=true,backgroundcolor=\color{lightgray},basicstyle=\ttfamily,frame=single,numbers=left,numberstyle=\ttfamily,aboveskip=\baselineskip}
+
+% Additional commands
+\DeclareRobustCommand{\code}[1]{{\sethlcolor{lightgray}\texttt{\hl{#1}}}}
+\soulregister{\code}{1}
+\makeatletter
+\pdfstringdefDisableCommands{\let\code\@firstofone}
+\makeatother
+
+\providecommand{\tightlist}{%
+  \setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}
+
+\newcommand*{\fullref}[1]{\hyperref[{#1}]{\autoref*{#1} \nameref*{#1} (Page \pageref*{#1})}}
+
+% Document start
+\begin{document}
+
+\title{
+	The \textsf{lexend} package\\
+	\large{The \href{https://www.lexend.com/}{\textsf{Lexend} fonts} for \hologo{XeLaTeX} and
+	\hologo{LuaLaTeX} through \textsf{fontspec}}
+}
+\author{
+	Yannick Schinko\\
+	\texorpdfstring{\url{https://github.com/BrainStone/latex-lexend}}{}
+}
+\date{
+	\today\\
+	v0.1.1.51
+}
+
+\pagenumbering{roman}
+\maketitle
+
+\bigskip
+
+\begin{abstract}
+The purpose of this package is pretty straight forward:\\
+The Lexend font collection has been designed by Dr. Bonnie Shaver-Troup and Thomas Jockin to make
+reading easier for everyone.\\
+Now my goal is it to bring this wonderful collection to world of \hologo{LaTeX}.
+\end{abstract}
+
+\bigskip
+\tableofcontents
+\newpage
+
+\pagenumbering{arabic}
+
+\section{Changelog}
+
+\subsection*{Version 0.1.1}\label{version-0.1.1}
+
+* Fixed detecting tags as branches that should not be added to the version.
+
+\subsection*{Version 0.1.0}\label{version-0.1.0}
+
++ Created the lexend package.\\
++ Created the lexend(.sty) style.\\
++ Added build system.\\
++ Added package docs (including font samples).\\
++ Added acknowledgements.
+
+\section{Acknowledgements}
+
+I would like to take the time to thank everyone that helped me along my journey of creating this
+package. It would not have been possible without every single one of you.
+
+Special thanks to David Carlisle, Ulrike Fischer and Phelype Oleinik who helped me tremendously and
+continuously in the \hologo{LaTeX} Stack Exchange chat. I really can't put it in words how much your
+continued contributions and willingness to help helped me during the creation of this package.
+
+Special thanks to Dr. Bonnie Shaver-Troup and Thomas Jockin for creating these fonts and allowing
+people to have an easier time reading.
+
+Consider this contribution to the great \hologo{LaTeX} community as my thank you to you all.
+
+\section{Package Loading and Options}
+
+\subsection{Loading behavior}
+
+First of all this package depends on the \textsf{fontspec} package and therefore requires
+\hologo{XeLaTeX} and \hologo{LuaLaTeX}. So when you load this package the \textsf{fontspec} will
+also be loaded.
+
+When this package is loaded it sets the main font to \textsf{LexendDeca} and the sans font to
+\textsf{LexendGiga} using \textsf{fontspec}'s \code{\textbackslash{}setmainfont} and
+\code{\textbackslash{}setsansfont} commands.\footnote{See \fullref{subsec:package-options}}
+
+If you do wish to change the default fonts, just override the set fonts yourself with the same
+commands.
+
+\subsection{Package Options}\label{subsec:package-options}
+
+\textit{None at the moment}\footnote{See \fullref{subsec:future-features}}
+
+\section{Features}
+
+There aren't many features to talk about yet\footnote{See \fullref{subsec:future-features}}, but it
+certainly doesn't hurt documenting them.
+
+\subsection{Commands}
+
+\begin{function}{
+	\LexendDeca,
+	\LexendExa,
+	\LexendGiga,
+	\LexendMega,
+	\LexendPeta,
+	\LexendTera,
+	\LexendZetta
+}
+This collection of commands allows you to use any of the Lexend fonts ad-hoc.\\
+The usage is identical to any font modification commands (like \code{\textbackslash{}textit} for
+example.)
+
+It is equivelent to using the \code{\textbackslash{}fontspec} command with the corresponding font
+variant name as the parameter to the \code{\textbackslash{}fontspec} command.
+
+Using it looks as follows:
+
+\begin{lstlisting}[language={[LaTeX]TeX},caption={\code{\textbackslash{}LexendPeta Example}}]
+\LexendPeta{
+	Text here.
+}
+\end{lstlisting}
+
+\LexendPeta{
+	Text here.
+}
+\end{function}
+
+\begin{function}{\LexendVariants}
+This command is just a list containing all variants of the Lexend font collection.\\
+Mainly useful if you want to iterate over all font variants.
+
+\bigskip
+Using it as is will yield this result:
+
+\bigskip
+\LexendVariants
+\end{function}
+
+\subsection{.fontspec Files}
+
+Every Lexend font has its own \code{.fontspec} file. Though they are all identical (excluding the
+actual name) and look like this (\code{<FONTNAME>} will be replaced with the font's name of course):
+
+\lstinputlisting[language={[LaTeX]TeX},caption={template.fontspec}]{template.fontspec}
+
+\subsubsection{Expanding the Default Fontspecs}
+
+If you want to keep the default font settings but would like to add onto them, that's really easy:\\
+Use the \code{\textbackslash{}defaultfontfeatures+} command of \textsf{fontspec}.
+
+\bigskip
+
+For example if you would like to set the default color for every time you use the font
+\textsf{LexendPeta}, all you have to do is this:
+
+\begin{lstlisting}[language={[LaTeX]TeX}]
+\defaultfontfeatures+[LexendPeta]{
+	Color=888888
+}
+\end{lstlisting}
+
+Since this is handled by the \textsf{fontspec} package, please refer to their documentation at
+\url{https://ctan.org/pkg/fontspec}.
+
+\subsection{Future Features}\label{subsec:future-features}
+
+This package is still very young and also fairly incomplete. There's a list of things I'd like to
+add over time. Ordered by how soon I wish to implement them myself.
+
+\begin{itemize}
+\item Package option to turn off setting the main and sans font\tightlist
+\item Support for the continuous spacing font variant of Lexend\tightlist
+\item Support for other \hologo{LaTeX} engines\\
+	That's something I definately need help with. So feel free to reach out to me or to create a
+	Pull Request on GitHub.\tightlist
+\end{itemize}
+
+\section{License}
+
+The licensing of this project is a bit uncommon, so let me explain:
+
+The final package, the one you find on \href{https://ctan.org/}{CTAN}, is licensed under
+\href{https://ctan.org/license/lppl1.3c}{The \hologo{LaTeX} Project Public License 1.3c}. So use it
+like you would use most other packages on \href{https://ctan.org/}{CTAN}.
+
+The source repository, the one you find under \url{https://github.com/BrainStone/latex-lexend},
+however is licensed under the \href{https://www.gnu.org/licenses/gpl-3.0.html}{GNU General Public
+License v3.0}.
+
+Lastly, the font collection itself is licensed under the
+\href{https://opensource.org/licenses/OFL-1.1}{SIL Open Font License 1.1}. You can find the license
+file under \url{https://github.com/ThomasJockin/lexend/blob/master/OFL.txt}.
+
+\section{Font Samples}
+
+While this whole document uses \textsf{LexendDeca} as the main font and \textsf{LexendGiga} as the
+sans font, it doesn't hurt showing them off individually.\\
+Each font will be shown off in the sizes \small\textbackslash{}small\normalsize{},
+\textbackslash{}normalsize and \large\textbackslash{}large\normalsize{} and the variants
+\textbf{\textbackslash{}textbf}, \textit{\textbackslash{}textit} and
+\textbf{\textit{\textbackslash{}textbf\{\textbackslash{}textit\}}}
+
+\foreach \fontVariant in \LexendVariants
+{
+	\subsection{\texorpdfstring{\fontspec{\fontVariant}{\fontVariant}}{\fontVariant}}
+	
+	\fontspec{\fontVariant}{
+		\small\blindtext\normalsize\bigskip
+
+		\blindtext\bigskip
+
+		\large\blindtext\normalsize\bigskip
+
+		\textbf{\blindtext}\bigskip
+
+		\textit{\blindtext}\bigskip
+
+		\textbf{\textit{\blindtext}}
+	}
+}
+
+\end{document}