Open FrankMittelbach opened 2 years ago
Maybe I'm missing something, but the output with v2.2 (oldest version that supports a second optional argument that I could find) and v2.7 seems to be the same (TL 2018 and 2022). This:
\documentclass{article}
\usepackage
% [nopar]
{lipsum}
\begin{document}
\fmtversion --- \csname ver@lipsum.sty\endcsname\par
\small
\lipsum [1][1-4]¶
\lipsum*[2][1-3]
\lipsum [3][1-2]¶
\lipsum [4][1-3]¶
\ldots
\end{document}
with TL 2018 gives:
and with LT 2022:
The only difference is a line break on line 7 of the output PDF, but that's because on v2.7 lipsum
uses latin hyphenation patterns (ul-lam-cor-per
with english hyphenation vs ul-la-m-cor-per
with latin).
maybe you are missing nothing and it is broken since 2018, but the documentation still states that \lipssum
and \lipssum*
differ in whether or not they issue a \par
or a space
and that nopar
swaps the behavior.
It it was certainly the case when I wrote the documentation for it (which is unfortunately that long ago :-( ). Looks to me as if the star form doesn't have any effect at all any more and perhaps that's since 2018.
Also, the corresponding package kantlipsum has exactly that behavior (i.e., if you replace \lipsum
with \kant
).
That's true for \lipsum
with one optional argument. With two optional arguments it runs in "sentence mode", outputting a range of sentences, and ending with a \par
would not allow hello \lipsum[1][1] world
, so I think it's the right default.
You can do \setlipsum{sentence-after=\par}
to make it add a \par
at the end.
According to the documentation (and past behavior)
\lipsum
issued a\par
and\lipsum*
a space and the other way around if the optionnopar
is used. Neither seems to be the case any more:Breaks the TLC3 documentation on that package :-(