Re: manual translation

[Paul Kienzle]

DOCSTRINGS is created as part of the Octave build.

With the octave.tar.gz file, you need to:

        tar xzf octave.tar.gz
        ./configure
        cd src
        make DOCSTRINGS
        cd ../scripts
        make DOCSTRINGS

This gives you two files containing all the function documentation.

- Paul

On Jul 5, 2005, at 4:58 AM, Jorge Barros de Abreu wrote:

> I take this files in 
> ftp://ftp.octave.org/pub/octave/octave-2.1.71.tar.gz???
>
>
> Em Mon 04 Jul 2005 16:29, Paul Kienzle escreveu:
> > Each translation should start with the md5 hash of the doc string 
> > being
> > translated as the first line of the file so that the help system can
> > warn the user that the translation is out of date and show the new
> > English text in addition to the translated text.  Use the text in
> > octave/src/DOCSTRINGS and octave/scripts/DOCSTRINGS to calculate the
> > md5 hash for the individual functions. The md5 hash can also be used 
> > to
> > generate a list of functions which are out of date or not yet
> > translated for a particular language.
> >
> > There are some details to work out about where to store the
> > translations.  For now I would put them ./lang/pt/fn.pt where fn is
> > defined in the directory .
> >
> > - Paul