summaryrefslogtreecommitdiff
path: root/macros/latex/contrib/tkz/tkz-base/doc/latex/TKZdoc-base-initialisation.tex
diff options
context:
space:
mode:
Diffstat (limited to 'macros/latex/contrib/tkz/tkz-base/doc/latex/TKZdoc-base-initialisation.tex')
-rw-r--r--macros/latex/contrib/tkz/tkz-base/doc/latex/TKZdoc-base-initialisation.tex10
1 files changed, 5 insertions, 5 deletions
diff --git a/macros/latex/contrib/tkz/tkz-base/doc/latex/TKZdoc-base-initialisation.tex b/macros/latex/contrib/tkz/tkz-base/doc/latex/TKZdoc-base-initialisation.tex
index b95c3e3fc6..6973481795 100644
--- a/macros/latex/contrib/tkz/tkz-base/doc/latex/TKZdoc-base-initialisation.tex
+++ b/macros/latex/contrib/tkz/tkz-base/doc/latex/TKZdoc-base-initialisation.tex
@@ -11,7 +11,7 @@ The following code gives an error
\end{tkzltxexample}
{\color{red} Latex Error: ... Dimension too large.}
-Indeed, the default unit is a centimeter or \TEX\ cannot store a dimension greater than 575 cm, which leads to an error. \TEX\ however, can store integers up to $2^{31}-1$, so it is possible to work on integers first and then define the dimensions.
+Indeed, the default unit is a centimeter but \TEX\ cannot store a dimension greater than 575 cm, which leads to an error. \TEX\ however, can store integers up to $2^{31}-1$, so it is possible to work on integers first and then define the dimensions.
\begin{tkzltxexample}[right margin=7cm]
\begin{tikzpicture}[x=0.01 cm]
@@ -22,7 +22,7 @@ Indeed, the default unit is a centimeter or \TEX\ cannot store a dimension great
{\color{red} Latex Error: ... Dimension too large.}
The previous code still makes an error. Indeed, 600 cm is a dimension
- and does not take into account the change of unit. Correct is:
+ and does not take into account the change of unit. The correct version is:
\begin{tkzltxexample}[right margin=7cm]
\begin{tikzpicture}[x=0.01 cm]
@@ -30,7 +30,7 @@ The previous code still makes an error. Indeed, 600 cm is a dimension
\end{tikzpicture}
\end{tkzltxexample}
-This time, the stored dimension is 6 cm which is acceptable. It is possible with \TEX\ to handle large whole numbers,but, on the other hand, the dimensions cannot exceed \numprint{16384} pt or approximately 5.75 m.
+This time, the stored dimension is 6 cm which is acceptable. It is possible with \TEX\ to handle large whole numbers, but, on the other hand, the dimensions cannot exceed \numprint{16384} pt or approximately 5.75 m.
With \TEX, it's also possible to work with the \tkzname{xfp} package. This allows him to work at longer intervals, but at the cost of a certain slowness. This is the method I have preferred for some sensitive calculations that require good precision, such as calculations to measure angles or segment length, but it is necessary once a number has been found to assign it to a dimension. We always find the same constraints.
@@ -72,12 +72,12 @@ All this makes little sense for Euclidean geometry, and in this case it is recom
I tried to generalize the following syntax:
\begin{itemize}
- \item The syntax is close to that of \LATEX, there's no need for "; "
+ \item The syntax is close to that of \LATEX, there's no need for ";" with \tkzname{tkz-base}.
\item all the macros have names beginning with \tkzname{tkz};
\item braces are used to pass a parameter that will be the reference of an object created by the macro;
\item parentheses are used to refer to an object that has already been created or to a coordinate pair;
\item square brackets are necessary to pass optional arguments or options, some choices are sometimes mandatory. The use of the comma even in a Math mode requires to be protected in a TeX group;
- \item blanks (space) are prohibited between [...] and (...), [...] and \{...\}, as well as between (...) and \{…\}, but it is possible to put spaces between past optional arguments [...].
+ \item blanks (space) are prohibited between [...] and (...), [...] and \{...\}, as well as between (...) and \{…\}, but it is possible to put spaces between passed in optional arguments [...].
\end{itemize}
\section{Initialization \tkzcname{tkzInit}}