Re: #+ATTR_MY-ASCII: in derived backend?

[Thorsten Jolitz <tjolitz@gmail.com>]

Nicolas Goaziou <n.goaziou@gmail.com> writes:

Hello,

> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> do derived backends set their attributes always via the 
>>
>> ,--------------
>> | +ATTR_BACKEND:
>> `--------------
>>
>> construct of the parent backend and don't have their own 
>>
>> ,--------------
>> | +ATTR_MY-BACKEND:
>> `--------------
>>
>> construct?
>
> You can use any name you want for attributes
>
>   #+attr_my-special-name
>
> and then retrieve it with
>
>   (org-export-read-attribute :attr_my-special-name element)

I've seen this in ox backends, but since I sometimes simply use the
parse-tree as produced by `org-element-parse-buffer', I wonder why
something like 

,------------------------------------------------
| #+CAPTION: My minimal table
| #+ATTR_HTML: :border 2 :rules all :frame border
| | col1 | col2 |
| |------+------|
| | val1 | val2 |
`------------------------------------------------

actually is included in the tables property list

,--------------------------------------------------------------------------
| (table (begin 205... attr_html (":border 2 ... :frame border") ...) )
`--------------------------------------------------------------------------

although the exporter is never called - only org-element?


PS
I would like to have that too - how is that achieved?

-- 
cheers,
Thorsten