From: Matt Jolly <kangie-S+5N7tjWkgv8X0x+8FA6VA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Docx / OpenDocument output based on template
Date: Mon, 12 Apr 2021 20:56:57 -0700 (PDT) [thread overview]
Message-ID: <55062ea0-a237-4835-860b-e4ca5290e5cdn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1635 bytes --]
Hi All,
I've been working on implementing a 'word processor' compatible output from
the Markdown source that I'm using to build my existing LaTeX/PDF documents.
At this stage I've managed to implement styles, margins, header and footer,
etc by using a docx reference-doc, however I also need to implement some
branding (etc) to create a Title Page and some additional (templated)
content / pages prior to the document body (or ToC) preferably with the
ability to pull from document metadata.
Based on a look at the various writers and pandoc templates available it
doesn't seem like this is easily possible using docx in the same way as say
LaTeX, however there is a default.opendocument template; If my
understanding is corrrect this works in conjunction with a .odt
`--reference-doc` to produce output. Am I on the right track here, or does
odt output behave similarly to docx, only using the reference doc to inform
the output?
What would be the best way to implement something like this? Am I best off
attempting to use docx and implementing a filter to get my additional
content injected before the body, or is modifying the opendocument template
likely to be a better option?
Thanks for the advice!
--
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/55062ea0-a237-4835-860b-e4ca5290e5cdn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1969 bytes --]
next reply other threads:[~2021-04-13 3:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 3:56 Matt Jolly [this message]
[not found] ` <55062ea0-a237-4835-860b-e4ca5290e5cdn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-04-19 7:06 ` krulis....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
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=55062ea0-a237-4835-860b-e4ca5290e5cdn@googlegroups.com \
--to=kangie-s+5n7tjwkgv8x0x+8fa6va@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).