Hi,

The manual is written in docbook-XML, so it is somewhat hard to edit,
but we're always looking for eager people who want to do it. You
should first grab the source from git:

git://csound.git.sourceforge.net/gitroot/csound/manual

Then you can edit the files and send the changes to the development
list, or ask John for git access and commit yourself. The manual
repository contains a readme file with details about building the
manual from the docbook-xml sources.

Cheers,
Andrés

On Wed, Oct 31, 2012 at 4:41 PM, Aurelius Prochazka  wrote:
> Thanks Victor, but please, teach a man to fish, where did you find this
> information.  :)  I know its in the source code, but as a new user whose
> using WinXound to interface with Csound, I haven't had to dive in to that
> level.  But I want to!
>
> Thanks in advance,
> Aure
>
> Sent from my iPhone
> Sent with Sparrow
>
> On Wednesday, October 31, 2012 at 4:31 PM, Victor Lazzarini wrote:
>
>
> According to the code, the default is 2500Hz for freq1 and 4000Hz for freq2
>
> Victor
>
> On 31 Oct 2012, at 23:02, Aurelius Prochazka wrote:
>
> Perhaps Menno can chime in on the manner to submit patches.  Or it would
> also be great make a page about submitting fixes within the manual itself.
>
> Second issue: In "guiro"
>
> ifreq1 (optional) -- the first resonant frequency.
>
> Since this is an optional parameter, I'd like to know more about what the
> default value is.
>
> Thanks,
> Aure
>
>
> Sent from my iPhone
> Sent with Sparrow
>
> On Wednesday, October 31, 2012 at 12:54 PM, Victor Lazzarini wrote:
>
> Menno is your man for this. His in this list and he is managing the manual.
> You're welcome to contribute patches as well.
>
> Victor
> On 31 Oct 2012, at 19:10, Aurelius Prochazka wrote:
>
> What is the preferred way of fixing errors in the manual?  I have run across
> quite a few (mostly minor) problems recently, enough that I think I should
> contribute by telling someone about them.  Should I just post the error
> here?  Email someone directly?  Or is there a way for the community to
> contribute patches?
>
> Here's what I just noticed
>
> http://www.csounds.com/manual/html/vibes.html
>  has
>
> idoubles (optional) -- percentage of double strikes. Default is 40%.
>
> itriples (optional) -- percentage of triple strikes. Default is 20%.
>
> in the initialization documentation, but those variables do not appear in
> the syntax signature.
>
> Thanks,
>
> Aure
>
>
> Dr Victor Lazzarini
> Senior Lecturer
> Dept. of Music
> NUI Maynooth Ireland
> tel.: +353 1 708 3545
> Victor dot Lazzarini AT nuim dot ie
>
>
>
>
>
> Dr Victor Lazzarini
> Senior Lecturer
> Dept. of Music
> NUI Maynooth Ireland
> tel.: +353 1 708 3545
> Victor dot Lazzarini AT nuim dot ie
>
>
>
>

That should be:
git clone git://csound.git.sourceforge.net/gitroot/csound/manual

Cheers,
Andrés

On Wed, Oct 31, 2012 at 4:53 PM, Andres Cabrera  wrote:
> Hi,
>
> The manual is written in docbook-XML, so it is somewhat hard to edit,
> but we're always looking for eager people who want to do it. You
> should first grab the source from git:
>
> git://csound.git.sourceforge.net/gitroot/csound/manual
>
> Then you can edit the files and send the changes to the development
> list, or ask John for git access and commit yourself. The manual
> repository contains a readme file with details about building the
> manual from the docbook-xml sources.
>
> Cheers,
> Andrés
>
> On Wed, Oct 31, 2012 at 4:41 PM, Aurelius Prochazka  wrote:
>> Thanks Victor, but please, teach a man to fish, where did you find this
>> information.  :)  I know its in the source code, but as a new user whose
>> using WinXound to interface with Csound, I haven't had to dive in to that
>> level.  But I want to!
>>
>> Thanks in advance,
>> Aure
>>
>> Sent from my iPhone
>> Sent with Sparrow
>>
>> On Wednesday, October 31, 2012 at 4:31 PM, Victor Lazzarini wrote:
>>
>>
>> According to the code, the default is 2500Hz for freq1 and 4000Hz for freq2
>>
>> Victor
>>
>> On 31 Oct 2012, at 23:02, Aurelius Prochazka wrote:
>>
>> Perhaps Menno can chime in on the manner to submit patches.  Or it would
>> also be great make a page about submitting fixes within the manual itself.
>>
>> Second issue: In "guiro"
>>
>> ifreq1 (optional) -- the first resonant frequency.
>>
>> Since this is an optional parameter, I'd like to know more about what the
>> default value is.
>>
>> Thanks,
>> Aure
>>
>>
>> Sent from my iPhone
>> Sent with Sparrow
>>
>> On Wednesday, October 31, 2012 at 12:54 PM, Victor Lazzarini wrote:
>>
>> Menno is your man for this. His in this list and he is managing the manual.
>> You're welcome to contribute patches as well.
>>
>> Victor
>> On 31 Oct 2012, at 19:10, Aurelius Prochazka wrote:
>>
>> What is the preferred way of fixing errors in the manual?  I have run across
>> quite a few (mostly minor) problems recently, enough that I think I should
>> contribute by telling someone about them.  Should I just post the error
>> here?  Email someone directly?  Or is there a way for the community to
>> contribute patches?
>>
>> Here's what I just noticed
>>
>> http://www.csounds.com/manual/html/vibes.html
>>  has
>>
>> idoubles (optional) -- percentage of double strikes. Default is 40%.
>>
>> itriples (optional) -- percentage of triple strikes. Default is 20%.
>>
>> in the initialization documentation, but those variables do not appear in
>> the syntax signature.
>>
>> Thanks,
>>
>> Aure
>>
>>
>> Dr Victor Lazzarini
>> Senior Lecturer
>> Dept. of Music
>> NUI Maynooth Ireland
>> tel.: +353 1 708 3545
>> Victor dot Lazzarini AT nuim dot ie
>>
>>
>>
>>
>>
>> Dr Victor Lazzarini
>> Senior Lecturer
>> Dept. of Music
>> NUI Maynooth Ireland
>> tel.: +353 1 708 3545
>> Victor dot Lazzarini AT nuim dot ie
>>
>>
>>
>>

Hi 

thanks Aurelius and others for finding and reporting errors and new ideas
for the manual.

I have quickly copypasted your suggestions in a blog page:
http://www.csounds.com/node/1577
,for reference and that it will not be forgotten, and hope to be able to
work on the manual in the days to come. 
I'm pretty busy right now, but suggestions for improvements of the manual
are very welcome and will be noted there!

There is a list of opcodes that are still without a decent example:
http://www.csounds.com/node/1394
If anyone can help out on making this list shorter, please let me know.

thanks,
Menno





--
View this message in context: http://csound.1045644.n5.nabble.com/fixing-manual-errors-tp5717524p5717534.html
Sent from the Csound - General mailing list archive at Nabble.com.

The list of undocumented/exampled opcodes seems rather out of date.

Would it be possible to add a file to the manual git with the aberations,
so it will be easy to update when examples are added?

==John ff