emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Max Nikulin <manikulin@gmail.com>,  emacs-orgmode@gnu.org
Subject: Re: Exporting multiple #+AUTHOR keywords
Date: Fri, 02 Feb 2024 22:26:23 +0000	[thread overview]
Message-ID: <878r424i5s.fsf@posteo.net> (raw)
In-Reply-To: <87r0husjl9.fsf@localhost> (Ihor Radchenko's message of "Fri, 02 Feb 2024 20:21:38 +0000")

Ihor Radchenko writes:

> Juan Manuel Macías <maciaschain@posteo.net> writes:
>> Sorry if this is off topic, but something like this:
>> #+AUTHOR: Fred Astaire
>> #+AUTHOR: Ginger Rogers
>> is exported to LaTeX as:
>> \author{Fred Astaire Ginger Rogers}
>> Shouldn't there be some separation? In LaTeX the usual thing is:
>> \author{Fred Astaire \and Ginger Rogers}
> You can do
> #+AUTHOR: Fred
> #+AUTHOR: Astaire
> #+AUTHOR: and Ginger
> #+AUTHOR: Rogers
> The values are simply concatenated before passing to the exporter.
> Can we concatenate with "\and"? Sure. But not by default or it would be
> a breaking change.

Thanks for the explanation. I've never made documents with more than one
author, so I've never thought about this scenario. For a moment I
thought org supported more than one author (explicitly, I mean).

Anyway, \and is just a formatting command: add a space between two
authors. Some people may prefer to put a line break \\ or anything else.
Of course, \and (and any other format command) will have a negative
effect on the pdfauthor metadata, which only collects text strings. It
is a similar problem to the one with footnotes, which Maxim commented
on. I think the basic problem is that org uses #+author, #+title, etc.
as a single source for both the metadata strings and the exported
format, i.e. the title, the author, the date that is printed somewhere.

Perhaps the ideal would be to distinguish in some way between
author-metadata and author-exported-format. For example something like:

#+AUTHOR[John Doe and Luke Skywalker]: John Doe @@latex:\and@@ Luke

The optional string in square brackets would be the metadata; the rest
would be the direct exported format. If there is no optional string, the
value is used for both metadata and format. Could this be also a
possible solution to the footnote problem?

Best regards,

Juan Manuel 

Juan Manuel Macías -- Composición tipográfica, tratamiento de datos, diseño editorial y ortotipografía

  reply	other threads:[~2024-02-02 22:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 20:42 Possible LaTeX export bug: Footnotes in items Eric Anderson
2024-01-24 12:11 ` [BUG] Footnotes in section titles Ihor Radchenko
2024-01-24 14:14   ` Max Nikulin
2024-01-24 15:23     ` Juan Manuel Macías
2024-01-24 15:31       ` Colin Baxter
2024-01-24 15:41         ` Juan Manuel Macías
2024-01-26 12:53           ` Ihor Radchenko
2024-01-26 13:17             ` Juan Manuel Macías
2024-01-26 16:43             ` Max Nikulin
2024-02-01 14:44               ` [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc) (was: [BUG] Footnotes in section titles) Ihor Radchenko
2024-02-01 17:44                 ` [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc) Juan Manuel Macías
2024-02-01 17:57                   ` Marvin Gülker
2024-02-02 17:00                   ` Ihor Radchenko
2024-02-02 17:12                     ` Marvin Gülker
2024-02-02 17:49                       ` Ihor Radchenko
2024-02-02 18:10                     ` Juan Manuel Macías
2024-02-02 20:21                       ` Exporting multiple #+AUTHOR keywords (was: [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc)) Ihor Radchenko
2024-02-02 22:26                         ` Juan Manuel Macías [this message]
2024-02-04 15:21                           ` Exporting multiple #+AUTHOR keywords Ihor Radchenko
2024-02-04 16:16                             ` Max Nikulin
2024-02-04 22:13                               ` Juan Manuel Macías
2024-02-05 14:57                               ` Ihor Radchenko
2024-01-26 12:09     ` [BUG] Footnotes in section titles Ihor Radchenko
2024-02-09 16:41       ` Ihor Radchenko
  -- strict thread matches above, loose matches on Subject: below --
2024-02-17  0:36 Exporting multiple #+AUTHOR keywords ypuntot
2024-02-17 10:34 ` Juan Manuel Macías

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:

  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=878r424i5s.fsf@posteo.net \
    --to=maciaschain@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.com \
    --cc=yantar92@posteo.net \


* 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


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).