I will do as you say regarding the license and authors -- if I can ever get
the manual to build. If I can't, would you be willing to update the manual
and commit it? I will send you sgml for the new stuff.

----- Original Message ----- 
From: "steven yi" 
To: "Csound Developers Discussion List" 
Sent: Thursday, September 30, 2004 1:27 AM
Subject: [CSOUND-DEV:5373] Re: Manual woes


> Hi Michael,
>
> I've built the docs a number of times to HTML.  I got around to trying
> it just now with Kevin's gdp-both.dsl file and now it pretty much
> produced results just as Kevin had it in the ACRM (I did not use any of
> his other files in the acrm-dsl.zip he sent to me).  What point do you
> get to before you get errors?  One thing that I've found is that
> generating the index for the manual takes quite a while and it feels
> like the command may have hung, but in fact it is working.  (I think it
> less than a minute to produce all of the document pages, but took like 5
> minutes to produce the index.html).  I'm using Fedora Core 2 wiith the
> default install from RPM's.  I haven't touched the toolchain at all.
> The only thing I've modified is the Makefile to point to gdp-both.dsl.
> (I've just now checked in both the modified Makefile and gdp-both.dsl).
>
> I can send you a copy of my /usr/share/sgml directory; I'm not sure what
> else you might need.  Let me know and I'll try to help out as best as
> I'm able (which is only so much, as my knowledge of docbook is minimal).
>
> Also, we need to be careful to respect the license and maintain a
> History file and set up a new publisher in the Manual (how does "Csound
> Documentation Team" or "Csound Documentation Project" sound for a
> blanket name?  Kevin suggested using one of these to me in email) , as
> I've changed the title from "Alternative Csound Reference Manual" to
> "Canonical Csound Reference Manual".
>
> steven
>
>
> Michael Gogins wrote:
>
> >Still no luck building the Conder manual, either on Fedora Core 1 or on
> >Cygwin, even after messing with gdb-both.dsl and all sorts of other dsl
> >files, dtd files, and so on. I am now a firmly convinced hater of DocBook
> >and would infinitely prefer to use LaTeX, but I fear to lose all the good
> >work that Kevin Conder did in improving the Csound documentation even if
it
> >is in a format that I can't get to work and is wasting acres of my time.
> >
> >If anyone can actually build the docs, please zip up all the docbook,
oasis,
> >dsl, etc., etc. files in the dir structure that works for them and email
it
> >to me. Please! Or else tell me that no, you were not actually able to
build
> >the docs.
> >
> >
> >
> >
> >
>
>

The information I sent about the license and authors was more a reminder 
for me to do it than for you! =)

I'd gladly commit and test building anything you'd care to send over. 

steven


Michael Gogins wrote:

>I will do as you say regarding the license and authors -- if I can ever get
>the manual to build. If I can't, would you be willing to update the manual
>and commit it? I will send you sgml for the new stuff.
>  
>

I sometimes update the text of the manual, but when I run "make" it
prints a lot of stuff to the screen.  What make targets make
sense/work?

...and I was thinking that the busi/buso opcodes should be renamed
chani/chano as the bus word has different means in audio buses and
software buses.  Next round of objections?

==John ffitch

Hi John,

jpff@cs.bath.ac.uk wrote:
> I sometimes update the text of the manual, but when I run "make" it
> prints a lot of stuff to the screen.  What make targets make
> sense/work?

I use just "make" and it builds the html version.  I haven't tried the 
"make pdf" target, but I know it's there.  When I built it yesterday, I 
saw pretty much nothing on the screen except the call to openjade, and 
then it hung around for about 5 minutes and finished up.

I think I did used to get things printed to screen, but I did a capture 
of either the stderr or stdout stream and found that there was an error 
and gdp-both.dsl was pointing to a file that was in a different 
directory on the system, or something like that.

Kevin warned me a number of times a while back that getting the docbook 
chain setup could be problematic, but I guess I was lucky and didn't 
have too many problems.

I'm going to try building on Cygwin today to see if I can build on that.

steven