On Sun, Apr 14, 2013 at 06:13:40PM +0800, Eric Abrahamsen wrote:
> Rick Frankel <r...@rickster.com> writes:
>
> > On Sat, Apr 13, 2013 at 01:31:17PM +0800, Eric Abrahamsen wrote:
> >> * Org HTML5 Test
> >> #+ATTR_HTML: :options html-container article
> >> - a :: foo
> >> - b :: bar
> > note that you just just set #+HTML_CONTAINER: article in the head of the
> > file if you want all the containers to be "article"s.
>
> That would be pretty drastic, though -- it would wrap "article" around a
> whole bunch of stuff that shouldn't be an article! I think ultimately
> the HTML exporter should grow a slightly more flexible system for
> wrapping document sections in containers, but this patch definitely
> shouldn't get hung up on that.
It specifies the element for the top-level container---by default,
something like:
<div id="outline-container-sec-1" class="outline-2">
In the case of e.g., a blog or slideshow, <article> is an appropriate
top-level wrapper lelement.
Regardless, I'm not sure which object you are expecting the
#+ATTR_HTML to apply to in the example above. Here's the html the
above section generates:
#+BEGIN_HTML
<div id="outline-container-sec-5" class="outline-2">
<h2 id="sec-5"><span class="section-number-2">5</span> A definiton list</h2>
<div class="outline-text-2" id="text-5">
<dl class="org-dl">
<dt> a </dt><dd>foo
</dd>
<dt> b </dt><dd>bar
</dd>
</dl>
</div>
</div>
Where the 'outline-text-2' div is actually around the entire body of
the section, not just the definition list (there is no explicit
wrapper around the definition list).
I would argue that to set the element type fro the outer
(outline-container) div or the inner (outline-text) div, a property
setting would make more sense. I can see using a (headline level)
:HTML_CONTAINER property to set the container on a given headline
(which i think i will impliment as it is very low impact), and perhaps
either an :HTML_CHILD_CONTAINER or :HTML_TEXT_CONTAINER to specify the
wrapper on the inner section.
rick
