emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [Patch] HTML export -- Allow to change the name of the global DIV
Date: Fri, 11 Mar 2011 10:09:55 +0100	[thread overview]
Message-ID: <80k4g6gh0c.fsf@somewhere.org> (raw)
In-Reply-To: 874o7aoxxr.fsf@gnu.org

Hi Bastien,

Bastien wrote:
> Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> Here is a patch which allows one to change the (currently) hard-coded DIV
>> name in which the page contents is being inserted.
>> It currently is "content", but some prefer "container" or "wrapper".
>> If accepted, my next patch will be to make this a per-project
>> variable.
> Are there other hardcoded HTML classes/ids that the user might want to
> customize? If so, can we think about a simple way to define all of them at
> once?

I did not find any other element -- yet -- that should be un-hardcoded. Maybe
other people will have more info about this.

Anyway, next step is to allow such element(s) to be specifiable per project,
so that one can manage different projects with different CSS sources
(remember the question about CSS blueprint, a couple of days ago).

Best regards,

Sébastien Vauban

  reply	other threads:[~2011-03-11  9:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 13:07 [Patch] HTML export -- Allow to change the name of the global DIV Sébastien Vauban
2011-03-11  8:37 ` Bastien
2011-03-11  9:09   ` Sébastien Vauban [this message]
2011-03-14 13:11   ` Matt Lundin
2011-03-14 15:22     ` Jambunathan K
2011-03-14 15:25       ` Jambunathan K

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=80k4g6gh0c.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).