From: Victor Hupay <impoorbuthappy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Export to a specific file format (APA)
Date: Sat, 13 Jan 2018 10:22:52 -0800 (PST) [thread overview]
Message-ID: <6d26685a-20a6-439b-815e-9b43c8d36ec9@googlegroups.com> (raw)
In-Reply-To: <0add799b-37f4-4180-837a-e6958040178d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2221 bytes --]
Thank you so much. This solves my issue explicitly. Exactly what I needed.
Best,
Victor
On Saturday, January 13, 2018 at 12:02:49 PM UTC-5, Mikolaj Machowski wrote:
>
> Quoting from manual:
>
> --reference-doc=*FILE*
>
> Use the specified file as a style reference in producing a docx or ODT
> file.
>
> For best results, the reference docx should be a modified version of a
> docx file produced using pandoc. The contents of the reference docx are
> ignored, but its stylesheets and document properties (including margins,
> page size, header, and footer) are used in the new docx. If no reference
> docx is specified on the command line, pandoc will look for a file
> reference.docx in the user data directory (see --data-dir). If this is
> not found either, sensible defaults will be used.
>
> To produce a custom reference.docx, first get a copy of the default
> reference.docx: pandoc --print-default-data-file reference.docx >
> custom-reference.docx. Then open custom-reference.docx in Word, modify
> the styles as you wish, and save the file. For best results, do not make
> changes to this file other than modifying the styles used by pandoc:
> [paragraph] Normal, Body Text, First Paragraph, Compact, Title, Subtitle,
> Author, Date, Abstract, Bibliography, Heading 1, Heading 2, Heading 3,
> Heading 4, Heading 5, Heading 6, Heading 7, Heading 8, Heading 9, Block
> Text, Footnote Text, Definition Term, Definition, Caption, Table Caption,
> Image Caption, Figure, Captioned Figure, TOC Heading; [character] Default
> Paragraph Font, Body Text Char, Verbatim Char, Footnote Reference,
> Hyperlink; [table] Table.
>
>
>
--
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/6d26685a-20a6-439b-815e-9b43c8d36ec9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2943 bytes --]
prev parent reply other threads:[~2018-01-13 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 16:40 Victor Hupay
[not found] ` <78011305-5431-4838-b3a0-dbb33319fde0-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-13 17:02 ` Mikolaj Machowski
[not found] ` <0add799b-37f4-4180-837a-e6958040178d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-13 18:22 ` Victor Hupay [this message]
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=6d26685a-20a6-439b-815e-9b43c8d36ec9@googlegroups.com \
--to=impoorbuthappy-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).