This list is closed, nobody may subscribe to it.
2000 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
(10) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
|
Feb
(4) |
Mar
|
Apr
(3) |
May
(13) |
Jun
(2) |
Jul
(7) |
Aug
|
Sep
(2) |
Oct
(5) |
Nov
(8) |
Dec
|
2002 |
Jan
|
Feb
|
Mar
(19) |
Apr
(8) |
May
(8) |
Jun
(8) |
Jul
(4) |
Aug
(8) |
Sep
(19) |
Oct
(13) |
Nov
(37) |
Dec
(2) |
2003 |
Jan
(7) |
Feb
(23) |
Mar
(16) |
Apr
(4) |
May
(18) |
Jun
(9) |
Jul
(7) |
Aug
(6) |
Sep
(7) |
Oct
|
Nov
(39) |
Dec
(57) |
2004 |
Jan
(21) |
Feb
(15) |
Mar
(17) |
Apr
(9) |
May
(17) |
Jun
(65) |
Jul
(33) |
Aug
(48) |
Sep
(93) |
Oct
(35) |
Nov
(18) |
Dec
(4) |
2005 |
Jan
(20) |
Feb
(59) |
Mar
(17) |
Apr
(59) |
May
(77) |
Jun
(32) |
Jul
(34) |
Aug
(8) |
Sep
(34) |
Oct
(26) |
Nov
(65) |
Dec
(66) |
2006 |
Jan
(45) |
Feb
(37) |
Mar
(50) |
Apr
(32) |
May
(48) |
Jun
(42) |
Jul
(12) |
Aug
(53) |
Sep
(51) |
Oct
(79) |
Nov
(46) |
Dec
(25) |
2007 |
Jan
(120) |
Feb
(78) |
Mar
(45) |
Apr
(91) |
May
(155) |
Jun
(66) |
Jul
(96) |
Aug
(110) |
Sep
(145) |
Oct
(189) |
Nov
(68) |
Dec
(160) |
2008 |
Jan
(163) |
Feb
(212) |
Mar
(209) |
Apr
(157) |
May
(216) |
Jun
(120) |
Jul
(80) |
Aug
(83) |
Sep
(98) |
Oct
(120) |
Nov
(80) |
Dec
(129) |
2009 |
Jan
(45) |
Feb
(80) |
Mar
(174) |
Apr
(142) |
May
(133) |
Jun
(191) |
Jul
(183) |
Aug
(138) |
Sep
(77) |
Oct
(141) |
Nov
(209) |
Dec
(131) |
2010 |
Jan
(85) |
Feb
(213) |
Mar
(245) |
Apr
(222) |
May
(168) |
Jun
(82) |
Jul
(50) |
Aug
(144) |
Sep
(92) |
Oct
(80) |
Nov
(64) |
Dec
(78) |
2011 |
Jan
(58) |
Feb
(98) |
Mar
(112) |
Apr
(98) |
May
(64) |
Jun
(150) |
Jul
(126) |
Aug
(59) |
Sep
(271) |
Oct
(154) |
Nov
(321) |
Dec
(183) |
2012 |
Jan
(146) |
Feb
(217) |
Mar
(426) |
Apr
(208) |
May
(206) |
Jun
(230) |
Jul
(158) |
Aug
(170) |
Sep
(237) |
Oct
(260) |
Nov
(178) |
Dec
|
From: David B. <Dav...@mo...> - 2005-11-04 09:59:27
|
Quentin Spencer wrote: > I tried compiling the cvs version of octave-forge with the cvs version > of octave, and two functions failed to compile: > > 1. main/fixed/fixedNDArray.cc > > fixedNDArray.o > fixedNDArray.cc:407:59: error: macro "MX_ND_REDUCTION" passed 5 > arguments, but takes just 3 > fixedNDArray.cc:421:61: error: macro "MX_ND_REDUCTION" passed 5 > arguments, but takes just 3 > fixedNDArray.cc:436:61: error: macro "MX_ND_REDUCTION" passed 5 > arguments, but takes just 3 > > This appears to be caused by recent changes to octave. I don't know > enough about this code to debug it, but from looking at it, it appears > that this macro has changed periodically in the past and there is > already some cruft in the code to handle different cases. To whoever > fixes this I suggest removing the old stuff since we are trying to > clean up before octave 3.0. > Try the attached patch, that I'll commit soon. Yes it adds more cruft, but we'll get rid of that soon, as I said.. D. -- David Bateman Dav...@mo... Motorola Labs - Paris +33 1 69 35 48 04 (Ph) Parc Les Algorithmes, Commune de St Aubin +33 1 69 35 77 01 (Fax) 91193 Gif-Sur-Yvette FRANCE The information contained in this communication has been classified as: [x] General Business Information [ ] Motorola Internal Use Only [ ] Motorola Confidential Proprietary |
From: David B. <Dav...@mo...> - 2005-11-04 09:02:15
|
Quentin Spencer wrote: > I tried compiling the cvs version of octave-forge with the cvs version > of octave, and two functions failed to compile: > > 1. main/fixed/fixedNDArray.cc > > fixedNDArray.o > fixedNDArray.cc:407:59: error: macro "MX_ND_REDUCTION" passed 5 > arguments, but takes just 3 > fixedNDArray.cc:421:61: error: macro "MX_ND_REDUCTION" passed 5 > arguments, but takes just 3 > fixedNDArray.cc:436:61: error: macro "MX_ND_REDUCTION" passed 5 > arguments, but takes just 3 > > This appears to be caused by recent changes to octave. I don't know > enough about this code to debug it, but from looking at it, it appears > that this macro has changed periodically in the past and there is > already some cruft in the code to handle different cases. To whoever > fixes this I suggest removing the old stuff since we are trying to > clean up before octave 3.0. Grrr, that ones mine. It seems to me that a new 2.1.x release of octave-forge is a reasonable goal as the code in octave-forge is still compatible with 2.1.x. So I'd like to keep a 2.1.71 (or 2.1.72 if it comes out) and 2.9.4 (when it comes out) compatible version of the this change for now. I'd suggest an octave-forge release soon after the next 2.9 and perhaps 2.1 release. There doesn't seem all that much point to me in completely decrufting octave-forge at this point as when Soren's package management code is include in octave, then the whole paradigm of octave-forge will change and that is the best point to do the decrufting at the time of that transition... Regards David -- David Bateman Dav...@mo... Motorola Labs - Paris +33 1 69 35 48 04 (Ph) Parc Les Algorithmes, Commune de St Aubin +33 1 69 35 77 01 (Fax) 91193 Gif-Sur-Yvette FRANCE The information contained in this communication has been classified as: [x] General Business Information [ ] Motorola Internal Use Only [ ] Motorola Confidential Proprietary |
From: Jorge B. de A. <fic...@so...> - 2005-11-04 06:26:06
|
I want to say that i assume the "updater" work at "the permanent form" (wh= ile=20 suitable for project) (type error) =2D-=20 Data Estelar 2453678.817813 http://www.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. |
From: Jorge B. de A. <fic...@so...> - 2005-11-04 06:17:10
|
Em Thursday 03 November 2005 12:15, Paul Kienzle escreveu: > It should not matter who updates it, but I'm happy to leave you to it. ok. This avoid upload conflicts. > In what way is this update not permanent? Is it a branch? excuse me. My english needs update :-)). The "permanent" is not for the files The permanent is for "updater" ( for me in the "updater" work) I want to say that i assume the "updater" work at he for permanent (while=20 suitable for project) > Please, if you have scripts to help out with the admin or translation > process, add them to octave-lang/admin so that other languages can > benefit. ok. is good for me see the work to be used (freely) around the world and=20 turning the world better. =2D-=20 Data Estelar 2453678.817813 http://www.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. |
From: Dmitri A. S. <das...@gm...> - 2005-11-03 22:03:41
|
On 11/3/05, Quentin Spencer <qsp...@ie...> wrote: > 2. main/image/pngread.cc > > /usr/include/pngconf.h:307: error: expected constructor, destructor, or > type conversion before '.' token > /usr/include/pngconf.h:308: error: '__dont__' does not name a type > pngread.cc: In function 'canvas* load_canvas(char*)': > pngread.cc:156: warning: ignoring return value of 'size_t fread(void*, > size_t, size_t, FILE*)', declared with attribute warn_unused_result > > I'm not sure what's causing this. I'm using Fedora Core 4, with > libpng-1.2.8-2 installed, and the compiler is gcc 4.0.1. This is libpng doing. If you look at pngconf.h it has the following: #ifdef PNG_SETJMP_SUPPORTED /* This is an attempt to force a single setjmp behaviour on Linux. If * the X config stuff didn't define _BSD_SOURCE we wouldn't need this. */ # ifdef __linux__ # ifdef _BSD_SOURCE # define PNG_SAVE_BSD_SOURCE # undef _BSD_SOURCE # endif # ifdef _SETJMP_H /* If you encounter a compiler error here, see the explanation * near the end of INSTALL. */ __png.h__ already includes setjmp.h; __dont__ include it again.; # endif # endif /* __linux__ */ I do not know who this problem should be handled... > -Quentin > Sincerely, Dmitri. -- |
From: Quentin S. <qsp...@ie...> - 2005-11-03 19:36:53
|
I tried compiling the cvs version of octave-forge with the cvs version of octave, and two functions failed to compile: 1. main/fixed/fixedNDArray.cc fixedNDArray.o fixedNDArray.cc:407:59: error: macro "MX_ND_REDUCTION" passed 5 arguments, but takes just 3 fixedNDArray.cc:421:61: error: macro "MX_ND_REDUCTION" passed 5 arguments, but takes just 3 fixedNDArray.cc:436:61: error: macro "MX_ND_REDUCTION" passed 5 arguments, but takes just 3 This appears to be caused by recent changes to octave. I don't know enough about this code to debug it, but from looking at it, it appears that this macro has changed periodically in the past and there is already some cruft in the code to handle different cases. To whoever fixes this I suggest removing the old stuff since we are trying to clean up before octave 3.0. 2. main/image/pngread.cc /usr/include/pngconf.h:307: error: expected constructor, destructor, or type conversion before ‘.’ token /usr/include/pngconf.h:308: error: ‘__dont__’ does not name a type pngread.cc: In function ‘canvas* load_canvas(char*)’: pngread.cc:156: warning: ignoring return value of ‘size_t fread(void*, size_t, size_t, FILE*)’, declared with attribute warn_unused_result I'm not sure what's causing this. I'm using Fedora Core 4, with libpng-1.2.8-2 installed, and the compiler is gcc 4.0.1. I have a related question to this. I see that octave-forge now has the option of using ImageMagick++, but I didn't follow the earlier discussion about this closely. Is this intended to provide new features that are unavailable in libjpg and libpng, or does it provide an alternate way of getting the same features? This will influence whether I add ImageMagick-c++-devel as a build dependency for the Fedora Extras octave-forge package. -Quentin |
From: Paul K. <pki...@us...> - 2005-11-03 12:15:59
|
It should not matter who updates it, but I'm happy to leave you to it. In what way is this update not permanent? Is it a branch? Please, if you have scripts to help out with the admin or translation=20 process, add them to octave-lang/admin so that other languages can=20 benefit. - Paul On Nov 3, 2005, at 12:46 AM, Jorge Barros de Abreu wrote: > Is suitable that only one update it. > If there is no problem i will like to make this update permanent to=20 > avoid > conflicts. I will need some time ( 15 days) for adjust my personal=20 > scripts > for this work. > > Thanks > > Em Thursday 03 November 2005 02:40, Paul Kienzle escreveu: >> On Nov 2, 2005, at 9:00 AM, Jorge Barros de Abreu wrote: >>> ????You or i update octave-lang/base/octave/help???? >> >> Probably you or one of the other translators. >> >> I did so for 2.9.3 so that I could write the documentation in >> octave-lang/admin/translation.html. >> >> Please read it. Let me know what parts you do not understand. >> >> Thanks, >> >> - Paul > > --=20 > Data Estelar 2453677.856123 > http://www.solar.com.br/~ficmatin > Desejo-lhe Paz, Vida Longa e Prosperidade. > S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. > > |
From: Jorge B. de A. <fic...@so...> - 2005-11-03 06:27:36
|
I remake the src/DOCSTRINGS and put the results in: http://usr.solar.com.br/~ficmatin/DOCSTRINGS_SRC http://usr.solar.com.br/~ficmatin/DOCSTRINGS_SRC_BAD Em Thursday 03 November 2005 02:57, Paul Kienzle escreveu: > Are you sure? I rebuilt DOCSTRINGS without using omit_deps and I get > the same result: =2D-=20 Data Estelar 2453677.885567 http://www.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. |
From: Jorge B. de A. <fic...@so...> - 2005-11-03 06:27:30
|
Is suitable that only one update it. If there is no problem i will like to make this update permanent to avoid=20 conflicts. I will need some time ( 15 days) for adjust my personal scripts= =20 for this work. Thanks Em Thursday 03 November 2005 02:40, Paul Kienzle escreveu: > On Nov 2, 2005, at 9:00 AM, Jorge Barros de Abreu wrote: > > ????You or i update octave-lang/base/octave/help???? > > Probably you or one of the other translators. > > I did so for 2.9.3 so that I could write the documentation in > octave-lang/admin/translation.html. > > Please read it. Let me know what parts you do not understand. > > Thanks, > > - Paul =2D-=20 Data Estelar 2453677.856123 http://www.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. |
From: Paul K. <pki...@us...> - 2005-11-03 02:57:48
|
Are you sure? I rebuilt DOCSTRINGS without using omit_deps and I get=20 the same result: Avocado:~/Downloads/octave-2.9.3/src paulkienzle$ diff -cp DOCSTRINGS=20= DOCSTRINGS-nodep Avocado:~/Downloads/octave-2.9.3/src paulkienzle$ Can you please tell me how they differs? - Paul On Nov 2, 2005, at 6:00 AM, Jorge Barros de Abreu wrote: > Hi Paul and all > > The DOCSTRINGS generated by this process: > > (cd src && make omit_deps=3D1 DOCSTRINGS) > > is different of DOCSTRINGS generated by: > > (cd src && make DOCSTRINGS) > > --=20 > Data Estelar 2453676.325312 > http://www.solar.com.br/~ficmatin > Desejo-lhe Paz, Vida Longa e Prosperidade. > S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server.=20 > Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Octave-dev mailing list > Oct...@li... > https://lists.sourceforge.net/lists/listinfo/octave-dev > |
From: Paul K. <pki...@us...> - 2005-11-03 02:40:32
|
On Nov 2, 2005, at 9:00 AM, Jorge Barros de Abreu wrote: > ????You or i update octave-lang/base/octave/help???? > Probably you or one of the other translators. I did so for 2.9.3 so that I could write the documentation in octave-lang/admin/translation.html. Please read it. Let me know what parts you do not understand. Thanks, - Paul |
From: Paul K. <pki...@us...> - 2005-11-03 02:37:07
|
You don't need to remove the old files before putting in the new ones. - Paul On Nov 2, 2005, at 8:52 AM, Jorge Barros de Abreu wrote: > Hi Paul. > > remove all file and put new file. > > Em Wednesday 02 November 2005 12:20, Paul Kienzle escreveu: >> Jorge, >> >> I'm not sure what you did with your big CVS post. I now get the >> following errors when updating: >> >> Avocado:~/cvs/octave-lang/base/octave/help paulkienzle$ cvs -q=20 >> update >> -dP >> cvs update: move away ./errno; it is in the way >> C errno >> cvs update: move away ./i; it is in the way >> C i >> cvs update: move away ./inf; it is in the way >> C inf >> cvs update: move away ./j; it is in the way >> C j >> cvs update: move away ./nan; it is in the way >> C nan >> >> >> All these files are mixed case and I'm running OS X. >> >> Anyone have any suggestions? >> >> - Paul >> >> On Nov 2, 2005, at 3:39 AM, Jorge Barros de Abreu wrote: >>> You are welcome Paul. >>> >>> []=B4s >>> >>> Em Wednesday 02 November 2005 03:49, Paul Kienzle escreveu: >>>> Jorge, >>>> >>>> I don't see any problem with adding new files to base/octave for >>>> 2.9.4. >>> >>> .............. >>> ............. >>> >>>> Given that, updating existing files should be okay too. >>>> >>>> - Paul >>> >>> -- >>> Data Estelar 2453676.964653 >>> http://www.solar.com.br/~ficmatin >>> Desejo-lhe Paz, Vida Longa e Prosperidade. >>> S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: >> Tame your development challenges with Apache's Geronimo App Server. >> Download it for free - -and be entered to win a 42" plasma tv or your=20= >> very >> own Sony(tm)PSP. Click here to play:=20 >> http://sourceforge.net/geronimo.php >> _______________________________________________ >> Octave-dev mailing list >> Oct...@li... >> https://lists.sourceforge.net/lists/listinfo/octave-dev > > --=20 > Data Estelar 2453677.118056 > http://www.solar.com.br/~ficmatin > Desejo-lhe Paz, Vida Longa e Prosperidade. > S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server.=20 > Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Octave-dev mailing list > Oct...@li... > https://lists.sourceforge.net/lists/listinfo/octave-dev > |
From: Jorge B. de A. <fic...@so...> - 2005-11-02 15:05:06
|
Paul This errors will occurs until we "correct the hands" (complete the project= =20 scripts). Will survive. []=B4s Em Wednesday 02 November 2005 12:20, Paul Kienzle escreveu: > Jorge, =2D-=20 Data Estelar 2453677.250648 http://www.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. |
From: Jorge B. de A. <fic...@so...> - 2005-11-02 13:50:36
|
Hi Paul. Remove all files and put new. ????You or i update octave-lang/base/octave/help???? Thanks Em Wednesday 02 November 2005 12:20, Paul Kienzle escreveu: > Jorge, > > I'm not sure what you did with your big CVS post. I now get the > following errors when updating: > > Avocado:~/cvs/octave-lang/base/octave/help paulkienzle$ cvs -q update > -dP > cvs update: move away ./errno; it is in the way > C errno > cvs update: move away ./i; it is in the way > C i > cvs update: move away ./inf; it is in the way > C inf > cvs update: move away ./j; it is in the way > C j > cvs update: move away ./nan; it is in the way > C nan > > > All these files are mixed case and I'm running OS X. > > Anyone have any suggestions? > > - Paul > > On Nov 2, 2005, at 3:39 AM, Jorge Barros de Abreu wrote: > > You are welcome Paul. > > > > []=B4s > > > > Em Wednesday 02 November 2005 03:49, Paul Kienzle escreveu: > >> Jorge, > >> > >> I don't see any problem with adding new files to base/octave for > >> 2.9.4. > > > > .............. > > ............. > > > >> Given that, updating existing files should be okay too. > >> > >> - Paul > > > > -- > > Data Estelar 2453676.964653 > > http://www.solar.com.br/~ficmatin > > Desejo-lhe Paz, Vida Longa e Prosperidade. > > S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download it for free - -and be entered to win a 42" plasma tv or your very > own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Octave-dev mailing list > Oct...@li... > https://lists.sourceforge.net/lists/listinfo/octave-dev =2D-=20 Data Estelar 2453677.118056 http://www.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. |
From: Jorge B. de A. <fic...@so...> - 2005-11-02 13:42:37
|
Hi Paul and all The DOCSTRINGS generated by this process: (cd src && make omit_deps=3D1 DOCSTRINGS) is different of DOCSTRINGS generated by: (cd src && make DOCSTRINGS) =2D-=20 Data Estelar 2453676.325312 http://www.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. |
From: Jorge B. de A. <fic...@so...> - 2005-11-02 13:42:36
|
Hi Paul. remove all file and put new file. Em Wednesday 02 November 2005 12:20, Paul Kienzle escreveu: > Jorge, > > I'm not sure what you did with your big CVS post. I now get the > following errors when updating: > > Avocado:~/cvs/octave-lang/base/octave/help paulkienzle$ cvs -q update > -dP > cvs update: move away ./errno; it is in the way > C errno > cvs update: move away ./i; it is in the way > C i > cvs update: move away ./inf; it is in the way > C inf > cvs update: move away ./j; it is in the way > C j > cvs update: move away ./nan; it is in the way > C nan > > > All these files are mixed case and I'm running OS X. > > Anyone have any suggestions? > > - Paul > > On Nov 2, 2005, at 3:39 AM, Jorge Barros de Abreu wrote: > > You are welcome Paul. > > > > []=B4s > > > > Em Wednesday 02 November 2005 03:49, Paul Kienzle escreveu: > >> Jorge, > >> > >> I don't see any problem with adding new files to base/octave for > >> 2.9.4. > > > > .............. > > ............. > > > >> Given that, updating existing files should be okay too. > >> > >> - Paul > > > > -- > > Data Estelar 2453676.964653 > > http://www.solar.com.br/~ficmatin > > Desejo-lhe Paz, Vida Longa e Prosperidade. > > S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download it for free - -and be entered to win a 42" plasma tv or your very > own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Octave-dev mailing list > Oct...@li... > https://lists.sourceforge.net/lists/listinfo/octave-dev =2D-=20 Data Estelar 2453677.118056 http://www.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. |
From: Paul K. <pki...@us...> - 2005-11-02 12:21:01
|
Jorge, I'm not sure what you did with your big CVS post. I now get the=20 following errors when updating: Avocado:~/cvs/octave-lang/base/octave/help paulkienzle$ cvs -q update=20= -dP cvs update: move away ./errno; it is in the way C errno cvs update: move away ./i; it is in the way C i cvs update: move away ./inf; it is in the way C inf cvs update: move away ./j; it is in the way C j cvs update: move away ./nan; it is in the way C nan All these files are mixed case and I'm running OS X. Anyone have any suggestions? - Paul On Nov 2, 2005, at 3:39 AM, Jorge Barros de Abreu wrote: > You are welcome Paul. > > []=B4s > > Em Wednesday 02 November 2005 03:49, Paul Kienzle escreveu: >> Jorge, >> >> I don't see any problem with adding new files to base/octave for=20 >> 2.9.4. > .............. > ............. >> Given that, updating existing files should be okay too. >> >> - Paul >> > --=20 > Data Estelar 2453676.964653 > http://www.solar.com.br/~ficmatin > Desejo-lhe Paz, Vida Longa e Prosperidade. > S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. > > |
From: Jorge B. de A. <fic...@so...> - 2005-11-02 09:05:02
|
You are welcome Paul. []=B4s Em Wednesday 02 November 2005 03:49, Paul Kienzle escreveu: > Jorge, > > I don't see any problem with adding new files to base/octave for 2.9.4. =2E............. =2E............ > Given that, updating existing files should be okay too. > > - Paul > =2D-=20 Data Estelar 2453676.964653 http://www.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. |
From: Paul K. <pki...@us...> - 2005-11-02 05:33:34
|
Jorge, I've implemented part of octlang as described on: http://octave.sourceforge.net/translation.html Copy this from admin/octlang to your ~/bin directory and type cd octave-lang/pt/octave/help octlang update You will see that contour.pt has been updated in base. Type the following to get the changes octlang diff contour.pt Note that this process is slow. You could speed it up considerably by=20= keeping a list of precalculated md5sums in base and in each=20 subdirectory. Then it is a matter of joining those two files, sorting=20= and looking at the diff. - Paul On Oct 28, 2005, at 9:13 AM, Jorge Barros de Abreu wrote: > Hi for all. > I have two directories: > > directory "new" with updated docstrigs after "split_docstrings" script=20= > applied > directory "old" with the same files but with old form. > > The question is: > How i compare it with via md5 string to know which files need update > translation? > There is some already created script? > Thanks > --=20 > Data Estelar 2453672.158171 > http://www.solar.com.br/~ficmatin > Desejo-lhe Paz, Vida Longa e Prosperidade. > S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. > Get Certified Today * Register for a JBoss Training Course > Free Certification Exam for All Training Attendees Through End of 2005 > Visit http://www.jboss.com/services/certification for more information > _______________________________________________ > Octave-dev mailing list > Oct...@li... > https://lists.sourceforge.net/lists/listinfo/octave-dev > |
From: Paul K. <pki...@us...> - 2005-11-02 03:49:46
|
Jorge, I don't see any problem with adding new files to base/octave for 2.9.4. I'm not sure about updating existing files with the 2.9.4 version since=20= there may be some value in keeping a consistent set of docs as the=20 basis for translation. You are correct that the determination of whether the translated doc=20 accurately reflects the doc in octave is based on the md5sum of the doc=20= in octave matching the md5sum stored with the translation. So even=20 though it will display the translation of the wrong document, it will=20 warn the user that the translation is out of date and display the=20 original. Given that, updating existing files should be okay too. - Paul On Nov 1, 2005, at 4:48 PM, Jorge Barros de Abreu wrote: > Hi for all. > > Do i can update all octave-lang/base/octave/help? > Or only when 2.9.4 was released? > > I have a new version file but this file is not released on octave-lang=20= > and do > not have cvs-version. > > I thing that is no problem as information for update translation cames=20= > from > md5sum and not from cvs-version > > Thanks > > --=20 > Data Estelar 2453676.325312 > http://www.solar.com.br/~ficmatin > Desejo-lhe Paz, Vida Longa e Prosperidade. > S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server.=20 > Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Octave-dev mailing list > Oct...@li... > https://lists.sourceforge.net/lists/listinfo/octave-dev > |
From: Jorge B. de A. <fic...@so...> - 2005-11-01 21:39:29
|
Hi for all. Do i can update all octave-lang/base/octave/help? Or only when 2.9.4 was released? I have a new version file but this file is not released on octave-lang and = do=20 not have cvs-version. I thing that is no problem as information for update translation cames from= =20 md5sum and not from cvs-version Thanks =2D-=20 Data Estelar 2453676.325312 http://www.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. |
From: Paul K. <pki...@us...> - 2005-10-31 05:43:05
|
Jorge, I have written up a more complete set of instructions in octave-lang/admin/translation.html. Please correct any errors in it. I put a copy at octave.sf.net/translation.html - Paul On Oct 29, 2005, at 6:53 AM, Jorge Barros de Abreu wrote: > Hi for all. > > Please correct me if the english is not good or if there is another > mistake. > > How to begin a new language translation in octave |
From: Jorge B. de A. <fic...@so...> - 2005-10-29 11:48:51
|
Me too. I develop a script (texi.sh) using shell and sed that allow to you type =A0= in=20 your native language. After you end the translation file you load the scrip= t=20 and its convert the diacritical marks in your language to texinfo code. Need to be changed for your language At the moment the script work for portuguese and partial spanish. Hope that this make easy your translation. []=B4s http://usr.solar.com.br/~ficmatin/texi.sh =2D-=20 Data Estelar 2453673.001215 http://www.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. |
From: Jorge B. de A. <fic...@so...> - 2005-10-29 10:43:52
|
Hi for all. Please correct me if the english is not good or if there is another mistake. How to begin a new language translation in octave 1-create a directory named, say, cvs_octave. Get octave-lang using the scri= pt: #!/bin/bash export CVS_RSH=3Dssh cvs -d :pserver:ano...@cv...:/cvsroot/octave login cvs -d :pserver:ano...@cv...:/cvsroot/octave get octave-lang cvs -d :pserver:ano...@cv...:/cvsroot/octave logout unset CVS_RSH 2-in the same directory get octave from cvs using the script: #!/bin/bash export CVS_RSH=3Dssh cvs -d :ext:an...@ww...:/cvs checkout octave unset CVS_RSH At this point we have two directories: octave ioctave-lang 2- compile octave using(without make install): cd octave =2E/configure make if make install was used your previous instalation of the stable version=20 will be updated/changed ( i do not recommend it) 3 -still in main local octave directory type the commands: ls -l src/DOCSTRINGS ls -l scripts/DOCSTRINGS the two commands return is informations about the the two=20 archives that is the translation basis. If these two files was been=20 generated in copilation then is all good for translation: If the translation directory is /home/user/octave/translation then: mv src/DOCSTRINGS /home/user/octave/translation/DOCSTRINGS_SRC mv scripts/DOCSTRINGS /home/user/octave/translation/DOCSTRINGS_SCRIPTS 4- copy the file "octave-lang/admin/split_docstrings" to=20 "/home/user/octave/translation/split_docstrings" 5- type "split_docstrings DOCSTRINGS_SRC" and=20 "split_docstrings DOCSTRINGS_SCRIPTS" 6- if is the translation begin move all created files to=20 "octave-lang/base/octave/help" 7- translated file model is on the "octave-lang/pt/octave/help" and the new= =20 file=20 translated for language xx must be in "octave-lang/xx/octave/help" and=20 uploaded for=20 cvs.sf.net. 8- the translation maintenance is another chapter that is not write yet. May the force be with you because you will be need it. > Dear octave-dev, >=20 > A translation of about 9-10 sections of the octave documentation - from > the point of view of a reader, i.e. not at all integrated into the > source tree - in polish - is available here: >=20 > http://cosmo.torun.pl/cgi-bin/twiki/view/Cosmo/OctavePl >=20 >=20 > It would be a pity if this work gets lost - several people did a lot of > good work in doing the translation. >=20 > IMHO at least some sort of link to this, or the file itself - the file > is essentially in=20 >=20 > pre >=20 > html format - i could attach it or > someone can just copy/paste - should go somewhere in the source tree, > so that anybody working more "systematically" on polish translation > can at least know about it, maybe do some cutting/pasting rather than > starting from zero. >=20 > i realise that, with hindsight, it may have been better to find out the > "right" way to translate right from the beginning. In any case, maybe this > could at least motivate some polish-english speaking people to work furth= er > on this. :) >=20 > Since the translations are translations of GPL material, i assume that th= ey > automatically are covered by the GPL. >=20 > cheers > boud >=20 >=20 =2D-=20 Data Estelar 2453673.001215 http://www.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. |
From: Paul K. <pki...@us...> - 2005-10-29 02:04:37
|
boud, We have the kernel of an octave translation project in the module octave-lang at the sourceforge site. Jorge Barros de Abreu has been systematically working his way through the documentation of the individual functions, translating them into Portuguese. Since much of the manual is built by gathering the documentation from the individual functions, this means he has made progress on the manual and he can get help for the individual functions online. The rest of the manual (the part that describes the syntax) is somewhat out of date, and should be updated before translating. You can take your individual function descriptions off the wiki and put them into separate .pl files in the directory octave-lang/pl/octave/help. Then you need to write a help function (presumably named after the Polish word for 'help') which finds the function definition and displays it. At the head of every file you should include the md5sum of the corresponding help text in the base octave function in octave-lang/base/octave/help. That way you will be able to tell help has changed since it was translated, and display both the Polish and the English help. You also need to store the CVS revision number of the file in octave-lang/base/octave/help. That way when someone finally has an opportunity to update the translation they can run 'cvs diff -cp -r version file' in the base directory and learn exactly how the text has changed. The text of the functions is indeed under GPL license. - Paul On Oct 28, 2005, at 10:49 AM, Boud Roukema wrote: > Dear octave-dev, > > A translation of about 9-10 sections of the octave documentation - from > the point of view of a reader, i.e. not at all integrated into the > source tree - in polish - is available here: > > http://cosmo.torun.pl/cgi-bin/twiki/view/Cosmo/OctavePl > > > It would be a pity if this work gets lost - several people did a lot of > good work in doing the translation. > > IMHO at least some sort of link to this, or the file itself - the file > is essentially in <pre>pre</pre> html format - i could attach it or > someone can just copy/paste - should go somewhere in the source tree, > so that anybody working more "systematically" on polish translation > can at least know about it, maybe do some cutting/pasting rather than > starting from zero. > > i realise that, with hindsight, it may have been better to find out the > "right" way to translate right from the beginning. In any case, maybe > this > could at least motivate some polish-english speaking people to work > further > on this. :) > > Since the translations are translations of GPL material, i assume that > they > automatically are covered by the GPL. > > cheers > boud > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. > Get Certified Today * Register for a JBoss Training Course > Free Certification Exam for All Training Attendees Through End of 2005 > Visit http://www.jboss.com/services/certification for more information > _______________________________________________ > Octave-dev mailing list > Oct...@li... > https://lists.sourceforge.net/lists/listinfo/octave-dev > |