From: Pierre de Buyl <firstname.lastname@example.org>
To: Sebastien Vauban <email@example.com>
Subject: Re: HTML Postamble is inside Content DIV
Date: Wed, 29 Jun 2011 15:26:56 +0200 [thread overview]
Message-ID: <0903D18D-AB13-430D-81EF-93421BDB7D01@ulb.ac.be> (raw)
Le 28 juin 11 à 23:45, Sebastien Vauban a écrit :
> "Sebastien Vauban" wrote:
>> Sébastien Vauban wrote:
>>> Jonathan BISSON wrote:
>>>> Sébastien Vauban <wxhgmqzgwmuf@...> writes:
>>>>> After a couple of tests, I've observed that the postamble is
>>>>> forced to be
>>>>> included *inside* the div "content".
>>>>> Proof on Line 1764... These are the ending tags of every HTML
>>>>> #+begin_src emacs-lisp
>>>>> (unless body-only (insert "\n</div>\n</body>\n</html>\n"))
>>>>> ... the closing </div> referring to the opening of "content".
>>>>> Shouldn't it make sense to be able to insert something *out of*
>>>>> "content" div?
>>>> I think so (and the same for preamble)!
>>>> I rewrote org-export-as-html and did a custom org-publish-org-to-
>>>> html to
>>>> call it, in order to get them out off the content div (you can
>>>> look at a
>>>> first test on my webpage http://www.bjonnh.net). It's easy to do
>>>> it I can
>>>> send you my file if you are interested.
>>> I think sharing the code here is always a good idea.
>>> However, I'd favor an approach commonly shared by others, ie by
>>> - moving the postamble out of the content DIV
>>> - adding an extra "environment" next to the content DIV, if the
>>> postamble must
>>> stay where it currently is -- for historical or compliance
>>> (same applies for preamble)
>> I'm hijacking my own thread, as it received little support, and as
>> the new
>> question is quite related to that:
>> - if we customize the preamble, our string will be inserted as is;
>> - if we customize the postamble, our string will be inserted as
>> is... between
>> a wrapping div called "postamble".
>> Shouldn't it be normal to apply the same reasoning for both cases:
>> impose a wrapper, either not?
>>> Any comment for others?
> Except for the reply of Jonathan, I received no answer on this.
> Here is thus
> my proposition for a better div-structured HTML.
> There are only four parts required in the HTML for all the magic to
> work with
> the CSS:
> - The first part is a container div ("content", by default) that
> - Inside that are three more parts:
> + a preamble (in a div, if the user wants it),
> + a div "body" and
> + a postamble (in a div, if the user wants it).
> The patch is attached.
> Best regards,
I think my regular use of the html export would be broken.
I add a <div id="wrapper"> in the preamble and a </div> in the
This allows me to make a "boxed" page (see http://homepages.ulb.ac.be/
~pdebuyl/ ) which I like.
If I cannot end my div in the postamble, I think it would break my
Here is my setup:
HERE, some static menu items.
I tried without that extra div and I cannot reproduce my former layout.
next prev parent reply other threads:[~2011-06-29 13:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 22:15 Sébastien Vauban
2011-04-30 18:41 ` Jonathan BISSON
2011-05-03 11:17 ` Sébastien Vauban
2011-05-31 18:56 ` Sebastien Vauban
2011-06-28 21:45 ` Sebastien Vauban
2011-06-29 13:26 ` Pierre de Buyl [this message]
2011-07-01 14:06 ` Sebastien Vauban
2011-07-06 6:49 ` Pierre de Buyl
2011-07-08 7:36 ` Sebastien Vauban
2011-07-08 9:28 ` Pierre de Buyl
2011-07-21 20:47 ` [patch] " Sebastien Vauban
2011-07-21 23:35 ` Jambunathan K
2011-07-24 18:56 ` Bastien
2011-07-23 17:11 ` Bastien
2011-07-23 21:58 ` Sebastien Vauban
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).