From: Jambunathan K <email@example.com>
To: Sebastien Vauban
Subject: Re: [patch] Re: HTML Postamble is inside Content DIV
Date: Fri, 22 Jul 2011 05:05:35 +0530 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Sebastien Vauban's message of "Thu, 21 Jul 2011 22:47:04 +0200")
> Hi Pierre, Bastien et al.,
> Pierre de Buyl wrote:
>> Le 8 juil. 11 à 09:36, 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
>>>> - 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).
>>> Any objection for applying this patch?
>> Not at all.
> After off-line discussion with Bastien, here is the updated proposition --
> and patch!
> There is no global DIV anymore directly inside the body, as there is already
> (in CSS) a virtual DIV called "#body"...
> Inside the "body" tags, 3 DIV:
> - "preamble" (useful for adding a static menu, outside of the "content" DIV)
> - "content" (by default, see "org-export-html-content-div")
> - "postamble"
> Preamble and postamble DIV are only inserted if they're not void.
> The "content" DIV (name free to be customized) will always be inserted.
> Any comment or objection?
Specifically can it do this:
I think having <div class="presentation"> is significant for org-s5
(though I haven't verified it). What the org-s5 use-case emphasizes is
that the user should have the flexibility to add attributes of his own
choosing to the div element and not merely the name of the id tag.
I see that there has been a lot of ping-ponging around this area for a
while now and you now seem to have a new proposal at hand. Your patch
seems to be touching Bastien's commit pursuant to my above request
. I don't understand or use html or org-s5. I hope the proposal here
is the final one :-). Please make Eric Schulte a respondent or reviewer
for this patch (from org-s5 side of things) and insist on a feedback
from him before committing..
ps: I would desire that any changes to org-html.el also need to be
ported to org-lparse.el and (or) org-xhtml.el.
> Best regards,
 I was not happy with Bastien's change which I felt was ignoring the
core of my proposal)
next prev parent reply other threads:[~2011-07-21 23:36 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
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 [this message]
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).