From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: "Juan Manuel Macías" <maciaschain@posteo.net>, emacs-orgmode@gnu.org
Subject: Re: Exporting multiple #+AUTHOR keywords
Date: Mon, 05 Feb 2024 14:57:01 +0000 [thread overview]
Message-ID: <87a5of9cxu.fsf@localhost> (raw)
In-Reply-To: <72477546-954c-4c1e-a6e2-9ffb524ad86f@gmail.com>
Max Nikulin <manikulin@gmail.com> writes:
>> Another option is to have a new set of keywords:
>> #+LATEX_AUTHOR: <author with formatting goes here>
>> #+HTML_AUTHOR: ...
> ...
> Another idea:
>
> #+metadata:
> - author ::
> - John Doe
> - Luke Skywalker
> - title :: Some text
>
> With overrides for specific backends
This implies that #+AUTHOR may contain markup, while #+metadata should
not; as opposed to my idea with #+AUTHOR being reserved to "plain"
author and #+BACKEND_AUTHOR defining more specific markup.
I feel that my approach is slightly better because you can have
different author markup for different backends when using my suggestion.
> Perhaps backends may declare if they support footnotes, etc. by defining
> some backend property.
The comment about footnotes belongs to parent thread, not to this
branch.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-02-05 14:54 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 ` Exporting multiple #+AUTHOR keywords Juan Manuel Macías
2024-02-04 15:21 ` 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 [this message]
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:
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=87a5of9cxu.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=maciaschain@posteo.net \
--cc=manikulin@gmail.com \
/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).