>>>
>>
>> May be I should specify the packages that are being called, so the user can
>> make sure those are installed or modify the config file. But I prefer the
>> basic set of LaTeX packages being called by default rather than being added
>> in every file.
>
> This will be a problem when one of your collaborators doesn't use your config
> files.
> There are many packages for tabular/table environments.
> Having them in the document gives a strong hint that there is something
> different that may collide with the packages another user prefers. (No-one
> can agree on a basic set of LaTeX packages:-)
>
> If you keep them in the configuration file, the user has to extract the
> relevant information
>
> (setq org-latex-default-packages-alist …)
>
> from your configuration and add it to their configuration file.
>
> You can always supply a template file with all the relevant
> +LaTeX_HEADER
> definitions.
>
> You can even have lines like
>
> #+LaTeX_HEADER: \usepackage{tabulary} % provides column specification LCRJ
> #+LaTeX_HEADER: \usepackage{threeparttable} % A table with cation and notes
> #+LaTeX_HEADER: \renewcommand{\TPTminimum}{\linewidth} % configure
> threeparttable
> #+Latex_HEADER: %\usepackage{tgschola} % enable to use the Schola font
> #+Latex_HEADER: %\usepackage{tgbonum} % enable to use the Bonum font
> #+Latex_HEADER: %\usepackage{tgpagella} % enable to use the Pagella font
> #+Latex_HEADER: \usepackage[urw-garamond]{mathdesign} \linespread{1.0609}
This may be a better solution. We could even provide a separate file with
sample lines that need to go at the top, which can be modified if needed, to be
called in using #+INCLUDE: into a document.
Since Suvayu has offered to have a go at modifying the document for Worg, I
would wait for him to do what he thinks may be best.
Vikas
