public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: I can't find default reference.docx in my system
Date: Sun, 06 Sep 2020 10:35:36 +0200	[thread overview]
Message-ID: <87eenfz4iv.fsf@zeitkraut.de> (raw)
In-Reply-To: <0781f908-8993-406d-b8b0-3e235aa6c9adn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Hi Alan,

Alan writes:

> I can't find default reference.docx in my system (Win 10) Or, I
> don't understand manual
> <https://pandoc.org/MANUAL.html#option--reference-doc>:
>
> * To produce a custom reference.docx, first get a copy of the default
> reference.docx: pandoc -o custom-reference.docx --print-default-data-file
> reference.docx. *

On many (most?) installations, pandoc's data files are not shipped
as separate entities. Instead, they are baked into the main
`pandoc` executable. The command mentioned in the manual extracts
the reference.docx from the pandoc executable and writes it into a
file (the argument to `-o`, in this case `custom-reference.docx`).

Does that help to clear things up a little?

--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124


  parent reply	other threads:[~2020-09-06  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-05 20:31 Alan
     [not found] ` <0781f908-8993-406d-b8b0-3e235aa6c9adn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-06  8:35   ` Albert Krewinkel [this message]
     [not found]     ` <87eenfz4iv.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2020-09-06 10:46       ` Alan Ford

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=87eenfz4iv.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).