3 ms·
Hi, an arXiv HTML Papers developer here. As a very brief update - we are pending a larger update. You will spot many (many) issues with our current coverage a
by dginev 10mo ago
Hi, an arXiv HTML Papers developer here.
As a very brief update - we are pending a larger update.
You will spot many (many) issues with our current coverage and fidelity of the paper rendering. When they jump at you, please report them to us. All reports from the last 2 years have landed on github. We have made a bit of progress since, but there are (a lot of) more low-hanging fruit to pick.
Project issues:
https://github.com/arXiv/html_feedback/issues/ https://github.com/arXiv/html_feedback/issues/
The main bottleneck at the moment is developer time. And the main vehicle for improvements on the LaTeX side of things continues to be LaTeXML. Happy to field any questions.
- istillwritecode 10mo agoI would like to write code for latexml to translate a package but I found the documentation to be hard to understand. That might be what is holding developers back. I looked at this a year ago and gave up.
- dginev 10mo agoTell us what you would need described in a tutorial to be productive, as well as your background with the technologies involved (TeX/LaTeX, perl, XML, XSLT, HTML). Probably best as a new issue: https://github.com/brucemiller/LaTeXML/issues https://github.com/brucemiller/LaTeXML/issues It's a pretty deep rabbit hole, but I wholeheartedly agree most standard package support incantations should be easy and few to use.