Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jats Conversion breaks References #870

Closed
Thanathan-k opened this issue Sep 4, 2017 · 8 comments
Closed

Jats Conversion breaks References #870

Thanathan-k opened this issue Sep 4, 2017 · 8 comments

Comments

@Thanathan-k
Copy link
Contributor

@Thanathan-k Thanathan-k commented Sep 4, 2017

After converting a arXiv document with LaTeXML and then with LaTeXMLpost into the Jats format the references are broken.

Example-Document: https://arxiv.org/abs/1708.08473

Problem: The references in the text still reference the old key (), however the key is deleted from the bibliography and only the xml:id is set as id.

@dginev
Copy link
Collaborator

@dginev dginev commented Sep 4, 2017

Thanks for the report!

Can you share with us the exact commands you ran, just so that we have a clear path to reproduce? Also feel free to attach the JATS document to this issue.

@Thanathan-k
Copy link
Contributor Author

@Thanathan-k Thanathan-k commented Sep 4, 2017

The commands I ran were:

latexml --destination=ManuscroptShutov_arXiv.xml ManuscroptShutov_arXiv.tex
latexmlpost --destination=ManuscroptShutov_arXiv_jats.nxml --format=jats ManuscroptShutov_arXiv.xml

The produced JATS document is:
https://gist.github.com/Thanathan-k/977d19f79a7f1e70d214dfb2632f8b14

@brucemiller
Copy link
Owner

@brucemiller brucemiller commented Sep 5, 2017

Hmm... I just ran the document through the current LaTeXML, and I'm getting, eg
<xref ref-type="bibr" rid="bib.bib39">[39]</xref> for \cite{Reiner}, and with the corresponding bibitem starting <ref id="bib.bib39"><mixed-citation>Reiner M....... I don't know if that's actually correct, but it's consistent, and different from what you got.

What version of LaTeXML are you running?

@dginev
Copy link
Collaborator

@dginev dginev commented Sep 5, 2017

[Syntax aside] Markdown reminder: using single ticks for inline code and triple-ticks for display style

code

works best.

@brucemiller
Copy link
Owner

@brucemiller brucemiller commented Sep 5, 2017

ok, but why does triple ticks not actually give display, unless it's on newlines?

@dginev
Copy link
Collaborator

@dginev dginev commented Sep 5, 2017

Markdown is a limited thing.

@dginev dginev added this to the LaTeXML-0.8.3 milestone Sep 5, 2017
@brucemiller
Copy link
Owner

@brucemiller brucemiller commented Oct 22, 2017

Not sure if there is a bug here or not; what is the markup that is expected?

@brucemiller
Copy link
Owner

@brucemiller brucemiller commented Nov 15, 2017

apparently it's ok, now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants