summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/latex/base/usrguide.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/latex/base/usrguide.tex')
-rw-r--r--Master/texmf-dist/doc/latex/base/usrguide.tex55
1 files changed, 14 insertions, 41 deletions
diff --git a/Master/texmf-dist/doc/latex/base/usrguide.tex b/Master/texmf-dist/doc/latex/base/usrguide.tex
index 42d5e401f8b..05fc93e7af0 100644
--- a/Master/texmf-dist/doc/latex/base/usrguide.tex
+++ b/Master/texmf-dist/doc/latex/base/usrguide.tex
@@ -142,7 +142,7 @@ arguments. The mandatory types
is read between two identical characters, which cannot be any of |%|, |\|,
|#|, |{|, |}| or \verb*| |. The verbatim argument can also be enclosed
between braces, |{| and |}|. A command with a verbatim argument will
- produce an error when it appears within an argument of another function.
+ produce an error when it appears within an argument of another command.
\item[\texttt{b}] Only suitable in the argument specification of an
environment, it denotes the body of the environment, between
|\begin|\marg{environment} and |\end|\marg{environment}. See
@@ -244,7 +244,7 @@ defined.
\item \cs{RenewDocumentCommand} will issue an error if \meta{cmd}
has not previously been defined.
\item \cs{ProvideDocumentCommand} creates a new definition for
- \meta{function} only if one has not already been given.
+ \meta{cmd} only if one has not already been given.
\item \cs{DeclareDocumentCommand} will always create the new
definition, irrespective of any existing \meta{cmd} with the
same name. This should be used sparingly.
@@ -619,7 +619,8 @@ Spaces are trimmed at each end of each item parsed.
The \texttt{E} argument type is somewhat special, because with a single
\texttt{E} in the command declaration you may end up with several
arguments in a command (one formal argument per embellishment token).
-Therefore, when an argument processor is applied to an \texttt{E}-type
+Therefore, when an argument processor is applied to an
+\texttt{e}/\texttt{E}-type
argument, all the arguments pass through that processor before being fed
to the \meta{code}. For example, this command
\begin{verbatim}
@@ -640,9 +641,9 @@ processed argument can be further processed using a mapping function
\NewDocumentCommand \foo {>{\SplitList{;}} m}
{\MappingFunction#1}
\end{verbatim}
-If only a single character \meta{token} is used for the split, any
-category code $13$ (active) character matching the \meta{token} will
-be replaced before the split takes place.
+If only a single character \meta{token} is used for the split, it will
+take account of the possibility that the \meta{token} has been made active
+(category code~$13$) and will split at such tokens.
Spaces are trimmed at each end of each item parsed. Exactly one set
of braces will be stripped if an entire item is surrounded by them,
i.e.~the following inputs and outputs result (each separte item as
@@ -658,11 +659,11 @@ a,{b}c ==> {a}{{b}c}
\end{verbatim}
\begin{decl}
- |\ProcessList| \arg{list} \arg{function}
+ |\ProcessList| \arg{list} \arg{cmd}
\end{decl}
To support \cs{SplitList}, the function \cs{ProcessList} is available
-to apply a \meta{function} to every entry in a \meta{list}. The
-\meta{function} should absorb one argument: the list entry. For example
+to apply a \meta{cmd} to every entry in a \meta{list}. The
+\meta{cmd} should absorb one argument: the list entry. For example
\begin{verbatim}
\NewDocumentCommand \foo {>{\SplitList{;}} m}
{\ProcessList{#1}{\SomeDocumentCommand}}
@@ -751,10 +752,10 @@ This facility should only be used when \emph{necessary}.
|\ProvideExpandableDocumentCommand| \arg{cmd} \arg{arg spec} \arg{code} \\
|\DeclareExpandableDocumentCommand| \arg{cmd} \arg{arg spec} \arg{code}
\end{decl}
-This family of commands is used to create a document-level \meta{function},
+This family of commands is used to create a document-level \meta{cmd},
which will grab its arguments in a fully-expandable manner. The
argument specification for the function is given by \meta{arg spec},
-and the function will execute \meta{code}. In general, \meta{code} will
+and the \meta{cmd} will execute \meta{code}. In general, \meta{code} will
also be fully expandable, although it is possible that this will
not be the case (for example, a function for use in a table might
expand so that \cs{omit} is the first non-expandable non-space token).
@@ -832,7 +833,7 @@ and the command call is aborted.
\subsubsection{Control sequence tokens}
-A control sequence (or control character) token is characterized by is
+A control sequence (or control character) token is characterized by
its name, and its meaning is its definition.
A token cannot have two different meanings at the same time.
When a control sequence is defined as delimiter in a command,
@@ -876,33 +877,6 @@ defined as
[As an aside: the code is written in \pkg{expl3}, so we don't have to
worry about spaces creeping into the definition.]
-\subsection{Access to the argument specification}
-
-The argument specifications for document commands and environments are
-available for examination and use.
-
-\begin{decl}
- |\GetDocumentCommandArgSpec| \arg{cmd} \\
- |\GetDocumentEnvironmentArgSpec| \arg{environment}
-\end{decl}
-These functions transfer the current argument specification for the
-requested \meta{cmd} or \meta{environment} into the token list
-variable \cs{ArgumentSpecification}. If the \meta{cmd} or
-\meta{environment} has no known argument specification then an error
-is issued. The assignment to \cs{ArgumentSpecification} is local to
-the current \TeX{} group.
-
-\begin{decl}
- |\ShowDocumentCommandArgSpec| \arg{cmd} \\
- |\ShowDocumentEnvironmentArgSpec| \arg{environment}
-\end{decl}
-These functions show the current argument specification for the
-requested \meta{cmd} or \meta{environment} at the terminal. If
-the \meta{cmd} or \meta{environment} has no known argument
-specification then an error is issued.
-
-
-
\section{Copying and showing (robust) commands and environments}
If you want to (slightly) alter an existing command you may want to
@@ -1211,8 +1185,7 @@ Upper- and lower-casing are well-understood in general conversation.
Titlecasing here follows the definition given by the Unicode Consortium: the
first character of the input will be converted to (broadly) uppercase, and the
rest of the input to lowercase. The full range of Unicode UTF-8 input can be
-supported, with the proviso that at present the characters set up with 8-bit
-engines match those available in standard input encodings (|T1|, |T2|, |LGR|).
+supported.
\begin{quotation}
\begin{tabular}{rl}
|\MakeUppercase{hello WORLD ßüé}| & \MakeUppercase{hello WORLD ßüé} \\