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: Colin Baxter <m43cap@yandex.com>,
	 Max Nikulin <manikulin@gmail.com>,
	Eric Anderson <kluwak@gmail.com>,
	 ihor Timothy <orgmode@tec.tecosaur.net>,
	 orgmode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Footnotes in section titles
Date: Fri, 26 Jan 2024 13:17:28 +0000	[thread overview]
Message-ID: <87il3gkzdj.fsf@posteo.net> (raw)
In-Reply-To: <875xzgfe8b.fsf@localhost> (Ihor Radchenko's message of "Fri, 26 Jan 2024 12:53:08 +0000")

Ihor Radchenko writes:

> Juan Manuel Macías <maciaschain@posteo.net> writes:
>> ...
>> \title{Lorem ipsum dolor\thanks{blah blah}}
>> ...
>> Org does not have support for this type of notes in the #+title or
>> #+author keywords. For LaTeX you can use a macro.
> Hmm.
> The reason footnotes are not allowed in #+title and other keywords is
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=7ebe87e2d5fb6c
>     Inserting footnote references in parsed keywords (e.g., TITLE or
>     CAPTION) can lead to subtle bugs.  Indeed, it is impossible to know in
>     time if that particular footnote is going to be used in the output,
>     and, therefore, if it should count, e.g., in
>     `org-export-get-footnote-number'.
> However, I am not sure about that line of reasoning - we generally don't
> know if *any* given footnote reference is going to be used in the output
> or not because export backend may skip references or whole parts of the
> original Org file. Same for user filters.
> So, I am leaning towards reverting that commit - that will allow things
> like
> #+TITLE: This is a test title[fn::This is test]
> If we need special handling for footnotes in title (like using \thanks
> instead of \footnote), it is easy.

I completely agree. I think it would be a great improvement, since, as
Colin Baxter says, in academic articles it is a very common practice to
add foot notes to the title of the article or the name of the author.

As for the \thanks{} command, org exports the keyword #+email within a
\thanks{} command as '\author{Name\thanks{email}}0. I don't think two
\thanks macros collide within author (assuming the user adds the email
and puts a footnote in #+author. Anyway, I think the most common thing
is to put the email below the author's name, not as a footnote, but that
is another topic and also depends on the style of each publication,
journal, etc.

>> ... For backends like odt
>> it is trickier. Look at this thread:
>> https://lists.gnu.org/archive/html/emacs-humanities/2024-01/msg00000.html
>> I think it would be nice if Org had some kind of support for notes in
>> #+title and #+author...
> No idea about how to do it in ODT. If someone familiar with OpenDocument
> spec can help, it would be welcome.

I don't have much idea about odt, but I think the problem comes from a
type of nesting that is not allowed in the odt xml. I think org exports
#+author inside the initial-creator tag:

(format "<meta:initial-creator>%s</meta:initial-creator>\n" author)

And within that tag the code for a footnote produces an error when
opening the document. If the footnote is placed right after
</meta:initial-creator>, there would be no 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-01-26 13:18 UTC|newest]

Thread overview: 24+ 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 [this message]
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
2024-01-26 12:09     ` [BUG] Footnotes in section titles Ihor Radchenko
2024-02-09 16:41       ` Ihor Radchenko

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=87il3gkzdj.fsf@posteo.net \
    --to=maciaschain@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=kluwak@gmail.com \
    --cc=m43cap@yandex.com \
    --cc=manikulin@gmail.com \
    --cc=orgmode@tec.tecosaur.net \
    --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).