hi all -

i am putting together some examples and explanations for using arrays. i 
am wondering whether there is already anything anywhere, except the 
release notes?

the best place to put may be in the media wiki, right?

all best -

	joachim

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Joachim,

I think you are correct and that there is no overview documentation
for arrays.  At least, I did not see it in the manual6 repo.  I would
imagine the best place for this might be in the manual.

Thanks!
steven

On Mon, Jul 15, 2013 at 5:17 AM, joachim heintz  wrote:
> hi all -
>
> i am putting together some examples and explanations for using arrays. i
> am wondering whether there is already anything anywhere, except the
> release notes?
>
> the best place to put may be in the media wiki, right?
>
> all best -
>
>         joachim
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

hi steven -

thanks, and yes: i will put something together which may find its place 
in the manual.

is it ok to write a txt document, like the release notes, or can i 
simplify the workflow in using anything else?

best -

	joachim



Am 15.07.2013 17:53, schrieb Steven Yi:
> Hi Joachim,
>
> I think you are correct and that there is no overview documentation
> for arrays.  At least, I did not see it in the manual6 repo.  I would
> imagine the best place for this might be in the manual.
>
> Thanks!
> steven
>
> On Mon, Jul 15, 2013 at 5:17 AM, joachim heintz  wrote:
>> hi all -
>>
>> i am putting together some examples and explanations for using arrays. i
>> am wondering whether there is already anything anywhere, except the
>> release notes?
>>
>> the best place to put may be in the media wiki, right?
>>
>> all best -
>>
>>          joachim
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Joachim,

The manual is itself written in Docbook XML.  It is of course easiest
if it's written in the same format, but I think any contribution in
easy to read formats would be very welcome. If it's best for you to
use a text file, then someone here can do the formatting and get it
linked into the manual.

This makes me curious about the ticket system.  I thought we used to
have a section for tickets for the manual, but I don't see it anymore.
 I wonder if we shouldn't reinstate that, and direct manual
edits/contributions/change requests there.  Do you think that's a good
idea?

Thanks!
steven


On Mon, Jul 15, 2013 at 12:46 PM, joachim heintz  wrote:
> hi steven -
>
> thanks, and yes: i will put something together which may find its place
> in the manual.
>
> is it ok to write a txt document, like the release notes, or can i
> simplify the workflow in using anything else?
>
> best -
>
>         joachim
>
>
>
> Am 15.07.2013 17:53, schrieb Steven Yi:
>> Hi Joachim,
>>
>> I think you are correct and that there is no overview documentation
>> for arrays.  At least, I did not see it in the manual6 repo.  I would
>> imagine the best place for this might be in the manual.
>>
>> Thanks!
>> steven
>>
>> On Mon, Jul 15, 2013 at 5:17 AM, joachim heintz  wrote:
>>> hi all -
>>>
>>> i am putting together some examples and explanations for using arrays. i
>>> am wondering whether there is already anything anywhere, except the
>>> release notes?
>>>
>>> the best place to put may be in the media wiki, right?
>>>
>>> all best -
>>>
>>>          joachim
>>>
>>> ------------------------------------------------------------------------------
>>> See everything from the browser to the database with AppDynamics
>>> Get end-to-end visibility with application monitoring from AppDynamics
>>> Isolate bottlenecks and diagnose root cause in seconds.
>>> Start your free trial of AppDynamics Pro today!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I think that might be a problem though, no?  I'd certainly like to see
tickets for "bugs", "features", "manual".  Versions/releases could be
used as the metadata for the tickets, rather than have a whole tracker
for CS6.  That's my preference at least.

On Mon, Jul 15, 2013 at 3:01 PM, Michael Gogins
 wrote:
