Re: [O] [PATCH] Improve usage of odt content templates

2014-05-22 Thread Detlef Steuer
Am Wed, 21 May 2014 14:47:37 +0200 schrieb Nicolas Goaziou n.goaz...@gmail.com: Hello, Christian Kellermann ck...@pestilenz.org writes: I first thought about using ODT_STYLES_FILE in the list form and pick out the content.xml from there, but maybe that's a bit unexpected as one might

Re: [O] [PATCH] Improve usage of odt content templates

2014-05-22 Thread Rasmus
Detlef Steuer detlef.ste...@gmx.de writes: Introducing the item is easy, but making something out of it in each back-end is not, as it requires to define what title:nil means there. In particular, should it be an empty title or something else? For example, ascii back-end provides a banner

Re: [O] [PATCH] Improve usage of odt content templates

2014-05-21 Thread Nicolas Goaziou
Hello, Christian Kellermann ck...@pestilenz.org writes: I first thought about using ODT_STYLES_FILE in the list form and pick out the content.xml from there, but maybe that's a bit unexpected as one might use a different content than from the style. But the control flow as it is now would

Re: [O] [PATCH] Improve usage of odt content templates

2014-05-20 Thread Eric Abrahamsen
Rasmus ras...@gmx.us writes: Nicolas Goaziou n.goaz...@gmail.com writes: 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

Re: [O] [PATCH] Improve usage of odt content templates

2014-05-20 Thread Christian Kellermann
Rasmus ras...@gmx.us writes: That's nicer than a blank title (#+TITLE: ). I prefer the earlier ox-behavior where no title would be printed if title was missing, rather than using the file-name. The file name is never interesting in my work flow. If introducing a title option it would be

Re: [O] [PATCH] Improve usage of odt content templates

2014-05-20 Thread Detlef Steuer
Am Tue, 20 May 2014 16:37:45 +0800 schrieb Eric Abrahamsen e...@ericabrahamsen.net: Rasmus ras...@gmx.us writes: Nicolas Goaziou n.goaz...@gmail.com writes: I think this is a more general issue: should we implement an #+OPTIONS: title:nil feature? I think it makes some sense

Re: [O] [PATCH] Improve usage of odt content templates

2014-05-20 Thread Bastien
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: 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

Re: [O] [PATCH] Improve usage of odt content templates

2014-05-19 Thread Nicolas Goaziou
Hello, Christian Kellermann ck...@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. *

Re: [O] [PATCH] Improve usage of odt content templates

2014-05-19 Thread Rasmus
Nicolas Goaziou n.goaz...@gmail.com writes: 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

Re: [O] [PATCH] Improve usage of odt content templates

2014-05-19 Thread Christian Kellermann
Hi! * Nicolas Goaziou n.goaz...@gmail.com [140519 18:16]: 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