From: Tim Cross <theophilusx@gmail.com>
To: Rohit Patnaik <quanticle@quanticle.net>
Cc: Vangelis Evangelou <evangelou@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] Markdown export of description list with nested list [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/local/share/emacs/28.1/lisp/org/)]
Date: Sat, 03 Sep 2022 11:11:04 +1000 [thread overview]
Message-ID: <86bkrxtfpq.fsf@gmail.com> (raw)
In-Reply-To: <c9bde5bc-51a4-4faf-b5e4-ad8ab879bac5@www.fastmail.com>
"Rohit Patnaik" <quanticle@quanticle.net> writes:
> As I understand it, the bug is in `org-md-item'. It formats the tag portion of the
> description with **%s**, and then simply concatenates the content. This is fine
> when the content is a simple string, but when the content includes line breaks
> (i.e. when content is itself a list), it doesn't realize that it needs to
> include a line break between the tag and the content.
>
> ox-html handles this case correctly because ox-html distinguishes between plain
> list types, using <li> for ordered and unordered lists and <dt> & <dd> for
> description lists.
>
> I think this issue can be fixed by prefixing `contents' with a newline if `tag'
> is present and `contents' itself contains multiple lines. However, this feels
> like a hack, and I'd be open to better approaches.
>
> -- Rohit
I think the real issue here is that the particular version of markdown
used by org-mode (see http://daringfireball.net/projects/markdown/) does
not include support for description lists - it simply isn't part of the
supported syntax.
I"m not convinced adding support is a good idea as I suspect it will
create other complications and only reveal other syntax limitations - it
will be like pulling on a thread and could result in just unravelling
everything. As it says in the version of markdown syntax used -
| For any markup that is not covered by Markdown’s syntax, you simply use
| HTML itself. There’s no need to preface it or delimit it to indicate
| that you’re switching from Markdown to HTML; you just use the tags.
prev parent reply other threads:[~2022-09-03 1:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 8:09 [BUG] Markdown export of description list with nested list [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/local/share/emacs/28.1/lisp/org/)] Vangelis Evangelou
2022-09-02 18:12 ` Rohit Patnaik
2022-09-03 1:11 ` Tim Cross [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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86bkrxtfpq.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=evangelou@gmail.com \
--cc=quanticle@quanticle.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).