> For Csound 6, all tickets are one.
>
> Regards,
> Mike
>
>
> ===========================
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Mon, Jul 15, 2013 at 2:49 PM, Steven Yi  wrote:
>>
>> Hi Joachim,
>>
>> The manual is itself written in Docbook XML.  It is of course easiest
>> if it's written in the same format, but I think any contribution in
>> easy to read formats would be very welcome. If it's best for you to
>> use a text file, then someone here can do the formatting and get it
>> linked into the manual.
>>
>> This makes me curious about the ticket system.  I thought we used to
>> have a section for tickets for the manual, but I don't see it anymore.
>>  I wonder if we shouldn't reinstate that, and direct manual
>> edits/contributions/change requests there.  Do you think that's a good
>> idea?
>>
>> Thanks!
>> steven
>>
>>
>> On Mon, Jul 15, 2013 at 12:46 PM, joachim heintz 
>> wrote:
>> > hi steven -
>> >
>> > thanks, and yes: i will put something together which may find its place
>> > in the manual.
>> >
>> > is it ok to write a txt document, like the release notes, or can i
>> > simplify the workflow in using anything else?
>> >
>> > best -
>> >
>> >         joachim
>> >
>> >
>> >
>> > Am 15.07.2013 17:53, schrieb Steven Yi:
>> >> Hi Joachim,
>> >>
>> >> I think you are correct and that there is no overview documentation
>> >> for arrays.  At least, I did not see it in the manual6 repo.  I would
>> >> imagine the best place for this might be in the manual.
>> >>
>> >> Thanks!
>> >> steven
>> >>
>> >> On Mon, Jul 15, 2013 at 5:17 AM, joachim heintz 
>> >> wrote:
>> >>> hi all -
>> >>>
>> >>> i am putting together some examples and explanations for using arrays.
>> >>> i
>> >>> am wondering whether there is already anything anywhere, except the
>> >>> release notes?
>> >>>
>> >>> the best place to put may be in the media wiki, right?
>> >>>
>> >>> all best -
>> >>>
>> >>>          joachim
>> >>>
>> >>>
>> >>> ------------------------------------------------------------------------------
>> >>> See everything from the browser to the database with AppDynamics
>> >>> Get end-to-end visibility with application monitoring from AppDynamics
>> >>> Isolate bottlenecks and diagnose root cause in seconds.
>> >>> Start your free trial of AppDynamics Pro today!
>> >>>
>> >>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> >>> _______________________________________________
>> >>> Csound-devel mailing list
>> >>> Csound-devel@lists.sourceforge.net
>> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> See everything from the browser to the database with AppDynamics
>> >> Get end-to-end visibility with application monitoring from AppDynamics
>> >> Isolate bottlenecks and diagnose root cause in seconds.
>> >> Start your free trial of AppDynamics Pro today!
>> >>
>> >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> >> _______________________________________________
>> >> Csound-devel mailing list
>> >> Csound-devel@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > See everything from the browser to the database with AppDynamics
>> > Get end-to-end visibility with application monitoring from AppDynamics
>> > Isolate bottlenecks and diagnose root cause in seconds.
>> > Start your free trial of AppDynamics Pro today!
>> >
>> > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

hi steven -

yes, i think any simple-to-use channel for people who are willing to 
contribute is good for us all. so if it is possible to add tickets 
particularily for the manual, i am for it.

which tool do you use for writing docbook xml?

and is there a description how to build the manual?

thanks and best regards -

	joachim


