Nicolas Goaziou writes:
> I think the cleanest way to implement this would be to _not_ modify Org
> syntax, because it is export back-end very specific. Something like:
>
> #+attr_html: :header-groups (1 3)
> | This | will |
> | be| a header |
> |---+---|
Achim Gratz writes:
> But going this route takes us even further from "Your life in plain
> text." towards "Your life in another programming language." because you
> will need a special viewer or editor to make sense of it for all but the
> most trivial cases.
Point taken too -- this is even mor
On 22.2.2013, at 21:33, Achim Gratz wrote:
> Carsten Dominik writes:
>>> I think the cleanest way to implement this would be to _not_ modify Org
>>> syntax, because it is export back-end very specific. Something like:
>>>
>>> #+attr_html: :header-groups (1 3)
>>> | This | will |
>>> |
Carsten Dominik writes:
>> I think the cleanest way to implement this would be to _not_ modify Org
>> syntax, because it is export back-end very specific. Something like:
>>
>> #+attr_html: :header-groups (1 3)
>> | This | will |
>> | be| a header |
>> |---+-
On 17 feb. 2013, at 09:35, Nicolas Goaziou wrote:
> Hello,
>
> Achim Gratz writes:
>
>> I've just looked at how to implement this using org-element and the
>> new exporter. Much to my dismay I found that table headers are not
>> a separate row or row group type and the new exporter is still u
Achim Gratz writes:
> Nicolas Goaziou writes:
>> You only need to modify org-element if Org syntax has been changed.
>
> Yes, thats exactly what I want.
A new rule type was easy enough to implement:
http://repo.or.cz/w/org-mode/org-tableheadings.git/commit/17a4e9c599c555f53c2831fe8c473f169ccd8679
Nicolas Goaziou writes:
> You only need to modify org-element if Org syntax has been changed.
Yes, thats exactly what I want.
>> Also, it appears that each element can have only one property or did
>> I miss something? It seems that having a way to get the (main)
>> property and then asking if t
Hello,
Achim Gratz writes:
> I've just looked at how to implement this using org-element and the
> new exporter. Much to my dismay I found that table headers are not
> a separate row or row group type and the new exporter is still using
> this "everything before the first separator is a heading"
I've just looked at how to implement this using org-element and the new
exporter. Much to my dismay I found that table headers are not a
separate row or row group type and the new exporter is still using this
"everything before the first separator is a heading" kludge. It's easy
enough to introd
