Re: [PATCH] Improve usage of odt content templates

[Nicolas Goaziou <n.goaziou@gmail.com>]

Hello,

Christian Kellermann <ckeen@pestilenz.org> writes:

> I have been using org-mode's odt exporter heavily for the last days
> with the attached patches. These scratch an itch I have and I submit
> them to this list in the hope of being useful to others.

Thank you for your patches.

> * Possibility to override the globally defined
> org-odt-content-template-file variable in the document

It is already possible to override the varible file-wise with:

  #+BIND: org-odt-content-template-file "somefile"

I'm not sure it is worth adding another keyword. OTOH, there's also
ODT_STYLES_FILE and they are quite symmetric, so one could expect to be
able to set both. But then, `org-odt-content-template-file''s docstring
needs to be updated, and the feature should be documented in the manual.

Also, it should be

  (:odt-content-template-file "ODT_CONTENT_TEMPLATE_FILE" nil org-odt-content-template-file t)

> * Avoid inserting the document title as the first thing in the
> document contents, as there already is a title set in a title page
> in the template. As org-mode already sets the title data tag this
> can be used in the template to generate the correct title. However
> inserting the title as text is not desireable in that scenario.

I think this is a more general issue: should we implement an

  #+OPTIONS: title:nil

feature? I think it makes some sense since we already have date:nil and
author:nil. In any case, keywords are not meant to be used for booleans.
This should be an OPTIONS item.


Regards,

-- 
Nicolas Goaziou