LaTeX release of 2024-06-01 (or rather perhaps the array package update) appears to have broken tabulary about latex2e HOT 16 CLOSED

Yes, the error is known. There is already a version with a fix in the tabulary repo https://github.com/davidcarlisle/dpctex and it will be uploaded to ctan soon.

from latex2e.

@u-fischer good that it is already fixed, I had very hastily checked https://github.com/davidcarlisle/dpctex and did not see there a ticket matching my issue... (doesn't seem to be davidcarlisle/dpctex#47

from latex2e.

@jfbu no the issue was reported by email so there isn't a github issue. Perhaps I should make one but I'm hoping to release a new version today anyway (still got a few things to test) and I may decide to try to fix
https://github.com/davidcarlisle/dpctex/issues?q=is%3Aissue+is%3Aopen+tabulary
at same time, plus add a rollback, so it may not get done today.

from latex2e.

Closing this here as it's being handled at https://github.com/davidcarlisle/dpctex

from latex2e.

@jfbu would it be possible for you to test your installations with the -dev release prior to the nominal date? This way such incompatibilities would be caught in time if we miss them because it is very hard for us to test all combinations even if something like tabulary is by an author of the LaTeX team? Would really help I think.

from latex2e.

@FrankMittelbach I usually do have such a set-up. I am aware of -dev. I do not alway work on same computers. I am not involved with LaTeX all year long. I may remain for months without doing any LaTeX. I became engaged in a project at end of May and was not paying attention to upcoming LaTeX release. The nature of the project already obliged me to complete my LaTeX installation as I do not have for reasons of disk space full TL. So in the end indeed that project does provide a test bed with about 800 documents but almost all of them are with packages not maintained by LaTeX team. If i had set-up my Makefile to use latex-dev this would have indeed helped find out about these problems. I will probably push a commit so that their project uses latex-dev. I can't do a similar thing in the Sphinx project I am involved with. People may have installations which are so old that latex-dev does not exist. We even test whether xcolor is there or not.

from latex2e.

I was not trying to critizise. It is just that the more the -dev formats are used in test suites the better, so whenever it is possible it is good to do so and helps ... sometimes it isn't.

from latex2e.

A similar problem seems to have affected nicematrix when used in combination with bidi. When I compile

\RequirePackage{latexbug}
\documentclass{article}

\usepackage{nicematrix}
\usepackage{bidi}

\begin{document}
\begin{NiceTabular}{lllll}
a & b & c & d & e \\
\end{NiceTabular}
\end{document}

I get the error message

! Extra alignment tab has been changed to \cr.
<template> \endtemplate 
                        
l.10 \end{NiceTabular}

foo.log

Is the cause the same as for the problem reported here for tabulary? (I already e-mailed the nicematrix maintainer about this, but thought I would ask here in case it's known that a similar fix needs to be applied to their package.)

from latex2e.

@logological imho the problem lies in the redefinitions of bidi, it overwrites most of the array definitions. You could try something like this, but it is quite possible that more corrections are needed.

\documentclass{article}

\usepackage{nicematrix}
\usepackage{bidi}
\makeatletter
\def\@tabarray{\@ifnextchar[{\@@array}{\@@array[c]}}
\makeatother%

\begin{document}
\begin{NiceTabular}{lllll}
a & b & c & d & e \\
\end{NiceTabular}
\end{document}

from latex2e.

I've since discovered that use of bidi now interferes with other tabular-like environments, including longtable. I can try reporting all this to the bidi maintainer.

from latex2e.

@u-fischer Thanks; that seems to work for me. Any chance you could suggest a similar workaround for kvafa/bidi#41? It looks like the bidi maintainer hasn't been active for about ten months, so I am not hopeful that they will release a fix soon.

from latex2e.

@logological no work-around needed. The hotfix we sent to ctan yesterday and will in texlive hopefully tomorrow should repair this.

from latex2e.