[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#48334: No <title> elements in HTML manual pages
|
From: |
Eli Zaretskii |
|
Subject: |
bug#48334: No <title> elements in HTML manual pages |
|
Date: |
Mon, 04 Jul 2022 14:36:07 +0300 |
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: m.a.nikulin@gmail.com, 48334@debbugs.gnu.org
> Date: Mon, 04 Jul 2022 12:42:42 +0200
>
> I tried running the code now (and commented out the
> manual-html-fix-headers function), and I ended up with:
>
> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
> "http://www.w3.org/TR/html4/loose.dtd";>
> <html>
> <!-- Created by GNU Texinfo 6.8, https://www.gnu.org/software/texinfo/ -->
> <head>
> <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
> <!-- This file describes the Emacs auth-source library.
>
> Copyright (C) 2008-2022 Free Software Foundation, Inc.
>
> Permission is granted to copy, distribute and/or modify this document
> under the terms of the GNU Free Documentation License, Version 1.3 or
> any later version published by the Free Software Foundation; with no
> Invariant Sections, with the Front-Cover Texts being "A GNU Manual,"
> and with the Back-Cover Texts as in (a) below. A copy of the license
> is included in the section entitled "GNU Free Documentation License".
>
> (a) The FSF's Back-Cover Text is: "You have the freedom to copy and
> modify this GNU manual." -->
> <title>Emacs auth-source Library 0.3</title>
>
> This is with texi2any (GNU texinfo) 6.8. If I'm reading the code right,
> the delete-region here is just deleting that <meta, the comment, and the
> <title>.
That's strange, because I remember testing the changes, and I also
used Texinfo 6.8. Did you compare the produced HTML with what's on
the Web site? That should show the differences clearly. Also, I
think the title (and the file I worked mostly) is index.html -- did
you look at that, or did you look at some other file?
> > > Failing that, I think the only alternative is to see how the original
> > > Texinfo output looks in a browser, compare that with the edited
> > > manuals, and then decide which of the edits are really needed. One
> > > problem with that is that we'll probably have to require Texinfo 6.8
> > > or later if we go that way, because maintaining compatibility with
> > > multiple Texinfo versions is really too much. Ideally, we should keep
> > > the edits to the absolute minimum.
> >
> > I think altering the HTML in this way isn't idea. It'd be much better
> > to just parse the HTML, alter the DOM (to remove/insert elements), and
> > then write the DOM out to HTML again. That'd be a whole lot less
> > brittle.
That's fine with me, but that, too, assumes someone who can understand
the resulting DOM, and which of its parts we want to change and why.