summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/xlop/xlop-doc.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/xlop/xlop-doc.tex')
-rw-r--r--Master/texmf-dist/doc/generic/xlop/xlop-doc.tex39
1 files changed, 23 insertions, 16 deletions
diff --git a/Master/texmf-dist/doc/generic/xlop/xlop-doc.tex b/Master/texmf-dist/doc/generic/xlop/xlop-doc.tex
index 68dbdd3b871..396c09e141d 100644
--- a/Master/texmf-dist/doc/generic/xlop/xlop-doc.tex
+++ b/Master/texmf-dist/doc/generic/xlop/xlop-doc.tex
@@ -179,7 +179,7 @@ Here is a table showing a \TeX{} compilation for a multiplication with
two operands of same size, on a linux computer, pentium~II~600 and
256~Mb RAM:\footnote{In fact it was the author computer in 2004. The
actual author computer is \emph{more} powerfull but the author is
- lazy, and he have not remake the tests!}
+ lazy, and he has not remake the tests!}
\begin{center}
\begin{tabular}{|l|*{6}{c|}}
\hline
@@ -234,7 +234,7 @@ following code show it:
\end{SideBySideExample}
\index{number!name}%
Note particullary that \verb+a/b_{^c}!&$+ and \verb+\prefix_{^c}!&$+
-produce exactly the same name\ldots{} obviously if \verb+\prefix+ have
+produce exactly the same name\ldots{} obviously if \verb+\prefix+ has
the right definition! This possibility to have a name using macro
could seem useless but it is not true. For instance, you can realize
loops\index{loop} with names as \verb+r1+, \verb+r2+, \ldots,
@@ -571,7 +571,7 @@ matching digit in the second operand.
The \parameter{deletezero} parameter is also a boolean parameter. It
indicates if non-significant zeros must be deleted or not. Its default
value is \texttt{true}. When this parameter is \texttt{false}, the
-operands and the result have the same number of digits. For that,
+operands and the result has the same number of digits. For that,
\package{xlop} package adds non-significant zeros. Also, the
non-significant zeros of operands are not removed.
\begin{SideBySideExample}
@@ -730,6 +730,12 @@ except when second factor has only one digit.
\opmul[displayintermediary=nonzero]{3.14159}{4}
\end{CenterExample}
+Finally, parameter \parameter{displayintermediary} accepts the value
+\texttt{None} which don't display any intermediary numbers in all cases.
+\begin{CenterExample}[xrightmargin=0pt]
+ \opmul[displayintermediary=None]{453}{1001205}
+\end{CenterExample}
+
The \parameter{hfactor} parameter indicates how align operands. The
default value, \texttt{right}, gives a raggedleft alignment. The
\texttt{decimal} value gives an alignment on dot.
@@ -759,11 +765,11 @@ The \package{xlop} package deals with ``normal'' division via
macro. Division is a very complex operation so it is not strange that
there are many parameters to control it.
-Pay attention that the \package{xlop} package v. 0.24 is unable to
-deal with ``english'' division. In this package version, the division
-is the ``french'' one, which is more or less used as it in some other
-countries. The \package{xlop} package v. 0.3 will allow ``enlish''
-division (and many more feautures).
+Pay attention that the \package{xlop} package v. \fileversion{} is
+unable to deal with ``english'' division. In this package version, the
+division is the ``french'' one, which is more or less used as it in
+some other countries. The \package{xlop} package v. 0.3 will allow
+``enlish'' division (and many more feautures).
\subsection{End Control}
\label{subsec:Controle de l'arret}
@@ -853,7 +859,7 @@ you obtain the warning message:
which indicates that this division period is~272 and that it can be
achieved because of the \texttt{safedivstep} value.
-The inline mode for division with period have some particularities.
+The inline mode for division with period has some particularities.
\begin{SideBySideExample}
\opdiv[period,style=text]{150}{7}
\end{SideBySideExample}
@@ -1203,7 +1209,7 @@ it can't be greater than \texttt{214748364} for
\macro{opdivperiod}. A warning is displayed for an overflow. Result is
put in the third parameter.
-There is also some checks on the two first parameters: a gcd mustn't
+There is also some checks on the two first parameters: a gcd must not
have null argument; length of period can't be processed with null
quotient. Futhermore, if an argument is a non integer number, only the
integer part will be take account.
@@ -1219,7 +1225,7 @@ mathematical details, square of prime numbers are good choices. For
instance with $257^2=66049$ you obtain:
\begin{SideBySideExample}
\opdivperiod{1}{66049}{p}%
- $\frac{1}{66049}$ have a period
+ $\frac{1}{66049}$ has a period
of length $\opprint{p}$.
\end{SideBySideExample}
@@ -1605,7 +1611,7 @@ expected.
\\\hline
\verb+\opdisplay[P]{S}{n}+ &
Display number \verb+n+ width style \verb+S+ puting each figure in a
- box which have a width of \verb+\opcolumnwidth+ and a height of
+ box which has a width of \verb+\opcolumnwidth+ and a height of
\verb+\oplineheight+. \\\hline
\verb+\opdiv[P]{n1}{n2}+ &
Display result of n1/n2. \\\hline
@@ -1886,7 +1892,8 @@ In this table, parameters:
Indicates the displayed operation behavior depending of
contry. Package \package{xlop} put forward only \verb+french+,
\verb+american+, and \verb+russian+ but these different ways to
- display operations aren't encoded in version 0.24. \\\hline
+ display operations aren't encoded in version
+ \fileversion{}. \\\hline
\verb+operandstyle+ &
&
Style for operands. \\\hline
@@ -2215,9 +2222,9 @@ braces. In this case, the simplest is to use \macro{opexport} macro
\chapter{Future Versions}
\label{chap:Versions futures}
-Version of \package{xlop} package is~0.24 which is only a debuging
-version of version~0.2, which is itself a correcting version of
-version~0.1 (first public release). The next release will be
+Version of \package{xlop} package is~\fileversion{} which is only a
+debuging version of version~0.2, which is itself a correcting version
+of version~0.1 (first public release). The next release will be
version~0.3 and its ``stable'' version will be version~0.4.
The features of version~0.3 aren't definitively fixed but there are