Re: Problem with gnome-terminal 2.24.1
cc'ing gnome-i18n to get feedback on what translators prefer. Note: we need a quick decision (in the next few hours) I put some comments below: Le mercredi 22 octobre 2008, à 11:28 +0200, Christian Persch a écrit : Hi; Le Tue, 21 Oct 2008 22:29:22 -0400, Matthias Clasen [EMAIL PROTECTED] a écrit : Due to an incomplete regression fix from http://bugzilla.gnome.org/show_bug.cgi?id=548600 the gconf schema shipped in gnome-terminal 2.24.1 is invalid. See e.g. https://bugzilla.redhat.com/show_bug.cgi?id=467980 I'm sorry about this. I wanted to be 'clever' and put in the regression fix without having to do an UI and string freeze break, but that evidently backfired :-( I've fixed this in Fedora by pulling in the locale elements from the trunk schema, which brings in a lot of strings. But those strings were present in 2.22, and building the patched package reveals that a lot of the translations are still present in the 2.24.1 po files. I'd like to propose that we do the same thing (pulling in the missing locale elements from trunk) for 2.24.1. The possible translation regressions would only ever be visible in gconf-editor anyway. Alternatively, I could take the generated schemas file from a 2.22 build and put them into an extra schemas file, so there won't be any extra strings to translate. That would get only those translations present in 2.22 the translated strings, but since they're gconf only and rather dull, it shouldn't be too bad. This avoids the string freeze break. Isn't this way a bit risky? I can do a 2.24.1.1 release asap if you tell me which one you prefer. I'll wait for the tarball for the GNOME release. Vincent -- Les gens heureux ne sont pas pressés. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Problem with gnome-terminal 2.24.1
2008/10/22 Vincent Untz [EMAIL PROTECTED]: cc'ing gnome-i18n to get feedback on what translators prefer. Note: we need a quick decision (in the next few hours) I put some comments below: Le mercredi 22 octobre 2008, à 11:28 +0200, Christian Persch a écrit : Hi; Le Tue, 21 Oct 2008 22:29:22 -0400, Matthias Clasen [EMAIL PROTECTED] a écrit : Due to an incomplete regression fix from http://bugzilla.gnome.org/show_bug.cgi?id=548600 the gconf schema shipped in gnome-terminal 2.24.1 is invalid. See e.g. https://bugzilla.redhat.com/show_bug.cgi?id=467980 I'm sorry about this. I wanted to be 'clever' and put in the regression fix without having to do an UI and string freeze break, but that evidently backfired :-( I've fixed this in Fedora by pulling in the locale elements from the trunk schema, which brings in a lot of strings. But those strings were present in 2.22, and building the patched package reveals that a lot of the translations are still present in the 2.24.1 po files. I'd like to propose that we do the same thing (pulling in the missing locale elements from trunk) for 2.24.1. The possible translation regressions would only ever be visible in gconf-editor anyway. Alternatively, I could take the generated schemas file from a 2.22 build and put them into an extra schemas file, so there won't be any extra strings to translate. That would get only those translations present in 2.22 the translated strings, but since they're gconf only and rather dull, it shouldn't be too bad. This avoids the string freeze break. Isn't this way a bit risky? I can do a 2.24.1.1 release asap if you tell me which one you prefer. I'll wait for the tarball for the GNOME release. Vincent I don't fully understand the different solutions here, but don't waste time explaining that to me, probably somebody else will understand. Could I just know, how many strings are we talking about, worst case scenario i.e. for the teams that don't have any previous translations? Regards Kenneth Nielsen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Problem with gnome-terminal 2.24.1
Hi; I don't fully understand the different solutions here, but don't waste time explaining that to me, probably somebody else will understand. Could I just know, how many strings are we talking about, worst case scenario i.e. for the teams that don't have any previous translations? If we pull in just the schemas it's 2 strings; if we take the UI it's another string, for a total of 3. Times 12, with each string just varying by the number in it, 1 to 12. Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Problem with gnome-terminal 2.24.1
Le mercredi 22 octobre 2008 à 13:32 +0200, Kenneth Nielsen a écrit : Hi; I don't fully understand the different solutions here, but don't waste time explaining that to me, probably somebody else will understand. Could I just know, how many strings are we talking about, worst case scenario i.e. for the teams that don't have any previous translations? If we pull in just the schemas it's 2 strings; if we take the UI it's another string, for a total of 3. Times 12, with each string just varying by the number in it, 1 to 12. Christian Well I can't evaluate the importance of the fix, I will leave that to someone else. But if it is considered important enough (probably is with the regression being in the title and all ;) ), and it is no more than at most 3 strings, (and 33 more with copy and paste) then my opinion would be that you should do it whatever is the right way, risky fixes is not worth it for 3 strings. But I'm not in any of the important teams, so this is not a formal approval, just a translator opinion. I would share the opinion of Kenneth, if we were not some hours before the release. IMHO, you should retract the patch (rev. 3181) in gnome-2-24 and add it back for GNOME 2.24.2. That would give time for translators to get back the strings from 2.22 po files. Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Problem with gnome-terminal 2.24.1
Hi; I don't fully understand the different solutions here, but don't waste time explaining that to me, probably somebody else will understand. Could I just know, how many strings are we talking about, worst case scenario i.e. for the teams that don't have any previous translations? If we pull in just the schemas it's 2 strings; if we take the UI it's another string, for a total of 3. Times 12, with each string just varying by the number in it, 1 to 12. Christian Well I can't evaluate the importance of the fix, I will leave that to someone else. But if it is considered important enough (probably is with the regression being in the title and all ;) ), and it is no more than at most 3 strings, (and 33 more with copy and paste) then my opinion would be that you should do it whatever is the right way, risky fixes is not worth it for 3 strings. But I'm not in any of the important teams, so this is not a formal approval, just a translator opinion. Regards Kenneth Nielsen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
