emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc) (was: [BUG] Footnotes in section titles)
Date: Thu, 01 Feb 2024 14:44:36 +0000	[thread overview]
Message-ID: <87le84i6qz.fsf@localhost> (raw)
In-Reply-To: <up0ng2$1037$1@ciao.gmane.io>

Max Nikulin <manikulin@gmail.com> writes:

> On 26/01/2024 19:53, Ihor Radchenko wrote:
>> So, I am leaning towards reverting that commit - that will allow things
>> like
>> 
>> #+TITLE: This is a test title[fn::This is test]
>
> I hope, document metadata will be generated with stripped footnotes.

This is a good point.

For now, [fn::This is test], when passed to exporters, is simply treated
as plain text.

If we change the parser nesting rules, Org will pass footnote-reference
objects instead.

Then, in a number of parsers, if something like
(org-export-data (plist-get info :title) info) or
(org-export-data author info)
is used, footnotes may break export because metadata fields often have
special rules about markup that is allowed inside.

In particular, ox-odt will be broken; ox-latex will be broken.

Of course, we can adjust built-in backends to take into account the new
parsing rules, but we have no control over the third-party backends.

On the other hand, when user exports something like
#+AUTHOR: John Doe[fn::935 Pennsylvania Avenue, NW Washington, D.C. 20535-0001]
it is probably not exported as expected anyway.
So, changing things from unexpected export to failing export may not be
a critical regression.

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


  reply	other threads:[~2024-02-01 14:42 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
2024-01-26 16:43             ` Max Nikulin
2024-02-01 14:44               ` Ihor Radchenko [this message]
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:
  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=87le84i6qz.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --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).