From: Gu Lu <guill.louvel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Correctly convert back tightlist from latex to markdown
Date: Tue, 8 Oct 2019 09:51:09 -0700 (PDT) [thread overview]
Message-ID: <48be16f3-b5ac-4bb3-8395-59eefb7aa12c@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1250 bytes --]
Dear Pandoc users/developpers,
I am trying to produce markdown *from latex*.
However, regular lists (itemize environment) are converted to the "loose"
type of list, i.e the markdown output has blank lines between each item:
* item1
* item2
* item3
While I would personally always prefer the markdown compact list format,
this choice is consistent with the conversion from markdown *to latex* (where
the \tightlist command is added to compact lists).
I therefore tried to add the \tightlist command to my itemize environments,
but pandoc simply ignored it: it still produces loose markdown lists.
Is there a way to produce markdown compact lists from latex? Either by
interpreting the \tightlist command when seen, or by simply converting all
lists to compact using some command-line option?
Thanks a lot for your 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/48be16f3-b5ac-4bb3-8395-59eefb7aa12c%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2287 bytes --]
next reply other threads:[~2019-10-08 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 16:51 Gu Lu [this message]
[not found] ` <48be16f3-b5ac-4bb3-8395-59eefb7aa12c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-08 17:04 ` John MacFarlane
[not found] ` <yh480k8spv1858.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-10-08 17:09 ` Gu Lu
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=48be16f3-b5ac-4bb3-8395-59eefb7aa12c@googlegroups.com \
--to=guill.louvel-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).