public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Denis Bitouzé" <denis.bitouze-PToOLB6qFnLddoiwg0DPyg@public.gmane.org>
To: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
Cc: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: [SOCIAL]Re: [SOCIAL]Re: LaTeX to Markodown: nested lists converted to code blocks
Date: Tue, 25 Oct 2022 10:31:07 +0200	[thread overview]
Message-ID: <87k04o5mpg.fsf@example.com> (raw)
In-Reply-To: <87ilk8l3v6.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org> (Albert Krewinkel's message of "Tue, 25 Oct 2022 10:05:16 +0200")

Le 25/10/22 à 10h05, Albert Krewinkel a écrit :

> You might like Babelmark, which is a great tool to compare the behavior
> of different Markdown implementations.
>
> https://babelmark.github.io

Very helpful, thanks!
-- 
Denis

-- 
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/87k04o5mpg.fsf%40example.com.


      parent reply	other threads:[~2022-10-25  8:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25  7:15 Denis Bitouzé
     [not found] ` <87zgdk5q6q.fsf-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org>
2022-10-25  7:31   ` Bastien DUMONT
2022-10-25  7:39     ` [SOCIAL]Re: " Denis Bitouzé
     [not found]       ` <87sfjc5p48.fsf-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org>
2022-10-25  8:05         ` Albert Krewinkel
     [not found]           ` <87ilk8l3v6.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-10-25  8:31             ` Denis Bitouzé [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=87k04o5mpg.fsf@example.com \
    --to=denis.bitouze-ptoolb6qfnlddoiwg0dpyg@public.gmane.org \
    --cc=albert+pandoc-9EawChwDxG8hFhg+JK9F0w@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).