Am 15.07.2013 20:49, schrieb Steven Yi:
> Hi Joachim,
>
> The manual is itself written in Docbook XML.  It is of course easiest
> if it's written in the same format, but I think any contribution in
> easy to read formats would be very welcome. If it's best for you to
> use a text file, then someone here can do the formatting and get it
> linked into the manual.
>
> This makes me curious about the ticket system.  I thought we used to
> have a section for tickets for the manual, but I don't see it anymore.
>   I wonder if we shouldn't reinstate that, and direct manual
> edits/contributions/change requests there.  Do you think that's a good
> idea?
>
> Thanks!
> steven
>
>
> On Mon, Jul 15, 2013 at 12:46 PM, joachim heintz  wrote:
>> hi steven -
>>
>> thanks, and yes: i will put something together which may find its place
>> in the manual.
>>
>> is it ok to write a txt document, like the release notes, or can i
>> simplify the workflow in using anything else?
>>
>> best -
>>
>>          joachim
>>
>>
>>
>> Am 15.07.2013 17:53, schrieb Steven Yi:
>>> Hi Joachim,
>>>
>>> I think you are correct and that there is no overview documentation
>>> for arrays.  At least, I did not see it in the manual6 repo.  I would
>>> imagine the best place for this might be in the manual.
>>>
>>> Thanks!
>>> steven
>>>
>>> On Mon, Jul 15, 2013 at 5:17 AM, joachim heintz  wrote:
>>>> hi all -
>>>>
>>>> i am putting together some examples and explanations for using arrays. i
>>>> am wondering whether there is already anything anywhere, except the
>>>> release notes?
>>>>
>>>> the best place to put may be in the media wiki, right?
>>>>
>>>> all best -
>>>>
>>>>           joachim
>>>>
>>>> ------------------------------------------------------------------------------
>>>> See everything from the browser to the database with AppDynamics
>>>> Get end-to-end visibility with application monitoring from AppDynamics
>>>> Isolate bottlenecks and diagnose root cause in seconds.
>>>> Start your free trial of AppDynamics Pro today!
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>> ------------------------------------------------------------------------------
>>> See everything from the browser to the database with AppDynamics
>>> Get end-to-end visibility with application monitoring from AppDynamics
>>> Isolate bottlenecks and diagnose root cause in seconds.
>>> Start your free trial of AppDynamics Pro today!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Joachim,

If you clone the csound manual from GIT, there is a README that
describes what tools you need to install and how to compile the
manual.  (The manual uses a Makefile).  For editing the xml files, I
myself use vim, but any text editor works.  Docbook can be tricky to
learn, but if you know XML formatting, it is not so bad, especially if
you just copy an existing manual entry and start from there.  I'd say,
the only really tricky thing is getting any new pages linked in, as
you have to add it to a number of places.  I don't remember them at
the moment, but if you go that route someone here can help.

Other than that, as the manual ticket tracker idea is up in the air,
I'd say you should feel free to attach any documentation you write to
an email to this list. Someone can then volunteer to get it
integrated.

Thanks!
steven



