public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "rob...-5iOHWkcWBbejKv3TNrM5DQ@public.gmane.org" <robert-5iOHWkcWBbejKv3TNrM5DQ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: filters and ODT reference doc to generate letter from MD
Date: Fri, 23 Oct 2020 06:44:50 -0700 (PDT)	[thread overview]
Message-ID: <dc642f3b-8c29-4041-ac34-f2bfe42fe39an@googlegroups.com> (raw)


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


Dear all,

I explore the separation of layout and data to inspire my colleagues in a 
public institution.

I use markdown for the text and the YAML header for metadata like 
recipients etc.
I have a very nice output as a PDF (via latex already).

Now, I would like to take the same input and generate an ODT for e.g. last 
minute changes by the hierarchy.

I found already out that I can use in the reference.odt custom fields in 
the header and footer and that I can configure header and footer for 1st 
and other pages separately.

However, I still have a few problems. Can you advise me?


   1. How can I add programatically (like in latex) the closure and 
   signature text at the end of the text?
   2. How can I pass metadata fields with line breaks (recpient address) to 
   the odt? Custom fields do not keep line breaks.
   3. How can I pass metadata arrays/hashes to the odt? Currently, they are 
   not exported to custom fields.

I could of course avoid arrays and hashes, but this would remove much 
flexibility and the nice metadata structure.

Best,
Robert

-- 
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/dc642f3b-8c29-4041-ac34-f2bfe42fe39an%40googlegroups.com.

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

                 reply	other threads:[~2020-10-23 13:44 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=dc642f3b-8c29-4041-ac34-f2bfe42fe39an@googlegroups.com \
    --to=robert-5iohwkcwbbejkv3tnrm5dq@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).