[OctDev] Re: help spinv (2.9.3 version)

[Paul K. <pki...@us...>]

On Oct 26, 2005, at 3:55 AM, David Bateman wrote:

> Jorge Barros de Abreu a =E9crit :
>
>> How i receive a message saying to me that the file xxxxxxx was=20
>> changed?
>>
>>
> Jorge,
>
> I think you need to ask these questions to Paul, as I'm not sure how=20=

> the translation packages work. I believe he extracted the DOCSTRINGS=20=

> file and split it into individual files for you to translate though I=20=

> can't be sure that is how he did it. I believe that 2.9.4 will be=20
> released fairly soon from what John has been saying and so I'd suggest=20=

> that to have a solid base that when 2.9.4 is release Paul can create=20=

> or show you how to create a new set of base files from which to=20
> translate and check against...

David is correct.  We need to get the two DOCSTRINGS files from the new=20=

octave build and split them in octave-lang/base/octave/help with the=20
command octave-lang/admin/split_docstrings.  Then we do a cvs commit on=20=

that directory (to update all the revision numbers of the files that=20
have changed) and 'cvs rtag 2.9.4' in the octave/help directory.

Next we will need to write octave-lang/admin/listnew which lists the=20
files in the pt subtree which have a version number older than the=20
files in octave-lang/base.

Then we will need to write octave-lang/admin/changes which pops up a=20
'cvs diff' or 'tkdiff' between the version number listed in the=20
translated file and the latest version in the base archive.

- Paul