Patchwork [O] customize latex table export

Carsten Dominik <carsten.dominik@gmail.com> writes, a long time ago:

> On May 19, 2011, at 2:34 PM, Christophe Rhodes wrote:
>
>> To produce documents in something approaching my organization's house
>> style, I need to be able to style the headers of tables.  It's nice that
>> orgtbl has the functionality for this, but the call to orgtbl-to-latex
>> has a hard-coded list of parameters with no possibility for extension.
>> With the attached patch, I am able to put e.g.
>> 
>> #+BIND: org-export-latex-tables-orgtbl-extra-parameters (:hfmt "\\multicolumn{1}{c}{\\bf\\color{white}\\cellcolor{blue}%s}")
>> 
>> in the header of my document, and tables throughout the document all
>> pick up this style.
>> 
>> I daresay that this is not the optimal way of doing things; while this
>> solves my immediate problem there is likely to be a more general way of
>> doing things.
>
> would it be better to be able to set these parameters on a per-table basis with ATTR_LaTeX ?
> Would you like to try to prepare a patch to this effect?

Find attached a patch to this effect.  It is the combination of two
changes which I consider tiny: one is the support for hfmt itself as an
ATTR_LaTeX attribute; the other is the consolidation of the
word-matching on the attributes into local macros, which I needed
because my use case (as above) includes the string "multicolumn", which
was otherwise confusing the attribute parser into thinking that I needed
a table* LaTeX environment.

Please let me know if this suits better.
Christophe

Hi Christophe,

Could you provide us with a minimal example of how this new functionality
can be used?

I am trying to test it and see if there are any conflicts with my patch of
late to supports the booktabs package @
http://patchwork.newartisans.com/patch/1016/  (aside from one of the two
patches not applying without some minor human intervention around line
1998).

Besides that, it would in general be good to have an example for
documentation purposes.

On Tue, Nov 29, 2011 at 6:44 PM, Christophe Rhodes <csr21@cantab.net> wrote:

> Carsten Dominik <carsten.dominik@gmail.com> writes, a long time ago:
>
> > On May 19, 2011, at 2:34 PM, Christophe Rhodes wrote:
> >
> >> To produce documents in something approaching my organization's house
> >> style, I need to be able to style the headers of tables.  It's nice that
> >> orgtbl has the functionality for this, but the call to orgtbl-to-latex
> >> has a hard-coded list of parameters with no possibility for extension.
> >> With the attached patch, I am able to put e.g.
> >>
> >> #+BIND: org-export-latex-tables-orgtbl-extra-parameters (:hfmt
> "\\multicolumn{1}{c}{\\bf\\color{white}\\cellcolor{blue}%s}")
> >>
> >> in the header of my document, and tables throughout the document all
> >> pick up this style.
> >>
> >> I daresay that this is not the optimal way of doing things; while this
> >> solves my immediate problem there is likely to be a more general way of
> >> doing things.
> >
> > would it be better to be able to set these parameters on a per-table
> basis with ATTR_LaTeX ?
> > Would you like to try to prepare a patch to this effect?
>
> Find attached a patch to this effect.  It is the combination of two
> changes which I consider tiny: one is the support for hfmt itself as an
> ATTR_LaTeX attribute; the other is the consolidation of the
> word-matching on the attributes into local macros, which I needed
> because my use case (as above) includes the string "multicolumn", which
> was otherwise confusing the attribute parser into thinking that I needed
> a table* LaTeX environment.
>
> Please let me know if this suits better.
>
>
>
> Christophe
>
>

Niels Giesen <niels.giesen@gmail.com> writes:

> Could you provide us with a minimal example of how this new functionality
> can be used?

Sure, sorry.  Here we go:

--- start here ---
#+TITLE: Example of using hfmt
#+AUTHOR: Christophe Rhodes

* Introduction
  This document shows the use of the =hfmt= tag in =#+LaTeX_ATTR=
  lines to customize table headings.  Analgous functionality is
  available in HTML export by customizing the style of =th= tags.
* Example table

#+ATTR_LaTeX: hfmt=\multicolumn{1}{c}{\textbf{%s}}
| table       | headings  |
|-------------+-----------|
| body        | cells     |
| have        | unchanged |
| formatting. |           |
---  end here  ---

> I am trying to test it and see if there are any conflicts with my patch of
> late to supports the booktabs package @
> http://patchwork.newartisans.com/patch/1016/  (aside from one of the two
> patches not applying without some minor human intervention around line
> 1998).

Apart from the code conflict itself, I don't see why it shouldn't work:
this patch only changes the export of individual cells, while the
booktabs one alters the export of lines :-).  Your patch took the
approach I originally took too, with a customization variable; Carsten
(in May, aeons ago) suggested that an attribute might be preferable,
which is why I've reworked it in this way.  (It might be sensible for my
patch to have a configuration variable so that there could be a
document-wide default, too; I don't know whether it would be sensible
for yours to be customizeable using ATTR_LaTeX...

> Besides that, it would in general be good to have an example for
> documentation purposes.

I hope this helps,

Christophe

Hi,

Christophe Rhodes <csr21@cantab.net> writes:

> Carsten Dominik <carsten.dominik@gmail.com> writes, a long time ago:
>
>>
>> would it be better to be able to set these parameters on a per-table
>> basis with ATTR_LaTeX ?  Would you like to try to prepare a patch to
>> this effect?
>
> Find attached a patch to this effect.

Is there anything else that I can do to encourage this patch into the
upstream org-mode?

Thanks,

Christophe

Christophe Rhodes <csr21@cantab.net> writes:

> Christophe Rhodes <csr21@cantab.net> writes:
>
>> Carsten Dominik <carsten.dominik@gmail.com> writes, a long time ago:
>>
>>>
>>> would it be better to be able to set these parameters on a per-table
>>> basis with ATTR_LaTeX ?  Would you like to try to prepare a patch to
>>> this effect?
>>
>> Find attached a patch to this effect.
>
> Is there anything else that I can do to encourage this patch into the
> upstream org-mode?

Again, is there anything more I can do to get this functionality
(customizing header lines of tables in LaTeX export, in case everyone
has lost the context) into org-mode?

Best,

Christophe

Hi Christophe,

Christophe Rhodes <csr21@cantab.net> writes:

> Again, is there anything more I can do to get this functionality
> (customizing header lines of tables in LaTeX export, in case everyone
> has lost the context) into org-mode?

I saw your patch, thanks for it.

I'm willing to apply it, but I will do when I have a good idea of how it
interacts with Niels proposal, and maybe a generalization of Niels idea,
where it would be possible to set a default #+ATTR for tables, images,
etc.

Best,