Hello all (Sorry for the cross-posting to the two lists, but I wanted to make sure I got everyone). We're now close to the point of releasing gretl 1.8.0, having assembled quite a few new features and a lot of bug fixes. See http://gretl.sourceforge.net/ChangeLog.html . But the most exasperating thing in this business is when you make a new release and immediately get a report of a serious bug and so have to make a further release right away. In this regard, everyone can help. The Windows snapshot, at http://ricardo.ecn.wfu.edu/pub/gretl/gretl_install.exe and the OS X (Intel) snapshot, at http://ricardo.ecn.wfu.edu/pub/gretl/gretl.dmg are both up to date with gretl CVS as of January 12. If you can find 15 minutes to run your favourite gretl scripts, or try your favourute gretl GUI operations, then please do, and report any problems on one or other of the mailing lists. If any errors come up, we'll fix them tout de suite, then make gretl 1.8.0 available. Also, if any translators have things they want to update for the forthcoming release, please do that in the next day or two. Thanks!

Hello! I've found two small bugs with function manager (File - Function files - On server...): 1) When I install function package, the local status changes from "Not installed" to "Up to date" and it becomes installed locally. But, if I close the manager and open it again, the local status is "Not installed" again. 2) When I use Russian locale this manager doesn't correctly display local status. I get some readable Russian characters and some "rectangles" instead of translated string "Not installed" ("Не установлен" in Russian). Also, I've marked some untranslated strings (see .diff attached) Alexander Gedranovich Allin Cottrell wrote: Hello all (Sorry for the cross-posting to the two lists, but I wanted to make sure I got everyone). We're now close to the point of releasing gretl 1.8.0, having assembled quite a few new features and a lot of bug fixes. See http://gretl.sourceforge.net/ChangeLog.html . But the most exasperating thing in this business is when you make a new release and immediately get a report of a serious bug and so have to make a further release right away. In this regard, everyone can help. The Windows snapshot, at http://ricardo.ecn.wfu.edu/pub/gretl/gretl_install.exe and the OS X (Intel) snapshot, at http://ricardo.ecn.wfu.edu/pub/gretl/gretl.dmg are both up to date with gretl CVS as of January 12. If you can find 15 minutes to run your favourite gretl scripts, or try your favourute gretl GUI operations, then please do, and report any problems on one or other of the mailing lists. If any errors come up, we'll fix them tout de suite, then make gretl 1.8.0 available. Also, if any translators have things they want to update for the forthcoming release, please do that in the next day or two. Thanks! _______________________________________________ Gretl-devel mailing list Gretl-devel(a)lists.wfu.edu http://lists.wfu.edu/mailman/listinfo/gretl-devel

I've found two small bugs with function manager (File - Function files - On server...): 1) When I install function package, the local status changes from "Not installed" to "Up to date" and it becomes installed locally. But, if I close the manager and open it again, the local status is "Not installed" again. 2) When I use Russian locale this manager doesn't correctly display local status. I get some readable Russian characters and some "rectangles" instead of translated string "Not installed" ("Не установлен" in Russian).

Also, I've marked some untranslated strings (see .diff attached)

On Thu, 15 Jan 2009, Alexander B. Gedranovich wrote: > I've found two small bugs with function manager (File - Function files - > On server...): > 1) When I install function package, the local status changes from "Not > installed" to "Up to date" and it becomes installed locally. But, if I > close the manager and open it again, the local status is "Not installed" > again. > 2) When I use Russian locale this manager doesn't correctly display local > status. I get some readable Russian characters and some "rectangles" > instead of translated string "Not installed" ("Не установлен" > in Russian). I think this is now fixed in CVS. However, I'm seeing one apparently odd thing that is maybe introduced by gettext and I wonder if anyone can comment. It's to do with the string "Not installed" for function packages and databases. In ru.po this is given as (transliterated): "Ne ustanovlen". But when it appears to the user it's "Ne ustanovlen(a)". I added debugging code to print this translation to stderr as well as the GUI and it's the same in both cases, i.e.

On Thu, 15 Jan 2009, Allin Cottrell wrote: > On Thu, 15 Jan 2009, Alexander B. Gedranovich wrote: > > Also, I've marked some untranslated strings (see .diff attached) > > Thanks. I've applied most of the changes. But one sort of change maybe wants some discussion: namely, should we be translating the descriptive labels we write out for new variables created by, for example, the filter functions? As in, "4-period moving average of foo" I'm not sure we're fully consistent on this. Just checking. Allin.

there seems to be a problem with nested loops. Try this with CVS: <script> nulldata 10 loop 2 x = normal() y = normal() loop 2 k = 0 end loop ols y 0 x end loop </script> You get 4 ols-es instead of 2.

Everything is displayed correctly now. Thanks.

I do agree with Ignacio - we should try to translate as much as we can, including labels of auto-generated variables. Allin, in the first .diff I've sent was one change for 'pca.c' that wasn't applied for CVS. I hope it was missed accidentally :). Sending it once again in separate file. Ignacio Diaz-Emparanza wrote: El Thursday 15 January 2009 16:15:52 Allin Cottrell escribió: On Thu, 15 Jan 2009, Allin Cottrell wrote: On Thu, 15 Jan 2009, Alexander B. Gedranovich wrote: Also, I've marked some untranslated strings (see .diff attached) Thanks. I've applied most of the changes. But one sort of change maybe wants some discussion: namely, should we be translating the descriptive labels we write out for new variables created by, for example, the filter functions? As in, "4-period moving average of foo" I'm not sure we're fully consistent on this. Just checking. Allin. In my opinion, we should try to translate as much as we can through the xx.po files (through gettext). If I had more free time, I would like to translate the information in the data files (variable names, descriptive labels,... ). ... although it seems not possible in the short term ;-)) _______________________________________________ Gretl-devel mailing list Gretl-devel(a)lists.wfu.edu http://lists.wfu.edu/mailman/listinfo/gretl-devel

Hope this helps.

Hope this helps.

On Thu, 15 Jan 2009, Allin Cottrell wrote: > On Thu, 15 Jan 2009, Alexander B. Gedranovich wrote: >> Also, I've marked some untranslated strings (see .diff attached) > Thanks. I've applied most of the changes. But one sort of change maybe wants some discussion: namely, should we be translating the descriptive labels we write out for new variables created by, for example, the filter functions? As in, "4-period moving average of foo" I'm not sure we're fully consistent on this. Just checking.

Surely, command scripts must be portable. But this case shouldn't break the portability, just all newly created by functions variables will have locale-dependant descriptive labels. I think, it's logical, moreover - it's already working (see "Logs..", "Lags.." etc. commands in "Add" menu).