-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tabu uses wrong box with longtable 4.14 and newer. #26
Comments
Got from tabu-issues-for-future-maintainer/tabu#26 More info at https://tex.stackexchange.com/questions/600724/dimension-too-large-after-recent-longtable-update Not tested with older Texlive
Is there a solution with if/fi for this patch being in a preamble of document being comaptible with older compilers (like the one from TexLive 2018)? Just to have document compilable without errors with old and new compilers. |
@Lenchik this issue has only been opened in case there is ever going to be a new maintainer for the package. The package is badly broken and I rather doubt that this will happen, so the only advice I can give you is not to use it. It is not as if it now has an issue, it had issues for a long time and they are just increasing. In my opinion it should be taken off the distributions. |
@Lenchik you can test for the date of a package with |
Is there any good guidance anywhere of what to do if working with old documents that use tabu and how to update them to something that does work? |
@TC-RAC remove tabu and rework the tabulars. How depends on their layout. Often tabu isn't really needed and you can use tabular, in other cases try tabularray. |
tabu уже давно не поддерживают и всякие обновления то и дело ломают проекты с ним. Примеры переделаны на tabularray пакет, который точно есть в TexLive 2023 и выше. Tabularray was suggested at tabu-issues-for-future-maintainer/tabu#26 (comment)
longtable has changed the internal box names, instead of
\@ne
is now uses\LT@gbox
. tabu must be adapted accordinglysee also https://tex.stackexchange.com/questions/600724/dimension-too-large-after-recent-longtable-update
The text was updated successfully, but these errors were encountered: