public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Parsing Insides of SVGs
Date: Tue, 10 Oct 2017 09:22:49 -0700	[thread overview]
Message-ID: <20171010162249.GD70978@protagoras> (raw)
In-Reply-To: <8e4a0ced-c209-43bf-a267-565d19aa76cc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

The dev version of pandoc has a special syntax for raw
blocks and inlines.

    here's the svg: `<svg...> ... </svg>`{=html}. This
    will be passed verbatim to HTML (and formats that
    allow raw HTML).

+++ Saivan Hamama [Oct 09 17 19:43 ]:
>   I have a situation where I need to be able to include inline SVG's
>   inside a html document created by pandoc;
>   The problem is that when I paste an svg into one of my markdown files,
>   pandoc parses the contents of the svg as markdown, and adds unwanted
>   tags inside the svg (which makes it unusable).
>   Is there some way to input html that says *pandoc don't touch this* :P
>   I know I can just disable the parsing inside of html tags,
>   but I also need to use that elsewhere.
>   Is there a way to have an area in my document that pandoc will just
>   copy directly over to the html?
>
>   --
>   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-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/8e4a0ced-c209-43bf-
>   a267-565d19aa76cc%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/8e4a0ced-c209-43bf-a267-565d19aa76cc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. https://groups.google.com/d/optout


      parent reply	other threads:[~2017-10-10 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10  2:43 Saivan Hamama
     [not found] ` <8e4a0ced-c209-43bf-a267-565d19aa76cc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-10 16:22   ` John MACFARLANE [this message]

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=20171010162249.GD70978@protagoras \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).