Open manueldeprada opened 10 months ago
Thanks for the report! As you say, this could be a useful test to keep in mind when working on latexml enhancements for pgfplots.
Two additions to the issue: forest.sty
and linguex.sty
are reported as missing packages in the log. Possibly those are separate enhancements from the pgfplots issue, but bookkeeping for completeness.
Quick update here: if we disable the customizations in pgfutil-common.tex.ltxml
for \pgfutil@in@
and \ifpgfutil@in@
the reason for the Fatal error is addressed, and the article converts to a healthy Warning status.
There are some other issues to address (a curious --0.5
offender in pgfmath, and a vertical overflow in height for Figure 1), and the missing files I mentioned in the previous comment.
But we can resolve the Fatal with very little pain it looks like.
Thanks for the hard work!! Is there any "nightly ar5iv" url where we can see the result of latest commits?
"nightly ar5iv" is not really the timescale we are working on - I am afraid we are not yet in a position to rerender articles on demand at all, let alone nightly. Also our team is small, so most nights there are no meaningful changes for the vast majority of articles.
The commits I mentioned are not yet in latexml proper, the PR there is a draft, which will likely get merged by the end of this month. We have a scheduled v0.8.8 release of latexml soon after, which we have been wrapping up since summer.
Once we have v0.8.8 I will reconvert the entire corpus and sync up with the live ar5iv site, then walk issues which have been resolved and close them. So you won't see the improvement until at least early 2024, as a full rerun on our current hardware takes about 3 weeks of runtime.
What can be done overnight - naturally - is to install a local latexml at a newly changed commit, then reconvert a specific article locally. That is one of the reasons I made ar5ivist, so that people who don't want to wait on ar5iv updates have an easy alternative course of action.
"nightly ar5iv" is not really the timescale we are working on - I am afraid we are not yet in a position to rerender articles on demand at all, let alone nightly. Also our team is small, so most nights there are no meaningful changes for the vast majority of articles.
The commits I mentioned are not yet in latexml proper, the PR there is a draft, which will likely get merged by the end of this month. We have a scheduled v0.8.8 release of latexml soon after, which we have been wrapping up since summer.
Once we have v0.8.8 I will reconvert the entire corpus and sync up with the live ar5iv site, then walk issues which have been resolved and close them. So you won't see the improvement until at least early 2024, as a full rerun on our current hardware takes about 3 weeks of runtime.
What can be done overnight - naturally - is to install a local latexml at a newly changed commit, then reconvert a specific article locally. That is one of the reasons I made ar5ivist, so that people who don't want to wait on ar5iv updates have an easy alternative course of action.
Oh thanks! I will test my latex locally :). What a pity that a nice project like this does not have that much resources. This should be part of the future of arXiv!! Keep up the good work :)
This should be part of the future of arXiv!!
Well, that's the good news - it likely is! Keep your eyes open for an announcement soon, as ar5iv may be sunset when arXiv itself starts providing HTML in-house. Currently tracked at:
https://info.arxiv.org/about/accessible_HTML.html
On our end, we will keep pushing for 100% conversion coverage, since we are at 75% successful conversions today.
This article has healthy HTML with the latest ar5iv update to latexml v0.8.8.
One remaining issue is sizing of the resulting SVG figure in the Introduction, which has a pathologically large height of 22,000+
The rest of the article is still available, but one has to scroll for quite some time to reach it.
This file: https://ar5iv.labs.arxiv.org/html/2310.01693 fails to render completely. I have seen some other issues with pgfplots, most related to a infinite loop. This does not seem the case, it looks a totally different error.
Exact location of issue fig/test.tex :
Problem details
The log outputs:
@dginev , you seem to be tackling some pgfplots problems. Hope this helps! :)