Hi Matt,

Based on a similar issue 
<https://groups.google.com/forum/#!msg/pandoc-discuss/xuqEmhWgf9A/VPKIePhUvscJ>, 
could you please try this:

---
example: |
  |  foo@bar {
  |          baz = <11>;
  |  };
...


Angel brackets are still escaped, 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/b348f468-2622-4f1f-9b33-e5f672237bb6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.