Open rrrnld opened 7 months ago
Thanks for the question @heyarne . An even better place for the issue would be the latexmls repository. Then again, since latexmlc is in latexml itself, maybe the current setup is OK as well.
A positive value for the --expire
option is all you should need to leverage a latexmls which is visible in the $PATH
.
For example, I can check with:
The issue is a helpful reminder to double-check latexmls with the v0.8.8 release of LaTeXML - I just updated a test case that had its XML markup move and will push a new latexmls on CPAN soon.
As to a POST request, the Example use section in the latexmls README should still have a functioning example. The key bit is to have format=jats
to emit JATS, but a lot of the other details may vary (e.g. if you'd like the output archived as a ZIP and streamed back via a web service, or written to the local drive instead).
Hi,
I'm having some trouble understanding how I can use
latexmls
to speed up compilation a bit. My understanding is that it allows me to do all the--preload
s once and havelatexmlc
communicate with it. Bothlatexmlc
andlatexmls
are on my path, and this is my current invocation:latexmls
is not started, everything is loaded on each invocation and I don't notice any speedup even on frequent subsequent conversions. I tried changing--expire
/--address
/--port
, startinglatexmls
manually, but still see the same behavior.My use-case is making small changes to different tex file until it is converted to a JATS that looks good. I think they could benefit quite a bit from the speedup.
Am I misunderstanding something? What do I have to do to get
latexmlc
to do the conversions withlatexmls
?Or if I want to skip
latexmlc
completely and managelatexmls
myself -- what would the POST body look like to convert the input tex (which can potentially\include
other tex files)?