all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: seb@k-7.ch, stefan@marxist.se, npostavs@gmail.com,
	contovob@tcd.ie, 31405@debbugs.gnu.org, larsi@gnus.org
Subject: bug#31405: 25.3; Python.el doesn't provide infos to info-lookup-symbol
Date: Sat, 28 Aug 2021 13:05:52 +0300	[thread overview]
Message-ID: <83a6l1opdr.fsf@gnu.org> (raw)
In-Reply-To: <87k0k5evut.fsf@gmail.com> (message from Augusto Stoffel on Sat,  28 Aug 2021 11:56:10 +0200)

> From: Augusto Stoffel <arstoffel@gmail.com>
> Date: Sat, 28 Aug 2021 11:56:10 +0200
> Cc: contovob@tcd.ie, larsi@gnus.org, stefan@marxist.se, npostavs@gmail.com,
>  seb@k-7.ch
> 
> FWIW, the Info version of the Python manual doesn't look very good.  The
> (only) reason being that Info doesn't let you write a plain hyperlink in
> the middle of a sentence; rather it assumes that all hyperlinks are part
> of the phrase “See [link target].”.
> 
> Since the Python manual wasn't written specifically for Texinfo, it has
> lots of hyperlinks, and so will say things like "this function takes a
> see string. as argument and return a see boolean."

That's because they use tools that mainly target HTML docs, and don't
much care about the other output formats.  These inline references
look badly in print.  GCC is migrating to the same tools, and its
manuals will have the same problems (because people who drive this
migration don't seem to care too much about Info, either).

> I brought this up in [1], but unfortunately the Texinfo people seem to
> like this limitation a lot.

The way to overcome this difficulty is to use Texinfo macros, so that
these inline references look in HTML as HTML users expect, but at the
same time don't uglify Info or PS/PDF output.  I believe this was
mentioned on the Texinfo list more than once.





  reply	other threads:[~2021-08-28 10:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-10 15:24 bug#31405: 25.3; Python.el doesn't provide infos to info-lookup-symbol Sébastien Gendre
2019-05-07 17:36 ` npostavs
2019-08-23  7:04 ` Stefan Kangas
2021-08-12 14:13   ` Lars Ingebrigtsen
2021-08-12 15:13     ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-12 15:21       ` Lars Ingebrigtsen
2021-08-12 15:42         ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-28  9:56           ` Augusto Stoffel
2021-08-28 10:05             ` Eli Zaretskii [this message]
2021-08-12 16:06         ` Eli Zaretskii
2021-08-12 16:02       ` Eli Zaretskii
2021-08-13 11:34         ` Lars Ingebrigtsen

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=83a6l1opdr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31405@debbugs.gnu.org \
    --cc=arstoffel@gmail.com \
    --cc=contovob@tcd.ie \
    --cc=larsi@gnus.org \
    --cc=npostavs@gmail.com \
    --cc=seb@k-7.ch \
    --cc=stefan@marxist.se \
    /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.