[latex3-commits] [latex2e-public] r1324 - added some info about the advspace fix

noreply at latex-project.org noreply at latex-project.org
Mon Jan 9 19:14:10 CET 2017

Author: mittelba
Date: 2017-01-09 19:14:10 +0100 (Mon, 09 Jan 2017)
New Revision: 1324

added some info about the advspace fix

Modified: trunk/doc/ltnews26.tex
--- trunk/doc/ltnews26.tex	2017-01-09 16:12:31 UTC (rev 1323)
+++ trunk/doc/ltnews26.tex	2017-01-09 18:14:10 UTC (rev 1324)
@@ -84,7 +84,7 @@
 Unicode base hyphenation patterns in the format.  In practice this has
 not been a major problem as documents use the contributed
 \textsf{fontspec} package in order to switch to a
-Unicode encoded font..
+Unicode encoded font.
 In this release we are adding TU as a new supported
 encoding in addition to the previously supported encodings such as OT1
@@ -164,4 +164,39 @@
+\section{An addendum to the release changes in 2015}
+In 2015 we announced the introduction of the roll-back\slash
+roll-forward concept to manage bug fixes and additions to core
+\LaTeX{} in a manageable way for the user base. We also announced back
+then that we now incorporate all fixes from \textsf{fixltx2e} into the
+kernel (as the old mechanism produced problems instead of improving
+the situation). Refer to
+for details.
+One of the fixes from \textsf{fixltx2e} was for a glaring bug in
+\cs{addvspace} that was originally detected in the mid-nineties and
+back then added to the \textsf{fixltx2e} support package. In certain
+situations \cs{addvspace} would result in a page/column break below
+the baseline of the last line. As a result documents using
+\cs{flushbottom} would show a clear misalignment (even more prominent
+when typesetting in two-column mode).
+Starting with release 2015/01/01 this is now finally corrected already
+in the kernel and not only in \textsf{fixltx2e}. In nearly all
+circumstances this will either not make any difference to existing
+documents or if it does locally impove the visual appearence of that
+document. It is, however, by the nature of the change also possible
+that there are changes to the page breaks due to the different break
+positions introduced by the fix.
+Thus, for documents that have been written before 2015 and that should
+be preserved unchanged at all costs you may have to add
+at the top of the document, to roll back the format to a date before
+the policy change.

More information about the latex3-commits mailing list