>>>>> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> On Fri, Aug 09, 2002 at 03:37:37PM +0200, Herbert Voss wrote:
>> this loads by default the _official_ latex fixes, which will never
>> get in the latex source.
John> Does this make any difference to any "normal" users who wouldn't
John> know how to load the fixes ?
For reference, here is the list of fixes. I've never had a problem
with any of these.
JMarc
% \subsection{2-col: 1-col fig can come before earlier 2-col fig
% (pr/2346)}
%
%\begin{verbatim}
% >Number: 2346
% >Category: latex
% >Synopsis: 2-col: 1-col fig can come before earlier 2-col fig
% >Arrival-Date: Wed Dec 18 15:41:07 1996
% >Originator: [EMAIL PROTECTED] (bil kleb)
% >Description:
% as documented in lamport's book, p. 198, concerning figure
% placement, "a figure will not be printed before an earlier
% figure, and a table will not be printed before an earlier
% table." however, there is a footnote stating, "However,
% in two-column page style, a single-column figure can come before
% an earlier double-column figure, and vice versa."
%
% this twocolumn behavior is undesireable---at least by me and
% most professional organizations i publish in. ed snyzter developed
% a hack fix for 2.09 several years ago which links the two
% counters, but i have not run across a similar "fix" for 2e...
% \end{verbatim}
[...]
% \subsection{Wrong headline for twocolumn (pr/2613)}
%
%\begin{verbatim}
% >Number: 2613
% >Category: latex
% >Synopsis: wrong headline for twocolumn
% >Arrival-Date: Mon Sep 22 16:41:09 1997
% >Originator: [EMAIL PROTECTED] (Daniel Reischert)
% >Description:
% When setting the document in two columns
% the headline shows the top mark of the second column,
% but it should show the top mark of the first column.
% \end{verbatim}
[...]
% \subsection{\texttt{\textbackslash @} discards spaces when moving
% (pr/3039)}
%
%\begin{verbatim}
% >Number: 3039
% >Category: latex
% >Synopsis: \@ discards spaces when moving
% >Arrival-Date: Sat May 22 09:01:06 1999
% >Originator: [EMAIL PROTECTED] (Donald Arseneau)
% >Description:
% The \@ command expands to \spacefactor\@m in auxiliary files,
% which then ignores following spaces when it is reprocessed.
%\end{verbatim}
%
% \subsection{\texttt{\textbackslash setlength} produces error if
% used with registers like \texttt{\textbackslash dimen0} (pr/3066)}
%
%\begin{verbatim}
% >Number: 3066
% >Category: latex
% >Synopsis: \setlength{\dimen0}{10pt}
% >Arrival-Date: Tue Jul 6 15:01:06 1999
% >Originator: [EMAIL PROTECTED] (Heiko Oberdiek)
% >Description:
% The current implementation of \setlength causes an error,
% because the length specification isn't terminated properly.
% More safe:
% \def\setlength#1#2{#1=#2\relax}
%\end{verbatim}
%
% \subsection{\texttt{\textbackslash addpenalty} ruins flush-bottom (pr/3073)}
%
%\begin{verbatim}
% >Number: 3073
% >Category: latex
% >Synopsis: \addpenalty ruins flush-bottom
% >Arrival-Date: Sat Jul 17 05:11:05 1999
% >Originator: [EMAIL PROTECTED] (Donald Arseneau)
% >Description:
% Just to keep in mind for further development eh?
% A page break at an \addpenalty after \vspace does *not*
% give a flush-bottom page. (The intent of \addpenalty is
% apparently just to preserve the flush bottom by putting
% the breakpoint `above' the skip.)
%\end{verbatim}
%