On Mon, Jul 15, 2013 at 3:23 PM, joachim heintz  wrote:
> hi steven -
>
> yes, i think any simple-to-use channel for people who are willing to
> contribute is good for us all. so if it is possible to add tickets
> particularily for the manual, i am for it.
>
> which tool do you use for writing docbook xml?
>
> and is there a description how to build the manual?
>
> thanks and best regards -
>
>         joachim
>
>
> Am 15.07.2013 20:49, schrieb Steven Yi:
>> Hi Joachim,
>>
>> The manual is itself written in Docbook XML.  It is of course easiest
>> if it's written in the same format, but I think any contribution in
>> easy to read formats would be very welcome. If it's best for you to
>> use a text file, then someone here can do the formatting and get it
>> linked into the manual.
>>
>> This makes me curious about the ticket system.  I thought we used to
>> have a section for tickets for the manual, but I don't see it anymore.
>>   I wonder if we shouldn't reinstate that, and direct manual
>> edits/contributions/change requests there.  Do you think that's a good
>> idea?
>>
>> Thanks!
>> steven
>>
>>
>> On Mon, Jul 15, 2013 at 12:46 PM, joachim heintz  wrote:
>>> hi steven -
>>>
>>> thanks, and yes: i will put something together which may find its place
>>> in the manual.
>>>
>>> is it ok to write a txt document, like the release notes, or can i
>>> simplify the workflow in using anything else?
>>>
>>> best -
>>>
>>>          joachim
>>>
>>>
>>>
>>> Am 15.07.2013 17:53, schrieb Steven Yi:
>>>> Hi Joachim,
>>>>
>>>> I think you are correct and that there is no overview documentation
>>>> for arrays.  At least, I did not see it in the manual6 repo.  I would
>>>> imagine the best place for this might be in the manual.
>>>>
>>>> Thanks!
>>>> steven
>>>>
>>>> On Mon, Jul 15, 2013 at 5:17 AM, joachim heintz  wrote:
>>>>> hi all -
>>>>>
>>>>> i am putting together some examples and explanations for using arrays. i
>>>>> am wondering whether there is already anything anywhere, except the
>>>>> release notes?
>>>>>
>>>>> the best place to put may be in the media wiki, right?
>>>>>
>>>>> all best -
>>>>>
>>>>>           joachim
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> See everything from the browser to the database with AppDynamics
>>>>> Get end-to-end visibility with application monitoring from AppDynamics
>>>>> Isolate bottlenecks and diagnose root cause in seconds.
>>>>> Start your free trial of AppDynamics Pro today!
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>> ------------------------------------------------------------------------------
>>>> See everything from the browser to the database with AppDynamics
>>>> Get end-to-end visibility with application monitoring from AppDynamics
>>>> Isolate bottlenecks and diagnose root cause in seconds.
>>>> Start your free trial of AppDynamics Pro today!
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> See everything from the browser to the database with AppDynamics
>>> Get end-to-end visibility with application monitoring from AppDynamics
>>> Isolate bottlenecks and diagnose root cause in seconds.
>>> Start your free trial of AppDynamics Pro today!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Yes, metadata for version.

hi steven -

the readme.txt file was only in the csound5 manual git. i have copied it 
in csound-manual6-git and pushed to git.

very useful document -- building the manual went out of the box!

best -

	joachim


