From: Sebastian Rose <firstname.lastname@example.org>
To: Richard Riley <email@example.com>
Cc: Org Mode List <firstname.lastname@example.org>
Subject: Re: Adding HTML into exported files
Date: Tue, 10 Feb 2009 15:27:58 +0100 [thread overview]
Message-ID: <87wsby1i4x.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <email@example.com> (Richard Riley's message of "Tue, 10 Feb 2009 15:05:54 +0100")
Richard Riley <firstname.lastname@example.org> writes:
> Sebastian Rose <email@example.com> writes:
>> This is the cleanest way to do it.
>> #+ATTR_HTML: alt="an image" id="mySpecialImmage"
>> [[./img/a.jpg] ]
>> and use CSS.
> I didn't know about this!
> Should this maybe be documented somewhere other than in the Links section
> of the manual?
I'm used to search the `list of user visible changes' though. I can
imagine it's always a lot of work to incorporate all those new features
into the manual, and still keep that clean and easy to follow (forgot
the word... I know there is one...).
So the `hottest' features are often found in the news file :-)
I'm shure this will change as soon as we start to order printed manuals
on Amazon :)
I'll also by the `Book of user visible changes', just to be shure.
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.: +49 (0)511 - 36 58 472
Fax: +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
next prev parent reply other threads:[~2009-02-10 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 13:06 Adding HTML into exported files Jan Seeger
2009-02-10 14:03 ` Sebastian Rose
2009-02-10 14:05 ` Richard Riley
2009-02-10 14:27 ` Sebastian Rose [this message]
2009-02-10 15:20 ` Richard Riley
2009-02-10 19:30 ` Carsten Dominik
2009-02-10 19:56 ` Richard Riley
2009-02-11 2:04 ` Sebastian Rose
2009-02-11 10:34 ` Carsten Dominik
2009-02-10 14:27 ` Jan Seeger
2009-02-11 1:48 ` Sebastian Rose
2009-02-11 17:34 ` Jan Seeger
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).