Re: Attributes on HTML tables?

[Christian Moe <mail@christianmoe.com>]

Nicolas Goaziou writes:
>> When I export, both the defaults /and/ the "options" are applied,
>> resulting in duplicated attributes, like this:
>>
>>   <table border="2" cellspacing="0" cellpadding="6" rules="groups"
>>   frame="hsides" border="2" rules="all" frame="border">
>
> This is a bug.

Ah, good (from my perspective, anyway, I was getting concerned about
my setup).

> The idea is to define some widely used
> attributes that will be written directly like:
>
>   #+attr_html: :border 0 :width 400
>
> Then, :options attribute is used as a bucket for every other attribute,
> since we cannot support all of them.

I'm sorry, you've probably explained this many times before and I should
go read the archives. 

But what is it that nees to be supported, and why couldn't you just pass
through *whatever* :attribute value pair the user puts in attr_html? I
really like the switch to plist style, but I think the combination with
:options and literal syntax is confusing.

> Unfortunately, no attribute is current recognized in table HTML
> transcoder. It needs to be improved.
>
> If Someone provides a list of such attributes, I can implement it.

I'd be happy to, but I need to understand the above. On what basis
should attributes be selected for either plist style or the :options
bucket, and what does the exporter need to know about them in order to
support them?

Yours,
Christian