summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/latex/curve2e/README.txt
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2020-01-05 23:11:08 +0000
committerKarl Berry <karl@freefriends.org>2020-01-05 23:11:08 +0000
commit81e3895f623a90cd9effa1316ff86721fac1c685 (patch)
treed3c47201908aa161db7c5994fbebd511146a09f9 /Master/texmf-dist/doc/latex/curve2e/README.txt
parent151d643febdfc2f4147d920463fec10668b03be9 (diff)
curve2e (6jan20)
git-svn-id: svn://tug.org/texlive/trunk@53331 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/latex/curve2e/README.txt')
-rw-r--r--Master/texmf-dist/doc/latex/curve2e/README.txt25
1 files changed, 15 insertions, 10 deletions
diff --git a/Master/texmf-dist/doc/latex/curve2e/README.txt b/Master/texmf-dist/doc/latex/curve2e/README.txt
index 84e7fecffbb..1d74851d13a 100644
--- a/Master/texmf-dist/doc/latex/curve2e/README.txt
+++ b/Master/texmf-dist/doc/latex/curve2e/README.txt
@@ -6,11 +6,11 @@
%%
%% curve2e.dtx (with options: `readme')
%%
-%% Copyright (C) 2005--2019 Claudio Beccari all rights reserved.
+%% Copyright (C) 2005--2020 Claudio Beccari all rights reserved.
%% License information appended
%%
File README.txt for package curve2e
- [2019-12-06 v.2.0.7 Extension package for pict2e]
+ [2020-01-05 v.2.0.8 Extension package for pict2e]
@@ -24,7 +24,9 @@ ltxdoc.cfg
curve2e.dtx is the documented TeX source file of file curve2e.sty; you
get curve2e.sty, curve2e.pdf, and curve2e-v161.sty by running pdflatex
on curve2e.dtx. The ltxdoc.cfg file customises the way the documentation
-file is typeset. This specific .cfg file is part of the ltxdoc package functionality and it is supposed to be configured for each specifica other bundle.
+file is typeset. This specific .cfg file is part of the ltxdoc package
+functionality and it is supposed to be configured for each specific
+other bundle.
README.txt, this file, contains general information.
@@ -41,7 +43,7 @@ slope, to draw arcs and curved vectors, to draw curves where just
the interpolating nodes are specified together with the slopes at
the nodes; closed paths of any shape can be filled with color; all
coordinates are treated as ordered pairs, i.e. 'complex numbers';
-coordinates may be expressed also in polar form.
+coordinates may be expressed also in polar form. Coordinates may be specified with macros, so that editing any drawing is rendered much simpler: any point specified with a macro is modified only once in the macro definition.
Some of these features have been incorporated in the 2011 version of
pict2e; therefore this package avoids any modification to the original
pict2e commands.
@@ -49,9 +51,12 @@ pict2e commands.
Curve2e now accepts polar coordinates in addition to the usual cartesian
ones; several macros have been upgraded and a new macro for tracing cubic
Bezier splines with their control nodes specified in polar form is
-available. The same applies to quadratic Bezier splines. The \multiput
+available. The same applies to quadratic Bezier splines. The multiput
command has been completely modified in a backwards compatible way, as
-to manipulate the increment components in a configurable way.
+to manipulate the increment components in a configurable way. A new
+xmultiput command has been defined that is more configurable than the
+original one; both \multiput and \xmultiput are backwards compatible with
+the original picture environment definition.
This version solves a conflict with package eso-pic.
@@ -71,10 +76,10 @@ have an older or a basic/incomplete installation of the TeX system,
such L3 functions might not be available. This is why this
package checks the presence of the developer interface; in case
such interface is not available it falls back to the previous version
-renamed curve2e-v161.sty, which is part of this bundle, and that must
-not be renamed in any way. The compatibility mentioned above implies
-that the user macros remain the same, but their implementation requires
-the L3 interface.
+renamed curve2e-v161.sty, which is part of this bundle; this order
+package name must not be modified in any way. The compatibility mentioned
+above implies that the user macros remain the same, but their
+implementation requires the L3 interface.
The package has the LPPL status of author maintained.