[gimp] Release of GIMP 2.8.20 planned for end of October
Hi Translation Teams, we are planning to do a release of the stable 2.8 branch of GIMP at the end of October. The GIMP 2.8 series does only get bug fixes, no new features, so its strings are pretty much considered frozen all the time - actually, it was quite surprising to find that a few of them had changed recently. We're not really used to formal string freezes yet, but will make an extra effort to keep the strings of the gimp-2-8 branch frozen until 2016-10-27. For most of the previously complete or almost-complete translations, the number of fuzzy or untranslated strings is quite low, and it would be nice to see complete translations for these. Please note that unlike some other applications, GIMP uses multiple po files for various parts of its UI. The GIMP docs are kept in their own git module, gimp-help-2. We are currently working on getting them built again. They follow their own release "schedule", so if you are translating these as well, please don't feel obligated to finish them in time for the 2.8.20 release. Pointers GIMP 2.8 releases are done from the gimp-2-8 branch of the gimp git module: https://git.gnome.org/browse/gimp/tree/?h=gimp-2-8 L10N Module statistics https://l10n.gnome.org/module/gimp/#gimp-2-8 Distribution GIMP 2.8 releases enjoy a large number of users. As GIMP is a cross-platform application, the releases are made available to users on the Microsoft Windows and Apple OS X / macOS platforms via packages we distribute directly from https://www.gimp.org, so any translation updates done for a release will reach a bug audience pretty fast. With Linux distros, it depends on how their release schedules are and /or how they handle package updates. Debian Testing, for example, has recently added the packages for 2.8.18, which we had released earlier this year. -- Regards, Michael GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD signature.asc Description: OpenPGP digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Balsa help files
I did it for the Czech language (cs). Regards Marek Černocký Dne 7.10.2016 19:20, Peter Bloomfield napsal: Dear Translators, Balsa development is now taking place in master, which is essentially the same as the previous gtk3 branch. The old master is now the gtk2 branch, which will be used only for bug-fix releases in the Gtk2 series. In master, doc/Makefile.am has "HELP_LINGUAS = de es fr sl", whereas the gtk2 branch has "DOC_LINGUAS = cs de el es fr sl". Apparently doc/de/de.po and doc/sl/sl.po are the same in both branches; "cs" and "el" must have been added to the old master branch after the gtk3 branch was created. Would it make sense to add "cs" and "el" to HELP_LINGUAS, create corresponding subdirectories, and copy the ??.po files from the gtk2 branch to master? Or should that be left to the corresponding translation teams? Thanks for your thoughts! Peter ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Balsa help files
Dear Translators, Balsa development is now taking place in master, which is essentially the same as the previous gtk3 branch. The old master is now the gtk2 branch, which will be used only for bug-fix releases in the Gtk2 series. In master, doc/Makefile.am has "HELP_LINGUAS = de es fr sl", whereas the gtk2 branch has "DOC_LINGUAS = cs de el es fr sl". Apparently doc/de/de.po and doc/sl/sl.po are the same in both branches; "cs" and "el" must have been added to the old master branch after the gtk3 branch was created. Would it make sense to add "cs" and "el" to HELP_LINGUAS, create corresponding subdirectories, and copy the ??.po files from the gtk2 branch to master? Or should that be left to the corresponding translation teams? Thanks for your thoughts! Peter pgp7r3uJYq_kr.pgp Description: PGP signature ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'evolution-data-server.gnome-3-22'
Hi, On Thu, 2016-10-06 at 20:01 +0200, Piotr Drąg wrote: > + "Failed to construct refresh_token request" > + "Failed to encode new access token to Google secret" > + "Failed to get Google secret from credentials" > + "Failed to get access token from refresh_token server response" > + "Failed to refresh token" > + "Refresh token not found in Google secret" > > Your commit broke the string freeze. Please revert it in the > gnome-3-22 branch and ask for a permission, if you want. ouch, I knew I forgot something. I did know that I'm adding new strings, I even know that I should ask first, but then I completely forgot of it when committing to master and I just blindly committed it to the stable branch as well. I'm sorry for that. I'm CC'ing the relevant parties and doing the right thing now: I'd like to ask for a string freeze break in the gnome-3-22 branch for the evolution-data-server, where I made a change for [bug #771547] "Internal Google OAuth2 authentication fails with expired token". The change is somewhat important, because it fixes broken behaviour in OAuth2 Google tokens handling. I added couple error messages, translated (quoted above), which can show up in a user interface, though only in a very very very rare cases, like when users manually edit or remove the secrets in the seahorse. I didn't want to add strings without being marked for translation (and diverge from git master), thus I'd rather left them untranslated. I know this is pretty late, quite close before the 3.22.1 release, but I hope you'll still understand the importance of the change. Let me apologize once again for my failure in the string freeze break approval procedure, it really wasn't intentional. Bye, Milan [bug #771547] https://bugzilla.gnome.org/show_bug.cgi?id=771547 ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
