From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/23335 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Oliver Baumann Newsgroups: gmane.text.pandoc Subject: How to inject YAML-style metadata Date: Thu, 29 Aug 2019 21:50:21 -0700 (PDT) Message-ID: <05a24a0b-9441-4aa4-8f07-84922a6c7196@googlegroups.com> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_333_1453741648.1567140621983" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="111122"; mail-complaints-to="usenet@blaine.gmane.org" To: pandoc-discuss Original-X-From: pandoc-discuss+bncBCEMPL7DTEMRBD6WULVQKGQEADZ4JSY-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Fri Aug 30 06:50:26 2019 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane.org Original-Received: from mail-oi1-f191.google.com ([209.85.167.191]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1i3Yrh-000SnZ-RS for gtp-pandoc-discuss@m.gmane.org; Fri, 30 Aug 2019 06:50:26 +0200 Original-Received: by mail-oi1-f191.google.com with SMTP id u10sf2372854oic.3 for ; Thu, 29 Aug 2019 21:50:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20161025; h=sender:date:from:to:message-id:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=9R6i63Ojz98+mwSblFvhrROpdxD1HPFZs/YO796e9s4=; b=g03ilDRNu5hsI0ftzayW3qEbunesZCpadd7Jso9kNfEyJ3BqdbKtkGLFgQY+QIcQOi aerKnS+PFEhMXEk48PvUD9ogUoT4E6OzL6aKKIZ6r+iXQjlS2fe5DMNb3OFw5jRPjZ8M 3fX5ue7PPK0J3/uEdySAdUGte47evv+gt3BX0iv6OZsSK183xBi3HxIAYxOMnnSzGm3D aWyQp8PiynmK+mTzHPAgnJjbxPajN6uWaZeY92AVzpYgw5RsgbpCSwP5NlTENjW55ofm OpspLMRtK4mVEBYPCFrRx8V5mmt2RX9AOZAeqT3OvM9IzfcpNYBiBhfo9uEOpf6VC5YB 2jyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=sender:x-gm-message-state:date:from:to:message-id:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=9R6i63Ojz98+mwSblFvhrROpdxD1HPFZs/YO796e9s4=; b=OeOtDkl7Fi95IsRFrKJ2W8QpnnuCV8rr2yaiPwFppyiv8rmSpbCKx9qguLrTzLU5kS ryZF4tcxlLret1F9WcaiN/u1N17LbTq3PvmEiS9io8HOoTUoq/QjEPmpuAHtYacd1g5g 65Xis54JEAH8vq/3yqQxn4nbwlm2D9DJQTu9wHSg4Eb5c4ZbWgJW4/fYZJjDZOd7tN16 TnUJ+PxTPemxq+z4cN4w7HCLNzimKEdBPHd+rE6eXi0QSbOQUdvsckwOLJRPmfg4rYTg Nfb4KCHpNisrqlqyUxURY3DnHf7wGDaGMyFbMTgwiWI0+aMC+Saes9Fv348pn6nwUplx TySg== Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Gm-Message-State: APjAAAXbz4zAUgblQreX7ce9euVMvtaquyLR7KQ3gp6Fjb+AlRqXhZL2 2BPFJQJJHgm3czG4NXomx5Y= X-Google-Smtp-Source: APXvYqx7MKJe6cP9Rbd/sJuiRODSI5Ev7t/fxDeIY2pSOk1WHetmjVDqsePy4Ka3T6U4A3Bf1BaZ0g== X-Received: by 2002:aca:d14:: with SMTP id 20mr8988436oin.114.1567140624186; Thu, 29 Aug 2019 21:50:24 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 2002:a9d:6250:: with SMTP id i16ls11739otk.1.gmail; Thu, 29 Aug 2019 21:50:22 -0700 (PDT) X-Received: by 2002:a9d:7754:: with SMTP id t20mr10439014otl.56.1567140622797; Thu, 29 Aug 2019 21:50:22 -0700 (PDT) X-Original-Sender: news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org Precedence: list Mailing-list: list pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; contact pandoc-discuss+owners-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-ID: X-Google-Group-Id: 1007024079513 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Xref: news.gmane.org gmane.text.pandoc:23335 Archived-At: ------=_Part_333_1453741648.1567140621983 Content-Type: multipart/alternative; boundary="----=_Part_334_535865968.1567140621984" ------=_Part_334_535865968.1567140621984 Content-Type: text/plain; charset="UTF-8" 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/05a24a0b-9441-4aa4-8f07-84922a6c7196%40googlegroups.com. ------=_Part_334_535865968.1567140621984 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I write my Markdown files with a YAML header consisting on= ly of metadata fields relating to the content, like title, author, e= tc.

In another file format.yaml I have the YAML metadata applying to the formatt= ing, 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 looki= ng for something like = --include-in-header, but for YAML and injected before the template i= s set-up.

Many thanks for any pointers!


--
You received this message because you are subscribed to the Google Groups &= quot;pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to pand= oc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/= msgid/pandoc-discuss/05a24a0b-9441-4aa4-8f07-84922a6c7196%40googlegroups.co= m.
------=_Part_334_535865968.1567140621984-- ------=_Part_333_1453741648.1567140621983--