Re: [OctDev] New release system and web page up and running

2010-02-13 Thread Søren Hauberg
ons, 10 02 2010 kl. 16:26 -0800, skrev Søren Hauberg: > tir, 09 02 2010 kl. 14:19 +, skrev Riccardo Corradini: > > I have just observed that in http://octave.sourceforge.net/links.html > > the following link is broken: > > http://perso.orange.fr/prthomas/intro.html: Dal Segno al Coda - The > >

Re: [OctDev] How are md5 checksums generated in the translations?

2010-02-13 Thread Søren Hauberg
tir, 09 02 2010 kl. 23:49 +0100, skrev David Bateman: > > The md5 check sums are generated with the command admin/octlang tag > > FILENAME, where FILENAME is the name of the file (without extension). > > > > http://octave.sourceforge.net/translation.html > > > > > But note that the script octlan

Re: [OctDev] New release system and web page up and running

2010-02-13 Thread David Bateman
Carlo de Falco wrote: > On 12 Feb 2010, at 23:13, Søren Hauberg wrote: > > >> I don't think an elegant solution to this problem is feasibly. What I >> have written is quite a hack, but it works most of the time. We >> could in >> principle introduce a new texinfo macro that marks the first sen

Re: [OctDev] OctPROJ: a new package for Octave-Forge

2010-02-13 Thread c.
On 12 Feb 2010, at 20:30, José Luis García Pallero wrote: > Sorry, but I think that I've done something wrong. > I've followed the instructions > > If you are uploading an entire package, then put your directory into > the octave-forge tree and do the following: > > $ cd octave-forge/main > $

Re: [OctDev] OctPROJ: a new package for Octave-Forge

2010-02-13 Thread c.
On 12 Feb 2010, at 20:10, José Luis García Pallero wrote: > 2010/2/9 c. : >> I have added you to the developers, >> please follow the instructions at >> http://octave.sourceforge.net/packages.php >> to upload your code to SVN and then make a release >> c. > > I suppose the instructuins are http:/

Re: [OctDev] New release system and web page up and running

2010-02-13 Thread Carlo de Falco
On 12 Feb 2010, at 23:13, Søren Hauberg wrote: > I don't think an elegant solution to this problem is feasibly. What I > have written is quite a hack, but it works most of the time. We > could in > principle introduce a new texinfo macro that marks the first sentence, > i.e. something like > >