public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Dominik Wujastyk <wujastyk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Why does GFM to markdown not convert HTML?
Date: Thu, 7 Oct 2021 06:31:38 -0700 (PDT)	[thread overview]
Message-ID: <eca62f3a-d4e3-4459-830c-ca4a3de2d125n@googlegroups.com> (raw)


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

Using  
pandoc -v
pandoc 2.14.2
Compiled with pandoc-types 1.22, texmath 0.12.3.1, skylighting 0.11,
citeproc 0.5, ipynb 0.1.0.1

Gfm input example:

# NAK 1-1079

<h2>
  Chapter-wise concordance of folios
</h2> 
<h3> 
  Prepared by Dominik Wujastyk (DW) and Andrey Klebanov (AK) 
</h3>

Note that this MS (a single physical object kept at the __NAK__ under the 
accession number __1-1079__) 
was microfilmed twice, as **A 45-5 (on 16.10.1970)** and **A 1267-11 (on 
16.11.1987)**. Digital copies 
of both microfilms are available to us.

```

Command:  

pandoc -f gfm -t commonmark -o outfile.md infile.gfm

Commonmark output:

# NAK 1-1079

<h2>
  Chapter-wise concordance of folios
</h2> 
<h3> 
  Prepared by Dominik Wujastyk (DW) and Andrey Klebanov (AK) 
</h3>

Note that this MS (a single physical object kept at the **NAK** under
the accession number **1-1079**) was microfilmed twice, as **A 45-5 (on
16.10.1970)** and **A 1267-11 (on 16.11.1987)**. Digital copies of both
microfilms are available to us.


I was expecting that this command would turn the HTML codes in the gfm file 
into commonmark Markdown.  But it didn't.  Am I doing something silly?  
Have I failed to understand what commonmark is?  The HTML-coded text does 
render in Github and editors like Typora.  So it seems wrong to treat them 
as raw blocks.

Furthermore, a markdown-encoded table in the gfm document is converted to 
an HTML-encoded one.  Why?  This seems counterintuitive to me. 

-- 
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/eca62f3a-d4e3-4459-830c-ca4a3de2d125n%40googlegroups.com.

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

             reply	other threads:[~2021-10-07 13:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07 13:31 Dominik Wujastyk [this message]
     [not found] ` <eca62f3a-d4e3-4459-830c-ca4a3de2d125n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-10-08 11:34   ` BPJ

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=eca62f3a-d4e3-4459-830c-ca4a3de2d125n@googlegroups.com \
    --to=wujastyk-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).