public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Saivan Hamama <dragons6666x-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Specifying Raw Block Elements
Date: Sun, 8 Oct 2017 20:58:40 -0700 (PDT)	[thread overview]
Message-ID: <bed5a293-ddf6-4ef6-9e8c-c55f5e4aced2@googlegroups.com> (raw)


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

Now that html5 makes defining your own custom blocks pretty usual, I have a 
problem where I can't specify whether my particular tag should be a block 
element or an inline element.

For example:

# Heading

We put words here

<canvas></canvas>

## More

Words should go here

Will correctly leave the canvas out as a block element, without wrapping it 
with paragraph tags. 

However, if I use a custom version of the canvas

# Heading

We put words here

<myowncanvas></myowncanvas>

## More

Words should go here

myowncanvas gets wrapped with a paragraph tag. I could avoid this by 
wrapping with a div, I'm aware of that,
but I need to be able to specify my own custom tags,

Is there a way to achieve this?



-- 
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/bed5a293-ddf6-4ef6-9e8c-c55f5e4aced2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

             reply	other threads:[~2017-10-09  3:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09  3:58 Saivan Hamama [this message]
     [not found] ` <bed5a293-ddf6-4ef6-9e8c-c55f5e4aced2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-10  2:57   ` Saivan Hamama
     [not found]     ` <ae0ccc2e-6c5c-4d64-9a0f-33f27b8e028b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-10 16:24       ` John MACFARLANE
2017-10-11  0:52         ` Saivan Hamama
     [not found]           ` <f81758a8-93c5-4d35-bb61-d4255d248339-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-11  0:53             ` Saivan Hamama
2017-10-11  3:36             ` John MacFarlane
     [not found]               ` <20171011033629.GA29983-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-10-12  3:58                 ` Saivan Hamama
     [not found]                   ` <ce0b4c71-f89e-48ce-a0f1-d49f4edebbf0-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-12 15:08                     ` 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=bed5a293-ddf6-4ef6-9e8c-c55f5e4aced2@googlegroups.com \
    --to=dragons6666x-re5jqeeqqe8avxtiumwx3w@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).