Hi Victor,

I put together a readme.txt in the manual CVS a while back that should
explain the process. Basically it involves:

-The opcode page created (making sure all id's in tags are unique)
-creating an entity reference in manual.xml
-linking in the page itself to the opcodes/top.xml
-adding link references to the page from relevant section pages

Let me know if the readme.txt is not enough and I can answer here as
well as use that to modify the information in the readme.txt (should
this be renamed to README to make it stick out more?)

steven

On 2/24/06, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
> Steven (or anyone who knows),
>
> besides adding a manual page for an opcode, what else is needed to
> link it up with the rest of the manual?
>
> Thanks
>
> Victor Lazzarini
> Music Technology Laboratory
> Music Department
> National University of Ireland, Maynooth
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net