It's pretty straightforward XML. All opcodes follow the same pattern or
style sheet. 

In CVS, look at csound/manual/readme.txt. Steven Yi has provided a very
clear set of instructions on how to add a new opcode (about halfway down in
readme.txt).

Once you've added the entry, "make" rebuilds the manual.

Original Message:
-----------------
From: Istvan Varga istvan@csounds.com
Date: Thu, 17 Feb 2005 13:04:13 +0100
To: csound-devel@lists.sourceforge.net
Subject: Re: [Cs-dev] CVS changes: new opcodes and bug fixes


Michael Gogins wrote:

> Are you updating the manual sources in CVS? If you do, then as we 
> rebuild the manual relatively frequently, your changes will be reflected 
> there.

No I do not, I am not very familiar with the manual sources.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net