On Thu, 17 Feb 2011 19:35:39 -0500 "D. Michael McIntyre" <[email protected]> wrote:
> On Sunday, February 13, 2011, Detlef Schütz wrote: > > > By the way: there seems to be an old manual written in 2005. Is this > > manual near enough to the actual program? > > It may still be useful if you can get it cheap, but it is out of > date. I wrote that just as Rosegarden 1.0 was coming out, and a > great deal has changed since then. > > Unfortunately, there is no easy way to put together a print version > of our current documentation. We have moved all of it to a wiki now, > in order to make it easier to maintain, and easier for people to help > with writing documentation, but this has made it more difficult to > produce PDF files. > > The documentation is not in the best of shape either, I fear. I used > to be the documentation writer, and that was my only responsibility. > Now I manage the entire project, and do a lot of the development. > Documentation has fallen way down on my list of priorities, and I > don't have much time to be involved with keeping it up to date. We > have help from several people who have taken up some of my slack in > this area, but the job is very large, and our documentation is always > the last thing to get done. Michael, I remembered something from when I had a docuwiki set up as a collaborative website for a course I did. You can export dokuwiki pages to pdf with a plugin called bookcreator. http://www.dokuwiki.org/plugin:bookcreator Perhaps this might be a solution to people asking for a downloadable manual? I could look into how it works and see if it might be a suitable candidate for publishing the wiki to a pdf. Shelagh -- ---------------------------------------------------------------- Email: [email protected] Wave: [email protected] BA(Asian Studies) | ANU Grad Dip IST | UOW ---------------------------------------------------------------- ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Rosegarden-user mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
