Hi
I´m having problems compiling the manual. 

C:\csound cvs\manual>make html
mkdir -p html
xsltproc --nonet --xinclude -o html/ docbook-xsl-1.73.2/customXHTMLchunk.xsl
manual.xml
make: xsltproc: Command not found
make: *** [html] Error 127

I have installed xsltproc from http://zlatkovic.com/libxml.en.html: 
C:\csound cvs\manual>xsltproc --version
Using libxml 20632, libxslt 10123 and libexslt 813
xsltproc was compiled against libxml 20632, libxslt 10123 and libexslt 813
libxslt 10123 was compiled against libxml 20632
libexslt 813 was compiled against libxml 20632

What could be wrong?

And a sub question: I want to use makefile to create a collection of simpler
and more elaborated xml files. That is; without entities and with the syntax
of opcodes more elaborated into input, output, command and optionals,
instead of as it is now outputcommandinput.
Does this exist allready? is the opcodes available in some database form?
I know i asked some similar question before (months ago), just wanted to
make sure that i didnt spend time doing something that had allready been
done.

Thank you
Carsten
-- 
View this message in context: http://www.nabble.com/make-html-manual%3A-xsltproc-not-found-tp18168828p18168828.html
Sent from the Csound - Dev mailing list archive at Nabble.com.


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.

Andres Cabrera wrote:
> 
> Hi,
> 
> I'm not sure what's wrong there... It makes no sense that xsltproc is
> found
> but not found...
> 
> But, what you're asking for already exists, I wrote it to go with my
> frontend qutecsound. I wrote a script called opcodeparser.py, and thought
> I
> had committed to cvs, but now checking I see that I haven't. I do have the
> output here, which I'm attaching, which I think is what you're looking
> for.
> (I'll commit this week when I have access to the computer where it's
> located)
> 
> Cheers,
> Andrés
> 


Great. Please alert me when you upload it. Looking over the output i can see
that you have maintained the structure of the syntax with "," separating the
parameteres and "[" encapsulating the optional parameters. While i was
writing a similar solution in C++ i realized that the encapsulation was not
consistent. Sometimes it would be [, para] other times ,[para]. All kinds of
small differences existed between opcodes. Eventually i decided there had to
be a simpler way. So i started looking at wxXmlDocument, TinyXML and Xerces.
But apparently the solution is closely knit with docbook. Im looking forward
to be investigating your code.

Thanks
Carsten 
-- 
View this message in context: http://www.nabble.com/make-html-manual%3A-xsltproc-not-found-tp18168828p18209771.html
Sent from the Csound - Dev mailing list archive at Nabble.com.


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lis

That is part of what I´m working on right now. Something like this


  
    parameter
  
  
    parameter
  
  
    parameter
  
  
    parameter 2
  
  
    parameter
  
  
    parameter 2
  


Maybe some other markup is better?

The trouble is, as you write, that the process cannot really be automated
without a risk of unknown errors.
If people would be willing to let this kind of syntax into the official
manual, i wouldnt mind doing the work.
The great thing about this is that we would be able to use the manual as a
database. FX. i want to populate a list of opcodes from the information
given in the manual. That would be no problem with a more elaborated syntax.
If we also could avoid entities, which you allready created, it would be a
much simpler task to effectively use the manual in other programs. fx.
wxWidgets, TinyXML and Xerces will not cooperate with the manual as it is
today. (ok, maybe Xerces will, buts its complicated :-))

If this is really what it takes to advance with my own program i guess i
will have to recreate all the opcode files in the manual. But for now i will
just wait for awhile to hear what you all have to say about this.

Thanks
Carsten


Andres Cabrera wrote:
> 
> Hi Carsten,
> 
> There's not not really anything in my code about that. The [ ]'s are very
> inconsistent throughout the manual, and they are written that way
> literally
> (no docbook there). It might be a better idea to review each opcode syntax
> entry and define a unified structure, so that each entry follows that
> convention. I personally don't have the time, but it would be nice =).
> 
> Cheers,
> Andrés
> 
> 
> On Tue, Jul 1, 2008 at 12:58 AM, Carsten Hoyer 
> wrote:
> 
>>
>>
>>
>> Andres Cabrera wrote:
>> >
>> > Hi,
>> >
>> > I'm not sure what's wrong there... It makes no sense that xsltproc is
>> > found
>> > but not found...
>> >
>> > But, what you're asking for already exists, I wrote it to go with my
>> > frontend qutecsound. I wrote a script called opcodeparser.py, and
>> thought
>> > I
>> > had committed to cvs, but now checking I see that I haven't. I do have
>> the
>> > output here, which I'm attaching, which I think is what you're looking
>> > for.
>> > (I'll commit this week when I have access to the computer where it's
>> > located)
>> >
>> > Cheers,
>> > Andrés
>> >
>>
>>
>> Great. Please alert me when you upload it. Looking over the output i can
>> see
>> that you have maintained the structure of the syntax with "," separating
>> the
>> parameteres and "[" encapsulating the optional parameters. While i was
>> writing a similar solution in C++ i realized that the encapsulation was
>> not
>> consistent. Sometimes it would be [, para] other times ,[para]. All kinds
>> of
>> small differences existed between opcodes. Eventually i decided there had
>> to
>> be a simpler way. So i started looking at wxXmlDocument, TinyXML and
>> Xerces.
>> But apparently the solution is closely knit with docbook. Im looking
>> forward
>> to be investigating your code.
>>
>> Thanks
>> Carsten
>> --
>> View this message in context:
>> http://www.nabble.com/make-html-manual%3A-xsltproc-not-found-tp18168828p18209771.html
>> Sent from the Csound - Dev mailing list archive at Nabble.com.
>>
>>
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 

-- 
View this message in context: http://www.nabble.com/make-html-manual%3A-xsltproc-not-found-tp18168828p18233357.html
Sent from the Csound - Dev mailing list archive at Nabble.com.


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https: