On Fri, 2009-06-26 at 22:14 +0200, Javier Enciso wrote:
> On Sun, 2009-06-07 at 14:25 -0500, Stephen Montgomery-Smith wrote:
> > Søren Hauberg wrote:
> > > søn, 07 06 2009 kl. 19:39 +0200, skrev Søren Hauberg:
> > >> søn, 07 06 2009 kl. 12:11 -0500, skrev Stephen Montgomery-Smith:
> > >>> I noticed that in the latest package release cycle that "spanish" isn't 
> > >>> listed any more.  Has this package been removed, or was this a mistake?
> > >> It's a mistake. I'll investigate it.
> > > 
> > > I case people need access to the package right now, it is available at
> > > 
> > > http://sourceforge.net/project/downloading.php?group_id=2888&filename=spanish-1.0.1.tar.gz&a=22099542
> > > 
> > > I'll figure out why it wasn't part of the web page.
> > > 
> > > Søren
> > > 
> > > 
> > > 
> > 
> > Maybe this is the problem:
> > 
> > make[1]: Entering directory 
> > `/usr/ports/math/octave-forge-spanish/work/spanish-1.0.1/src'
> > make[1]: *** No rule to make target `help.icc', needed by `ayuda.oct'. 
> > Stop.

I added the help.icc file to octave-forge/language/es/src/

> > make[1]: Leaving directory 
> > `/usr/ports/math/octave-forge-spanish/work/spanish-1.0.1/src'
> > make: *** [build] Error 2
> > *** Error code 1
> > 
> By inspection of the file languages/es_CO/Makefile, I have noticed that
> the rules are defined as:
> pre-pkg/%::
> post-pkg/%::
> 
> which contrast with their equivalent in the Portuguese version, where
> the rules are defined as follow:
> pre-pkg::
> post-pkg::
> 
> Could anyone please tell me which one is the right one?
> 
> 
I'm still working on the Spanish translation for help strings and have
completed around 230 files.

I decided to change the directory name from 'es_CO' to 'es' this is to
avoid difficulties with the upper and lower case (I originally took that
idea from the Portuguese package, however, I don't think that's useful
afterwards). So please, could anyone delete the 'es_CO' folder from the
repository? I tried but I got a message from SF.net asking for
authorization. 

I also have difficulties following the instructions on 'Update base'
http://octave.sourceforge.net/translation.html

In the third step, after I execute (note, there is missing '../' on the
web):
../../../../admin/split_docstrings $OCTAVE_ROOT/src/DOCSTRINGS

I get

error: number of rows must match (1 != 618) near line 4, column 48
error: evaluating assignment expression near line 4, column 9

Could any of you guys tell me how to fix it?

On the other hand, I haven't found the way to relink the Spanish Package
to 
http://octave.sourceforge.net/packages.html

I really appreciate if someone can help me with this issue. :)

Regards,
Javier


> 
> > ------------------------------------------------------------------------------
> > OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
> > looking to deploy the next generation of Solaris that includes the latest 
> > innovations from Sun and the OpenSource community. Download a copy and 
> > enjoy capabilities such as Networking, Storage and Virtualization. 
> > Go to: http://p.sf.net/sfu/opensolaris-get
> > _______________________________________________
> > Octave-dev mailing list
> > Octave-dev@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/octave-dev
> 
> Best regards,
> ------------------------------------------------------------------------------
> _______________________________________________
> Octave-dev mailing list
> Octave-dev@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/octave-dev

Best regards,
-- 
Ing. Javier Enciso                Email: encis...@in.tum.de
CSE Master Student                Tel.:  +49 (0)174-213-9631
Technische Universität München    WWW:   http://home.in.tum.de/~encisomo

Attachment: signature.asc
Description: This is a digitally signed message part

------------------------------------------------------------------------------
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev

Reply via email to