From: Manuel Giraud <manuel.giraud@univ-nantes.fr>
To: Aankhen <aankhen@gmail.com>
Cc: Bastien <bzg@altern.org>, Org-mode ml <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] * org-html.el (org-html-handle-links): add an alternate for inline images
Date: Wed, 20 Apr 2011 11:41:36 +0200 [thread overview]
Message-ID: <87pqoh6yzz.fsf@univ-nantes.fr> (raw)
In-Reply-To: <BANLkTinm3nmEynzQ39tfC08yyyxXf-OKdw@mail.gmail.com> (aankhen@gmail.com's message of "Wed, 20 Apr 2011 14:40:16 +0530")
Aankhen <aankhen@gmail.com> writes:
> On Wed, Apr 20, 2011 at 13:39, Manuel Giraud
> <manuel.giraud@univ-nantes.fr> wrote:
>
>> I knew it was not the best solution: all i wanted was to validate. But
>> an empty alt or maybe just "image" is fine by me too.
>
> Fair enough. :-) ‘image’ would be about the same as the file name in
> terms of useful alt text.
:-) and as useful as "" which is 5 bytes shorter: I think you've won
here.
> Well, there /is/ a way to do that already, it’s just verbose:
>
> ,----[ Org ]
> | * Foo
> | #+ATTR_HTML: alt="The elusive foo in its native habitat."
> | [[file:foo.png]]
> `----
Yes, discovered that in the doc just after posting my reply. But, this
doesn't work on [[big.jpg][small.jpg]] links as the alt attribute will
be placed in the anchor (which is wrong, AFAICT).
> I’d suggest using the description part of the link as the alt text,
> but then there’d be no way to provide the actual link text (or image,
> as the case may be), so that’s a non-starter.
Now, I'm looking into using the fragment part: less verbose and
hopefully it'll work for all kind of inline image.
--
Manuel Giraud
prev parent reply other threads:[~2011-04-20 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 8:34 [PATCH] * org-html.el (org-html-handle-links): add an alternate for inline images Manuel Giraud
2011-04-19 8:48 ` Jambunathan K
2011-04-19 9:12 ` Manuel Giraud
2011-04-19 9:22 ` [Accepted] " Bastien Guerry
2011-04-19 9:22 ` [PATCH] " Bastien
2011-04-19 21:08 ` Aankhen
2011-04-20 8:09 ` Manuel Giraud
2011-04-20 9:10 ` Aankhen
2011-04-20 9:41 ` Manuel Giraud [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=87pqoh6yzz.fsf@univ-nantes.fr \
--to=manuel.giraud@univ-nantes.fr \
--cc=aankhen@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.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.
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).