From: Bastien <email@example.com>
To: Jason Dunsmore <firstname.lastname@example.org>
Subject: Re: Rework org-export-html-preamble/postamble (again)
Date: Tue, 15 Mar 2011 19:11:04 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Jason Dunsmore's message of "Tue, 15 Mar 2011 10:55:01 -0500")
Jason Dunsmore <email@example.com> writes:
>> You mean that, without any :html-preamble and with
>> ̀org-export-html-preamble' set to `t' (as it is by default in these
>> patches), you don't see any <h1>title</h1> ?
> If :html-preamble isn't set, I see an <h1>title</h1>.
When :html-preamble in a publishing project, it falls back on
org-export-html-preamble, which defaults to `t'.
You need to set :html-preamble to nil so that the HTML export
doesn't insert <h1>title</h1>.
> If it is set,
> but without explicitly defining "<h1 class=\"title\">%t</h1>" in the
> :html-preamble string, there is no <h1>title</h1>.
When :html-preamble is set to `t' in a publishing project, and
org-export-html-preamble-format hasn't been modified, it should
insert <h1 class=\"title\">%t</h1> -- it does here. Can you give
an example I can test?
> This is not how
> it worked before the recent changes to html exporting (ie. previously it
> wasn't necessary to explicitly define <h1>%t</h1> in the :html-preamble
It is not -- just check that org-export-html-preamble is `t' and that
should be all right. In th recent changes, I tried to make sure that
the defaults produce the same HTML output than defaults in 7.4.
> The previous behavior seems more consistent.
> This is with the latest git version (commit b6b7057467b6b).
> `org-export-html-preamble' is set to `t' in all my testing.
Thanks for this report again...
next prev parent reply other threads:[~2011-03-15 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 16:17 Rework org-export-html-preamble/postamble (again) Bastien
2011-03-09 20:21 ` Jason Dunsmore
2011-03-10 9:27 ` Bastien
2011-03-10 14:46 ` Jason Dunsmore
2011-03-10 18:29 ` Bastien
2011-03-15 15:55 ` Jason Dunsmore
2011-03-15 18:11 ` Bastien [this message]
2011-03-15 20:26 ` Jason Dunsmore
2011-03-17 7:08 ` Bastien
2011-03-15 15:25 ` Bastien
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).