emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: HTML Postamble is inside Content DIV
Date: Tue, 03 May 2011 13:17:20 +0200	[thread overview]
Message-ID: <80ei4gdoe7.fsf@somewhere.org> (raw)
In-Reply-To: loom.20110430T203834-184@post.gmane.org

Hi Jonathan,

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 page:
>> #+begin_src emacs-lisp
>>       (unless body-only (insert "\n</div>\n</body>\n</html>\n"))
>> #+end_src
>> ... the closing </div> referring to the opening of "content".
>> 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)

Any comment for others?

Best regards,

Sébastien Vauban

  reply	other threads:[~2011-05-03 11:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 22:15 HTML Postamble is inside Content DIV Sébastien Vauban
2011-04-30 18:41 ` Jonathan BISSON
2011-05-03 11:17   ` Sébastien Vauban [this message]
2011-05-31 18:56     ` Sebastien Vauban
2011-06-28 21:45       ` Sebastien Vauban
2011-06-29 13:26         ` Pierre de Buyl
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

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:

  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=80ei4gdoe7.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


* 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).