2008-11-24 klockan 13:25 skrev Claude Paroz: > Le lundi 24 novembre 2008 à 07:13 -0500, A. Walton a écrit : > > 2008/11/24 Wouter Bolsterlee <[EMAIL PROTECTED]>: > > > 2008-11-24 klockan 09:41 skrev [EMAIL PROTECTED]: > > >> URL: http://svn.gnome.org/viewvc/gvfs?rev=2101&view=rev > > >> > > >> 2008-11-18 Alexander Larsson <[EMAIL PROTECTED]> > > >> > > >> * daemon/gvfsbackendsftp.c: > > >> If user is specified, add to name too, so we get a unique fuse path > > >> This is a backport from trunk with the translation marking removed. > > >> > > >> [snip] > > >> +++ branches/gnome-2-24/daemon/gvfsbackendsftp.c Mon Nov 24 > > >> 08:41:45 2008 > > >> + display_name = g_strdup_printf ("sftp for %s on %s", > > >> op_backend->user, op_backend->host); > > >> [snip] > > > > > > Alex, > > > > > > I don't think this is a good idea. This means that this clearly user > > > visible > > > string cannot be translated. Please add back the translations markers. > > > Furthermore, a short explanation to gnome-i18n@gnome.org why this fix is > > > critical for the stable branch would be appreciated. > > > > > > Thanks! > > > > Read the thread starting here: > > http://mail.gnome.org/archives/gtk-devel-list/2008-November/msg00013.html > > How can a member of the release team take such a position: > http://mail.gnome.org/archives/gtk-devel-list/2008-November/msg00028.html > > Sorry, but I cannot understand this behaviour. This is not acceptable > IMHO. At least, this should be discussed on relevant lists.
Well, to be honest I kind of agree with Matthias' reasoning. If the release
team decides this bug fix is critical, i.e. deemed important enough to fix
it in a stable branch by adding a string, I think that should take
precedence over the i18n coordination team's opinion.
However, I do *not* agree with the way this is handled. Adding strings to
string-frozen branches, without prior notice, i.e. without any
announcement/explanation to gnome-i18n, is simply not acceptable. Nor is
adding the string without translation markers an acceptable way to "work
around the string freeze issue".
That said... I'm not here to flame. I'm quite sure that noone was willfully
ignoring our well-established strings freeze handling process. I've had i18n
related discussions with Alex in the past, and he has always been friendly
and cooperative.
So, let's not blame people, but instead address this issue in a sensible
way. What is the way forward? I propose that we:
- have someone from r-t announce/explain this string addition to
[EMAIL PROTECTED] A "sorry for the miscommunication" would be nice.
- add back the translation markers in the stable branch, instead of
forcing a *very visible* (it appears in the Locations panel menu!)
untranslatable strings upon users.
- make sure translators have some time (2 weeks, I'd say) to update their
translations and make a new release.
How about that?
— Wouter
--
:wq mail [EMAIL PROTECTED]
web http://uwstopia.nl
looking back in a mirror · it all becomes clear — zero 7
signature.asc
Description: Digital signature
_______________________________________________ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
