From: nkalvi <kana-a9OgVwmGd9+sTnJN9+BGXg@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: convincing the markdown reader/writer to preserve yaml string literal formatting
Date: Tue, 25 Aug 2015 10:54:28 -0700 (PDT) [thread overview]
Message-ID: <6a5b87f8-1235-4226-898e-1b0a436852e4@googlegroups.com> (raw)
In-Reply-To: <26c50d7f-d78c-4b40-b76a-09ebf6026173-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1946 bytes --]
Hi M att,
Based on a similar issue
<https://groups.google.com/forum/#!msg/pandoc-discuss/xuqEmhWgf9A/VPKIePhUvscJ>,
could you try something like
---
example: |
| foo@bar {
| baz = <11>;
| };
...
Angel brackets are still escaped in the output, but that may not be a
problem.
On Tuesday, August 25, 2015 at 10:50:47 AM UTC-4, Matt Porter wrote:
>
> I'm experimenting with using pandoc to generate customized documentation
> based on a yaml data stream and a custom template.
>
> I have the following inputs:
>
> test.yaml
> ------------
>
> ---
> example: |
> foo@bar {
> baz = <11>;
> };
> ...
>
>
> test.template
> -----------------
>
> $if(example)$
> # Example
> $endif$
> $for(example)$
> ```
> $example$
> ```
> $endfor$
>
>
> command line
> -------------------
>
> $ pandoc test.yaml --from markdown+yaml_metadata_block --template
> test.template -s -o test.md
>
>
> test.md
> ----------
>
> # Example
> ```
> foo@bar { baz = \<11\>; };
> ```
>
>
> I see that the markdown support drops the newlines and whitespace in my
> yaml string. It also escapes
> other characters since it doesn't realize this is something I want
> preserved.
>
> Is there some way to convince pandoc's markdown reader/writer to yield
> output like the following?
>
> ```
> foo@bar {
> baz = <11>;
> };
> ```
>
> Thanks,
> Matt
>
--
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/6a5b87f8-1235-4226-898e-1b0a436852e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 4886 bytes --]
next prev parent reply other threads:[~2015-08-25 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 14:50 Matt Porter
[not found] ` <26c50d7f-d78c-4b40-b76a-09ebf6026173-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-08-25 17:54 ` nkalvi [this message]
2015-08-25 18:08 ` nkalvi
2015-08-25 18:17 ` nkalvi
2015-08-25 20:13 ` John MACFARLANE
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=6a5b87f8-1235-4226-898e-1b0a436852e4@googlegroups.com \
--to=kana-a9ogvwmgd9+stnjn9+bgxg@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).