Hi,
This is a question mostly for Dr.B, regarding the OLPC project. First, it's
really exciting that csound is part of this!

The question is if csound documentation will be included in OLPC, and if so,
since I guess not all opcodes are included, how should this documentation be
handled?

I have the following idea:

Each opcode entry in the manual can have an additional section which
specifies to which plugin library the opcode belongs. For this to be
effective and maintanable, opcodes should be in their final definitive
location (I remember there being talks of splitting opcodes into separate
libraries again, which I think might be good). It would be useful as well to
have a command line flag which lists available libraries, so users can
easily know which libraries are installed in their system (without having to
know where they are).

It would also be great to start translations of the manual. Any volunteers?
Does anyone know if it is possible to maintain -using docbook- a single set
of sources and decide at compile time which language to build?

Cheers,
Andres

-- 
View this message in context: http://www.nabble.com/OLPC-csound-documentation-tf2670378.html#a7446387
Sent from the Csound - Dev mailing list archive at Nabble.com.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net