From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
Subject: Re: HTML Postamble is inside Content DIV
Date: Tue, 31 May 2011 20:56:13 +0200
Message-ID: <801uzeu2b6.fsf@somewhere.org>
References: <80mxj8g0wl.fsf@somewhere.org>
	<loom.20110430T203834-184@post.gmane.org>
	<80ei4gdoe7.fsf@somewhere.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=unsubscribe>
List-Archive: </archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode-mXXj517/zsQ@public.gmane.org>
List-Help: <mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org

Hi,

S=C3=A9bastien Vauban wrote:
> Jonathan BISSON wrote:
>> S=C3=A9bastien Vauban <wxhgmqzgwmuf@...> writes:
>>> After a couple of tests, I've observed that the postamble is forced to =
be
>>> included *inside* the div "content".
>>>=20
>>> Proof on Line 1764... These are the ending tags of every HTML page:
>>>=20
>>> #+begin_src emacs-lisp
>>>       (unless body-only (insert "\n</div>\n</body>\n</html>\n"))
>>> #+end_src
>>>=20
>>> ... the closing </div> referring to the opening of "content".
>>>=20
>>> Shouldn't it make sense to be able to insert something *out of* the
>>> "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 either:
>
> - 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 reasons?
>
> (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... betwe=
en
  a wrapping div called "postamble".

Shouldn't it be normal to apply the same reasoning for both cases: either
impose a wrapper, either not?

> Any comment for others?

Best regards,
  Seb

--=20
Sebastien Vauban