You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first Baseprint pilot user relies on a custom \orcid command that is probably not worth attempting to parse. In general, my hunch is LaTeXML trying to parse out orcid generally is too hard.
But this kind of data probably shouldn't even be in LaTeX source and perhaps should be handled as post-post processing of the JATS XML after LaTeXML.
So it seems fine to me if the proper way is add this data to JATS XML after LaTeXML is done, using some other tool. Or perhaps LaTeXML can do something clever.
The text was updated successfully, but these errors were encountered:
This might relate to #1648.
The first Baseprint pilot user relies on a custom
\orcid
command that is probably not worth attempting to parse. In general, my hunch is LaTeXML trying to parse out orcid generally is too hard.But this kind of data probably shouldn't even be in LaTeX source and perhaps should be handled as post-post processing of the JATS XML after LaTeXML.
Interestingly, Baseprint Pilot User One keeps this kind of data in a YAML file:
https://github.com/castedo/ten-years-challenge-pulsed-drive/blob/baseprint/article/metadata.yaml
and then has a Python script
https://github.com/castedo/ten-years-challenge-pulsed-drive/blob/baseprint/article/yaml-to-latex.py
convert it into a tex file to be included.
So it seems fine to me if the proper way is add this data to JATS XML after LaTeXML is done, using some other tool. Or perhaps LaTeXML can do something clever.
The text was updated successfully, but these errors were encountered: