From: Maxim Nikulin <m.a.nikulin@gmail.com>
To: 48334@debbugs.gnu.org
Subject: bug#48334: No <title> elements in HTML manual pages
Date: Mon, 10 May 2021 21:48:26 +0700 [thread overview]
Message-ID: <476ffbc9-bd89-b9f1-9132-86b54ff8dded@gmail.com> (raw)
HTML pages of Emacs manual, e.g.
https://www.gnu.org/software/emacs/manual/html_node/elisp/Motion.html
do not have <title> element. Open page source in browser,
inspector in browser developer tools, or just fetch the page
using e.g. curl to see that metadata in <head> element
are rather scarce.
As a result, browser tab title is not informative. In the case of
Firefox in can be "google.com/url?q=http..." due to intermediate
redirection and a bug in Firefox https://bugzilla.mozilla.org/1401091
Even if Firefox had not this bug, node names instead of URLs
it tab titles would provide better user experience.
For the particular page, my expectation for <title> element content
is something like
- "30.2 Motion (Emacs Lisp)"
- "(elisp) Motion"
- "30.2 Motion"
Texinfo manual is not affected, its pages contains reasonable
<title>, e.g.
https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Generating-HTML.html
I hope, it is enough to change some settings of HTML export for Emacs
manuals to improve quality of generated pages. However I am not familiar
with texinfo enough to provide instructions which options should be tuned.
The reason why I use HTML format of Emacs manuals is that I have not
enough experience with Emacs yet. So it easier to find particular
sections using search engines that take into account relevance or even
synonyms. Docstrings for Emacs functions and variables rarely have
direct links to texinfo nodes from manuals that provides higher level
overview or guide for related functionality.
next reply other threads:[~2021-05-10 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 14:48 Maxim Nikulin [this message]
2021-10-05 14:14 ` bug#48334: No <title> elements in HTML manual pages Maxim Nikulin
2022-07-02 16:19 ` Lars Ingebrigtsen
2022-07-02 17:02 ` Eli Zaretskii
2022-07-03 12:16 ` Lars Ingebrigtsen
2022-07-03 13:13 ` Eli Zaretskii
2022-07-03 14:48 ` Max Nikulin
2022-07-04 10:42 ` Lars Ingebrigtsen
2022-07-04 11:36 ` Eli Zaretskii
2022-07-05 11:09 ` 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
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=476ffbc9-bd89-b9f1-9132-86b54ff8dded@gmail.com \
--to=m.a.nikulin@gmail.com \
--cc=48334@debbugs.gnu.org \
/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).