From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: 'Madhukar Vissapragada' via pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: content deletion while converting tex to docx
Date: Thu, 10 Jun 2021 09:52:19 -0700 [thread overview]
Message-ID: <m2r1h9hdbw.fsf@Johns-Air.hsd1.ca.comcast.net> (raw)
In-Reply-To: <1bb3d18d-9e89-4b9d-8dba-8b4f91425cfan-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
This issue is relevant:
https://github.com/jgm/pandoc/issues/3034
I don't think we have any support yet for parsing properties
from docx (though we do generate them).
"'Madhukar Vissapragada' via pandoc-discuss"
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> writes:
> Hi team,
> when I am trying to convert a tex to docx there are some content deletions
> are taking place
> for the following tags
> ('keywords', 'institute', 'address', 'affiliation', 'email')
>
> I'm executing the following command from the command line
> pandoc input.tex -o pandoc_output.docx
>
> I request someone to help me out with this.
>
> Thank you,
> Madhukar
>
> --
> 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/1bb3d18d-9e89-4b9d-8dba-8b4f91425cfan%40googlegroups.com.
prev parent reply other threads:[~2021-06-10 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 5:56 'Madhukar Vissapragada' via pandoc-discuss
[not found] ` <1bb3d18d-9e89-4b9d-8dba-8b4f91425cfan-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-10 16:52 ` 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=m2r1h9hdbw.fsf@Johns-Air.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@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).