public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Oliver Baumann <news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How to inject YAML-style metadata
Date: Fri, 30 Aug 2019 00:46:39 -0700 (PDT)	[thread overview]
Message-ID: <565694c1-c6b2-4903-97d8-90354a3acacf@googlegroups.com> (raw)
In-Reply-To: <71bf38c4-15ee-4b5d-9725-4695b04b799b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

 --metadata-file was *exactly *what I was looking for!

Suoer-many tahnks!


On Friday, August 30, 2019 at 5:23:52 PM UTC+10, mb21 wrote:
>
> If you're on macOS or Linux you can use the shell to concatenate the files 
> before feeding them to pandoc:
>
>     pandoc -t latex format.yaml input.md
>
> Alternatively, you can use:
>
>     pandoc --metadata-file format.yaml -t latex input.md
>
> On Friday, August 30, 2019 at 6:50:22 AM UTC+2, Oliver Baumann wrote:
>>
>> I write my Markdown files with a YAML header consisting only of metadata 
>> fields relating to the *content*, like title, author, etc.
>>
>> In another file format.yaml I have the YAML metadata applying to the 
>> *formatting*, like documentclass, font- or papersize.
>>
>> How can I inject format.yaml into pandoc, so that it is used when I 
>> convert my source to LaTeX? I'm looking for something like 
>> --include-in-header, but for YAML and injected before the template is 
>> set-up.
>>
>> Many thanks for any pointers!
>>
>>
>>

-- 
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/565694c1-c6b2-4903-97d8-90354a3acacf%40googlegroups.com.

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

      parent reply	other threads:[~2019-08-30  7:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30  4:50 Oliver Baumann
     [not found] ` <05a24a0b-9441-4aa4-8f07-84922a6c7196-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-30  7:23   ` mb21
     [not found]     ` <71bf38c4-15ee-4b5d-9725-4695b04b799b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-30  7:46       ` Oliver Baumann [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=565694c1-c6b2-4903-97d8-90354a3acacf@googlegroups.com \
    --to=news-wptjrydoupgeaopm6fajmqkbcandltla@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).