[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: using manual_html as output directory for HTML
From: |
Patrice Dumas |
Subject: |
Re: using manual_html as output directory for HTML |
Date: |
Sat, 5 Feb 2022 17:39:27 +0100 |
On Sat, Feb 05, 2022 at 02:36:47PM +0100, Patrice Dumas wrote:
> >
> > The URL for a manual is something different. Adding "_html" to the
> > name of the manual would make the URL worse. If the directory is
> > output with _html then the files should still be uploaded to the web
> > server in a directory named after the manual.
>
> I do not get it. My point was just that the HTML Xref could need to be
> updated to match with the change. Do you think that the manuals in the
> web should not have the _html prepended even if this is the default for
> a manual split?
The current rules has:
If the present manual is split, and the referent manual is also split, the
directory is ‘../referent/’ and the file is the expanded node name (described
later).
...
If the present manual is mono, and the referent manual is split, the directory
is referent/ and the file is the expanded node name.
In both of these cases, I think that it would be better to replace
'referent' by 'referent_html'.
As a side note, most of the actual cross manuals references are done
thanks to htmlxref.cnf anyway.
> > I believe it is the gendocs.sh script from Gnulib that is used by many
> > GNU packages for building web documentation; we should check this
> > still works with any changes.
>
> Indeed. Changes in automake are also probably needed.
It seems that automake also uses -o.
--
Pat