On 22.2.2013, at 21:33, Achim Gratz <strom...@nexgo.de> 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 | >>> | be | a header | >>> |-----------+-----------| >>> | This | won't | >>> |-----------+-----------| >>> | This will | be too | >>> |-----------+-----------| >>> | This | won't too | >> >> I really like this approach, to mark the header groups in an attribute >> - maybe an backend-independent attribute? > > I can see the appeal from a programmers' point of view, but from a user > perspective this is extremely obscure, especially if that table spans a > few pages and has many such extra header rows (hey, why not ask the user > to write the table in XML to start with?). In any case, the current way > of dealing with headers in org-element and the exporters doesn't admit > either. > >> The reason why I prefer this approach is that I am weary of new >> syntax in Org-mode that will take up new characters of character >> chains. For the case of tables, if I could go back, I would even >> remove some of the syntax I introduced, for example for defining the >> values of constants - that should have been an attribute-link thing as >> well. Probably even row and column naming, could have been done in >> this way. > > Hindsight is 20/20. :-) > > 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. - Carsten > > > Regards, > Achim. > -- > +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ > > SD adaptation for Waldorf microQ V2.22R2: > http://Synth.Stromeko.net/Downloads.html#WaldorfSDada > >
