You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to report a quite aesthetically serious issue.
It appears that some length values of the package have not been correctly set, causing ugly misalignment between the two columns. Please see my question on TeX StackExchange for an example of output.
Let me quote a comment from an expert there:
the package does not make \textheight-\topskip a multiple of \baselineskip so every column of just text can not be set without underful box warnings, spaces around section headings are not given enough stretch to compensat a full baselineskip and so on
I have no idea how to fix this but I hope the developer can figure it out.
Best regards.
The text was updated successfully, but these errors were encountered:
\flushbottom makes all pages have exactly the height specified in the
geometry settings. this is impossible when the page height is not a
multiple of the height of one line of text (as is curently the case)
and there is no stretchable space. it is also impossible on the first
page when the page height minus the titlebox height is not a multiple
of the line height. this leads to the two columns ending at different
heights when latex can make one column fit the page height, but not
the other.
this commit removes \flushbottom. now the two columns always match,
and the underfull vbox errors are gone, but the page heights of the
different pages of the paper are not always the same. I think that
is probably fine. ideally, \textheight-\top and \titlebox should
both be multiples of \baselineskip.
Fixes#11
I would like to report a quite aesthetically serious issue.
It appears that some length values of the package have not been correctly set, causing ugly misalignment between the two columns. Please see my question on TeX StackExchange for an example of output.
Let me quote a comment from an expert there:
I have no idea how to fix this but I hope the developer can figure it out.
Best regards.
The text was updated successfully, but these errors were encountered: