From: Pierre de Buyl <pdebuyl@ulb.ac.be>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: HTML Postamble is inside Content DIV
Date: Wed, 6 Jul 2011 08:49:16 +0200 [thread overview]
Message-ID: <A5CA8111-07FE-4A51-8662-4B8F61C809DE@ulb.ac.be> (raw)
In-Reply-To: <80y60iumbh.fsf@somewhere.org>
Hello,
I checked and indeed "content" is working well.
Pierre
Le 1 juil. 11 à 16:06, Sebastien Vauban a écrit :
> 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,
> Seb
>
> --
> Sebastien Vauban
>
>
next prev parent reply other threads:[~2011-07-06 6:49 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
2011-07-06 6:49 ` Pierre de Buyl [this message]
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:
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=A5CA8111-07FE-4A51-8662-4B8F61C809DE@ulb.ac.be \
--to=pdebuyl@ulb.ac.be \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).