From: Max Nikulin <manikulin@gmail.com>
To: Vladimir Alexiev <vladimir.alexiev@ontotext.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] ox-md image captions
Date: Fri, 7 Apr 2023 21:56:01 +0700 [thread overview]
Message-ID: <5e277449-fed7-7306-d599-b695eaa6d993@gmail.com> (raw)
In-Reply-To: <871qkzl9j2.fsf@localhost>
On 05/04/2023 02:41, Ihor Radchenko wrote:
> IMHO, it would make more sense if Pandoc had a toggle to treat captions
> differently. As an alternative.
printf '\n' |
pandoc -f org -t markdown_strict
disables generation of <figcaption>.
I think, it is unlikely that users with mobile devices (touchscreen
only) have chance to notice title attribute. The only site where I check
image titles is https://xkcd.com/1179/ . Alt text describes image for
those who do not see image while caption should be apparent for those
who see it.
I believe that it is Org bug that it places caption as title, but there
is no better alternatives besides HTML. Duplicating caption as alt text,
as pandoc does, is a bug as well.
next prev parent reply other threads:[~2023-04-07 14:57 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 [this message]
2023-04-07 15:29 ` Vladimir Alexiev
2023-04-07 17:21 ` Max Nikulin
2023-04-08 10:29 ` Ihor Radchenko
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=5e277449-fed7-7306-d599-b695eaa6d993@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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).