From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Improve usage of odt content templates
Date: Thu, 22 May 2014 10:23:32 +0200 [thread overview]
Message-ID: <874n0ikyrf.fsf@gmx.us> (raw)
In-Reply-To: 20140522100053.673d483f@gaia
Detlef Steuer <detlef.steuer@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 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.
IMO, it just shouldn't set title in LaTeX. When I use author:nil
\author{·} is simply not set and could be loaded via another file. I
would also remove the \maketitle command. I don't have any
particularly good argument for this, other than it feels right. . .
Alternatively, there could be a yet another option maketitle:if-title,
maketitle:always. . .
With the text backend. I would make the banner dependent on the
presence of a title. I.e. I'd probably go for no title, no banner.
Though it's less clear here to what extend a title-less banner makes
sense here.
—Rasmus
--
When in doubt, do it!
next prev parent reply other threads:[~2014-05-22 8:23 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
2014-05-22 8:23 ` Rasmus [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874n0ikyrf.fsf@gmx.us \
--to=rasmus@gmx.us \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.