As I said, it is available as a PDF or html, once someone gets around putting it there. Simpler for you however is get the manual sources from CVS and build it with docbook to your favourite medium. The README in the man sources will explain how to do it. ----- Original Message ----- From: Aaron Krister Johnson Date: Tuesday, January 18, 2011 7:14 pm Subject: [Csnd] Re: Re: Re: Re: Re: Re: Re: Re: Release of v5.13 To: csound@lists.bath.ac.uk > Hi, > > Some of us use a Linux distro! So, the manual should be clearly available somewhere as source...the various distros have different packaging paradigms; as a result each distro at some stage builds from source. So it's important for Linux users (I imagine a large percentage of Csound users overall), esp. those who maintain packages, to have a way of getting/creating an up-to-date manual. > > I'll try John's CVS approach and report back. > > Cheers, > AKJ > > On Tue, Jan 18, 2011 at 12:33 PM, wrote: > It's released with the OSX installer. I expect the same with Windows. Usually someone also puts the html and PDF versions in the same release directory. I think this will eventually will be done. > > ----- Original Message ----- > From: Aaron Krister Johnson > Date: Tuesday, January 18, 2011 5:44 pm > Subject: [Csnd] Re: Re: Re: Re: Re: Re: Release of v5.13 > To: csound@lists.bath.ac.uk > > > For heavens sake, let's make the manual part of the release...does it make it that much bigger? There's all sorts of extra stuff we are being, in effect, forced to download anyway that many may or may not use. (language extensions, CsoundAC, various GUIs, etc.)---surely these take up download space, and are at least no more essential than the *manual*!! > > > > I believe it is essential to have better overall install/packaging and documentation. At the very least, instructions on how to get/build the up-to-date manual from CVS or whatever should be *included* in the source, if not the html for the manual itself. And perhaps cleaning up the directory structure of the source download: it a huge chaotic swamp of files---it would be nice to see a clean hierarchy that gives the user an idea of the rhyme and reason for things.... > > > > AKJ > > > > On Tue, Jan 18, 2011 at 9:41 AM, wrote: > > > Hi Victor...the new opcodes et al do not seem to be in any manual I have > > > access to. There is no manual in the source download. Or if there is, I > > > don't know/can't find instructions on building it. > > > > > > Where does one get an up-to-date-hot-of-the-press manual? 5.12 canonical > > > is > > > the one that the csounds.com site links to.... > > > > > > AKJ > > > > > > > On sourceforge there is a complete manual in source. That is where all > > the documentation is. > > I used to build a manual as part of the release but there seemed to be a > > move against that. I could zip up the latest manual as html or pdf as I > > keep the current version on all my machines > > > > ==John ff > > > > > > > > > > > Send bugs reports to the Sourceforge bug tracker > > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > > Discussions of bugs and features can be posted here > > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" > > > > > > > > > > > -- > > Aaron Krister Johnson > > http://www.akjmusic.com > > http://www.untwelve.org > > > > > Dr Victor Lazzarini, Senior Lecturer, Dept. of Music, > National University of Ireland, Maynooth > > > > -- > Aaron Krister Johnson > http://www.akjmusic.com > http://www.untwelve.org > Dr Victor Lazzarini, Senior Lecturer, Dept. of Music, National University of Ireland, Maynooth Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"