Csound Csound-dev Csound-tekno Search About

[Cs-dev] making xml examples in manual

Date2012-06-15 12:03
Fromjohn ffitch
Subject[Cs-dev] making xml examples in manual
Again I am having trouble with creating example-xml files.  It seems
as if the csd2docbook.py program insists on importing something called
csnd, but the version it loads is totally out of date; not even sure
from whence it comes.  How can I direct it to the correct version?  I
really do not want to install csound as I change it so often.  Should
add that I do not know any python so just guessing what it is on about.
==John ffitch

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2012-06-15 16:03
FromAndres Cabrera
SubjectRe: [Cs-dev] making xml examples in manual
Hi John,

The csnd python module is the python wrapper for the Csound API. There
is another csd2docbook script (I think it is called csd2docbook2),
which doesn't require the python API, but relies on the opcodes.xml
file (which must be up to date to be accurate). There is a script
there as well to generate the opcodes.xml file.

This is all from memory, but hopefully it's right.

Cheers,
Andrés

On Fri, Jun 15, 2012 at 6:03 AM, john ffitch  wrote:
> Again I am having trouble with creating example-xml files.  It seems
> as if the csd2docbook.py program insists on importing something called
> csnd, but the version it loads is totally out of date; not even sure
> from whence it comes.  How can I direct it to the correct version?  I
> really do not want to install csound as I change it so often.  Should
> add that I do not know any python so just guessing what it is on about.
> ==John ffitch
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/l

Date2012-06-15 19:06
Fromjpff@cs.bath.ac.uk
SubjectRe: [Cs-dev] making xml examples in manual
Thanks; I did try csd2docbook2 but it crashed.  Did not know about
opcodes.xml but found the opcodeparser.py program that seems to create
opcodes.xml -- but it crashes

harvey:~/Sourceforge/csound/manual> python opcodeparser.py
Traceback (most recent call last):
  File "opcodeparser.py", line 51, in 
    xmldoc = minidom.parseString(newfile)
  File "/usr/lib64/python2.7/xml/dom/minidom.py", line 1921, in parseString
    return expatbuilder.parseString(string)
  File "/usr/lib64/python2.7/xml/dom/expatbuilder.py", line 940, in
parseString
    return builder.parseString(string)
  File "/usr/lib64/python2.7/xml/dom/expatbuilder.py", line 223, in
parseString
    parser.Parse(string, True)
xml.parsers.expat.ExpatError: syntax error: line 1654, column 0
harvey:~/Sourceforge/csound/manual>

version problem?  something missing?

==John

> Hi John,
>
> The csnd python module is the python wrapper for the Csound API. There
> is another csd2docbook script (I think it is called csd2docbook2),
> which doesn't require the python API, but relies on the opcodes.xml
> file (which must be up to date to be accurate). There is a script
> there as well to generate the opcodes.xml file.
>
> This is all from memory, but hopefully it's right.
>
> Cheers,
> Andrés
>
> On Fri, Jun 15, 2012 at 6:03 AM, john ffitch  wrote:
>> Again I am having trouble with creating example-xml files.  It seems
>> as if the csd2docbook.py program insists on importing something called
>> csnd, but the version it loads is totally out of date; not even sure
>> from whence it comes.  How can I direct it to the correct version?  I
>> really do not want to install csound as I change it so often.  Should
>> add that I do not know any python so just guessing what it is on about.
>> ==John ffitch
>>
>>


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2012-06-16 19:11
FromAndres Cabrera
SubjectRe: [Cs-dev] making xml examples in manual
Hi John,

In your own immortal words, it works for me... (you have to be careful
because if it crashes, it will leave an empty opcodes.xml file, which
you committed. I've put the right one back)

I've now fixed csd2docbook2 which was crashing when no CsOptions
section was present, and committed an updated version of opcodes.xml.

Cheers,
Andrés

On Fri, Jun 15, 2012 at 1:06 PM,   wrote:
> Thanks; I did try csd2docbook2 but it crashed.  Did not know about
> opcodes.xml but found the opcodeparser.py program that seems to create
> opcodes.xml -- but it crashes
>
> harvey:~/Sourceforge/csound/manual> python opcodeparser.py
> Traceback (most recent call last):
>  File "opcodeparser.py", line 51, in 
>    xmldoc = minidom.parseString(newfile)
>  File "/usr/lib64/python2.7/xml/dom/minidom.py", line 1921, in parseString
>    return expatbuilder.parseString(string)
>  File "/usr/lib64/python2.7/xml/dom/expatbuilder.py", line 940, in
> parseString
>    return builder.parseString(string)
>  File "/usr/lib64/python2.7/xml/dom/expatbuilder.py", line 223, in
> parseString
>    parser.Parse(string, True)
> xml.parsers.expat.ExpatError: syntax error: line 1654, column 0
> harvey:~/Sourceforge/csound/manual>
>
> version problem?  something missing?
>
> ==John
>
>> Hi John,
>>
>> The csnd python module is the python wrapper for the Csound API. There
>> is another csd2docbook script (I think it is called csd2docbook2),
>> which doesn't require the python API, but relies on the opcodes.xml
>> file (which must be up to date to be accurate). There is a script
>> there as well to generate the opcodes.xml file.
>>
>> This is all from memory, but hopefully it's right.
>>
>> Cheers,
>> Andrés
>>
>> On Fri, Jun 15, 2012 at 6:03 AM, john ffitch  wrote:
>>> Again I am having trouble with creating example-xml files.  It seems
>>> as if the csd2docbook.py program insists on importing something called
>>> csnd, but the version it loads is totally out of date; not even sure
>>> from whence it comes.  How can I direct it to the correct version?  I
>>> really do not want to install csound as I change it so often.  Should
>>> add that I do not know any python so just guessing what it is on about.
>>> ==John ffitch
>>>
>>>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge

Date2012-06-16 19:55
Fromjpff@cs.bath.ac.uk
SubjectRe: [Cs-dev] making xml examples in manual
Many thanks -- perhaps it was the lack of CsOptions that caused me problem
Seems OK now

==John ff
> Hi John,
>
> In your own immortal words, it works for me... (you have to be careful
> because if it crashes, it will leave an empty opcodes.xml file, which
> you committed. I've put the right one back)
>
> I've now fixed csd2docbook2 which was crashing when no CsOptions
> section was present, and committed an updated version of opcodes.xml.
>
> Cheers,
> Andrés
>



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net