Re: YAML metadata raw fields [was: Use of RCS with pandoc YAML blocks]

[msprevak <msprevak-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

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

Thanks! I'd be fine with this but I use a different way of doing per writer 
settings. I do it with a tool that sits around pandoc called 
panzer: https://github.com/msprev/panzer. panzer uses a yaml 'style' file 
to set pandoc's metadata plus other things (filters, scripts, etc) on a per 
style and per writer 
basis: https://github.com/msprev/dot-panzer/blob/master/styles.yaml.

I'd just be happy to have some way of inserting a raw string as the value 
of a metadata field.

Many thanks and best wishes,
Mark

On Wednesday, May 13, 2015 at 6:01:21 PM UTC+1, John MacFarlane wrote:
>
> My latest thought is that something like the following would be most 
> useful: 
>
> --- 
> header-includes: 
>   _html:  '<link src="mycss.css">' 
>   _latex: '\include{myformatting}' 
>   _*:     'fallback for other formats' 
> ... 
>
> `bar` would then resolve in templates differently depending on the 
> output format, with `*` as the wildcard. 
>
> This makes sense to me, since generally literals are going to vary 
> from one output format to another. 
>
> For passing to a JSON filter, you'd use `_json`. 
>
> +++ msprevak [May 13 15 01:31 ]: 
> >I too would like to have the ability to add raw strings to the metadata. 
> >This would be particularly useful for passing (non-markdown) strings to 
> >external filters. I like the proposed underscore syntax. Is there any 
> >update on this? 
> > 
> >All the best, 
> >Mark 
> > 
> >On Friday, August 22, 2014 at 1:57:19 AM UTC+1, John MacFarlane wrote: 
> >> 
> >> Another option would be to have some other signal, besides 
> >> the name, for a raw string. This would be better in many ways. 
> >> E.g., 
> >> 
> >> --- 
> >> foo:  markdown 
> >> bar:  _ 'plain string' 
> >> ... 
> >> 
> >> 
> >> 
> >> +++ John MacFarlane [Aug 21 14 17:33 ]: 
> >> >By the way, this kind of application suggests it might be 
> >> >useful to have a type of variable whose contents were 
> >> >interpreted as raw strings (not as markdown). 
> >> > 
> >> >The docs currently say that a field name ending with _ 
> >> >is just ignored -- it doesn't add anything to the metadata. 
> >> > 
> >> >But what we need is something that adds a raw MetaString. 
> >> > 
> >> >Is there a natural convention for field names whose 
> >> >contents should be interpreted as plain strings, not 
> >> >markdown?  What if field names starting with a colon were 
> >> >treated as strings? 
> >> > 
> >> >--- 
> >> >foo:  This is *markdown* 
> >> >:foo: This is just a *plain string* with asterisks. 
> >> >... 
> >> > 
> >> >The template parser currently doesn't allow 
> >> >$:foo$, but that could be changed. 
> >> > 
> >> >Alternatively, ALLCAPS could be the signal. 
> >> > 
> >> >+++ John MacFarlane [Aug 21 14 17:08 ]: 
> >> >>I meant for you to define \noop as 
> >> >>\newcommand{\noop}[1]{#1} so it passes through the contained 
> >> >>command.  If you do that, and put in the single quotes so YAML 
> >> >>doesn't get confused, it works: 
> >> >> 
> >> >> 
> >> >>--- 
> >> >>title: Test  Document 
> >> >>header-includes: 
> >> >>- '\usepackage{fancyhdr}' 
> >> >>- '\usepackage{lastpage}' 
> >> >>- '\usepackage{rcs}' 
> >> >>- '\newcommand{\noop}[1]{#1}' 
> >> >>- '\noop{\RCS $Revision: 1.1 $}' 
> >> >>- '\noop{\RCS $Date: 2014/08/18 14:24:49 $}' 
> >> >>- '\pagestyle{fancy}' 
> >> >>- '\fancyfoot[R]{Revision:\ \RCSRevision}' 
> >> >>- '\fancyfoot[L]{\RCSDate}' 
> >> >>- '\date{\RCSDate}' 
> >> >>author: Pete Phillips 
> >> >>... 
> >> >> 
> >> >>ok 
> >> >>\newpage 
> >> >>then 
> >> >> 
> >> >>+++ Pete Phillips [Aug 21 14 02:16 ]: 
> >> >>> Hi John. 
> >> >>> On Wednesday, 20 August 2014 17:32:55 UTC+1, John MacFarlane wrote: 
> >> >>> 
> >> >>>   The difference is explained by the following item in the 
> changelog: 
> >> >>>       + Inline math must have nonspace before final `$` (#1313). 
> >> >>>   In 1.12.4, your RCS string was being erroneously parsed as LaTeX 
> >> >>>   math.  This had the good consequence (for you) that it was 
> rendered 
> >> >>>   verbatim, without escaping the $'s.  But this was a bug in the 
> >> >>>   markdown 
> >> >>>   reader, which has now been fixed. 
> >> >>> 
> >> >>> OK - that explains my few months of happiness then. ;-) 
> >> >>> 
> >> >>> 
> >> >>> 
> >> >>>   >   If it was possible to revert to that behaviour for the YAML 
> >> >>>   block I 
> >> >>>   >   would be a happy bunny.  Is that possible ? 
> >> >>>   Sorry, no.  I did think of a workaround which is a bit kludgy, 
> but 
> >> >>>   might 
> >> >>>   work.  Suppose you defined a do-nothing macro \noop{..}, then 
> >> >>>   enclosed 
> >> >>>   your RCS in that: 
> >> >>>       \noop{\RCS $blah blah $} 
> >> >>> 
> >> >>> I have tried this: 
> >> >>> 
> >> >>> --- 
> >> >>> title: Test  Document 
> >> >>> header-includes: 
> >> >>>     - \usepackage{fancyhdr} 
> >> >>>     - \usepackage{lastpage} 
> >> >>>     - \usepackage{rcs} 
> >> >>>     - \newcommand{\noop}[1]{} 
> >> >>>     - \noop{\RCS $Revision: 1.1 $} 
> >> >>>     - \noop{\RCS $Date: 2014/08/18 14:24:49 $} 
> >> >>>     - \pagestyle{fancy} 
> >> >>>     - \fancyfoot[R]{Revision:\ \RCSRevision} 
> >> >>>     - \fancyfoot[L]{\RCSDate} 
> >> >>>     - \date{\RCSDate} 
> >> >>> author: Pete Phillips 
> >> >>> --- 
> >> >>> § test 
> >> >>> test 
> >> >>> \newpage 
> >> >>> § more test 
> >> >>> test 
> >> >>> 
> >> >>> And running 
> >> >>> 
> >> >>>  pandoc -s --parse-raw testoldrcs.mkd -o testoldrcs.pdf 
> >> >>> 
> >> >>> I get the error: 
> >> >>> 
> >> >>> ! LaTeX Error: Missing \begin{document}. 
> >> >>> 
> >> >>> This is the same error I was getting in the early days of trying 
> this 
> >> >>> out.  Previously it was solved by adding quotes -     - '\RCS 
> >> >>> $Revision: 1.2 $' 
> >> >>> 
> >> >>> but that makes no difference now.  The latex generated is attached. 
> >> >>> Note that using --parse-raw makes no difference to the latex code - 
> I 
> >> >>> get the same code with of without that option. 
> >> >>> 
> >> >>> Pete 
> >> >>> 
> >> >>> 
> >> >>> 
> >> >>> 
> >> >>> 
> >> >>> -- 
> >> >>> 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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> >> >>> To post to this group, send email to 
> >> >>> [2]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> >> >>> To view this discussion on the web visit 
> >> >>> [3] 
> >> https://groups.google.com/d/msgid/pandoc-discuss/d77c8bf8-79c6-4643- 
> >> >>> 82d6-407611fc2d13%40googlegroups.com. 
> >> >>> For more options, visit [4]https://groups.google.com/d/optout. 
> >> >>> 
> >> >>>References 
> >> >>> 
> >> >>> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:> 
> <javascript:> 
> >> >>> 2. mailto:pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:> 
> >> >>> 3. 
> >> 
> https://groups.google.com/d/msgid/pandoc-discuss/d77c8bf8-79c6-4643-82d6-407611fc2d13%40googlegroups.com?utm_medium=email&utm_source=footer 
> >> >>> 4. https://groups.google.com/d/optout 
> >> >> 
> >> >>>\documentclass[]{article} 
> >> >>>\usepackage{lmodern} 
> >> >>>\usepackage{amssymb,amsmath} 
> >> >>>\usepackage{ifxetex,ifluatex} 
> >> >>>\usepackage{fixltx2e} % provides \textsubscript 
> >> >>>\ifnum 0\ifxetex 1\fi\ifluatex 1\fi=0 % if pdftex 
> >> >>>\usepackage[T1]{fontenc} 
> >> >>>\usepackage[utf8]{inputenc} 
> >> >>>\else % if luatex or xelatex 
> >> >>>\ifxetex 
> >> >>>  \usepackage{mathspec} 
> >> >>>  \usepackage{xltxtra,xunicode} 
> >> >>>\else 
> >> >>>  \usepackage{fontspec} 
> >> >>>\fi 
> >> >>>\defaultfontfeatures{Mapping=tex-text,Scale=MatchLowercase} 
> >> >>>\newcommand{\euro}{€} 
> >> >>>\fi 
> >> >>>% use upquote if available, for straight quotes in verbatim 
> >> environments 
> >> >>>\IfFileExists{upquote.sty}{\usepackage{upquote}}{} 
> >> >>>% use microtype if available 
> >> >>>\IfFileExists{microtype.sty}{\usepackage{microtype}}{} 
> >> >>>\ifxetex 
> >> >>>\usepackage[setpagesize=false, % page size defined by xetex 
> >> >>>            unicode=false, % unicode breaks when used with xetex 
> >> >>>            xetex]{hyperref} 
> >> >>>\else 
> >> >>>\usepackage[unicode=true]{hyperref} 
> >> >>>\fi 
> >> >>>\hypersetup{breaklinks=true, 
> >> >>>          bookmarks=true, 
> >> >>>          pdfauthor={Pete Phillips}, 
> >> >>>          pdftitle={Test Document}, 
> >> >>>          colorlinks=true, 
> >> >>>          citecolor=blue, 
> >> >>>          urlcolor=blue, 
> >> >>>          linkcolor=magenta, 
> >> >>>          pdfborder={0 0 0}} 
> >> >>>\urlstyle{same}  % don't use monospace font for urls 
> >> >>>\setlength{\parindent}{0pt} 
> >> >>>\setlength{\parskip}{6pt plus 2pt minus 1pt} 
> >> >>>\setlength{\emergencystretch}{3em}  % prevent overfull lines 
> >> >>>\setcounter{secnumdepth}{0} 
> >> >>> 
> >> >>>\title{Test Document} 
> >> >>>\author{Pete Phillips} 
> >> >>>\date{} 
> >> >>>\usepackage{fancyhdr} 
> >> >>>\usepackage{lastpage} 
> >> >>>\usepackage{rcs} 
> >> >>>\newcommand{\noop}[1]{} 
> >> >>>true 
> >> >>>true 
> >> >>>\pagestyle{fancy} 
> >> >>>\fancyfoot[R]{Revision:\ \RCSRevision} 
> >> >>>\fancyfoot[L]{\RCSDate} 
> >> >>>\date{\RCSDate} 
> >> >>> 
> >> >>>\begin{document} 
> >> >>>\maketitle 
> >> >>> 
> >> >>>\section{test}\label{test} 
> >> >>> 
> >> >>>test 
> >> >>> 
> >> >>>\newpage 
> >> >>> 
> >> >>>\section{more test}\label{more-test} 
> >> >>> 
> >> >>>test 
> >> >>> 
> >> >>>\end{document} 
> >> >> 
> >> >>-- 
> >> >>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-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> >> >>To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org 
> >> <javascript:>. 
> >> >>To view this discussion on the web visit 
> >> 
> https://groups.google.com/d/msgid/pandoc-discuss/20140822000810.GH32670%40berkeley.edu. 
>
> >> 
> >> >>For more options, visit https://groups.google.com/d/optout. 
> >> > 
> >> >-- 
> >> >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-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> >> >To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org 
> >> <javascript:>. 
> >> >To view this discussion on the web visit 
> >> 
> https://groups.google.com/d/msgid/pandoc-discuss/20140822003345.GA1999%40berkeley.edu. 
>
> >> 
> >> >For more options, visit https://groups.google.com/d/optout. 
> >> 
> > 
> >-- 
> >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-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> >To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org 
> <javascript:>. 
> >To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pandoc-discuss/14456064-1273-444b-8f0e-1491036761ed%40googlegroups.com. 
>
> >For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/19f5136d-1475-4294-8951-5c9ba7ca15db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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