From: Lars Ingebrigtsen <larsi@gnus.org>
To: Maxim Nikulin <m.a.nikulin@gmail.com>
Cc: 48334@debbugs.gnu.org
Subject: bug#48334: No <title> elements in HTML manual pages
Date: Sat, 02 Jul 2022 18:19:44 +0200 [thread overview]
Message-ID: <87sfnjxza7.fsf@gnus.org> (raw)
In-Reply-To: <6f746a42-09eb-dffc-993f-a0ba3467aa08@gmail.com> (Maxim Nikulin's message of "Tue, 5 Oct 2021 21:14:04 +0700")
Maxim Nikulin <m.a.nikulin@gmail.com> writes:
>> HTML pages of Emacs manual, e.g.
>> https://www.gnu.org/software/emacs/manual/html_node/elisp/Motion.html
>> do not have <title> element.
> ...
>> 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
>
> Emacs manual is generated by texi2html, texinfo and e.g. Org mode by
> makeinfo --html ...
> In the latter case pages have <title> element, in the former they do
> not (at least without some tuning).
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
These manuals still seem to be missing <title>s. And texi2html has been
superseded by texi2any, which should be adding <title> elements
according to:
https://www.gnu.org/software/texinfo/manual/texinfo/html_node/HTML-Customization-Variables.html
Anybody know who's responsible for generating the HTML manuals?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-07-02 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 14:48 bug#48334: No <title> elements in HTML manual pages Maxim Nikulin
2021-10-05 14:14 ` Maxim Nikulin
2022-07-02 16:19 ` Lars Ingebrigtsen [this message]
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=87sfnjxza7.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=48334@debbugs.gnu.org \
--cc=m.a.nikulin@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).