From: Jesse Rosenthal <jrosenthal-4GNroTWusrE@public.gmane.org>
To: Nyoman Bennyamino
<nyoman.bennyamino-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: docx -> markdown & Citavi Content Control
Date: Tue, 12 Feb 2019 12:36:47 -0500 [thread overview]
Message-ID: <87o97gvrgw.fsf@jhu.edu> (raw)
In-Reply-To: <87d9e5ab-3b83-46cf-a538-a6f2308454d1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
The instructions are in `instrtext` inside `fldchar`, which we do
support (at least as far as parsing text). So this looks like a bug. It
would be great if you could submit it to the github issue tracker.
When you do sumbit a bug report, please make sure to note what version of
pandoc you're using (support for this was only added last year), as well
as a copy of your input docx.
--Jesse
Nyoman Bennyamino <nyoman.bennyamino-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Hello,
>
> I'd like to use pandoc to convert a MS Word 365 (*.docx) file to markdown.
> My reference management program (Citavi) is using Word Content Control
> fields to inject references into footnotes. Unfortunately, pandoc is
> omitting the all references instead of at least converting the references
> into plain text.
>
> For example:
>
> One of my footnote is: "92. See Author, New York 2018, p. 18"
>
> The source code for this footnote (from Word's footnotes.xml file):
>
> <w:footnote w:id="92"><w:p w14:paraId="315F39A7" w14:textId="2167C15F"
> w:rsidR="000B6667" w:rsidRDefault="000B6667"
> w:rsidP="00F42B65"><w:pPr><w:pStyle w:val="Funoten"/></w:pPr><w:r
> w:rsidRPr="002C10AE"><w:rPr><w:rStyle
> w:val="Funotenzeichen"/><w:b/><w:vertAlign
> w:val="baseline"/></w:rPr><w:footnoteRef/></w:r><w:r><w:t
> xml:space="preserve">
> </w:t></w:r><w:r><w:tab/></w:r><w:sdt><w:sdtPr><w:alias w:val="Don't edit
> this field"/><w:tag
> w:val="CitaviPlaceholder#ecdec0e6-4e94-491b-a6d1-74308e00ccd9"/><w:id
> w:val="827022648"/><w:placeholder><w:docPart
> w:val="B8F488EF9BC34FE5B5D83FE3A9CB28BD"/></w:placeholder></w:sdtPr><w:sdtContent><w:r><w:fldChar
> w:fldCharType="begin"/></w:r><w:r><w:instrText>ADDIN
> CitaviPlaceholder{ey....AifQ==}</w:instrText></w:r><w:r><w:fldChar
> w:fldCharType="separate"/></w:r><w:r w:rsidR="00BB051A"><w:t
> xml:space="preserve">*See* </w:t></w:r><w:r w:rsidR="00BB051A"
> w:rsidRPr="00BB051A"><w:rPr><w:smallCaps/></w:rPr><w:t>Author</w:t></w:r><w:r
> w:rsidR="00BB051A" w:rsidRPr="00BB051A"><w:t>*, **New York 2018*</w:t></w:r><w:r
> w:rsidR="00BB051A" w:rsidRPr="00BB051A"><w:rPr><w:vertAlign
> w:val="superscript"/></w:rPr><w:t>81</w:t></w:r><w:r w:rsidR="00BB051A"
> w:rsidRPr="00BB051A"><w:t>*, p. 18.*</w:t></w:r><w:r><w:fldChar
> w:fldCharType="end"/></w:r></w:sdtContent></w:sdt></w:p></w:footnote>
>
> Output after converting:
>
> pandoc -f docx "test.docx" -w markdown_strict --reference-location "block"
>
> "92. "
>
>
> Any ideas how to fix this?
>
>
> Thanks,
>
> Nyoman
>
> --
> 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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/87d9e5ab-3b83-46cf-a538-a6f2308454d1%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2019-02-12 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 16:31 Nyoman Bennyamino
[not found] ` <87d9e5ab-3b83-46cf-a538-a6f2308454d1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-02-12 17:14 ` John MacFarlane
2019-02-12 17:36 ` Jesse Rosenthal [this message]
[not found] ` <87o97gvrgw.fsf-4GNroTWusrE@public.gmane.org>
2019-02-12 18:47 ` Nyoman Bennyamino
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=87o97gvrgw.fsf@jhu.edu \
--to=jrosenthal-4gnrotwusre@public.gmane.org \
--cc=nyoman.bennyamino-Re5JQEeQqe8AvxtiuMwx3w@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).