diff options
author | Norbert Preining <norbert@preining.info> | 2022-10-13 03:01:48 +0000 |
---|---|---|
committer | Norbert Preining <norbert@preining.info> | 2022-10-13 03:01:48 +0000 |
commit | ba720f8eaac74c537fb16f8556e4cf0ab4cd8235 (patch) | |
tree | e6932ca49174877c4ef511fd5c01d614b988b449 /macros/latex/contrib/gensymb | |
parent | b9fbd9245255da7a36ca3b07890c471c708f7777 (diff) |
CTAN sync 202210130301
Diffstat (limited to 'macros/latex/contrib/gensymb')
-rw-r--r-- | macros/latex/contrib/gensymb/LICENSE | 416 | ||||
-rw-r--r-- | macros/latex/contrib/gensymb/README | 30 | ||||
-rw-r--r-- | macros/latex/contrib/gensymb/gensymb.dtx | 446 | ||||
-rw-r--r-- | macros/latex/contrib/gensymb/gensymb.ins | 8 | ||||
-rw-r--r-- | macros/latex/contrib/gensymb/gensymb.pdf | bin | 0 -> 220452 bytes |
5 files changed, 900 insertions, 0 deletions
diff --git a/macros/latex/contrib/gensymb/LICENSE b/macros/latex/contrib/gensymb/LICENSE new file mode 100644 index 0000000000..2244313901 --- /dev/null +++ b/macros/latex/contrib/gensymb/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/macros/latex/contrib/gensymb/README b/macros/latex/contrib/gensymb/README new file mode 100644 index 0000000000..233087075f --- /dev/null +++ b/macros/latex/contrib/gensymb/README @@ -0,0 +1,30 @@ +============================================================ + + gensymb – Generic symbols for both text and math mode + +============================================================ +Walter Schmidt + +Keiran Harcombe +kjh@harcombe.net + +This LaTeX package provides generic commands +\degree, \celsius, \perthousand, \micro and \ohm, which +work both in text and math mode. The package should +co-operate flawlessly with the well-known units.sty. +Various means are provided to fake the symbols or take +them from external symbol fonts, if they are not available +in the default fonts used in the document. The package +makes optionally use of upgreek.sty. + +The style files can be unpacked by running the particular +installation script (.ins) through LaTeX. The files will +be created immediately in the appropriate TDS directory +tex/latex/was, if this directory exists and the DOCSTRIP +tool is properly configured -- otherwise they are written +into the current directory. + +The documentation of a package can be generated by running +the particular .dtx file through LaTeX. + +==finis diff --git a/macros/latex/contrib/gensymb/gensymb.dtx b/macros/latex/contrib/gensymb/gensymb.dtx new file mode 100644 index 0000000000..8629a84f87 --- /dev/null +++ b/macros/latex/contrib/gensymb/gensymb.dtx @@ -0,0 +1,446 @@ +%\CheckSum{283} +% +% \iffalse +% +%% gensymb.dtx +% Copyright (c) 2005--2022 Walter Schmidt +% Copyright (c) 2022-- Keiran Harcombe +% +% 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 Keiran Harcombe +% +% This work consists of the files gensymb.dtx, gensymb.ins +% and the derived file gensymb.sty.% +% \fi +% +% \iffalse +% +%<*driver> +\ProvidesFile{gensymb.drv} +%</driver> +%<package>\ProvidesPackage{gensymb} + [2022/10 v1.0.1 (KJH)] +%<*driver> +\documentclass{ltxdoc} +\OnlyDescription +\usepackage{textcomp} +\CodelineNumbered +\begin{document} + \DocInput{gensymb.dtx} +\end{document} +%</driver> +% \fi +% +% \newcommand\Lopt[1]{\textsf{#1}} +% \let\Lpack\Lopt +% \GetFileInfo{gensymb.drv} +% +% \title{The \textsf{gensymb} package for \LaTeXe} +% \author{Walter Schmidt & Keiran Harcombe\thanks{{\ttfamily kjh@harcombe.net}}} +% \date{(\fileversion{} -- \filedate)} +% \maketitle +% \sloppy +% +% \section{The problem} +% Typesetting units of measurement with \LaTeX{} is sometimes difficult. +% Why? For instance, most (but no all) typefaces have an +% upright \textmu{} and also a degree symbol, but +% there is no obvious way to use these in math mode. On the other hand, +% an upright \textohm{} is part of all math fonts for \TeX, +% but most text fonts are lacking the corresponding \cmd{\textohm}. +% Thus, it is not only impossible to use the +% same notation in text and in formulas; +% depending on the fonts used, it may even be impossible to +% typeset units properly at all, if you are restricted to +% the means of `standard' \LaTeX. +% +% \section{The macro package} +% The \Lpack{gensymb} package provides a number of `generic' macros, +% which produce the same output in text and math mode: +% \begin{verse} +% \begin{tabular}{ccccc} +% \cmd{\degree} & +% \cmd{\celsius} & +% \cmd{\perthousand}& +% \cmd{\ohm} & +% \cmd{\micro} \\ +% \textdegree & +% \textcelsius & +% \textperthousand & +% \textohm & +% \textmu \\ +% \end{tabular} +% \end{verse} +% Thus, you can write, for instance: +% \begin{verse} +% |$ \lambda = 10.6\,\micro\mathrm{m} $|\\ +% |... a wavelength of 10.6\,\micro m| +% \end{verse} +% With the help of the package \Lpack{units}, you can even apply +% exactly the same notation in text and formulas: +% \begin{verse} +% |$ \lambda = \unit[10.6]{\micro m} $|\\ +% |... a wavelength of \unit[10.6]{\micro m}| +% \end{verse} +% +% Under normal circumstances you should use \Lpack{gensymb} in conjunction with +% the \Lpack{textcomp} package. In this case the above symbols +% are taken from a text font using the TS1 (text companion) +% encoding -- even in math. +% As a result, they will exhibit the style of the surrounding text or of the \cmd{\mathrm} +% alphabet, respectively. +% +% When \Lpack{textcomp} is \emph{not} used (for instance, because your text fonts +% are not available with TS1 encoding), +% the \Lpack{gensymb} package tries to emulate the above symbols +% using what is available in the math fonts. +% However, the symbols \textmu{} and \textperthousand{} cannot be faked, +% and the package will issue appropriate warning messages. +% The option \Lopt{upmu} is a workaround to provide at least the \textmu{} -- see below. +% +% The symbol \cmd{\ohm} is particular, too: Loading the \Lpack{textcomp} +% package does \emph{not ensure} that the text fonts actually include +% an \textohm. Unfortunately, many fonts don't. \LaTeX{} cannot detect this +% situation in advance, and the command \cmd{\ohm} will print some garbage +% then -- possibly without any error message. +% A workaround is to use the options \Lopt{Omega} or \Lopt{Upomega} +% described below. +% +% The default behavior of the \Lpack{gensymb} package can be modified +% using the following options: +% \begin{description} +% \item[\Lopt{upmu}] With this option, the \cmd{\micro} uses internally +% a math symbol with the name \cmd{\upmu}. +% The responsibility to provide this macro lies with you; for instance, +% load the package \Lpack{upgreek}\footnote{% +% available from the same CTAN directory as \Lpack{gensymb}} or use a set +% of math fonts which include an upright mu and make sure it is accessible as \cmd{\upmu}. +% This option is useful, +% when your text fonts are not available with TS1 (text companion) encoding, +% or when their \cmd{\textmu} is ugly or broken. The drawback is, +% that the style of this \textmu{} will not vary with the surrounding font. +% It is always upright roman, regardless of whether +% the surrounding text is sans serif, bold or whatever. +% +% \item[\Lopt{Omega}] makes \cmd{\ohm} always use the upright Greek Omega +% from the current math font, regardless of whether \Lpack{textcomp} is loaded. +% This makes sense, when there is no \textohm{} in your text font(s). +% The option works always, but the style of the Omega in text will +% not vary then. +% +% Various packages provide an option \Lopt{slantedGreek} to make +% uppercase Greek letters in formulas slanted. You may safely use +% this option in conjunction with the \Lopt{Omega} option of the package +% \Lpack{gensymb}: \cmd{\ohm} will be upright, though! +% +% \addtocounter{footnote}{-1} +% \item[\Lpack{Upomega}] A math symbol with the name \cmd{\Upomega} will +% be used to for the \cmd{\ohm}. +% The responsibility to provide this macro lies with you; for instance, +% load the package \Lpack{upgreek}\footnotemark. +% Again, the style of this \cmd{\ohm} in text never changes. +% The option may be useful, when the text font does not include a \cmd{\textomega} +% of its own and the mathematical \cmd{\Omega} is not a suitable substitute, +% for one reason or another. +% \end{description} +% +% \section{Examples} +% \subsection*{The optimum case} +% With text fonts providing \textmu{} as well as \textohm{} +% in the text companion encoding, the default behavior of +% \Lpack{gensymb} is appropriate. +% This holds, e.g., for the EC/TC fonts (i.e., Computer Modern with T1 +% and TS1 encoding), Palatino, Lucida Bright, the Fourier fonts, +% and most font families from MicroPress: +% \begin{verbatim} +% \usepackage[T1]{fontenc} +% \usepackage{textcomp} +% \usepackage{gensymb} +% \end{verbatim} +% +% \subsection*{The normal case} +% Many commercial text fonts have a correct `micro' symbol, but no Omega. +% In this case the package can be loaded with the \Lopt{Omega} option, +% to make sure that the mathematical Omega is used instead: +% \begin{verbatim} +% \usepackage[T1]{fontenc} +% \usepackage{textcomp} +% \usepackage{mathptmx} % for instance +% \usepackage[Omega]{gensymb} +% \end{verbatim} +% +% \subsection*{Using the `classical' CM fonts} +% When you are restricted to the classical Computer Modern fonts with +% OT1 encoding, you can still take the Omega from the math fonts, +% but you need to take the upright mu from an an extra font such as +% Euler Roman. +% Notice, however, that \cmd{\perthousand} is not made available. +% You may try \cmd{\permil} instead, which is provided in the +% WASY fonts. +% \begin{verbatim} +% \usepackage[Euler]{upgreek} +% \usepackage[Omega, upmu]{gensymb} +% \usepackage{wasysym} +% \let\perthousand=\permil +% \end{verbatim} +% +% \subsection*{A special case} +% Imagine that you are using the Bitstream Charter text fonts +% in conjunction with Euler-VM for math.\footnote{I do not actually +% recommend this combination\dots} +% Charter, like most typefaces from Bitstream, has a wrong mu symbol. +% The missing Omega could be taken from the math font (Euler), but it would not go well +% with Charter in a combination such as M$\Omega$. +% As a workaround, load the \Lpack{upgreek} package +% and take both \cmd{\micro} and \cmd{\ohm} from the `Adobe Symbol' font: +% \begin{verbatim} +% \usepackage[T1]{fontenc} +% \usepackage{textcomp} +% \usepackage{charter,eulervm} +% \usepackage[Symbol]{upgreek} +% \usepackage[Upomega, upmu]{gensymb} +% \end{verbatim} +% +% \section{Using \Lpack{gensymb} together with other packages} +% \begin{itemize} +% \item +% \Lpack{gensymb} goes well with the package \Lpack{units}, +% but it cannot be used in conjunction with the +% package \Lpack{SIunits}, because the latter has its own means to typeset +% prefixes. +% \item +% Using the package \Lpack{mathcomp} together with \Lpack{gensymb} +% is possible, if you need the additional `math companion' symbols. +% Both packages will use only one common math symbol font. +% \end{itemize} +% +% \section{Known deficiencies} +% The current version of the package does not work properly +% in conjunction with the LY1 font encoding. +% This will possibly be fixed in a future release, if there is an actual need. +% +% \StopEventually{} +% +% \section{Implementation} +% +% The options are implemented using switches: +% \begin{macrocode} +%<*package> +\newif\ifgns@Upomega +\newif\ifgns@Omega +\newif\ifgns@upmu +% \end{macrocode} +% \begin{macrocode} +\DeclareOption{Upomega}{\gns@Upomegatrue} +\DeclareOption{Omega}{\gns@Omegatrue} +\DeclareOption{upmu}{\gns@upmutrue} +\ProcessOptions\relax +% \end{macrocode} +% These are the generic commands: +% \begin{macrocode} +\newcommand\celsius{} +\newcommand\degree{} +\newcommand\ohm{} +% \end{macrocode} +% The following macros will be used later to actually define the generic commands. +% We start with a macro to fake \cmd{\degree} and \cmd{\celsius} and to generate +% a warning message for \cmd{\perthousand}: +% \begin{macrocode} +\def\gns@usefakedsymbols{% +\renewcommand{\degree}{\ensuremath{^\circ}} +\DeclareRobustCommand{\celsius}{% + \ifmmode^\circ\mathrm{C}\else$^\circ$C\fi} +\PackageInfo{gensymb}{% + Faking symbols for \protect\degree\space and \protect\celsius} +\PackageWarningNoLine{gensymb}{% + Not defining \protect\perthousand} +} +% \end{macrocode} +% The following macro sets up a SymbolFont for the text companion symbols to be +% used in math. If \cmd{\tcmu} is already defined, we assume that the +% \Lpack{mathcomp} package is already loaded, and that the `math companion' +% symbols need not be defined once again: +% \begin{macrocode} +\def\gns@setupmathcomp{% +\expandafter\ifx\csname tcmu\endcsname\relax + \DeclareSymbolFont{gns@font}{TS1}{\familydefault}{m}{n} + \ifx\mv@bold\@undefined\else + \SetSymbolFont{gns@font}{bold}{TS1}{\familydefault}{\bfdefault}{n} + \fi + \DeclareMathSymbol{\tccelsius}{\mathord}{gns@font}{137} % {'211} + \DeclareMathSymbol{\tcdegree}{\mathord}{gns@font}{176} % {'260} + \DeclareMathSymbol{\tcperthousand}{\mathord}{gns@font}{135} % {'207} + \DeclareMathSymbol{\tcmu}{\mathord}{gns@font}{181} % {'265} + \DeclareMathSymbol{\tcohm}{\mathord}{gns@font}{87} % {'127} + \PackageInfo{gensymb}{Math companion symbols declared} +\else + \PackageInfo{gensymb}{Math companion symbols found} +\fi +} +% \end{macrocode} +% A macro to define \cmd{\degree}, \cmd{\celsius} and \cmd{\perthousand} +% so as to use text companion symbols: +% \begin{macrocode} +\def\gns@usetcsymbols{% +\DeclareRobustCommand{\degree}{% + \ifmmode\tcdegree\else\textdegree\fi} +\DeclareRobustCommand{\celsius}{% + \ifmmode\tccelsius\else\textcelsius\fi} +\DeclareRobustCommand{\perthousand}{% + \ifmmode\tcperthousand\else\textperthousand\fi} +\PackageInfo{gensymb}{Using text companion symbols for % + \protect\degree, \protect\celsius\space and \protect\perthousand} +} +% \end{macrocode} +% A macro to define \cmd{\ohm} so as to use the math symbol \cmd{\Upomega}: +% \begin{macrocode} +\def\gns@useUpomega{% + \expandafter\ifx\csname Upomega\endcsname\relax + \PackageError{gensymb} + {You have requested the option Upomega,\MessageBreak + but the command \protect\Upomega\space is undefined} + {Load the upgreek package additionally and try again!} + \fi + \DeclareRobustCommand{\ohm}{\ifmmode\Upomega\else$\Upomega$\fi} + \PackageInfo{gensymb}{Using \protect\Upomega\space for \protect\ohm} +} +% \end{macrocode} +% A macro to define \cmd{\ohm} so as to use \cmd{\Omega} (or \cmd{\upOmega}, +% if it is provided): +% \begin{macrocode} +\def\gns@useOmega{% + \expandafter\ifx\csname upOmega\endcsname\relax + \DeclareRobustCommand{\ohm}{\ifmmode\Omega\else$\Omega$\fi} + \PackageInfo{gensymb}{Using \protect\Omega\space for \protect\ohm} + \else + \DeclareRobustCommand{\ohm}{\ifmmode\upOmega\else$\upOmega$\fi} + \PackageInfo{gensymb}{Using \protect\upOmega\space for \protect\ohm} + \fi +} +% \end{macrocode} +% A macro to define \cmd{\ohm} so as to use the text companion symbol: +% \begin{macrocode} +\def\gns@usetextohm{% + \DeclareRobustCommand{\ohm}{\ifmmode\tcohm\else\textohm\fi} + \PackageInfo{gensymb}{Using \protect\textohm\space for \protect\ohm} +} +% \end{macrocode} +% A macro to define \cmd{\micro} so as to use the math symbol \cmd{\upmu}: +% \begin{macrocode} +\def\gns@useupmu{% + \expandafter\ifx\csname upmu\endcsname\relax + \PackageError{gensymb} + {You have requested the option upmu,\MessageBreak + but the command \protect\upmu\space is undefined} + {Load the upgreek package additionally and try again!} + \fi + \DeclareRobustCommand{\micro}{\ifmmode\upmu\else$\upmu$\fi} + \PackageInfo{gensymb}{Using \protect\upmu\space for \protect\micro} +} +% \end{macrocode} +% A macro to define \cmd{\micro} so as to use the text companion symbol: +% \begin{macrocode} +\def\gns@usetextmu{% + \DeclareRobustCommand{\micro}{\ifmmode\tcmu\else\textmu\fi} + \PackageInfo{gensymb}{Using \protect\textmu\space for \protect\micro} +} +% \end{macrocode} +% A macro to issue a warning, if \cmd{\micro} cannot be made available: +% \begin{macrocode} +\def\gns@usenomu{% + \PackageWarningNoLine{gensymb}{% + Not defining \protect\micro} +} +% \end{macrocode} +% The actual work is executed AtBeginDocument, so that we can detect the +% presence of the \Lpack{textcomp} package and the availability of +% \cmd{\Upmu} and other commands, regardless of the sequence of loading the +% packages. +% \begin{macrocode} +\AtBeginDocument{% +% \end{macrocode} +% First, we check for \Lpack{textcomp}. If it is loaded, we set up the +% text companion symbols for use in math and define \cmd{\degree}, \cmd{\celsius} +% and \cmd{\perthousand} so that they use these. Otherwise, the symbols are faked +% as far as possible: +% \begin{macrocode} +\@ifpackageloaded{textcomp}{\gns@setupmathcomp\gns@usetcsymbols}% + {\gns@usefakedsymbols} +% \end{macrocode} +% Now we define \cmd{\ohm}. In case the options \Lopt{Upomega} +% or \Lopt{Omega} have been specified, behave acordingly. +% Otherwise, use the text companion symbol, if available. +% Default is to use the mathematical Omega: +% \begin{macrocode} +\ifgns@Upomega + \gns@useUpomega +\else +\ifgns@Omega + \gns@useOmega +\else +\@ifpackageloaded{textcomp}% + {\gns@usetextohm}% + {\gns@useOmega} +\fi\fi +% \end{macrocode} +% Next, define \cmd{\micro}. In case the option \Lopt{upmu} +% has been specified, behave acordingly. +% Otherwise, use the text companion symbol, if available. +% Default is not to provide \cmd{\micro} at all. +% \begin{macrocode} +\ifgns@upmu + \gns@useupmu +\else +\@ifpackageloaded{textcomp}% + {\gns@usetextmu}% + {\gns@usenomu} +\fi +% \end{macrocode} +% Finally, we destroy the commands that are no longer needed: +% \begin{macrocode} +\let\gns@usefakedsymbols\relax +\let\gns@setupmathcomp\relax +\let\gns@usetcsymbols\relax +\let\gns@useUpomega\relax +\let\gns@useOmega\relax +\let\gns@usetextohm\relax +\let\gns@useupmu\relax +\let\gns@usenomu\relax +\let\gns@usetextmu\relax +% \end{macrocode} +% \begin{macrocode} +} +%</package> +% \end{macrocode} +% +% The next line of code is only to prevent DocStrip from adding the +% character table to all modules: +% \begin{macrocode} +\endinput +% \end{macrocode} +% \Finale +%% \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 \~} +%% diff --git a/macros/latex/contrib/gensymb/gensymb.ins b/macros/latex/contrib/gensymb/gensymb.ins new file mode 100644 index 0000000000..fe37ed2d39 --- /dev/null +++ b/macros/latex/contrib/gensymb/gensymb.ins @@ -0,0 +1,8 @@ +% file gensymb.ins +\input docstrip +\usedir{tex/latex/contrib/gensymb} + +\generate{\file{gensymb.sty}{\from{gensymb.dtx}{package}}} + +\endbatchfile + diff --git a/macros/latex/contrib/gensymb/gensymb.pdf b/macros/latex/contrib/gensymb/gensymb.pdf Binary files differnew file mode 100644 index 0000000000..f0ab15cb81 --- /dev/null +++ b/macros/latex/contrib/gensymb/gensymb.pdf |