summaryrefslogtreecommitdiff
path: root/graphics/pgf
diff options
context:
space:
mode:
Diffstat (limited to 'graphics/pgf')
-rw-r--r--graphics/pgf/contrib/pixelart/CHANGELOG.md24
-rw-r--r--graphics/pgf/contrib/pixelart/LICENSE.txt416
-rw-r--r--graphics/pgf/contrib/pixelart/README.md43
-rw-r--r--graphics/pgf/contrib/pixelart/pixelart.dtx654
-rw-r--r--graphics/pgf/contrib/pixelart/pixelart.ins59
-rw-r--r--graphics/pgf/contrib/pixelart/pixelart.pdfbin0 -> 152344 bytes
6 files changed, 1196 insertions, 0 deletions
diff --git a/graphics/pgf/contrib/pixelart/CHANGELOG.md b/graphics/pgf/contrib/pixelart/CHANGELOG.md
new file mode 100644
index 0000000000..4a0fdfaee8
--- /dev/null
+++ b/graphics/pgf/contrib/pixelart/CHANGELOG.md
@@ -0,0 +1,24 @@
+* pixelart 0.2.0 (2018-02-25)
+
+ * Add a `draft` package option.
+
+ -- Louis Paternault <spalax+ctan@gresille.org>
+
+* pixelart 0.1.2 (2018-01-13)
+
+ * Fix bug: First line-break is now automatically ignored.
+ * Minor documentation fixes and improvements.
+
+ -- Louis Paternault <spalax+ctan@gresille.org>
+
+* pixelart 0.1.1 (2017-12-08)
+
+ * Fix CTAN URLs.
+
+ -- Louis Paternault <spalax+ctan@gresille.org>
+
+* pixelart 0.1.0 (2017-12-05)
+
+ * First published version.
+
+ -- Louis Paternault <spalax+ctan@gresille.org>
diff --git a/graphics/pgf/contrib/pixelart/LICENSE.txt b/graphics/pgf/contrib/pixelart/LICENSE.txt
new file mode 100644
index 0000000000..2244313901
--- /dev/null
+++ b/graphics/pgf/contrib/pixelart/LICENSE.txt
@@ -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/graphics/pgf/contrib/pixelart/README.md b/graphics/pgf/contrib/pixelart/README.md
new file mode 100644
index 0000000000..471df069b2
--- /dev/null
+++ b/graphics/pgf/contrib/pixelart/README.md
@@ -0,0 +1,43 @@
+pixelart 🎨 A LaTeX package to draw pixel-art pictures
+======================================================
+
+[![Sources](https://img.shields.io/badge/sources-pixelart-brightgreen.svg)](http://framagit.org/spalax/pixelart)
+[![CTAN](https://img.shields.io/ctan/v/pixelart.svg)](http://ctan.org/pkg/pixelart)
+[![Documentation](https://img.shields.io/badge/doc-pdf-brightgreen.svg)](http://mirrors.ctan.org/graphics/pixelart/pixelart.pdf)
+
+
+
+![Example](https://framagit.org/spalax/pixelart/raw/master/logo.png)
+
+It defines commands to convert a stream of bits (as characters `0` and `1`) to a
+black-and-white picture.
+
+- [Usage and installation instruction](http://mirrors.ctan.org/graphics/pixelart/pixelart.pdf).
+- Example: The picture above was produced using the following code.
+
+```latex
+\bwpixelart[color=red]{
+ 0011001100
+ 0111111110
+ 1111111111
+ 1111111111
+ 1111111111
+ 0111111110
+ 0011111100
+ 0001111000
+ 0000110000
+}
+```
+
+License
+-------
+
+*Copyright 2018 Louis Paternault*
+
+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.
diff --git a/graphics/pgf/contrib/pixelart/pixelart.dtx b/graphics/pgf/contrib/pixelart/pixelart.dtx
new file mode 100644
index 0000000000..472831348b
--- /dev/null
+++ b/graphics/pgf/contrib/pixelart/pixelart.dtx
@@ -0,0 +1,654 @@
+% \iffalse meta-comment
+% Copyright 2017-2018 Louis Paternault
+%
+% 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 Louis Paternault
+%
+% This work consists of the files pixelart.dtx and pixelart.ins
+% and the derived file pixelart.sty.
+% \fi
+%
+% \iffalse
+%<*driver>
+\ProvidesFile{pixelart.dtx}
+%</driver>
+%
+%<package>\NeedsTeXFormat{LaTeX2e}
+%<package>\ProvidesPackage{pixelart}
+%<*package>
+ [2018/02/25 v0.2.0 A package to draw pixel-art pictures]
+%</package>
+%
+%<*driver>
+\documentclass{ltxdoc}
+\EnableCrossrefs
+\CodelineIndex
+\RecordChanges
+\usepackage{hyperref}
+\usepackage{pixelart}
+\usepackage{listings}
+\usepackage{numprint}
+\lstset{
+ language=[LaTeX]TeX,
+ numbers=left,
+ numberstyle=\tiny,
+ backgroundcolor=\color{yellow!20},
+ basicstyle=\small\color{black}\ttfamily,
+ keywordstyle=\color{blue!80}\sffamily,
+ commentstyle=\color{olive},
+ stringstyle=\color{red},
+}
+\usepackage{textcomp}
+\usepackage{fontspec}
+\usepackage[english]{babel}
+% Smiley command published by percusse on https://tex.stackexchange.com/a/58913
+\newcommand{\smiley}{\tikz[baseline=-0.75ex, black]{
+ \draw circle (2mm);
+ \node[fill,circle,inner sep=0.5pt] (left eye) at (135:0.8mm) {};
+ \node[fill,circle,inner sep=0.5pt] (right eye) at (45:0.8mm) {};
+ \draw (-145:0.9mm) arc (-120:-60:1.5mm);
+}
+}
+\begin{document}
+\DocInput{pixelart.dtx}
+\end{document}
+%</driver>
+% \fi
+%
+% \CheckSum{0}
+% \CharacterTable
+% {Upper-case \A\B\C\D\E\F\G\H\I\J\K\L\M\N\O\P\Q\R\S\T\U\V\W\X\Y\Z
+% Lower-case \a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\z
+% Digits \0\1\2\3\4\5\6\7\8\9
+% Exclamation \! Double quote \" Hash (number) \#
+% Dollar \$ Percent \% Ampersand \&
+% Acute accent \' Left paren \( Right paren \)
+% Asterisk \* Plus \+ Comma \,
+% Minus \- Point \. Solidus \/
+% Colon \: Semicolon \; Less than \<
+% Equals \= Greater than \> Question mark \?
+% Commercial at \@ Left bracket \[ Backslash \\
+% Right bracket \] Circumflex \^ Underscore \_
+% Grave accent \` Left brace \{ Vertical bar \|
+% Right brace \} Tilde \~}
+%
+% \GetFileInfo{pixelart.dtx}
+%
+% \DoNotIndex{\#,\$,\%,\&,\@,\\,\{,\},\^,\_,\~,\ ,\!,\(,\),\,}
+% \DoNotIndex{\@bwpa@newline}
+% \DoNotIndex{\begin}
+% \DoNotIndex{\coordinate}
+% \DoNotIndex{\end, \else}
+% \DoNotIndex{\fill, \fi}
+% \DoNotIndex{\ifpixelart@draft}
+% \DoNotIndex{\makeatletter, \makeatother}
+% \DoNotIndex{\newcommand, \newif}
+% \DoNotIndex{\ProcessPgfPackageOptions, \pgfkeys, \pgfkeyssetvalue, \pgfkeysvalueof, \pgfparserdef, \pgfparserparse, \pgfparserswitch}
+% \DoNotIndex{\raisebox, \RequirePackage}
+% \DoNotIndex{\space}
+% \DoNotIndex{\tikz}
+% \DoNotIndex{\usepgfmodule, \usetikzlibrary}
+%
+% \title{
+% \begin{tikzpicture}
+% \tikzbwpixelart[scale=.037]{(-1.05, .14)}{%
+% 1111110001100000000000000000001110000010000000000000001000
+% 0110011001100000000000000000000110000111000000000000011000
+% 0110011000000000000000000000000110001101100000000000011000
+% 0110011011100110000110011111000110011000110110111001111110
+% 0111110001100011001100110001100110011000110011101100011000
+% 0110000001100001111000111111100110011111110011001100011000
+% 0110000001100000110000110000000110011000110011000000011000
+% 0110000001100001111000110000000110011000110011000000011000
+% 0110000001100011001100110001100110011000110011000000011011
+% 1111000011110110000110011111001111011000110111100000001110
+% }%
+% \draw (0, 0) node[opacity=0]{\LARGE PixelArt};
+% \end{tikzpicture}\thanks{
+% This document corresponds to \textsf{pixelart}~\fileversion, dated \filedate.
+% Home page, bug requests, etc. at \url{http://framagit.org/spalax/pixelart}
+% }\\A package to draw pixel-art pictures.}
+% \author{Louis Paternault\\ \texttt{spalax+ctan(at)gresille(dot)org}}
+%
+% \maketitle
+%
+% \begin{abstract}
+% This package defines macros to draw pixel-art pictures using \LaTeX{}.
+% \end{abstract}
+%
+% \setcounter{tocdepth}{2}
+% \tableofcontents
+%
+% \section{Introduction}
+% This document introduces the \textsf{pixelart} package, used to draw pixel-art pictures.
+%
+% \subsection{License}
+% 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.
+%
+% Further information can be found in the |.dtx| file used to build this
+% document.
+%
+% \subsection{Overview}
+% Installation instruction are given in section \ref{sec:install}.
+% Documentation about how to use this package (and examples) is given in section
+% \ref{sec:usage}. Section \ref{sec:bugs} lists some known bugs and
+% limitations, and implementation is given in section
+% \ref{sec:implementation}.
+%
+% \section{Download and Install}
+% \label{sec:install}
+%
+% \subsection{\textsc{Gnu}/Linux Distribution}
+%
+% If applicable, the easiest way to get |pixelart| working is by installing it by your distribution package. In Debian (and Ubuntu, and surely other distributions that inherit from Debian) it is packaged in |texlive-pictures| since version \texttt{2017.20180103-1}. So you can install it by running:
+%
+% \begin{quote}
+% |sudo apt install texlive-pictures|
+% \end{quote}
+%
+% \subsection{LaTeX distribution}
+%
+% This package is included both in \TeX{}Live and MiK\TeX{}. It can be installed using their respective package managers.
+%
+% \subsection{Manual installation}
+%
+% \begin{itemize}
+% \item Download the lastest archive :
+% \begin{description}
+% \item[Stable version] \url{http://mirrors.ctan.org/graphics/pixelart.zip}
+% \item[Development version] \url{https://framagit.org/spalax/pixelart/repository/archive.zip?ref=master}
+% \end{description}
+% \item Unzip the archive.
+% \item If you got the archive from CTAN (stable version), move file \texttt{tex/latex/pixelart/pixelart.sty} in a \LaTeX{} path.
+% \item If you got the development version, |cd| to the main archive directory, and run |latex pixelart.ins| to build |pixelart.sty|. Move this file into a \LaTeX{} path.
+% \end{itemize}
+%
+% \section{Usage}
+% \label{sec:usage}
+%
+% \subsection{Package options}
+% \changes{v0.2.0}{2018/01/25}{Add package option \texttt{draft}.}
+%
+% This package has a single package option: |draft|. If this option is set (\lstinline|\usepackage[draft]{pixelart}|), pixel-art pictures are ignored. This can make compilation \emph{way, way} faster\footnote{On a document I am writing, containing a lot of pixel-art pictures, option |draft| makes compilation time go from 6 minutes to 22 seconds.}.
+%
+% A downside is that since pixel-art pictures are ignored, this can mess up your document layout. A nicer option would be to have option |draft| guess the pixel-art size, and display a dummy picture with the same size. Patches are welcome! \smiley
+%
+% \subsection{Macros}
+%
+% This package defines two macros : |\bwpixelart|\footnote{\texttt{$\backslash{}$bwpixelart} stands for \emph{b}lack and \emph{w}hite \emph{pixel art}, although \emph{color and transparent pixel art} would be more accurate.}, used to insert a pixel-art picture, and |\tikzbwpixelart|, which has the same purpose, excepted that it is called from within a |tikzpicture| environment.
+%
+% \subsubsection{\textbackslash\texttt{bwpixelart}}
+% \DescribeMacro{\bwpixelart}
+% To insert a pixel-art picture in your text, use :
+% \begin{center}
+% \lstinline|\bwpixelart|\oarg{color, raise, scale}\marg{pixels}
+% \end{center}
+% Its optional arguments are:
+% \begin{description}
+% \item[color=black] Foreground color (the background is transparent);
+% \item[scale=1] Scale. By default, a pixel is the size of a |tikzpicture| default unit, which is probably bigger than what you want.
+% \item[raise=0pt] Raise the picture. By default, the bottom of the picture is on the baseline. You might want to lower it a little by giving this option a negative argument.
+% \end{description}
+%
+% Its mandatory argument is the picture pixels, as |0|'s and |1|'s. Line breaks in this argument are interpreted as line breaks in the pixel art pictures. How spaces are interpreted is undefined (see section \ref{ssec:spaces} for more information).
+%
+% For instance, this heart
+% \bwpixelart[color=red, scale=.05, raise=-1ex]{%
+% 001101100
+% 011111110
+% 111111111
+% 111111111
+% 111111111
+% 011111110
+% 001111100
+% 000111000
+% 000010000
+% }
+% was drawn using the following code:
+%
+% \iffalse
+%<*example>
+% \fi
+% \begin{lstlisting}
+ \bwpixelart[color=red, scale=.05, raise=-1ex]{%
+ 001101100
+ 011111110
+ 111111111
+ 111111111
+ 111111111
+ 011111110
+ 001111100
+ 000111000
+ 000010000
+ }
+\end{lstlisting}
+% \iffalse
+%</example>
+% \fi
+%
+% \subsubsection{\textbackslash\texttt{tikzbwpixelart}}
+% \DescribeMacro{\tikzbwpixelart}
+% The second macro, |\tikzbwpixelart| is almost identical to the first one, excepted that it is meant to be called from inside a |tikzpicture| environment. Actually, \lstinline|\bwpixelart{0101}| is more or less equivalent to calling :
+% \iffalse
+%<*example>
+% \fi
+% \begin{lstlisting}
+\begin{tikzpicture}
+ \tikzbwpixelart{(0, 0)}{0101}
+\end{tikzpicture}
+\end{lstlisting}
+% \iffalse
+%</example>
+% \fi
+
+% The signature of this macro is :
+% \begin{center}
+% \lstinline|\tikzbwpixelart|\oarg{color, scale}\marg{coordinates}\marg{pixels}
+% \end{center}
+% Its optional arguments are |color| and |scale|, used to set the color and scale of the picture.
+%
+% Its first mandatory argument is the coordinate of the top left corner of the picture; the second one is the list of pixels (using the same syntax as the |\bwpixelart| macro).
+%
+% For instance, this heart
+%\begin{tikzpicture}[scale=.05, baseline=-1em]
+% \fill[red] (5, -4) circle (6.5);
+% \tikzbwpixelart{(0, 0)}{%
+% 0011001100
+% 0111111110
+% 1111111111
+% 1111111111
+% 1111111111
+% 0111111110
+% 0011111100
+% 0001111000
+% 0000110000
+%}
+%\end{tikzpicture}
+% was drawn using the following code:
+%
+% \iffalse
+%<*example>
+% \fi
+% \begin{lstlisting}
+\begin{tikzpicture}[scale=.05, baseline=-1em]
+ \fill[red] (5, -4) circle (6.5);
+ \tikzbwpixelart{(0, 0)}{%
+ 0011001100
+ 0111111110
+ 1111111111
+ 1111111111
+ 1111111111
+ 0111111110
+ 0011111100
+ 0001111000
+ 0000110000
+}
+\end{tikzpicture}
+\end{lstlisting}
+% \iffalse
+%</example>
+% \fi
+%
+%\section{Bugs, Ideas, Undefined behaviours}
+%\label{sec:bugs}
+%
+% I have great ideas about what this package could do, but:
+% \begin{itemize}
+% \item I do not need them;
+% \item I am not sure there is a huge \emph{need} for some pixel-art package;
+% \item I have a full-time job, my wife has a far-more-than-full-time job, my daugther \emph{is} a full-time job, so I have very little time to hack…
+% \end{itemize}
+%
+% So, I am listing here some known bugs, undefined behaviours, limitations. You, random passer-by, will be greatly welcome if you were to fix or implement stuff listed in this section. \smiley
+%
+% \subsection{Missing \texttt{\textbackslash{}pixelart} macro}
+%
+% There is no |\pixelart| macro. This is on purpose: given that this package is more or less a working draft, I did not want to register a badly designed |\pixelart| macro. This means that some folk wanting to improve this package can extand the |\bwpixelart| macro and use the name |\pixelart| to fix my design mistakes.
+%
+% \subsection{It's insanely slooooow.}
+%
+% That's it. It takes alomst 30 seconds to compile a document containing only a $128\times128$ picture (about \numprint{16000} pixels). I have no idea how to fix it. Good luck.
+%
+% \subsection{Black and white}
+%
+% Right now, it is black and white only (or, to be more accurate, any single color on a transparent background).
+%
+% One \emph{could} produce colored pixel-art pictures, but… it's complicated. For instance, this heart (borrowed from the Django project\footnote{\url{https://www.djangoproject.com/}}):
+%
+% \definecolor{violet1}{RGB}{247, 176, 207}
+% \definecolor{violet2}{RGB}{238, 33, 120}
+% \definecolor{violet3}{RGB}{214, 45, 117}
+% \definecolor{violet4}{RGB}{217, 25, 92}
+% \definecolor{violet5}{RGB}{173, 29, 69}
+% \begin{center}
+% \begin{tikzpicture}[scale=.1]
+% \tikzbwpixelart[color=violet1]{(0, 0)}{%
+% 0000000
+% 0000010
+% }
+% \tikzbwpixelart[color=violet2]{(0, 0)}{%
+% 0000000
+% 0110100
+% 0000000
+% 0010100
+% 0000000
+% 0001000
+% }
+% \tikzbwpixelart[color=violet3]{(0, 0)}{%
+% 0000010
+% 0000000
+% 1000010
+% 0000000
+% 0001000
+% }
+% \tikzbwpixelart[color=violet4]{(0, 0)}{%
+% 0010100
+% 1001000
+% 0110100
+% 0001010
+% 0010100
+% }
+% \tikzbwpixelart[color=violet5]{(0, 0)}{%
+% 0100000
+% 0000001
+% 0001001
+% 0100000
+% }
+% \end{tikzpicture}
+% \end{center}
+%
+% could be produced using the following code. Basically (given that colors |violet1| to |violet5| have been correctly defined), we stack up several single-color pixel-art pictures.
+%
+% \iffalse
+%<*example>
+% \fi
+% \begin{lstlisting}
+\begin{tikzpicture}[scale=.1]
+ \tikzbwpixelart[color=violet1]{(0, 0)}{%
+ 0000000
+ 0000010
+ }
+ \tikzbwpixelart[color=violet2]{(0, 0)}{%
+ 0000000
+ 0110100
+ 0000000
+ 0010100
+ 0000000
+ 0001000
+ }
+ \tikzbwpixelart[color=violet3]{(0, 0)}{%
+ 0000010
+ 0000000
+ 1000010
+ 0000000
+ 0001000
+ }
+ \tikzbwpixelart[color=violet4]{(0, 0)}{%
+ 0010100
+ 1001000
+ 0110100
+ 0001010
+ 0010100
+ }
+ \tikzbwpixelart[color=violet5]{(0, 0)}{%
+ 0100000
+ 0000001
+ 0001001
+ 0100000
+ }
+\end{tikzpicture}
+\end{lstlisting}
+% \iffalse
+%</example>
+% \fi
+%
+% One could imagine a simpler syntax: we assign several colors to characters, and we use |1|, |2|, |3|, etc. as the pixels to define the picture. This would give the following code.
+%
+% \iffalse
+%<*example>
+% \fi
+% \begin{lstlisting}
+\begin{tikzpicture}[scale=.1]
+ \tikzpixelart[colors={
+ 1=violet1,
+ 2=violet2,
+ 3=violet3,
+ 4=violet4,
+ 5=violet5,
+ }]{(0, 0)}{%
+ 0540430
+ 4224215
+ 3445435
+ 0524240
+ 0043400
+ 0002000
+ }
+\end{tikzpicture}
+\end{lstlisting}
+% \iffalse
+%</example>
+% \fi
+%
+% Once again, patches are welcome! \smiley{}
+%
+% \subsection{Spaces}
+%\label{ssec:spaces}
+%
+% Spaces are interpreted as line breaks. For instance, this heart
+% \bwpixelart[scale=.03, raise=-1pt]{%
+% 0011001100 0111111110 1111111111
+% 1111111111 1111111111 0111111110
+% 0011111100 0001111000 0000110000
+% }
+% could be written as :
+% \iffalse
+%<*example>
+% \fi
+% \begin{lstlisting}
+\bwpixelart[scale=.03, raise=-1pt]{%
+ 0011001100 0111111110 1111111111
+ 1111111111 1111111111 0111111110
+ 0011111100 0001111000 0000110000
+}
+\end{lstlisting}
+% \iffalse
+%</example>
+% \fi
+%
+% This will work (right now), but is an undefined behaviour, and might change in a later version without prior notice.
+%
+% \subsection{Uneven lines}
+%
+% Right now, lines do not \emph{have} to have the same number of characters. For instance, the following heart
+% \bwpixelart[scale=.03, raise=-1pt]{%
+% 00110011
+% 011111111
+% 1111111111
+% 1111111111
+% 1111111111
+% 011111111
+% 00111111
+% 0001111
+% 000011
+%}
+% could be written as :
+%
+% \iffalse
+%<*example>
+% \fi
+% \begin{lstlisting}
+\bwpixelart[scale=.03, raise=-1pt]{%
+ 00110011
+ 011111111
+ 1111111111
+ 1111111111
+ 1111111111
+ 011111111
+ 00111111
+ 0001111
+ 000011
+}
+\end{lstlisting}
+% \iffalse
+%</example>
+% \fi
+%
+% This is an undefined behaviour and might raise an error in the future.
+%
+% \section{Implementation}
+% \label{sec:implementation}
+%
+% Load some packages.
+% \begin{macrocode}
+\RequirePackage{pgf}
+\RequirePackage{pgfopts}
+\usepgfmodule{parser}
+\RequirePackage{tikz}
+\usetikzlibrary{calc}
+\RequirePackage{pgfkeys}
+\RequirePackage{etoolbox}
+
+% \end{macrocode}
+%
+% Let the nasty stuff begin.
+%
+% \begin{macrocode}
+\makeatletter
+
+% \end{macrocode}
+%
+% Parse package options.
+%
+% \begin{macrocode}
+\newif\ifpixelart@draft
+\pgfkeys{
+ /PIXELART/.cd,
+ draft/.is if=pixelart@draft,
+ draft=false,
+}
+\ProcessPgfPackageOptions{/PIXELART}
+% \end{macrocode}
+%
+% Define macro arguments
+%
+% \begin{macrocode}
+\pgfkeys{
+ /PIXELART/BWPIXELART/.is family,
+ /PIXELART/BWPIXELART,
+ scale/.value required,
+ scale/.code={\pgfkeyssetvalue{/PIXELART/BWPIXELART/scale}{#1}},
+ scale=1,
+ raise/.code={\pgfkeyssetvalue{/PIXELART/BWPIXELART/raise}{#1}},
+ raise/.value required,
+ raise=0pt,
+ color/.value required,
+ color/.code={\pgfkeyssetvalue{/PIXELART/BWPIXELART/color}{#1}},
+ color=black,
+}
+
+\pgfkeys{
+ /PIXELART/TIKZBWPIXELART/.is family,
+ /PIXELART/TIKZBWPIXELART,
+ scale/.value required,
+ scale/.code={\pgfkeyssetvalue{/PIXELART/TIKZBWPIXELART/scale}{#1}},
+ scale=1,
+ color/.value required,
+ color/.code={\pgfkeyssetvalue{/PIXELART/TIKZBWPIXELART/color}{#1}},
+ color=black,
+}
+
+% \end{macrocode}
+%
+% Define argument parser, parsing the sequence of 0 and 1 defining the pixel art.
+%
+% \begin{macrocode}
+\pgfparserdef{@bwpixelart}{initial}{blank space \space}{
+ \@bwpa@newline
+}
+\pgfparserdef{@bwpixelart}{initial}{the character 0}{
+ \coordinate (@pixelart) at ($(@pixelart) + (1, 0)$);
+}
+\pgfparserdef{@bwpixelart}{initial}{the character 1}{
+ \fill (@pixelart) rectangle ++(1, 1);
+ \coordinate (@pixelart) at ($(@pixelart) + (1, 0)$);
+}
+\pgfparserdef{@bwpixelart}{initial}{the letter @}{
+ \pgfparserswitch{final}
+}
+
+\newcommand{\@bwpa@newline}{
+ \coordinate (@pixelart) at ($(@pixelart@startline) + (0, -1)$);
+ \coordinate (@pixelart@startline) at (@pixelart);
+}
+
+% \end{macrocode}
+%
+% \begin{macro}{\bwpixelart}
+% \changes{v0.1.2}{2018/01/13}{First line-break of pixelart argument is now automatically ignored.}
+% Define |\bwpixelart|, used to draw black-and-white pixelart.
+% \begin{macrocode}
+\newcommand{\bwpixelart}[2][]{{%
+ \pgfkeys{/PIXELART/BWPIXELART, #1}%
+ \raisebox{\pgfkeysvalueof{/PIXELART/BWPIXELART/raise}}{%
+ \tikz[
+ scale=\pgfkeysvalueof{/PIXELART/BWPIXELART/scale},
+ ]{
+ \tikzbwpixelart[%
+ color=\pgfkeysvalueof{/PIXELART/BWPIXELART/color},
+ ]{(0, 0)}{#2}
+ }%
+ }%
+}}
+
+% \end{macrocode}
+% \end{macro}
+% \begin{macro}{\tikzbwpixelart}
+% Define |\tikzbwpixelart|, used to draw black-and-white pixelart from inside a |tikzpicture| environment.
+% \begin{macrocode}
+\newcommand{\tikzbwpixelart}[3][]{
+ \pgfkeys{/PIXELART/TIKZBWPIXELART, #1}
+ \ifpixelart@draft
+ % Draft mode. Nothing to parse, nothing to show!
+ \else
+ \begin{scope}[shift={#2}]
+ \begin{scope}[#1]
+ \coordinate (@pixelart) at (0, 1);
+ \coordinate (@pixelart@startline) at (@pixelart);
+
+ \pgfparserparse{@bwpixelart}
+ #3 @
+ \end{scope}
+ \end{scope}
+ \fi
+}
+
+% \end{macrocode}
+% That's all, folks!
+% \begin{macrocode}
+\makeatother
+
+% \end{macrocode}
+% \end{macro}
+%
+% \changes{v0.1.0}{2017/12/05}{First published version.}
+%
+% \addcontentsline{toc}{section}{Change History}
+% \PrintChanges
+%
+% \StopEventually{%
+% \addcontentsline{toc}{section}{Index}
+% \PrintIndex
+% }
+% \Finale
+\endinput
diff --git a/graphics/pgf/contrib/pixelart/pixelart.ins b/graphics/pgf/contrib/pixelart/pixelart.ins
new file mode 100644
index 0000000000..add23f88ee
--- /dev/null
+++ b/graphics/pgf/contrib/pixelart/pixelart.ins
@@ -0,0 +1,59 @@
+%% Copyright 2017 Louis Paternault
+%%
+%% 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 Louis Paternault
+%%
+%% This work consists of the files pixelart.dtx and pixelart.ins
+%% and the derived file pixelart.sty.
+
+\input{docstrip}
+
+\keepsilent
+\usedir{tex/latex/pixelart}
+
+\preamble
+Copyright 2017 Louis Paternault
+
+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 Louis Paternault
+
+This work consists of the files pixelart.dtx and pixelart.ins
+and the derived file pixelart.sty.
+\endpreamble
+
+\generate{\file{pixelart.sty}{\from{pixelart.dtx}{package}}}
+
+\obeyspaces
+\Msg{****************************************************}
+\Msg{* *}
+\Msg{* To finish the installation you have to move the *}
+\Msg{* following file into a directory searched by TeX: *}
+\Msg{* *}
+\Msg{* pixelart.sty *}
+\Msg{* *}
+\Msg{* To produce the documentation run the file *}
+\Msg{* pixelart.dtx through LaTeX. *}
+\Msg{* *}
+\Msg{* Happy TeXing! *}
+\Msg{* *}
+\Msg{****************************************************}
+
+\endbatchfile
diff --git a/graphics/pgf/contrib/pixelart/pixelart.pdf b/graphics/pgf/contrib/pixelart/pixelart.pdf
new file mode 100644
index 0000000000..a651a085fe
--- /dev/null
+++ b/graphics/pgf/contrib/pixelart/pixelart.pdf
Binary files differ