[cdp] CDP Documentation updated

[Peter P.]

Hi Robert,
(I am sending this in carbon copy to the mailing list as well)

* Robert Fraser <mail at ensemble-software.net> [2020-04-03 15:23]:
> Hi Peter,
> 
> I've now updated the CDP Documentation (3rd Apr. 2020). With one exception
> (sfedit.pdf) the latest update date is/was 10th Oct. 2019.  The html files
> were updated then, as were their pdf versions (as accessed from the bottom
> of the page updates.htm). However, the zips were not up-to-date; they were
> still as at 10th March 2019. They have now been updated to 10th Oct. 2019,
> which is in effect today.
This is amazing, thank you so much!
 
> As for the exception - sfedit.pdf - I now see that the previous usage in
> SFEDIT ISOLATE referred in some modes to "outnam" instead of "outname", so
> I've updated the PDF version. 
Yes, it seems this is the case in all modes:
 $ isolate
 USAGE:
 isolate isolate 1-2 inf outnam cutsfile [-ssplice] [-x] [-r]
 isolate isolate 3   inf outnam dBon dBoff [-ssplice] [-mmin] [-llen] [-x] [-r]
 isolate isolate 4   inf outnam slicefile [-ssplice] [-x] [-r]
 isolate isolate 5   inf outnam slicefile [-ssplice] [-ddovetail] [-x] [-r]
[...]
 INF       Input soundfile
 OUTNAM    Generic outfile name. Outfiles numbered from 0

I feel it might be easier to read the USAGE lines if parameters names
were more unified. I and the students I teach CDP to are often looking
for filename extensions in the program help: infile.wav outfile.wav as
opposed to infile.ana and outfile.ana 
Can anyone think of a good reason, apart from horizontal line space, to
not use it?

[...]
> The online html files at www.ensemble-software.net/CDPDocs will always be
> the most up-to-date. Any changes are then reflected in the print versions,
> which are turned into PDFs. What CDP distributes with CDP, however, can be
> out-of-date, but that's something that remains to be sorted out within the
> CDP.
It would be great to hear everyone's oppinion about including the html
docs in or next to the git source repository, which would also mean
having to decide for a license. Ideally having the same license for
source code, binaries and documentation will greatly simplify
distribution of CDP releases, especially for new users.

While the webpage at www.ensemble-software.net/CDPDocs indicates Archer and CDP as the copyright
holders at the bottom of the page it does not mention any usage license.

Files at https://www.unstablesound.net/cdp.html include the html
docs are indicated to be a "free download", nevertheless
the page asks that "any commercial use needs to be licensed by CDP Ltd."

The source code at git is hosted under the GNU Lesser General Public License v2.1 
https://github.com/ComposersDesktop/CDP7/blob/master/COPYING
which permits commercial use.

So it might only be a matter of moving the .html docs from the "free
download" non-commercial-use license to the LPGL-2.1

with best regards,
Peter