summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-pgfkeysfiltered.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-pgfkeysfiltered.tex')
-rw-r--r--Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-pgfkeysfiltered.tex14
1 files changed, 7 insertions, 7 deletions
diff --git a/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-pgfkeysfiltered.tex b/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-pgfkeysfiltered.tex
index b5c7e260432..be115418442 100644
--- a/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-pgfkeysfiltered.tex
+++ b/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-pgfkeysfiltered.tex
@@ -115,7 +115,7 @@ Remaining: `\remainingoptions'.
\end{command}
\begin{handler}{{.install key filter}|=|\meta{optional arguments}}
- This handler install a key filter. A key filter is a command key which sets the \TeX-boolean |\ifpgfkeysfiltercontinue|, that means a key with existing `|/.@cmd|' suffix. A simple example is a key filter which returns always true:
+ This handler installs a key filter. A key filter is a command key which sets the \TeX-boolean |\ifpgfkeysfiltercontinue|, that means a key with existing `|/.@cmd|' suffix. A simple example is a key filter which returns always true:
\begin{codeexample}[code only]
\pgfkeys{/foo/bar/true key filter/.code={\pgfkeysfiltercontinuetrue}}
\pgfkeys{/foo/bar/true key filter/.install key filter}
@@ -126,7 +126,7 @@ Remaining: `\remainingoptions'.
\pgfkeysfiltered{/my group/A1=a1, /my group/A2=a2,
/my group/B=b, /my group/C=c, /tikz/color=blue, /my group/A3=a3}
\end{codeexample}
- If a key filter requires more than one argument, you need to provide the complete argument listing in braces like |{{first}{second}}|.
+ If a key filter requires more than one argument, you need to provide the complete argument list in braces like |{{first}{second}}|.
You can also use |\pgfkeysinstallkeyfilter|\meta{full key}\meta{optional arguments}, it has the same effect.
@@ -167,7 +167,7 @@ Remaining options: `\remainingoptions'.
\subsubsection{Family Support}
-\pgfname supports a family concept: every option can be associated with (at most) one family. Families form loose key groups which are independent of the key hierarchy. For example, |/my tree/key1| can belong to family |/tikz|.
+\pgfname{} supports a family concept: every option can be associated with (at most) one family. Families form loose key groups which are independent of the key hierarchy. For example, |/my tree/key1| can belong to family |/tikz|.
It is possible to `activate' or `deactivate' single families. Furthermore, it is possible to set only keys which belong to active families using appropriate key filter handlers.
@@ -265,7 +265,7 @@ The family support is fast: if there are $N$ options in a key-value-list and the
\subsubsection{Other Key Filters}
There are some more key filters which have nothing to do with family handling.
\begin{key}{/pgf/key filters/is descendant of=\marg{path}}
- Install this key filter to process only options belonging to the key tree \marg{path}. It returns true for every key which has key path \marg{path}. It also returns true for any unknown key, that means unknown keys are processed using the standard unknown handlers of \pgfname.
+ Install this key filter to process only options belonging to the key tree \meta{path}. It returns true for every key whose key path is equal to \meta{path}. It also returns true for any unknown key, that means unknown keys are processed using the standard unknown handlers of \pgfname.
\begin{codeexample}[]
\pgfkeys{
/group 1/A/.code={(A:#1)},
@@ -326,7 +326,7 @@ There are some more key filters which have nothing to do with family handling.
\subsubsection{Programmer Interface}
\label{section-key-filter-api}%
\begin{plainenvironment}{{pgfkeysinterruptkeyfilter}}%
- Temporarily disables key filtering inside of the environment. If key filtering is not active, this has no effect at all.
+ Temporarily disables key filtering inside the environment. If key filtering is not active, this has no effect at all.
Please note that no \TeX-group is introduced.
\end{plainenvironment}
@@ -351,11 +351,11 @@ switch the key filter.
\end{command}
\begin{command}{\pgfkeysdeactivatefamily\marg{family name}}%
- Equivalent to |\pgfkeys{|\meta{family name}|/.dactivate family}|.
+ Equivalent to |\pgfkeys{|\meta{family name}|/.deactivate family}|.
\end{command}
\begin{command}{\pgfkeysactivatefamilies\marg{family list}\marg{deactivate macro name}}%
- Activates each family in \meta{family list} and creates a macro \meta{deactivate macro name} which de-activates each family in \meta{family list}.
+ Activates each family in \meta{family list} and creates a macro \meta{deactivate macro name} which deactivates each family in \meta{family list}.
\begin{codeexample}[code only]
\pgfkeysactivatefamilies{/family 1,/family 2,/family 3}{\deactivatename}
\pgfkeysfiltered{foo,bar}