-
-
Notifications
You must be signed in to change notification settings - Fork 251
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
LaTeX release of 2024-06-01 (or rather perhaps the array package update) appears to have broken tabulary #1368
Comments
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. |
@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 |
@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 |
Closing this here as it's being handled at https://github.com/davidcarlisle/dpctex |
@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. |
@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. |
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. |
A similar problem seems to have affected
I get the error message
Is the cause the same as for the problem reported here for |
@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.
|
I've since discovered that use of |
@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 |
@logological no work-around needed. The hotfix we sent to ctan yesterday and will in texlive hopefully tomorrow should repair this. |
@u-fischer: Thanks; I can confirm that kvafa/bidi#41 and kvafa/bidi#42 are no longer reproducible with |
@u-fischer: I have discovered further breakage with |
@logological You are jumping to conclusions here. Only because the previous issues were related to array and a recent LaTeX change doesn't mean that every issue is an "array breakage". For a problem with hyphenation it is actually quite improbable as no tabular is involved. You can easily check that the issue is not new: Get yourself an overleaf account and compile with e.g. texlive 2022 and you will see that nothing changed here; it is a clearly bidi problem, which inserts a |
@u-fischer You're right, of course -- I noticed three issues in rapid succession and wrongly assumed that the third was related to the first two. I'll test more thoroughly in the future. |
Brief outline of the bug
I noticed the latexbug message but from a user point of view the idea is that my report will reach the maintainers of the relevant packages as they are to the best of my knowledge all members of the LaTeX team, and it is hard for me to decide whether to report to tabulary or to array or to kernel because for that I would have to spend the time identifying the root cause. Thanks for your understanding.
Minimal example showing the bug
Log file (required) and possibly PDF file
testtabulary.log
The text was updated successfully, but these errors were encountered: