Re: [Patch] HTML export -- Allow to change the name of the global DIV

["Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.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,
  Seb

-- 
Sébastien Vauban