Open jfine2358 opened 1 year ago
Thanks for the report!
Indeed, the \date{\today}
issue is a general problem with re-typesetting arXiv articles. I have considered completely disabling \today
in ar5iv, to avoid this mishap, which is the easiest direction of improvement.
\today
for each individual article. Indeed it is technically possible, as an add-on metadata service that precedes the main conversion pass (both for PDF and HTML).Figure 1 is a postscript file which appears to have failed to convert with our use of imagemagick.
The quoted expression is indeed not parsed by the current grammar. Upon "zooming in" the details, one spots:
[(e+(...)+(...)]
where the leftmost paren before the e
is never closed - making the full expression unbalanced/ill-formed.
I will keep the issue open at least until we can resolve the \today
question in some way.
Exact location of issue
https://arxiv.org/abs/1001.1015 https://ar5iv.labs.arxiv.org/html/1001.1015 https://ar5iv.labs.arxiv.org/log/1001.1015
This arises from #347. I used the https://ar5iv.labs.arxiv.org/feeling_lucky to retrieve this article.
I report three issues. For clarity, this is for information only. I'm not requesting that these issues be fixed.
Date mismatch.
(December 15, 2022)
as the article date.HTML shows Figure 1 as a black box.
Use of
$$ ... $$
repeated about 20 times in LaTeX source gives rise to a single MathParser error.Further information
The value of the
\year, \month, \day
can be set via TeX's command line, in a way that overrides the system provided values. This is a way to resolve (1) above.