From: Bastien <bzg@altern.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: RFC: Revisit org-export-content-div (in the context of org-s5)
Date: Mon, 11 Jul 2011 13:44:27 +0200 [thread overview]
Message-ID: <87pqlh82jo.fsf@gnu.org> (raw)
In-Reply-To: <81d3hi75oj.fsf@gmail.com> (Jambunathan K.'s message of "Sun, 10 Jul 2011 16:39:48 +0530")
Hi Jambunathan,
Jambunathan K <kjambunathan@gmail.com> writes:
> Couple of comments wrt org-export-content-div:
>
> 1. Should be renamed to org-export-html-content-div
Done.
> 2. If we look at org-s5.el[1], we see the following usage where
> apparently <div id="content"> is essentially replaced by "<div
> class="presentation"> with a bunch of leading and trailing stuff.
>
> #+begin_src emacs-lisp
> (lambda ()
> (save-excursion
> (replace-regexp
> (regexp-quote "<div id=\"content\">")
> (let ((info `(("author" . ,author)
> ("title" . ,title)
> ("date" . ,(substring date 0 10)))))
> (join `("<div class=\"layout\">"
> "<div id=\"controls\"><!-- no edit --></div>"
> "<div id=\"currentSlide\"><!-- no edit --></div>"
> "<div id=\"header\"></div>"
> "<div id=\"footer\">"
> ,(org-fill-template org-s5-title-string-fmt info)
> "</div>"
> "</div>"
> ""
> "<div class=\"presentation\">"
> ,(org-fill-template org-s5-title-page-fmt info)))))))
> #+end_src
>
> 3. Considering (2) above it might be worthwhile defining the
> customization as below (for a first cut)
>
> #+begin_src emacs-lisp
> (defcustom org-export-html-content-div "%s <div %s> %s" ; note the html in prefix
> "The name of the container DIV that holds all the page contents."
> :group 'org-export-htmlize
> :type 'string)
> #+end_src
This looks to complicated to me.
I've introduced a new defcustom `org-export-html-before-content-div'
which lets the user place arbitrary HTML code before the main container.
org-s5.el could you this instead of replacing the "<div id=content>".
--
Bastien
prev parent reply other threads:[~2011-07-11 11:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 11:09 RFC: Revisit org-export-content-div (in the context of org-s5) Jambunathan K
2011-07-10 11:28 ` Jambunathan K
2011-07-11 11:44 ` Bastien
2011-07-11 19:55 ` Using org-mode for Research and Notetaking Florian Beck
2011-07-12 14:23 ` John Hendy
2011-07-14 18:09 ` Florian Beck
2011-07-12 14:28 ` Giovanni Ridolfi
2011-07-13 8:55 ` Bastien
2011-07-13 9:59 ` Sebastien Vauban
2011-07-13 11:20 ` Bastien
2011-07-13 12:20 ` Sebastien Vauban
2011-07-13 13:43 ` Nicolas Goaziou
2011-07-16 11:40 ` Bastien
2011-07-18 12:42 ` Matt Lundin
2011-07-18 13:21 ` Sebastien Vauban
2011-07-18 14:53 ` Matt Lundin
2011-07-18 14:03 ` Sebastien Vauban
2011-07-18 14:58 ` Bastien
2011-07-14 18:40 ` Florian Beck
2011-07-14 18:59 ` Thomas S. Dye
2011-07-18 22:54 ` Bastien
2011-07-18 23:59 ` Thomas S. Dye
2011-07-19 1:34 ` Florian Beck
2011-07-26 11:27 ` Bastien
2011-07-26 14:17 ` Florian Beck
2011-07-26 15:15 ` Thomas S. Dye
2011-07-26 17:41 ` Christian Moe
2011-07-11 11:44 ` Bastien [this message]
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=87pqlh82jo.fsf@gnu.org \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.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).