public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: "Miguel Gualdrón" <dev-A7JrOCSl3gJWk0Htik3J/w@public.gmane.org>,
	pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: md->asciidoc inline code has plus signs
Date: Wed, 04 Sep 2019 14:45:30 -0700	[thread overview]
Message-ID: <yh480kr24vn3b9.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <CACu41f-KRNwFta3a=iiOvG8-RH7LUSWdKT4k5P-BTR7M+ks8hw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


Interesting, this seems to work differently in asciidoc and
asciidoctor (in asciidoctor you get the expected output).

Here's the commit that added this:

commit 98ee6ca289ad7117b7336a57bcfc6f4b54463f4e
Author: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
Date:   Sun May 5 21:57:30 2019 -0700

    Asciidoc writer: use `` `+...+` `` form for inline code.
    
    The old `` `a__b__c` `` yields emphasis inside code in asciidoc.
    To get a pure literal code span, use `` `+a__b__c+` ``.

Looks like this behavior is asciidoctor-specific.
Could you put an issue on our tracker so we won't forget
to fix this?  It should be easy enough to make the `+`s
conditional on the asciidoctor extension.

PS.  I get annoyed when I see online forums talking about how
asciidoc is superior to markdown because there aren't
N+1 versions!

Miguel Gualdrón <dev-A7JrOCSl3gJWk0Htik3J/w@public.gmane.org> writes:

> Hi,
>
> I've searched the archive for this, but wasn't able to find it.
>
> I'm using pandoc 2.7.3 under Mac OS X to convert docs from Markdown to
> Asciidoc.  Some of these may later be converted to HTML and/or PDF.
>
> The issue is that when converting inline code, pandoc surrounds the text
> with back-ticks AND plus signs, but both are not required by asciidoc, only
> one or the other.  So the question is:  how do I get the plus signs to go
> away?
>
> Here's a trivial example:
>
> echo 'Normal text `this is code`' |pandoc - -o- -f markdown -t asciidoc
> Normal text `+this is code+`
>
>
> If this output is then converted to HTML, the plus signs are rendered as if
> they had been part of the original text:
>
> echo 'Normal text `this is code`' |pandoc - -o- -f markdown -t asciidoc
> |asciidoc -o- -b xhtml11 -
> <div id="content">
> <div class="paragraph"><p>Normal text <code>+this is code+</code></p></div>
> </div>
>
>
> (I've omitted some of the HTML output for clarity.)
>
> Thanks in advance for any help.
>
> -- 
> 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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CACu41f-KRNwFta3a%3DiiOvG8-RH7LUSWdKT4k5P-BTR7M%2Bks8hw%40mail.gmail.com.

-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/yh480kr24vn3b9.fsf%40johnmacfarlane.net.


  parent reply	other threads:[~2019-09-04 21:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04 21:22 Miguel Gualdrón
     [not found] ` <CACu41f-KRNwFta3a=iiOvG8-RH7LUSWdKT4k5P-BTR7M+ks8hw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-09-04 21:45   ` John MacFarlane [this message]
     [not found]     ` <yh480kr24vn3b9.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-04 21:51       ` John MacFarlane
     [not found]         ` <yh480kftlbn30k.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-05 13:34           ` Miguel Gualdrón

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=yh480kr24vn3b9.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=dev-A7JrOCSl3gJWk0Htik3J/w@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).