Re: [Gnash-dev] Docbook derived documentation on the website
strk wrote: Mmm... I think we should have two versions on the manual published, one for the latest release and one for current CVS. Actually, when new releases come out it might be worth keeping the manual for older releases online, as an archive... I've always just updated the manual on the website by hand. For the last year, I've updated the manual to match CVS improvements. I think now that the 0.7.2 release is out, and is in pretty good shape, (plus it's in many distros) the manual on the gnu.org site should probably match the release. We can put the CVS version on the developers site, which should be publically available as soon as I can get somebody to make a pass through it, as I suck at writing these things... - rob - ___ Gnash-dev mailing list Gnash-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnash-dev
Re: [Gnash-dev] Docbook derived documentation on the website
I was wondering...is there some reason that we don't build the documentation by default? It seems to me that this would be more universally useful than, say, Klash support, which is default. Not that I don't think the manual should also be available in other places, it's just something I've been wondering about. - Ann Rob wrote: I've always just updated the manual on the website by hand. For the last year, I've updated the manual to match CVS improvements. I think now that the 0.7.2 release is out, and is in pretty good shape, (plus it's in many distros) the manual on the gnu.org site should probably match the release. We can put the CVS version on the developers site, which should be publically available as soon as I can get somebody to make a pass through it, as I suck at writing these things... ___ Gnash-dev mailing list Gnash-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnash-dev
Re: [Gnash-dev] Docbook derived documentation on the website
ann wrote: I was wondering...is there some reason that we don't build the documentation by default? It seems to me that this would be more universally useful than, say, Klash support, which is default. The main reason is that the dependencies for producing the various output formats are nasty, and aren't even supported on all platforms. Even worse, building docbook requires more than a trivial amount of packages, which aren't even the same on all distributions. So building doc by default would likely generate a huge pile of bug reports that we'd not be able to do much about. KDE support is available most everywhere, and there's a lot of KDE users out there, so it needs to be built by default. - rob - ___ Gnash-dev mailing list Gnash-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnash-dev
Re: [Gnash-dev] Docbook derived documentation on the website
strk wrote: BTW, I'd like to drop the Java dependency for that... anyone ? Only if you can find another way to generate PDF from Docbook. The Java dependency bugs me too, but many people prefer PDF output. I've tried several other tools for producing PDFs, but the current way is the only one that works so far. - rob - ___ Gnash-dev mailing list Gnash-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnash-dev
Re: [Gnash-dev] Docbook derived documentation on the website
On Tue, Dec 12, 2006 at 02:42:07PM +0100, ann wrote: Hi, How is the document http://www.gnu.org/software/gnash/manual/gnash.html updated? I am wondering if the file is copied manually, because it seems to be much older than the current version of the file. There's a repository for that website too, see : https://savannah.gnu.org/cvs/?group=gnash On commit, the website is updated. Should I update it, or is it meant to always describe the most recent release of the software, rather than the most recent version in the repository? I know that most of my changes to the files have been corrections, rather information about new functionality, but suspect that's not the case for the Testing chapter. Could someone please comment? Mmm... I think we should have two versions on the manual published, one for the latest release and one for current CVS. Actually, when new releases come out it might be worth keeping the manual for older releases online, as an archive... --strk; ___ Gnash-dev mailing list Gnash-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnash-dev
