On Mon, 7 Jan 2008, Dan Espen wrote:
Dominik Vogt <[EMAIL PROTECTED]> writes:
Hi Scott,
On Sat, Sep 01, 2007 at 12:38:34PM +0200, Dominik Vogt wrote:
Now that we have the html docs, someone has to write down detailed
instructions in docs/DEVELOPER how to get the html files into
fvwm-web during the release process. I can't do that.
I *really* need instruction in the docs/DEVELOPER file if we want
the man pages on the web page to be up to date. I don't have the
slightest idea what I have to do. Help!
There does seem to be an issue.
I was able to build with --enable-htmldoc.
That gave me some pretty nice man pages in
fvwm/share/2.5.25/doc/fvwm/fvwm.
Then I looked in fvwm-web and was surprised to see
the manpages2php script was still in there.
Then I looked at the Fvwm web site and I see we still have
the old web pages online at fvwm.org.
I think it's time to put the new pages in place.
I'll take care of this if you want.
I think we need to change the manpages2php script so it doesn't
do anything for the "unstable" branch.
There are currently two places with online manpages. And the manpages2html
does still work on the generated manpage. (But all links are lost.)
Document the new procedure which should just be:
build with --enable-htmldoc
then copy the whole hierarchy created in /share over to
fvwm-web/documentation/manpages/unstable.
Then update/commit.
In theory that is good. But right now the documentation seems to be
missing some files in the installed directory. (Which is a bug.) And it
also adds the need to actually install the source once except from within
the distcheck in order to update the documentation.
Files currently not properly installed are:
modules/FvwmTabs.html
commands/WindowsDesk.html
modules/images/FvwmTabs/*.png
/Viktor
