unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Multiple references to a footnote in texi sources
Date: Thu, 15 Dec 2022 04:47:37 +0000	[thread overview]
Message-ID: <87len9w9w6.fsf@localhost> (raw)
In-Reply-To: <CADwFkm=QkOYqXkjTOi5xPy4ZJO_72eC4CFVwkrSxVZebVe+xiQ@mail.gmail.com>

Stefan Kangas <stefankangas@gmail.com> writes:

> Ihor Radchenko <yantar92@posteo.net> writes:
>
>>> If they share the same footnote _text_, add the text to a variable and
>>> then use that variable.
>>
>> You mean TeX variable?
>
> Yes, that was my idea.

Well. It is what is already done then. Kind of.
Because Org manual is written in Org and Org does allow multiple
references to a footnote, we currently produce texinfo sources that
contain 2 footnotes with identical text.

But such footnotes look strange when referenced sequentially - texinfo
displays two identical footnotes one after another.

-- 
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:[~2022-12-15  4:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 11:41 Multiple references to a footnote in texi sources Ihor Radchenko
2022-12-13 13:18 ` Eli Zaretskii
2022-12-13 13:34   ` Ihor Radchenko
2022-12-13 14:29     ` Eli Zaretskii
2022-12-14 10:13       ` Ihor Radchenko
2022-12-13 19:08     ` Stefan Kangas
2022-12-14 10:10       ` Ihor Radchenko
2022-12-14 21:58         ` Stefan Kangas
2022-12-15  4:47           ` Ihor Radchenko [this message]
2022-12-15  7:49             ` Eli Zaretskii
2022-12-15  8:02               ` Ihor Radchenko
2022-12-15  8:54                 ` Eli Zaretskii
2022-12-14 12:47       ` Gregor Zattler

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87len9w9w6.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stefankangas@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.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).