summaryrefslogtreecommitdiff
path: root/graphics/pgf/base/doc/RELEASE_NOTES.md
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2020-12-26 03:02:09 +0000
committerNorbert Preining <norbert@preining.info>2020-12-26 03:02:09 +0000
commit7ae913a662e817e559620e1114b63e0f412ff2e3 (patch)
tree96a6fab8955d0a1a5632599d839a1006290a2930 /graphics/pgf/base/doc/RELEASE_NOTES.md
parent41eb4dfa0badd165fc762b85c3ba592b4e57d38a (diff)
CTAN sync 202012260302
Diffstat (limited to 'graphics/pgf/base/doc/RELEASE_NOTES.md')
-rw-r--r--graphics/pgf/base/doc/RELEASE_NOTES.md31
1 files changed, 28 insertions, 3 deletions
diff --git a/graphics/pgf/base/doc/RELEASE_NOTES.md b/graphics/pgf/base/doc/RELEASE_NOTES.md
index 677c2d0408..22437f3da7 100644
--- a/graphics/pgf/base/doc/RELEASE_NOTES.md
+++ b/graphics/pgf/base/doc/RELEASE_NOTES.md
@@ -1,9 +1,34 @@
+# BREAKING CHANGES
+
+If a topath is bent by any of the in=, out=, bend=, etc. options, a Bezier
+curve is constructed in the background. To infer the positions of the control
+points the start and end coordinate are converted to absolute coordinates.
+However, this has the effect that subsequent points on the path think that the
+endpoint of the topath was absolute which can lead to counter-intuitive path
+construction, e.g.
+```latex
+\draw (2,0) to[out=0,in=180] +(1,0) -- ++(0,-1) -- +(1,0);
+```
+If old code relies on this behavior, this drawing will silently break! Please
+open an issue if you rely on this.
+
# Bug fixes
-Another issue with the new LaTeX hook mechanism surfaced in the external
-library which is being worked around now.
+This release introduces a fix for path handling which concerns expansion of
+tokens on the path in particular with respect to conditional. Previously when
+the expansion of a conditonal resulted in a frozen \relax the parser would just
+give up. Now the parser will skip over the frozen \relax and continue to
+expand tokens. Whether this will result in a meaningful expansion is up to the
+user.
This release also includes other bug fixes. On GitHub you can click the commit
hashes and the issue numbers to get to the fix and the ticket, respectively.
-3c46a6974 #947
+a4c275704 #952
+8a997bbc1 #954
+8f37bca84 #962
+3cbe5a192 #844
+49e5f0a08 #654
+17a95e4c5 #966
+ad06895a6 #966
+79e613ae1 #966