From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: Vladimir Alexiev <vladimir.alexiev@ontotext.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] ox-md image captions
Date: Sat, 08 Apr 2023 10:29:28 +0000 [thread overview]
Message-ID: <87pm8ek6pj.fsf@localhost> (raw)
In-Reply-To: <f8e4ba11-8a02-a021-8783-877d73ed5d28@gmail.com>
Max Nikulin <manikulin@gmail.com> writes:
> On 07/04/2023 22:29, Vladimir Alexiev wrote:
>> It's not about the tooltip in HTML:
>> figure captions are very important in scholarly publishing.
>
> I see and I do not like that Org exports caption as title (tooltip). On
> the other hand neither original markdown nor GitHub flavored markdown
> have notion of figure caption. Pandoc extension has the issue with
> duplicated text in caption and alt. I have seen mention of <figcaption>
> block in commonmark, but I have never tried it.
>
> MarkDown is rather basic format and the closest approach it a paragraph
> below an image despite they are not grouped into figure.
>
> 
>
> Figure 1. Caption
In theory, we can directly use <figcaption> HTML tags + direct HTML in
the MD export. That will be actually the closest way. But direct HTML is
not well-received when using the MD in practice. For example, sourcehut,
GitHub, and Reddit do not allow arbitrary html fragments when rendering
MD (AFAIK).
> A workaround for Org is export snippet or block for the paragraph with
> caption
>
> #+md: Figure 1. Caption
A better workaround is a custom filter, or we may provide a
customization, if someone offers a patch.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-04-08 10:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 10:02 [BUG] ox-md image captions Vladimir Alexiev
2023-02-27 18:52 ` Ihor Radchenko
2023-04-04 8:48 ` Ihor Radchenko
2023-04-04 19:34 ` Vladimir Alexiev
2023-04-04 19:41 ` Ihor Radchenko
2023-04-07 14:56 ` Max Nikulin
2023-04-07 15:29 ` Vladimir Alexiev
2023-04-07 17:21 ` Max Nikulin
2023-04-08 10:29 ` Ihor Radchenko [this message]
2023-04-08 10:25 ` Ihor Radchenko
2023-04-05 9:43 ` Morgan Willcock
2023-04-05 10:04 ` Ihor Radchenko
2023-04-05 10:41 ` Morgan Willcock
2023-04-05 11:07 ` Ihor Radchenko
2023-04-05 15:30 ` Vladimir Alexiev
2023-04-16 15:36 ` Ihor Radchenko
2023-04-05 12:06 ` Max Nikulin
2023-04-05 13:05 ` Ihor Radchenko
2023-04-05 15:15 ` Max Nikulin
2023-04-05 15:22 ` Ihor Radchenko
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=87pm8ek6pj.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
--cc=vladimir.alexiev@ontotext.com \
/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).