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).

Alexander Gedranovich


Sven Schreiber wrote: 
Am 15.01.2009 16:15, Allin Cottrell schrieb:
  
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.
I'm not sure I understand exactly, but in general I think that scripts
should remain portable across language settings. So if translation here
would cause problems because a script assumes the default (English)
behavior for variable names which are then not created because it's run
under a different language setting, I would oppose this change.

cheers,
sven