texlive[52544] Master: circledsteps (27oct19)
commits+karl at tug.org
commits+karl at tug.org
Sun Oct 27 21:53:42 CET 2019
Revision: 52544
http://tug.org/svn/texlive?view=revision&revision=52544
Author: karl
Date: 2019-10-27 21:53:41 +0100 (Sun, 27 Oct 2019)
Log Message:
-----------
circledsteps (27oct19)
Modified Paths:
--------------
trunk/Master/tlpkg/bin/tlpkg-ctan-check
trunk/Master/tlpkg/tlpsrc/collection-latexextra.tlpsrc
Added Paths:
-----------
trunk/Master/texmf-dist/doc/latex/circledsteps/
trunk/Master/texmf-dist/doc/latex/circledsteps/README.md
trunk/Master/texmf-dist/doc/latex/circledsteps/circledsteps-manual.pdf
trunk/Master/texmf-dist/doc/latex/circledsteps/circledsteps-manual.tex
trunk/Master/texmf-dist/doc/latex/circledsteps/ctikzexample.tex
trunk/Master/texmf-dist/doc/latex/circledsteps/lppl-1-3c_license.txt
trunk/Master/texmf-dist/tex/latex/circledsteps/
trunk/Master/texmf-dist/tex/latex/circledsteps/circledsteps.sty
trunk/Master/tlpkg/tlpsrc/circledsteps.tlpsrc
Added: trunk/Master/texmf-dist/doc/latex/circledsteps/README.md
===================================================================
--- trunk/Master/texmf-dist/doc/latex/circledsteps/README.md (rev 0)
+++ trunk/Master/texmf-dist/doc/latex/circledsteps/README.md 2019-10-27 20:53:41 UTC (rev 52544)
@@ -0,0 +1,25 @@
+## Package `circledsteps` for LaTeX
+
+A package to generate circled numbers (or other kind of markers or small text) to mark "steps" in procedure, exercises, and so on.
+
+See [this question on tex.stackexchange.com](https://tex.stackexchange.com/questions/7032/good-way-to-make-textcircled-numbers)
+
+### DOCUMENTATION
+
+See the included file `circledsteps-manual.tex`; you can compile it running (twice) `pdflatex` on it. If you want to have a look before buying, you can find a compiled copy on the [release page](https://github.com/Rmano/circledsteps/releases).
+
+If you have already installed the package in your TeX distribution, use `texdoc circledsteps`; it should show you the manual of the installed version of the package.
+
+
+### LICENSE
+
+Licensed under [LPPL 1.3c](https://www.latex-project.org/lppl/lppl-1-3c/)
+
+### SOURCE REPO
+
+The source is hosted on [GitHub](https://github.com/Rmano/circledsteps).
+If you clone the repository, you can use
+
+ make local-install
+
+to install the package on [your local TEXMF tree](https://tex.stackexchange.com/questions/1137/where-do-i-place-my-own-sty-or-cls-files-to-make-them-available-to-all-my-te).
Property changes on: trunk/Master/texmf-dist/doc/latex/circledsteps/README.md
___________________________________________________________________
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: trunk/Master/texmf-dist/doc/latex/circledsteps/circledsteps-manual.pdf
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/latex/circledsteps/circledsteps-manual.pdf
===================================================================
--- trunk/Master/texmf-dist/doc/latex/circledsteps/circledsteps-manual.pdf 2019-10-27 20:52:56 UTC (rev 52543)
+++ trunk/Master/texmf-dist/doc/latex/circledsteps/circledsteps-manual.pdf 2019-10-27 20:53:41 UTC (rev 52544)
Property changes on: trunk/Master/texmf-dist/doc/latex/circledsteps/circledsteps-manual.pdf
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/pdf
\ No newline at end of property
Added: trunk/Master/texmf-dist/doc/latex/circledsteps/circledsteps-manual.tex
===================================================================
--- trunk/Master/texmf-dist/doc/latex/circledsteps/circledsteps-manual.tex (rev 0)
+++ trunk/Master/texmf-dist/doc/latex/circledsteps/circledsteps-manual.tex 2019-10-27 20:53:41 UTC (rev 52544)
@@ -0,0 +1,154 @@
+\documentclass{ltxdoc}
+\usepackage{doc}
+\usepackage[T1]{fontenc}
+\usepackage[utf8]{inputenc}
+\usepackage{a4wide}
+\usepackage{tikz}
+\usepackage[siunitx, RPvoltages]{circuitikz}
+\ctikzset{%
+ american,
+ cute inductors,
+}
+\usepackage{booktabs}
+\usepackage{hyperref}
+\hypersetup{colorlinks=true, % false: boxed links; true: colored links
+ linkcolor=blue, % color of internal links
+ urlcolor=blue, % color of external links
+}
+\usepackage{showexpl}
+\lstset{pos=t, overhang=0pt,hsep=\columnsep,vsep=\bigskipamount,
+ rframe=single,numbers=left,numberstyle=\tiny,numbersep=.3em, xleftmargin=1em,
+ columns=flexible, language=[LaTeX]TEX,breaklines=true,
+ basicstyle=\small\ttfamily,tabsize=3, varwidth}
+\usepackage{circledsteps}
+
+\title{The \texttt{circledsteps} package: circled numbers, circled steps and more}
+\author{Romano Giannetti <romano.giannetti at gmail.com>}
+% when we have lot of insets, this is better:
+\parindent=0pt\parskip=6pt plus 6pt minus 2pt\relax
+
+\begin{document}
+\maketitle
+
+\section{Introduction}
+
+This package was born thanks to the discussion on \href{https://tex.stackexchange.com/questions/7032/good-way-to-make-textcircled-numbers}{tex.stackexchange.com}, and with the help of the several authors that contributed to the answers. The base idea is to have a command that can create arbitrary ``circled'' text (numbers or letters) and that can work in normal text \textbf{and} in a node in a \texttt{tikzpicure} or derivative. That forbid to use \texttt{Ti\emph{k}Z} itself for the circles --- you can't safely nest \texttt{tikzpicture}s.
+
+This package provides two things: the first one, macros to generate the circled text that use the original \texttt{pict2e} method, and then a (simple, to be taken as an example) set of macro to generate sequential circled numbers that can be referenced afterward.
+
+\section{Basic commands}
+
+The basic commands are:
+
+\begin{tabular}{>{\ttfamily\textbackslash}ll}
+ \toprule
+ Circled\{\} & circled text using the package colors, text on the baseline\\
+ CircledTop\{\} & circled text using the package colors, circle on the baseline\\
+ CircledText\{\} & circled text using the current color (may fail\footnotemark{} in moving arguments)\\
+ \bottomrule
+\end{tabular}
+\footnotetext{in the sense it can select the wrong color.}
+
+The parameters for the output are controlled using \texttt{pgfkeys}; you can change them with \verb|\tikzset|; you can obviously limit the effect of change using normal \LaTeX{} scoping rules.
+
+\begin{tabular}{>{\ttfamily}lll}
+ \toprule
+ \textbf{Parameter} & \textbf{Meaning} & \textbf{Default value} \\
+ \midrule
+ /csteps/inner ysep & vertical spacing & 4pt\\
+ /csteps/inner xsep & horizontal spacing & 4pt\\
+ /csteps/inner color & color of the text & red\\
+ /csteps/outer color & color of the circle & blue\\
+ \bottomrule
+\end{tabular}
+
+The working of the package is better explained with examples.
+
+\begin{LTXexample}
+This is normal text: \Circled{1} is on the baseline, \CircledTop{2} is on top.
+
+This is more evident if you have descendents, like p:\Circled{p} and \CircledTop{p}.
+\end{LTXexample}
+
+
+\begin{LTXexample}
+For big horizontal things the circle becomes oval: \Circled{200} or \CircledTop{199}.
+\end{LTXexample}
+
+
+\begin{LTXexample}
+Inside \texttt{tikz} they work ok:
+
+\begin{tikzpicture}[scale=0.8, rotate=30,
+ text width=3cm, transform shape]
+ \node [draw,color=purple]{text \Circled{1}};
+\end{tikzpicture}
+\end{LTXexample}
+
+
+\begin{LTXexample}
+\tikzset{/csteps/inner ysep=10pt}
+\tikzset{/csteps/inner xsep=10pt}
+If you like more breathing space:
+\Circled{1} \Circled{2} \Circled{p} \Circled{200} \Circled{199}.
+\par\bigskip
+\end{LTXexample}
+
+\begin{LTXexample}
+\tikzset{/csteps/inner color=green}
+\tikzset{/csteps/outer color=gray}
+If you want to change colors it's easy:
+\Circled{1} \Circled{2} \Circled{p} \Circled{200} \Circled{199}.
+\par\bigskip
+\end{LTXexample}
+
+\begin{LTXexample}
+Or even you can have inline numbers like \CircledText{1} or
+exponents\textsuperscript{\CircledText{2}} and so on.
+\textcolor{red}{They follow the current color: \CircledText{1} and \CircledText{2} automatically,} as you can see: \CircledText{$1+1\approx3$}. In-text circled numbers look better when a bit smaller, though, as you can see in {\small\CircledText{1}} for example.
+\end{LTXexample}
+
+Notice that \verb|\CircledText{}| uses the special ``\texttt{.}'' color defined by \texttt{xcolor}; when page breaks occurs it can get the wrong color.
+
+No, you can't fill the circle/oval. Pull requests in that sense are welcome.
+
+\section{Automatically generated numbers}
+
+The command \verb|\cstep| will generate a circled number, starting from \texttt{1}, that can be referenced with the normal \verb|\label| mechanism. You can reset the numbering with
+\verb|\startcstep|. For example:
+
+\input{ctikzexample.tex}
+
+\lstinputlisting{ctikzexample.tex}
+
+\bigskip
+
+\section{Personalize it!}
+
+The definition of \verb|CircledTexT| is simply the following one; you can get idea and define your own easily (beware of spaces at the end of the lines, though!):
+
+\begin{lstlisting}
+\newcommand{\CircledText}[1]{%
+ \begingroup
+ \tikzset{/csteps/inner color=., /csteps/outer color=.}%
+ \Circled{#1}%
+ \endgroup
+}
+\end{lstlisting}
+
+
+Also the implementation of the \verb|\cstep| command and relatives is quite simple, and you can play a lot with it to change things (formats, colors, the type of numbering, and so on):
+
+\begin{lstlisting}
+\newcounter{cstepcnt}
+\newcommand{\startcstep}{\setcounter{cstepcnt}{0}}
+\newcommand{\resetcstep}{\setcounter{cstepcnt}{0}}
+\newcommand{\cstep}{%
+ \refstepcounter{cstepcnt}%
+ \Circled{\scriptsize\arabic{cstepcnt}}%
+}
+\renewcommand{\thecstepcnt}{\textbf{\arabic{cstepcnt}:}}
+\end{lstlisting}
+
+
+\end{document}
Property changes on: trunk/Master/texmf-dist/doc/latex/circledsteps/circledsteps-manual.tex
___________________________________________________________________
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: trunk/Master/texmf-dist/doc/latex/circledsteps/ctikzexample.tex
===================================================================
--- trunk/Master/texmf-dist/doc/latex/circledsteps/ctikzexample.tex (rev 0)
+++ trunk/Master/texmf-dist/doc/latex/circledsteps/ctikzexample.tex 2019-10-27 20:53:41 UTC (rev 52544)
@@ -0,0 +1,27 @@
+\begin{circuitikz}[scale=0.9, baseline=(VCC), transform shape]
+ \draw (0,0) node[ground](GND){} to[V=$v_s$] ++(0,2)
+ to[R, l2^=$R_1$ and \SI{1}{k\ohm}, l2 valign=b] ++(2,0) coordinate(firstb);
+ \node [above] at(firstb) {\cstep\label{c:b1}};
+ \node [below] at(firstb) {0};
+ \draw (firstb) node[npn, anchor=B](Q1){};
+ \draw (Q1.E) node[left]{\num{-0.7}\cstep};
+ \draw (Q1.C) to[R, l2_=$R_2$ and \SI{5}{k\ohm}, f<=\num{0.93}] ++(0,2.5)
+ node[vcc](VCC){$V_{CC}=\SI{10}{V}$} ;
+ \draw (Q1.E) to[R, l2_=$R_3$ and \SI{10}{k\ohm},
+ f=\num{0.93}] ++(0,-2.5) node[vee](VEE){$V_{EE}=\SI{-10}{V}$}
+ node[left]{\cstep\label{c:ie1}};
+ \path (VCC) node[right]{\cstep\label{c:ic1}};
+ \draw (Q1.E) -- ++(1,0) coordinate(tmp) to[C=$C_1$] (tmp |- GND) node[ground]{};
+ \draw (Q1.C) -- ++(1,0) coordinate(g1) to[short, -o] ++(1,0);
+ \node [above] at(g1) {\cstep\label{c:g1}};
+ \node [below] at(g1) {\num{5.35}};
+\end{circuitikz}\quad
+\begin{minipage}[t]{0.5\linewidth}
+ %% minipage reset these..
+ \parindent=0pt\parskip=6pt plus 6pt minus 2pt\relax
+ \ref{c:b1} let's neglect (to be confirmed!) $I_B$, $V_B\approx\SI{0}{V}$;\par
+ \ref{c:ie1} $I_{E1_Q}=(V_{E1_Q}-V_{EE})/R_3$;\par
+ \ref{c:ic1} $I_{C1_Q} \approx\SI{0.93}{mA}$;\par
+ \ref{c:g1} $V_{CC}-R_2I_{C2_Q}= \SI{5.35}{V}$; $V_{CE1_Q}=\SI{6.05}{V}$;\par
+\end{minipage}
+
Property changes on: trunk/Master/texmf-dist/doc/latex/circledsteps/ctikzexample.tex
___________________________________________________________________
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: trunk/Master/texmf-dist/doc/latex/circledsteps/lppl-1-3c_license.txt
===================================================================
--- trunk/Master/texmf-dist/doc/latex/circledsteps/lppl-1-3c_license.txt (rev 0)
+++ trunk/Master/texmf-dist/doc/latex/circledsteps/lppl-1-3c_license.txt 2019-10-27 20:53:41 UTC (rev 52544)
@@ -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.
+
Property changes on: trunk/Master/texmf-dist/doc/latex/circledsteps/lppl-1-3c_license.txt
___________________________________________________________________
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: trunk/Master/texmf-dist/tex/latex/circledsteps/circledsteps.sty
===================================================================
--- trunk/Master/texmf-dist/tex/latex/circledsteps/circledsteps.sty (rev 0)
+++ trunk/Master/texmf-dist/tex/latex/circledsteps/circledsteps.sty 2019-10-27 20:53:41 UTC (rev 52544)
@@ -0,0 +1,72 @@
+% \begin{macrocode}
+\NeedsTeXFormat{LaTeX2e}[1996/06/01]
+\ProvidesPackage{circledsteps}[2019/06/19 v1.0 Circled steps that you can reference]
+% \end{macrocode}
+%
+% Copyright (c) 2019 Romano Giannetti
+% Heavily helped by @marmot and other on
+% https://tex.stackexchange.com/questions/7032/good-way-to-make-textcircled-numbers
+% License: LPPL 1.3c
+%
+% \begin{macrocode}
+\RequirePackage{pict2e}
+\RequirePackage{picture}
+\RequirePackage{pgfkeys} % for the pgfkeys
+\pgfkeys{/csteps/inner ysep/.initial=4pt,
+ /csteps/inner xsep/.initial=4pt,
+ /csteps/inner color/.initial=red,
+ /csteps/outer color/.initial=blue,
+}
+\newsavebox\csteps at CBox
+\newlength\csteps at XLength \newlength\csteps at YLength \newlength\csteps at YDepth \newlength\csteps at tmplen
+\def\csteps at CircledParam#1#2{\sbox\csteps at CBox{#2}%
+ \csteps at XLength=\wd\csteps at CBox\advance\csteps at XLength by\pgfkeysvalueof{/csteps/inner xsep}\relax
+ \csteps at tmplen=\pgfkeysvalueof{/csteps/inner ysep}\relax
+ \csteps at YDepth=\dp\csteps at CBox\advance\csteps at YDepth by 0.5\csteps at tmplen\relax
+ \csteps at YLength=\ht\csteps at CBox\advance\csteps at YLength by\dp\csteps at CBox\advance\csteps at YLength by\pgfkeysvalueof{/csteps/inner ysep}\relax
+ % \typeout{DBG:#2\space X:\the\csteps at XLength\space Y:\the\csteps at YLength\space D:\the\csteps at YDepth}%
+ \raisebox{-#1\csteps at YDepth}{%
+ \ifdim\csteps at XLength>\csteps at YLength
+ \makebox[\csteps at XLength]{% X bigger than Y
+ \makebox(0,\csteps at YLength){%
+ \color{\pgfkeysvalueof{/csteps/outer color}}\put(0,0){\oval(\csteps at XLength,\csteps at YLength)}%
+ }%
+ \makebox(0,\csteps at YLength){%
+ \put(-.5\wd\csteps at CBox,0){\textcolor{\pgfkeysvalueof{/csteps/inner color}}{#2}}%
+ }}%
+ \else
+ \makebox[\csteps at YLength]{%
+ \makebox(0,\csteps at YLength){%
+ \color{\pgfkeysvalueof{/csteps/outer color}}\put(0,0){\circle{\csteps at YLength}}%
+ }%
+ \makebox(0,\csteps at YLength){%
+ \put(-.5\wd\csteps at CBox,0){\textcolor{\pgfkeysvalueof{/csteps/inner color}}{#2}}%
+ }}%
+ \fi
+ }%
+}
+% \end{macrocode}
+% Main commands:
+% \begin{macrocode}
+\def\Circled#1{\csteps at CircledParam{1}{#1}}
+\def\CircledTop#1{\csteps at CircledParam{0}{#1}}
+\newcommand{\CircledText}[1]{%
+ \begingroup
+ \tikzset{/csteps/inner color=., /csteps/outer color=.}%
+ \Circled{#1}%
+ \endgroup
+}
+% \end{macrocode}
+% Automatic counters code
+% \begin{macrocode}
+\newcounter{cstepcnt}
+\newcommand{\startcstep}{\setcounter{cstepcnt}{0}}
+\newcommand{\resetcstep}{\setcounter{cstepcnt}{0}}
+\newcommand{\cstep}{%
+ \refstepcounter{cstepcnt}%
+ \Circled{\scriptsize\arabic{cstepcnt}}%
+}
+\renewcommand{\thecstepcnt}{\textbf{\arabic{cstepcnt}:}}
+% \end{macrocode}
+%
+%
Property changes on: trunk/Master/texmf-dist/tex/latex/circledsteps/circledsteps.sty
___________________________________________________________________
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Modified: trunk/Master/tlpkg/bin/tlpkg-ctan-check
===================================================================
--- trunk/Master/tlpkg/bin/tlpkg-ctan-check 2019-10-27 20:52:56 UTC (rev 52543)
+++ trunk/Master/tlpkg/bin/tlpkg-ctan-check 2019-10-27 20:53:41 UTC (rev 52544)
@@ -157,7 +157,7 @@
chicago chicago-annote chickenize childdoc chivo
chkfloat chletter chngcntr chordbars chordbox chronology
chronosys chs-physics-report chscite churchslavonic
- cinzel circ circuit-macros circuitikz
+ cinzel circ circledsteps circuit-macros circuitikz
cite citeall citeref cje cjhebrew cjk cjk-gs-integrate cjk-ko cjkpunct
classics classpack classicthesis
cleanthesis clearsans clefval cleveref clipboard
Added: trunk/Master/tlpkg/tlpsrc/circledsteps.tlpsrc
===================================================================
Modified: trunk/Master/tlpkg/tlpsrc/collection-latexextra.tlpsrc
===================================================================
--- trunk/Master/tlpkg/tlpsrc/collection-latexextra.tlpsrc 2019-10-27 20:52:56 UTC (rev 52543)
+++ trunk/Master/tlpkg/tlpsrc/collection-latexextra.tlpsrc 2019-10-27 20:53:41 UTC (rev 52544)
@@ -164,6 +164,7 @@
depend chngcntr
depend chronology
depend circ
+depend circledsteps
depend classics
depend classpack
depend clefval
More information about the tex-live-commits
mailing list