emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien 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: Fri, 01 Jul 2011 16:06:58 +0200	[thread overview]
Message-ID: <80y60iumbh.fsf@somewhere.org> (raw)
In-Reply-To: 0903D18D-AB13-430D-81EF-93421BDB7D01@ulb.ac.be

Hi Pierre,

Pierre de Buyl wrote:
> Le 28 juin 11 à 23:45, Sebastien Vauban a écrit :
>> 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 surrounds
>>   everything.
>> - 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).
> I think my regular use of the html export would be broken.

We'll try to solve that, then.

> I add a <div id="wrapper"> in the preamble and a </div> in the postamble.
> 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 setup.
> Here is my setup:
> 	 :html-preamble "
>    <div id=\"wrapper\">
>    <div id=\"menu\">
>    HERE, some static menu items.
>    </div>
> "
> 	 :html-postamble "
>    </div>
> "

Why are you adding a `wrapper' div in the already existing `content' div (that
surrounds everything). I see no real difference between both.

> I tried without that extra div and I cannot reproduce my former layout.

Would you apply your CSS rule onto `content', would that make a diff?

Best regards,

Sebastien Vauban

  reply	other threads:[~2011-07-01 14:06 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
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 [this message]
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=80y60iumbh.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).