public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "'Adam Mackie' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Using YAML variables in docx
Date: Sun, 5 Nov 2017 08:28:39 -0800 (PST)	[thread overview]
Message-ID: <e3ad018a-2381-4b89-943f-9a347b3b9d7f@googlegroups.com> (raw)
In-Reply-To: <5f9a9b31-62b5-47b5-9db7-0a8ab5cae4e3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 367 bytes --]

At a minimum it would be useful to have YAML variables added as Custom Document Properties. I could do pretty much anything I want to if that feature existed. Docx seems to be a bit of a nightmare however, so that might be easier said than done. 

I'm curious how high a priority this is? I can see that new document properties (keywords) were added in 2.0 for docx.

  parent reply	other threads:[~2017-11-05 16:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01  1:18 'Adam Mackie' via pandoc-discuss
     [not found] ` <46936ce3-7335-4071-ab66-88bd60ecdf84-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-01  3:51   ` John MacFarlane
     [not found]     ` <20171101035147.GB19638-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-11-01 12:57       ` 'Adam Mackie' via pandoc-discuss
     [not found]         ` <edfcc38c-eb20-400f-822a-2c2f1231141c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-01 16:54           ` John MACFARLANE
2017-11-01 17:05             ` 'Adam Mackie' via pandoc-discuss
     [not found]               ` <eb861fe9-af97-4e32-bc6c-75662e0846a4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-01 17:14                 ` John MACFARLANE
2017-11-01 21:40                 ` Agustín Martín
     [not found]                   ` <b6259169-dba5-4aa7-9154-1816c021ce99-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-01 22:05                     ` 'Adam Mackie' via pandoc-discuss
     [not found]                       ` <caa2d23a-8956-4660-abb7-09835f3edc44-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-02  5:17                         ` Ophir Lifshitz
     [not found]                           ` <5f9a9b31-62b5-47b5-9db7-0a8ab5cae4e3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-05 16:28                             ` 'Adam Mackie' via pandoc-discuss [this message]
2017-11-05 17:40                             ` John MacFarlane
     [not found]                               ` <20171105174028.GC73700-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-11-07 21:54                                 ` BP Jonsson
2017-11-11 19:30                                 ` Ophir Lifshitz

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=e3ad018a-2381-4b89-943f-9a347b3b9d7f@googlegroups.com \
    --to=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).