emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: emacs-orgmode@gnu.org
Subject: Re: [Exporter] Why is :author a list in the communication channel?
Date: Mon, 4 Nov 2013 21:07:36 +0100	[thread overview]
Message-ID: <20131104210736.03f0e9b6@aga-netbook> (raw)
In-Reply-To: <87ob60c6cv.fsf@gmail.com>

Dnia 2013-11-04, o godz. 20:30:24
Nicolas Goaziou <n.goaziou@gmail.com> napisał(a):

> Thorsten Jolitz <tjolitz@gmail.com> writes:
> 
> > Ok, I understand, so this is all working fine just as intended. For
> > multiple authors one could use a workaround/convention like 
> >
> >  ,------------------------------------------
> >  | #+author: Thorsten_Jolitz Thomas_Mueller
> >  `------------------------------------------
> >
> > and then split the string two times (first blanks, then
> > underscores).
> 
> It is also possible to allow multiple author lines, by adding `space'
> behaviour in `org-export-options-alist', but I'm not sure this is
> really necessary.

It is well possible that I don't understand something here, but in some
LaTeX classes you use \author{...} many times instead of the default
\author{... \and ...}.  Maybe when exporting to such LaTeX classes,
allowing multiple #+AUTHOR: lines might make sense?

> Regards,

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University

  reply	other threads:[~2013-11-04 20:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-02 20:40 [Exporter] Why is :author a list in the communication channel? Thorsten Jolitz
2013-11-02 21:33 ` Nicolas Goaziou
2013-11-02 21:48   ` Thorsten Jolitz
2013-11-02 22:30 ` Aaron Ecay
2013-11-04 18:10   ` Thorsten Jolitz
2013-11-04 18:20     ` Nicolas Goaziou
2013-11-04 18:42       ` Thorsten Jolitz
2013-11-04 19:30         ` Nicolas Goaziou
2013-11-04 20:07           ` Marcin Borkowski [this message]
2013-11-04 19:45         ` Nick Dokos

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=20131104210736.03f0e9b6@aga-netbook \
    --to=mbork@wmi.amu.edu.pl \
    --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).