From: Phil <phillipruppert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Odd issue with pandoc generated docx and Microsof Word on macOS
Date: Tue, 19 Jul 2022 13:46:22 -0700 (PDT) [thread overview]
Message-ID: <c80ca91b-83b6-408c-bd56-7240e7530c6cn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1074 bytes --]
I use pandoc to convert markdown to docx. The docx file actually already
exists but is modified by pandoc to have the new content from the markdown
file.
If I then open the docx file in Microsoft Word, it shows the old version of
the docx and not the modified/updated content. Weird thing is that
Quicklook preview of the docx in Finder correctly shows the updated content
for the docx, and opening the docx with another rtf app like TextEdit also
shows the correct updated/modified content?
Has anyone else encountered this?
Word does eventually show the correct content if I quit Word after the
pandoc conversion but before opening the modified docx.
--
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/c80ca91b-83b6-408c-bd56-7240e7530c6cn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1424 bytes --]
reply other threads:[~2022-07-19 20:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c80ca91b-83b6-408c-bd56-7240e7530c6cn@googlegroups.com \
--to=phillipruppert-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).