public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Oliver Baumann <news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Reference document for DOCX format doesn't seem to be picked up
Date: Thu, 13 Jun 2019 22:00:38 -0700 (PDT)	[thread overview]
Message-ID: <76d6d82c-5f95-47af-a3c8-96307ecd1ca2@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1062 bytes --]

I use pandoc (version 2.5) on Linux to convert Markdown to DOCX:

pandoc -s file.md -t docx --reference-doc=style-ref.docx  -o file.docx

I created the file style-ref.docx via pandoc 
--print-default-data-file=reference.docx  > style-ref.docx and then 
modified it in MS Word.

However the formatting changes saved to style-ref.docx do not seem to be 
applied to the result document.

What's going wrong? 

How can I debug this? Calling pandoc with --verbose doesn't give any more 
clues.


-- 
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/76d6d82c-5f95-47af-a3c8-96307ecd1ca2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 2630 bytes --]

             reply	other threads:[~2019-06-14  5:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14  5:00 Oliver Baumann [this message]
     [not found] ` <76d6d82c-5f95-47af-a3c8-96307ecd1ca2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-06-14  5:56   ` John MacFarlane
     [not found]     ` <m2sgsc90cu.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-06-14  7:02       ` Oliver Baumann
     [not found]         ` <c1bb314e-7c5e-43d6-a5ef-05c7127b277f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-06-14 16:40           ` John MacFarlane
     [not found]             ` <m2woho9l2l.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-06-14 22:58               ` news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA
2019-06-21  7:23               ` Oliver Baumann
2019-06-24  9:01   ` Agustín Martín
     [not found]     ` <980be184-b406-42f3-bb6e-1b244fa51bc9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-06-26  5:31       ` Oliver Baumann

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=76d6d82c-5f95-47af-a3c8-96307ecd1ca2@googlegroups.com \
    --to=news-wptjrydoupgeaopm6fajmqkbcandltla@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).