Feature request: HTML export classes for "real" lists

Feature request: HTML export classes for "real" lists

[sand]

In org-html-export-list-line, Org list elements use the expected "dt", "dd" and
"li" tags:

	(insert (cond
		 ((equal type "d")
		  (format "<dt>%s</dt><dd>" desc-tag))
		 ((and (equal type "o") counter)
		  (format "<li value=\"%s\">" counter))
		 (t "<li>")))

But the exporter also uses HTML list elements in other contexts; the tags
are overloaded.  This means you can't set up CSS definitions to tweak
just "real" lists.  Can someone add class attributes to each of the
"dt", "dd" and "li" items in the above code block?  For example

    <dt class="org-dt">...</dt>
    <dd class="org-dd">...</dd>
    <li class="org-li">...</li>

or something similar.  This should provide enough hooks for people to work with.

Thanks,

Derek

-- 
Derek Upham
sand@blarg.net

Re: Feature request: HTML export classes for "real" lists

[Bastien]

Hi Derek,

<sand@blarg.net> writes:

> But the exporter also uses HTML list elements in other contexts; the tags
> are overloaded.  This means you can't set up CSS definitions to tweak
> just "real" lists.  Can someone add class attributes to each of the
> "dt", "dd" and "li" items in the above code block?  For example
>
>     <dt class="org-dt">...</dt>
>     <dd class="org-dd">...</dd>
>     <li class="org-li">...</li>
>
> or something similar.

I've implemented this in master for both the current exporter (famously
known as the "old" exporter) and the new exporter.  I think we should be
extra conservative and take care not to add useless classes/ids, but I
see the point in this case.

Thanks,

-- 
 Bastien

Re: Feature request: HTML export classes for "real" lists

[Eric Schulte]

Bastien <bzg@altern.org> writes:

> Hi Derek,
>
> <sand@blarg.net> writes:
>
>> But the exporter also uses HTML list elements in other contexts; the
>> tags
>> are overloaded.  This means you can't set up CSS definitions to tweak
>> just "real" lists.  Can someone add class attributes to each of the
>> "dt", "dd" and "li" items in the above code block?  For example
>>
>>     <dt class="org-dt">...</dt>
>>     <dd class="org-dd">...</dd>
>>     <li class="org-li">...</li>
>>
>> or something similar.
>
> I've implemented this in master for both the current exporter
> (famously known as the "old" exporter) and the new exporter.  I think
> we should be extra conservative and take care not to add useless
> classes/ids, but I see the point in this case.
>

Would it perhaps make sense to add classes to the un-normal use of these
tags outside of lists, rather than to their usage within lists?

I could see such an approach having a larger footprint in the code, but
resulting in smaller and arguably more meaningfully classed/tagged HTML
files.

Just a thought,

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

Re: Feature request: HTML export classes for "real" lists

[Bastien]

Eric Schulte <schulte.eric@gmail.com> writes:

> Would it perhaps make sense to add classes to the un-normal use of these
> tags outside of lists, rather than to their usage within lists?
>
> I could see such an approach having a larger footprint in the code, but
> resulting in smaller and arguably more meaningfully classed/tagged HTML
> files.

Agreed -- though I'm not sure what are the un-normal uses.  You mean 
in the table of content for example?

-- 
 Bastien