Am 15.07.2013 21:36, schrieb Steven Yi:
> Hi Joachim,
>
> If you clone the csound manual from GIT, there is a README that
> describes what tools you need to install and how to compile the
> manual.  (The manual uses a Makefile).  For editing the xml files, I
> myself use vim, but any text editor works.  Docbook can be tricky to
> learn, but if you know XML formatting, it is not so bad, especially if
> you just copy an existing manual entry and start from there.  I'd say,
> the only really tricky thing is getting any new pages linked in, as
> you have to add it to a number of places.  I don't remember them at
> the moment, but if you go that route someone here can help.
>
> Other than that, as the manual ticket tracker idea is up in the air,
> I'd say you should feel free to attach any documentation you write to
> an email to this list. Someone can then volunteer to get it
> integrated.
>
> Thanks!
> steven
>
>
>
> On Mon, Jul 15, 2013 at 3:23 PM, joachim heintz  wrote:
>> hi steven -
>>
>> yes, i think any simple-to-use channel for people who are willing to
>> contribute is good for us all. so if it is possible to add tickets
>> particularily for the manual, i am for it.
>>
>> which tool do you use for writing docbook xml?
>>
>> and is there a description how to build the manual?
>>
>> thanks and best regards -
>>
>>          joachim
>>
>>
>> Am 15.07.2013 20:49, schrieb Steven Yi:
>>> Hi Joachim,
>>>
>>> The manual is itself written in Docbook XML.  It is of course easiest
>>> if it's written in the same format, but I think any contribution in
>>> easy to read formats would be very welcome. If it's best for you to
>>> use a text file, then someone here can do the formatting and get it
>>> linked into the manual.
>>>
>>> This makes me curious about the ticket system.  I thought we used to
>>> have a section for tickets for the manual, but I don't see it anymore.
>>>    I wonder if we shouldn't reinstate that, and direct manual
>>> edits/contributions/change requests there.  Do you think that's a good
>>> idea?
>>>
>>> Thanks!
>>> steven
>>>
>>>
>>> On Mon, Jul 15, 2013 at 12:46 PM, joachim heintz  wrote:
>>>> hi steven -
>>>>
>>>> thanks, and yes: i will put something together which may find its place
>>>> in the manual.
>>>>
>>>> is it ok to write a txt document, like the release notes, or can i
>>>> simplify the workflow in using anything else?
>>>>
>>>> best -
>>>>
>>>>           joachim
>>>>
>>>>
>>>>
>>>> Am 15.07.2013 17:53, schrieb Steven Yi:
>>>>> Hi Joachim,
>>>>>
>>>>> I think you are correct and that there is no overview documentation
>>>>> for arrays.  At least, I did not see it in the manual6 repo.  I would
>>>>> imagine the best place for this might be in the manual.
>>>>>
>>>>> Thanks!
>>>>> steven
>>>>>
>>>>> On Mon, Jul 15, 2013 at 5:17 AM, joachim heintz  wrote:
>>>>>> hi all -
>>>>>>
>>>>>> i am putting together some examples and explanations for using arrays. i
>>>>>> am wondering whether there is already anything anywhere, except the
>>>>>> release notes?
>>>>>>
>>>>>> the best place to put may be in the media wiki, right?
>>>>>>
>>>>>> all best -
>>>>>>
>>>>>>            joachim
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> See everything from the browser to the database with AppDynamics
>>>>>> Get end-to-end visibility with application monitoring from AppDynamics
>>>>>> Isolate bottlenecks and diagnose root cause in seconds.
>>>>>> Start your free trial of AppDynamics Pro today!
>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> See everything from the browser to the database with AppDynamics
>>>>> Get end-to-end visibility with application monitoring from AppDynamics
>>>>> Isolate bottlenecks and diagnose root cause in seconds.
>>>>> Start your free trial of AppDynamics Pro today!
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> See everything from the browser to the database with AppDynamics
>>>> Get end-to-end visibility with application monitoring from AppDynamics
>>>> Isolate bottlenecks and diagnose root cause in seconds.
>>>> Start your free trial of AppDynamics Pro today!
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>> ------------------------------------------------------------------------------
>>> See everything from the browser to the database with AppDynamics
>>> Get end-to-end visibility with application monitoring from AppDynamics
>>> Isolate bottlenecks and diagnose root cause in seconds.
>>> Start your free trial of AppDynamics Pro today!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Joachim,

Thanks for discovering that the file was missing!  Glad it was helpful!

steven

