pspp-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: new .pot file?


From: Ben Pfaff
Subject: Re: new .pot file?
Date: Sat, 20 May 2017 11:36:09 -0700
User-agent: Mutt/1.5.23 (2014-03-12)

Yes, that works too.

Before I do that, I'd like to get the following problems fixed.  John,
can you take a look?  Thanks.

../src/ui/gui/psppire-dialog-action-k-independent.c:146:56: error: passing 
argument 1 of ‘psppire_dialog_run’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
   if (PSPPIRE_RESPONSE_CONTINUE == psppire_dialog_run (kid->subdialog))
                                                        ^~~
In file included from ../src/ui/gui/psppire-dialog-action.h:36:0,
                 from ../src/ui/gui/psppire-dialog-action-k-independent.h:21,
                 from ../src/ui/gui/psppire-dialog-action-k-independent.c:20:
../src/ui/gui/psppire-dialog.h:74:16: note: expected ‘PsppireDialog * {aka 
struct _PsppireDialog *}’ but argument is of type ‘GtkWidget * {aka struct 
_GtkWidget *}’
 gint           psppire_dialog_run             (PsppireDialog *);
                ^~~~~~~~~~~~~~~~~~
../src/ui/gui/psppire-dialog-action-k-independent.c: In function 
‘set_value_entry_variable’:
../src/ui/gui/psppire-dialog-action-k-independent.c:166:37: error: passing 
argument 1 of ‘psppire_value_entry_set_variable’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
   psppire_value_entry_set_variable (kid->lower_limit_entry, v);
                                     ^~~
In file included from ../src/ui/gui/psppire-dialog-action-k-independent.c:23:0:
../src/ui/gui/psppire-value-entry.h:78:6: note: expected ‘PsppireValueEntry * 
{aka struct _PsppireValueEntry *}’ but argument is of type ‘GtkWidget * {aka 
struct _GtkWidget *}’
 void psppire_value_entry_set_variable (PsppireValueEntry *,
      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/ui/gui/psppire-dialog-action-k-independent.c:167:37: error: passing 
argument 1 of ‘psppire_value_entry_set_variable’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
   psppire_value_entry_set_variable (kid->upper_limit_entry, v);
                                     ^~~
In file included from ../src/ui/gui/psppire-dialog-action-k-independent.c:23:0:
../src/ui/gui/psppire-value-entry.h:78:6: note: expected ‘PsppireValueEntry * 
{aka struct _PsppireValueEntry *}’ but argument is of type ‘GtkWidget * {aka 
struct _GtkWidget *}’
 void psppire_value_entry_set_variable (PsppireValueEntry *,
      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


On Sat, May 20, 2017 at 07:02:14PM +0200, Harry Thijssen wrote:
> Hi
> 
> The translationproject accepts names like  pspp-0.10.4-pre1  This gives the
> translators the time to translate before a release so the translation can
> be included in the release.
> 
> I agree that a new release might be useful as the current version is rather
> old.
> 
> Have fun
> 
> 2017-05-20 18:27 GMT+02:00 Ben Pfaff <address@hidden>:
> 
> > On Sat, May 20, 2017 at 03:54:19PM +0200, John Darrington wrote:
> > > On Sat, May 20, 2017 at 09:59:59AM +0200, Harry Thijssen wrote:
> > >      Hi
> > >
> > >      Currently the actual .pot file in master and the .pot file in the
> > >      translationproject differ significantly. I guess it is not the
> > right time
> > >      to bring out a new pspp version yet, but it might be a good idea to
> > upload
> > >      a newer .pot version to the translationproject so the translators
> > can work
> > >      against the newer .pot file.
> > >
> > >      What do you think?
> > >
> > > I suppose Ben could advise translationproject to take the pot file from
> > one of
> > > his nightly builds:  Eg:
> > >
> > > https://benpfaff.org/~blp/pspp-master/20170519030501/
> > source/pspp-0.10.4-g59adca.tar.gz
> >
> > I can't do it that way, because the translationproject is very picky
> > about the format of version numbers, but we could increment the version
> > to 0.10.5 or 0.10.4.1, etc.  Or we could actually release 0.10.4,
> > especially since it's been a long time since the last release.
> >
> > What do you think?
> >



reply via email to

[Prev in Thread] Current Thread [Next in Thread]