From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Footnote definition within a verse block has spurious line breaks when exported to LaTeX
Date: Sat, 05 Dec 2020 10:09:22 +0100 [thread overview]
Message-ID: <87360kpqkd.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87sg8prant.fsf@posteo.net> ("Juan Manuel Macías"'s message of "Tue, 01 Dec 2020 13:08:38 +0100")
Hello,
Juan Manuel Macías <maciaschain@posteo.net> writes:
> When a verse block includes a footnote reference, the
> corresponding footnote definition is
> understood in the LaTeX export as if it were part of the verses.
> In other words, every
> line in a =\footnote{}= macro ends with the string =\\=, and the
> spaces between paragraphs are understood as spaces
> between stanzas (\vspace*{1em}). If the text of the footnote
> definition contains one or more filled
> paragraphs, then the export result is catastrophic.
>
> For example, if we have something like this:
>
> #+begin_src org
> ,#+begin_verse
> lorem
> ipsum[fn:1]
> dolor
> ,#+end_verse
>
> [fn:1] Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
> Donec hendrerit tempor
> tellus. Donec pretium posuere tellus. Proin quam nisl, tincidunt
> et, mattis eget,
> convallis nec, purus.
>
> Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec
> hendrerit tempor tellus.
> Donec pretium posuere tellus. Proin quam nisl, tincidunt et,
> mattis eget, convallis nec,
> purus.
> #+end_src
This is hopefully fixed in master branch. Let me knows if it works for
you.
Thank you for the report.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2020-12-05 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 12:08 Footnote definition within a verse block has spurious line breaks when exported to LaTeX Juan Manuel Macías
2020-12-05 9:09 ` Nicolas Goaziou [this message]
2020-12-05 13:47 ` 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=87360kpqkd.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--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).