[latex3-commits] [latex2e-public] r1330 - fixltx2e
noreply at latex-project.org
noreply at latex-project.org
Tue Jan 10 16:37:44 CET 2017
Author: carlisle
Date: 2017-01-10 16:37:43 +0100 (Tue, 10 Jan 2017)
New Revision: 1330
Modified:
trunk/doc/ltnews26.tex
Log:
fixltx2e
Modified: trunk/doc/ltnews26.tex
===================================================================
--- trunk/doc/ltnews26.tex 2017-01-10 15:03:56 UTC (rev 1329)
+++ trunk/doc/ltnews26.tex 2017-01-10 15:37:43 UTC (rev 1330)
@@ -137,6 +137,26 @@
this change will be undone if an earlier
release is specified using the \textsf{latexrelease} package.
+\section{The \textsf{fixltx2e} Package}
+As described in \LaTeX{} News~22, the \textsf{fixltx2e} package has become
+obsolete with the new update policy. Since 2015 it has just made a
+warning and exited. In this release we have re-introduced all
+the code from the original fixes in the 2014 \LaTeX\ but guarded by
+\verb|\IncludeInRelease{2015/01/01}|.
+So for current releases \textsf{fixltx2e} still just makes a warning
+but for old releases, whether that is an old format, or a format with
+the version date reset via the \textsf{latexrelease} package, the
+fixes in the original \textsf{fixltx2e} will be applied.
+
+This improves the ability to run old documents in a way compatible
+with contemporary formats. If you have a 2014 document that used
+\verb|\usepackage{fixltx2e}| and you add
+\verb|\RequirePackage[2014/01/01]{latexrelease}| and process it with the
+current format then \textsf{latexrelease} will undo most changes made
+since 2014, but now when the document includes \textsf{fixltx2e} it
+will act like a 2014 version of the package and apply the code fixes,
+not just give a warning that the package is obsolete.
+
\section{The \textsf{latexbug} package}
As explained in more detail
More information about the latex3-commits
mailing list