public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: "Rached A." <rached.al-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Equation numbers and newlines not rendering as I expect in docx generated from LaTeX
Date: Mon, 28 Jun 2021 10:12:13 -0700	[thread overview]
Message-ID: <m2im1xncb6.fsf@MacBook-Pro-2.hsd1.ca.comcast.net> (raw)
In-Reply-To: <d9a2ff0a-7f05-4ee6-b5c4-cb650fcc66a5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Equation labels and references are not yet supported in the latex
reader.  You could submit an issue for this so we can track it.
It's a bit complex; we need to do conversions among multiple
math formats, and they all have their own way of doing
references. In addition, texmath (which does the equation
conversion) doesn't have access to all the information pandoc
has about references.

Another relevant issue is
https://github.com/jgm/pandoc/issues/2851

"Rached A." <rached.al-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Dear community,
>
> The following latex markup renders as expected in in overleaf:
>
> Here is equation \ref{eq:test}
> \begin{equation} \label{eq:test}
>     \begin{split}
>         a & = b \\
>         & = c
>     \end{split}
> \end{equation}
>
> Roughly looking like this in the complied pdf:
>
> Here is equation 9
> a = b
>                         (9)
>   = c
>
> When I try converting the .tex file to .docx using pandoc as shown below, 
> three problems arise:
>
> 1. The equation is not referenced properly in the paragraph. It looks like 
> this in the docx:
> Here is equation [eq:test]
>
> 2-3. The equation itself is not labelled with a number AND there is no 
> newline in the equation. It looks like this in the docx:
> a = b = c
>
> This is the command I ran to perform the conversion:
> pandoc main.tex --filter /usr/local/bin/pandoc-crossref -C --csl 
> ./springer-basic-brackets --bibliography=mybib.bib -N --wrap=preserve -o 
> mydoc.docx
>
> pandoc 2.14.0.2
> pandoc-crossref 0.3.12.0
>
> Could someone kindly point me in the right direction to resolve this issue?
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/d9a2ff0a-7f05-4ee6-b5c4-cb650fcc66a5n%40googlegroups.com.


      parent reply	other threads:[~2021-06-28 17:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-26 19:25 Rached A.
     [not found] ` <d9a2ff0a-7f05-4ee6-b5c4-cb650fcc66a5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-26 21:40   ` Rached A.
2021-06-28 17:12   ` John MacFarlane [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2im1xncb6.fsf@MacBook-Pro-2.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=rached.al-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).