From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: possible to have superscript in bracketed_span?
Date: Tue, 03 Sep 2019 10:45:12 -0700 [thread overview]
Message-ID: <yh480k8sr5xoif.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <f1caed49-eeff-16d9-d75b-71f5e5527547-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> On 2019-09-03 18:21, John MacFarlane wrote:
>> Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:
>>
>>> On 9/2/19 1:23 PM, John MacFarlane wrote:
>>>> Pandoc doesn't like the initial ^ because of a clash with
>>>> footnote syntax. You could use the <span class="fn"> (native
>>>> span) notation.
>>>
>>> When we use literal HTML, does it translate into output formats other than HTML? (I'm wondering the same about trying to force a page break using HTML notation in markdown.)
>>
>> It depends on the format. In most cases it will be ignored.
>>
>
> But `<div>` and `<span>` are still special cases in that they are parsed
> into Div and Span elements, or has that changed now that we have the
> Markdownish syntax?
That hasn't changed.
prev parent reply other threads:[~2019-09-03 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 16:44 Joseph Reagle
[not found] ` <413b56a7-78a4-573a-34d5-055727f8e322-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2019-09-02 17:08 ` Joseph Reagle
2019-09-02 17:23 ` John MacFarlane
[not found] ` <m236hed342.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-03 13:56 ` Joseph Reagle
[not found] ` <1e7433e7-6f07-c8e5-71ea-91aa47daa996-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2019-09-03 16:21 ` John MacFarlane
[not found] ` <yh480kblw1z6ym.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-03 17:23 ` BPJ
[not found] ` <f1caed49-eeff-16d9-d75b-71f5e5527547-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-09-03 17:45 ` 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=yh480k8sr5xoif.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=melroch-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).