emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org,
	Sebastien Vauban
Subject: Re: [patch] Re: HTML Postamble is inside Content DIV
Date: Sun, 24 Jul 2011 20:56:24 +0200	[thread overview]
Message-ID: <87aac3v6cg.fsf@altern.org> (raw)
In-Reply-To: <81pql35hrs.fsf@gmail.com> (Jambunathan K.'s message of "Fri, 22 Jul 2011 05:05:35 +0530")


Jambunathan K <kjambunathan@gmail.com> writes:

> Specifically can it do this:
> http://lists.gnu.org/archive/html/emacs-orgmode/2011-07/msg00524.html

We can modified the structure of `org-export-html-divs' so that it is an
alist instead of a list, with div ids and associated attributes.

If you think that's a good direction, can you provide a patch for this?

> 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
> [1]. 

Well, I didn't really like this proposed variable:

#+begin_src emacs-lisp
  (defcustom org-export-html-content-div "%s <div %s> %s"
    "The name of the container DIV that holds all the page contents."
    :group 'org-export-htmlize
    :type 'string)

It is not simple enough to my eyes...

> I don't understand or use html or org-s5. I hope the proposal here
> is the final one :-). 

I hope nothing is final in this world.  :)

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

I committed this yesterday.

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

(Can you take charge of this?)

This is the main reason why having duplicate code in this area is a

I still think our energy will be better spent by progressively adding
things from org-xhtml.el to org-html.el, feature by feature.  This is a
lot of (possibly boring) work, but being lazy now will just make it even
more difficult later.

In any case, working on porting changes from org-html.el to org-xhtml.el
isn't the right direction.

Let's keep up the good work!



  reply	other threads:[~2011-07-24 19:14 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
2011-07-24 18:56                       ` Bastien [this message]
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=87aac3v6cg.fsf@altern.org \
    --to=bzg@altern.org \
    --cc=kjambunathan@gmail.com \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.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).