From: Robert Kingett <kingettspeaks-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: How to find original reference document on Windows?
Date: Sat, 14 Jan 2023 09:13:10 -0800 (PST) [thread overview]
Message-ID: <7fc5b33e-c240-4ee9-90ab-d4b695592a67n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1759 bytes --]
I am running the latest version of Windows 10, and I believe I'm having a
unique problem.
Firstly, the user data folder doesn't appear to exist. I type in, pandoc
--version, and then attempt to go to the user data output in that result,
but Windows can never find the directory.
I'm trying to convert my markdown manuscript into Proper manuscript format
as outlined here,
<https://www.autodidacts.io/convert-markdown-to-standard-manuscript-format-odts-docs-and-pdfs-with-pandoc/>
but pandoc keeps ignoring the reference file I put in the folder I did
find, which was in local.
Since Pandoc keeps ignoring the reference file, I figured I'd just edit the
existing reference file, and that is why I am, in part, trying to find the
default, existing, reference file.
The ouput works if I manually specify the reference file, like below, but
I'd love to not specify the reference file every time.
pandoc -s manuscript.md --reference-doc=book.docx --output manuscript.docx
so, I am looking for,
1. Find the actual user data folder because Windows is saying the one in
pandoc --version does not exist.
2. How to change the reference.docx file in the /.pandoc directory so the
above can be a bit more automated.
3. How to overwrite the existing reference.docx in the /.pandoc directory
with a new, custom-styled reference document..
--
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/7fc5b33e-c240-4ee9-90ab-d4b695592a67n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2295 bytes --]
reply other threads:[~2023-01-14 17:13 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=7fc5b33e-c240-4ee9-90ab-d4b695592a67n@googlegroups.com \
--to=kingettspeaks-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).