From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Org-Mode Homepage error
Date: Tue, 26 Jul 2011 23:19:49 +0200 [thread overview]
Message-ID: <80y5zkwxhm.fsf@somewhere.org> (raw)
In-Reply-To: 87vcupdobh.fsf@Rainer.invalid
Hi Achim and Bastien,
Achim Gratz wrote:
> Bastien <bzg-whniv8GeeGkdnm+yROfE0A@public.gmane.org> writes:
>> I fail to understand why an additional <div id="preamble">
>> should break Sebastian's tool.
>> </mode lazybum>
>
> For starters, the title now resides in the preamble, but the script
> looks for it in content.
Good catch!
FYI, the title has always been in the preamble. See lines 354--381 in
org-html.el:
#+begin_src emacs-lisp
(defcustom org-export-html-preamble t
"Non-nil means insert a preamble in HTML export.
When `t', insert a string as defined by one of the formatting
strings in `org-export-html-preamble-format'. When set to a
string, this string overrides `org-export-html-preamble-format'.
When set to a function, apply this function and insert the
returned string. The function takes the property list of export
options as its only argument.
Setting :html-preamble in publishing projects will take
precedence over this variable."
:group 'org-export-html
:type '(choice (const :tag "No preamble" nil)
(const :tag "Default preamble" t)
(string :tag "Custom formatting string")
(function :tag "Function (must return a string)")))
(defcustom org-export-html-preamble-format
'(("en" "<h1 class=\"title\">%t</h1>"))
"The format for the HTML preamble.
%t stands for the title.
If you need to use a \"%\" character, you need to escape it
like that: \"%%\"."
:group 'org-export-html
:type 'string)
#+end_src
The difference I introduced is that -- when present -- the preamble (whatever
its contents) is wrapped inside a "preamble" DIV.
I did not change the fact that the title was part of the preamble.
Though, we can wonder if it makes sense to put the title as part of the
preamble. But I guess there is a good reason for it(TM).
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2011-07-26 21:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 19:33 Org-Mode Homepage error Renger van Nieuwkoop
2011-07-25 19:42 ` Michael Markert
[not found] ` <2152B3DFC552DE47A0A36CCC93D735310439FF7D@mx01.ecoplan.local>
2011-07-25 20:10 ` Michael Markert
2011-07-25 20:26 ` Sebastien Vauban
2011-07-25 20:30 ` Nick Dokos
2011-07-25 21:29 ` Bastien
2011-07-26 12:36 ` Sebastien Vauban
2011-07-26 15:04 ` Bastien
2011-07-26 16:00 ` Achim Gratz
2011-07-26 21:19 ` Sebastien Vauban [this message]
2011-07-27 17:33 ` Bastien
2011-07-28 18:49 ` Achim Gratz
2011-07-31 17:42 ` Achim Gratz
2011-08-16 20:10 ` Bastien
2011-08-17 15:58 ` Achim Gratz
2011-08-17 16:18 ` Bastien
2011-08-17 16:50 ` Achim Gratz
2011-08-18 7:02 ` Bastien
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=80y5zkwxhm.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).