2008/2/15 Johannes Schmid <[EMAIL PROTECTED]>:

> Hi!
>
> Am Freitag, den 15.02.2008, 13:14 +0100 schrieb Gil Forcada:
> > since it's the beginning of the string freeze and the strings are easy
> > to translate ... (drums)
> >
> > 2/2 !
>
> I have no problem with this change but what I do not understand: We
> allow a string freeze break here for 18 strings but reject to fix one
> (fuzzy) string in nautilus. Isn't that a quiet weak policy?
>
> I know that these strings fix potential translation bugs while the other
> one is just a fix of an original string but with the argument of being
> at the beginning of string freeze this is no real difference!

I also agree that the practics of  approving general, not-so-critical string
freeze breaks is bad very bad. It seems that developers don't think it's a
time for mandatory freeze rather time to begin fixing string problems. And
that's because we approve all their requests to break the rule. Bad too bad.

>
>
> Regards,
> Johannes
>
> >
> > cheers,
> >
> > El dv 15 de 02 del 2008 a les 10:50 +0100, en/na Gabor Kelemen va
> > escriure:
> > > Claude Paroz írta:
> > > > Le jeudi 14 février 2008 à 23:37 +0000, GNOME Status Pages a écrit :
> > > >> This is an automatic notification from status generation scripts
> on:
> > > >>     http://l10n.gnome.org/.
> > > >>
> > > >> There have been following string additions to module '
> gnome-keyring.HEAD':
> > > >>
> > > >>     + "An application wants access to the certificate '%s', but it
> is locked"
> > > >>     + "An application wants access to the private key '%s', but it
> is locked"
> > > >>     + "An application wants access to the public key '%s', but it
> is locked"
> > > >>     + "Automatically unlock this certificate when I log in."
> > > >>     + "Automatically unlock this private key when I log in."
> > > >>     + "Automatically unlock this public key when I log in."
> > > >>     + "Automatically unlock this when I log in"
> > > >>     + "Enter password to unlock the certificate"
> > > >>     + "Enter password to unlock the private key"
> > > >>     + "Enter password to unlock the public key"
> > > >>     + "The system wants to import '%s', but it is locked"
> > > >>     + "The system wants to import the certificate '%s', but it is
> locked"
> > > >>     + "The system wants to import the private key '%s', but it is
> locked"
> > > >>     + "The system wants to import the public key '%s', but it is
> locked"
> > > >>     + "Unlock certificate"
> > > >>     + "Unlock password for '%s'"
> > > >>     + "Unlock private key"
> > > >>     + "Unlock public key"
> > > >
> > > > Hi Stef,
> > > >
> > > > It's nice to have committed my patch :-) ... but we're now in string
> > > > freeze, so it needs to be approved before being committed.
> > > >
> > > > Translators, this patch was to resolve an issue where you had to
> > > > translate a sentence like "Enter password to unlock the %s", where
> %s
> > > > being replaced by either certificate, private key, public key. Of
> > > > course, this was a problem for most languages where the gender of
> the
> > > > nouns was different.
> > > >
> > > > Consider this as a string freeze break request ;-)
> > > >
> > >
> > > Approval 1/2 !
> > >
> > > Regards
> > > Gabor Kelemen
> > > _______________________________________________
> > > gnome-i18n mailing list
> > > gnome-i18n@gnome.org
> > > http://mail.gnome.org/mailman/listinfo/gnome-i18n
>
> _______________________________________________
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-i18n
>
>
_______________________________________________
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

Reply via email to