emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: 8dcc <8dcc.git@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Customize list of blocks that use "\footnotemark" in `org-latex-footnote-reference'
Date: Sun, 02 Feb 2025 17:05:26 +0000	[thread overview]
Message-ID: <87frkw1dm1.fsf@localhost> (raw)
In-Reply-To: <87o71015kv.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

>>> I am exporting an Org file that contains a large verse block to
>>> LaTeX. This verse block contains footnotes, but they appear in the page
>>> where the LaTeX verse environment ends. I looked at the exported .tex
>>> file and I noticed that it was using "\footnotemark" and
>>> "\footnotetext[N]{...}", instead of "\footnote{...}".
>> ...
>> I seem to remember that the problem you describe goes back to how Org
>> understood the footnote text. When exporting to LaTeX, each line of a
>> footnote was understood as if it were a verse, and Org added \\ at the
>> end. Hence the use of \footnotemark and the
>> ‘org-latex--delayed-footnotes-definitions’ function.
>
> Please try the attached tentative fix.
> I limited special verse contents processing to plain-text directly
> inside verse blocks (as in Org AST), except plain text inside inline
> footnote definitions.

Fixed, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=3218d376fa

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
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:[~2025-02-02 17:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11 17:25 Customize list of blocks that use "\footnotemark" in `org-latex-footnote-reference' 8dcc
2024-09-12 10:18 ` Juan Manuel Macías
2024-12-25  9:21   ` Ihor Radchenko
2025-02-02 17:05     ` Ihor Radchenko [this message]

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=87frkw1dm1.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=8dcc.git@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=maciaschain@posteo.net \
    /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).