What if I add new export options in the alist:

* :html-div-preamble

* :html-div-content

* :html-div-preamble

Each one have nil as default value and can have one of these 2 values:

* "tag-name": A tag name (ex: "div") as a string

* (:tag "tag-name" :id "id-name" :class "class-name"): A plist where
  only :tag is non-optional


If one of these 3 option are set, ox-html use it. Otherwise it use the
value of :html-divs/org-html-divs.

So, a user could set its option like this:

    #+OPTION: html-div-content:(:tag "article" :class "content")

Or with the variable `org-html-divs' if she or he want to set all in one
`(setq)'.

And for ox-html, I can write a function to extract the correct value
from the info plist.

What do you think ? Is it a good idea, or do I over-complicated it ?

Attachment: signature.asc
Description: PGP signature

Reply via email to