all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: stefankangas@gmail.com, emacs-devel@gnu.org
Subject: Re: Multiple references to a footnote in texi sources
Date: Thu, 15 Dec 2022 09:49:27 +0200	[thread overview]
Message-ID: <83sfhhksxk.fsf@gnu.org> (raw)
In-Reply-To: <87len9w9w6.fsf@localhost> (message from Ihor Radchenko on Thu, 15 Dec 2022 04:47:37 +0000)

> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> Date: Thu, 15 Dec 2022 04:47:37 +0000
> 
> 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.

In my book, this means a footnote is a wrong means to handle these
cases.  If you are talking about a reference to book or a URL, there
are other ways of doing that which don't use @footnote.  I'm guessing
people think they should use @footnote because the have something like
footnote-mode in mind.  But that's superficial similarity, based on
the presence of the same word and on nothing else.



  reply	other threads:[~2022-12-15  7:49 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
2022-12-15  7:49             ` Eli Zaretskii [this message]
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

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

  git send-email \
    --in-reply-to=83sfhhksxk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stefankangas@gmail.com \
    --cc=yantar92@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.