From: Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: LaTeX to Markodown: nested lists converted to code blocks
Date: Tue, 25 Oct 2022 07:31:49 +0000 [thread overview]
Message-ID: <Y1eQ5cOKQHJfkD2j@localhost> (raw)
In-Reply-To: <87zgdk5q6q.fsf-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org>
I don't know how other markdown processors would handle it, but if you parse the resulting output with pandoc, "Bar" will be recognized as the first item of a sublist. For it to be parsed as a code block, it should be indented eight spaces.
Le Tuesday 25 October 2022 à 09:15:57AM, Denis Bitouzé a écrit :
> Hi,
>
> consider the following `test.tex` `LaTeX` file, involving a nested list:
>
> --8<---------------cut here---------------start------------->8---
> \documentclass{article}
> \begin{document}
> \begin{itemize}
> \item Foo
> \begin{itemize}
> \item Bar
> \end{itemize}
> \end{itemize}
> \end{document}
> --8<---------------cut here---------------end--------------->8---
>
> When it is converted (with `pandoc` 2.19.2) to `Markdown`:
>
> ┌────
> │ pandoc test.tex -o test.md
> └────
>
> the resulting `test.md` file is:
>
> --8<---------------cut here---------------start------------->8---
> - Foo
>
> - Bar
> --8<---------------cut here---------------end--------------->8---
>
> >From the `Markdown` point of view, the nested list is a code block, not
> a nested list. Would it not be separated from its parent with a blank
> line, the problem wouldn't arise.
>
> Is it a bug? Is there a way to prevent these blank lines?
>
> 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/87zgdk5q6q.fsf%40example.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/Y1eQ5cOKQHJfkD2j%40localhost.
next prev parent reply other threads:[~2022-10-25 7: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 [this message]
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 ` [SOCIAL]Re: " Denis Bitouzé
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=Y1eQ5cOKQHJfkD2j@localhost \
--to=bastien.dumont-vwifzpto/vqstnjn9+bgxg@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).