On Tue, Aug 6, 2013 at 11:19 PM, joachim heintz  wrote:
> hi steven -
>
> the readme.txt file was only in the csound5 manual git. i have copied it
> in csound-manual6-git and pushed to git.
>
> very useful document -- building the manual went out of the box!
>
> best -
>
>         joachim
>
>
> Am 15.07.2013 21:36, schrieb Steven Yi:
>> Hi Joachim,
>>
>> If you clone the csound manual from GIT, there is a README that
>> describes what tools you need to install and how to compile the
>> manual.  (The manual uses a Makefile).  For editing the xml files, I
>> myself use vim, but any text editor works.  Docbook can be tricky to
>> learn, but if you know XML formatting, it is not so bad, especially if
>> you just copy an existing manual entry and start from there.  I'd say,
>> the only really tricky thing is getting any new pages linked in, as
>> you have to add it to a number of places.  I don't remember them at
>> the moment, but if you go that route someone here can help.
>>
>> Other than that, as the manual ticket tracker idea is up in the air,
>> I'd say you should feel free to attach any documentation you write to
>> an email to this list. Someone can then volunteer to get it
>> integrated.
>>
>> Thanks!
>> steven
>>
>>
>>
>> On Mon, Jul 15, 2013 at 3:23 PM, joachim heintz  wrote:
>>> hi steven -
>>>
>>> yes, i think any simple-to-use channel for people who are willing to
>>> contribute is good for us all. so if it is possible to add tickets
>>> particularily for the manual, i am for it.
>>>
>>> which tool do you use for writing docbook xml?
>>>
>>> and is there a description how to build the manual?
>>>
>>> thanks and best regards -
>>>
>>>          joachim
>>>
>>>
>>> Am 15.07.2013 20:49, schrieb Steven Yi:
>>>> Hi Joachim,
>>>>
>>>> The manual is itself written in Docbook XML.  It is of course easiest
>>>> if it's written in the same format, but I think any contribution in
>>>> easy to read formats would be very welcome. If it's best for you to
>>>> use a text file, then someone here can do the formatting and get it
>>>> linked into the manual.
>>>>
>>>> This makes me curious about the ticket system.  I thought we used to
>>>> have a section for tickets for the manual, but I don't see it anymore.
>>>>    I wonder if we shouldn't reinstate that, and direct manual
>>>> edits/contributions/change requests there.  Do you think that's a good
>>>> idea?
>>>>
>>>> Thanks!
>>>> steven
>>>>
>>>>
>>>> On Mon, Jul 15, 2013 at 12:46 PM, joachim heintz  wrote:
>>>>> hi steven -
>>>>>
>>>>> thanks, and yes: i will put something together which may find its place
>>>>> in the manual.
>>>>>
>>>>> is it ok to write a txt document, like the release notes, or can i
>>>>> simplify the workflow in using anything else?
>>>>>
>>>>> best -
>>>>>
>>>>>           joachim
>>>>>
>>>>>
>>>>>
>>>>> Am 15.07.2013 17:53, schrieb Steven Yi:
>>>>>> Hi Joachim,
>>>>>>
>>>>>> I think you are correct and that there is no overview documentation
>>>>>> for arrays.  At least, I did not see it in the manual6 repo.  I would
>>>>>> imagine the best place for this might be in the manual.
>>>>>>
>>>>>> Thanks!
>>>>>> steven
>>>>>>
>>>>>> On Mon, Jul 15, 2013 at 5:17 AM, joachim heintz  wrote:
>>>>>>> hi all -
>>>>>>>
>>>>>>> i am putting together some examples and explanations for using arrays. i
>>>>>>> am wondering whether there is already anything anywhere, except the
>>>>>>> release notes?
>>>>>>>
>>>>>>> the best place to put may be in the media wiki, right?
>>>>>>>
>>>>>>> all best -
>>>>>>>
>>>>>>>            joachim
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> See everything from the browser to the database with AppDynamics
>>>>>>> Get end-to-end visibility with application monitoring from AppDynamics
>>>>>>> Isolate bottlenecks and diagnose root cause in seconds.
>>>>>>> Start your free trial of AppDynamics Pro today!
>>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> See everything from the browser to the database with AppDynamics
>>>>>> Get end-to-end visibility with application monitoring from AppDynamics
>>>>>> Isolate bottlenecks and diagnose root cause in seconds.
>>>>>> Start your free trial of AppDynamics Pro today!
>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> See everything from the browser to the database with AppDynamics
>>>>> Get end-to-end visibility with application monitoring from AppDynamics
>>>>> Isolate bottlenecks and diagnose root cause in seconds.
>>>>> Start your free trial of AppDynamics Pro today!
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>> ------------------------------------------------------------------------------
>>>> See everything from the browser to the database with AppDynamics
>>>> Get end-to-end visibility with application monitoring from AppDynamics
>>>> Isolate bottlenecks and diagnose root cause in seconds.
>>>> Start your free trial of AppDynamics Pro today!
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> See everything from the browser to the database with AppDynamics
>>> Get end-to-end visibility with application monitoring from AppDynamics
>>> Isolate bottlenecks and diagnose root cause in seconds.
>>> Start your free trial of AppDynamics Pro today!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net