From: Detlef Steuer <detlef.steuer@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Improve usage of odt content templates
Date: Thu, 22 May 2014 10:00:53 +0200 [thread overview]
Message-ID: <20140522100053.673d483f@gaia> (raw)
In-Reply-To: 87bnur1eom.fsf@gmail.com
Am Wed, 21 May 2014 14:47:37 +0200
schrieb Nicolas Goaziou <n.goaziou@gmail.com>:
> Hello,
>
> Christian Kellermann <ckeen@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 need to be refactored to
> > make this a nice patch too.
> >
> > I shall resend this patch with proper docstrings and manual patches
> > if you like.
>
> Please do.
>
> >> 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.
> >
> > I don't feel qualified to decide on this. I can provide the needed
> > patches though.
>
> 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 as its title. Should
> title:nil remove the title from the banner or should it remove the
> banner altogether, thus overriding date:t and author:t items.
>
> Likewise, should title:nil insert "\title{}" in a LaTeX document
> header, remove the "\maketitle{}" line, or perhaps, both?
To be consistent over backends I think it should be implemented as
an empty title string. If date:t or/and author:t are specified these
should show up somewhere.
\maketitle{} should be removed only, if a titlepage would appear empty
in the exported document.
Just the usual 2c worth of opinion.
Detlef
>
> It seems that you answered to that question regarding ODT back-end
> though.
>
> WDYT?
>
>
> Regards,
>
next prev parent reply other threads:[~2014-05-22 8:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 10:42 [PATCH] Improve usage of odt content templates Christian Kellermann
2014-05-19 16:17 ` Nicolas Goaziou
2014-05-19 16:34 ` Rasmus
2014-05-20 7:56 ` Christian Kellermann
2014-05-20 8:37 ` Eric Abrahamsen
2014-05-20 10:39 ` Detlef Steuer
2014-05-19 16:41 ` Christian Kellermann
2014-05-21 12:47 ` Nicolas Goaziou
2014-05-22 8:00 ` Detlef Steuer [this message]
2014-05-22 8:23 ` Rasmus
2014-05-20 15:12 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140522100053.673d483f@gaia \
--to=detlef.steuer@gmx.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).