Re: gnome-control-center UI and string freeze break request
Marek Kasik wrote: Bug 698532 - Do not prompt for remote username / password when adding printer https://bugzilla.gnome.org/show_bug.cgi?id=698532 (screenshot - https://bug698532.bugzilla-attachments.gnome.org/attachment.cgi?id=253939) This change improves installing of printers shared on samba servers. It shows authenticated servers in the list of available devices and allows user to authenticate against them. The printers available on such servers are added to the list after authentication. I tried to do it as minimal as possible. This is an UI change and string change. The change was accepted by designers. And I said last week it would be fine if it came early this week, so here's the first release team approval. Fred ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'gnome-clocks.master'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'gnome-clocks.master': + _Help Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. http://git.gnome.org/browse/gnome-clocks/log/?h=master ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Web interface for translation for GNOME
Thank you for this very well explanation Dimitris. But when you said Translators stay away from the VCS. They don't need access to it any more I becamed confused because what happens if a translator needs to send the locale version of an image? (as some language teams do for documentations) or if we need to send our locale version of some audio files (for instance in GCompris)? Thanks a lot, Enrico. Em 04/09/2013 00:34, Dimitris Glezos escreveu: On 2 September 2013 15:50, Axel Hecht l10n@gmail.com wrote: What process do you suggest in between transifex and version control? I can only suggest what was worked with other projects and the rationale behind Tx's decisions. Based on what we've experienced with Django and other projects, the process could be fairly simple using the Transifex Client. I don't know if GNOME is ready for a setup like this, but here is what worked for other projects. ## Tx-git Bridge When a POT file changes, have the build system, git or cron push it to Tx. $ tx push --source Build systems or scripts are the most common. Developers can also do this manually when they want to (could be made part of the common Makefile across GNOME projects. When the software is ready to be packaged, have the build scripts pull the languages from Tx. $ tx pull --all For the pull, there a few options, like a) pull the translations only when the package is ready to be shipped (rel eng), b) commit them in the VCS too, but that's not necessary, c) use a cron job instead of a trigger to commit. ## Assumptions - You're using Tx as the canonical place where translations live. The VCS are for code. If you want to bypass this assumption, you'll need to also periodically push the translated files from the repo to Tx instead of just pulling. - The translators who want to work offline are not really attached to git, but rather the command-line. This is particularly tricky to convince people for. Most translators just want a way to mass-download and upload their files. So, they're OK to use Tx client to get their files and push them back. $ tx set --auto-remote url $ tx pull --lang pt_BR (downloads hundreds of files) $ tx push --lang pt_BR (uploads the ones modified) This, of course, is in addition to the options of using a web interface to DL/UL or actual access to git itself. ## Benefits - Translators have an online tool to work with a number of additional features, such as entity-level review, TM, Glossary etc. - Translators stay away from the VCS. They don't need access to it any more, and translation commits do not show up in the VCS history. - There are no merge conflicts. Tx handles them on an entity level. Source code line changes do not create issues, etc. Hope this helps. -d ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: UI and String Freeze Break Requests: GNOME Music AppData and Notifications
On Wednesday, 04 September, 2013 04:05 AM, Petr Kovar wrote: Piotr Drąg piotrd...@gmail.com, Tue, 3 Sep 2013 17:41:49 +0200: 2013/9/3 Arnel A. Borja kyous...@yahoo.com: We would like to request a UI and String Freeze Break for GNOME Music. The string freeze break is for the addition of translatable description using the new AppData specification, and translatable strings for notifications. The following are the strings to be added: Notifications: - by %s, from %s (by Artist, from Album) - Unknown Album - Not playing - Previous - Pause - Play - Next AppData: - Play and organize your music collection - Music is the new GNOME music playing application. Isn't this a bit too short? I remember Richard asking for a few paragraphs, but that's up to you. It's less work for me as it is, so I won't complain. :) Also, are you sure you want the appdata.xml file in git? Looks like a generated file to me. Anyway, notifications are an important feature and it's early in the freeze, so here is 1/2 approval from i18n. 2/2 for i18n. Cheers, Petr Kovar Thanks! I just committed the updated AppData so that the translators could start working on them. Still waiting for UI Freeze Break for Notifications. Regards, Arnel A. Borja ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Web interface for translation for GNOME
Good question Enrico. For images and other non-i18n files, the intention is to have a special type of file (resource type) in Transifex, Binary. This will either be 0% or 100% translated (no in-between) and the web editor would not open them, just offer download/upload. When the source file is updated (eg. English image), all of the translated versions of it are marked as untranslated. This shouldn't be hard to support if required. Any additional material such as guides, source files etc should be put in a general-purpose VCS. -d On Wed, Sep 4, 2013 at 6:39 AM, Enrico Nicoletto live...@gmail.com wrote: Thank you for this very well explanation Dimitris. But when you said Translators stay away from the VCS. They don't need access to it any more I becamed confused because what happens if a translator needs to send the locale version of an image? (as some language teams do for documentations) or if we need to send our locale version of some audio files (for instance in GCompris)? Thanks a lot, Enrico. Em 04/09/2013 00:34, Dimitris Glezos escreveu: On 2 September 2013 15:50, Axel Hecht l10n@gmail.com wrote: What process do you suggest in between transifex and version control? I can only suggest what was worked with other projects and the rationale behind Tx's decisions. Based on what we've experienced with Django and other projects, the process could be fairly simple using the Transifex Client. I don't know if GNOME is ready for a setup like this, but here is what worked for other projects. ## Tx-git Bridge When a POT file changes, have the build system, git or cron push it to Tx. $ tx push --source Build systems or scripts are the most common. Developers can also do this manually when they want to (could be made part of the common Makefile across GNOME projects. When the software is ready to be packaged, have the build scripts pull the languages from Tx. $ tx pull --all For the pull, there a few options, like a) pull the translations only when the package is ready to be shipped (rel eng), b) commit them in the VCS too, but that's not necessary, c) use a cron job instead of a trigger to commit. ## Assumptions - You're using Tx as the canonical place where translations live. The VCS are for code. If you want to bypass this assumption, you'll need to also periodically push the translated files from the repo to Tx instead of just pulling. - The translators who want to work offline are not really attached to git, but rather the command-line. This is particularly tricky to convince people for. Most translators just want a way to mass-download and upload their files. So, they're OK to use Tx client to get their files and push them back. $ tx set --auto-remote url $ tx pull --lang pt_BR (downloads hundreds of files) $ tx push --lang pt_BR (uploads the ones modified) This, of course, is in addition to the options of using a web interface to DL/UL or actual access to git itself. ## Benefits - Translators have an online tool to work with a number of additional features, such as entity-level review, TM, Glossary etc. - Translators stay away from the VCS. They don't need access to it any more, and translation commits do not show up in the VCS history. - There are no merge conflicts. Tx handles them on an entity level. Source code line changes do not create issues, etc. Hope this helps. -d __**_ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/**mailman/listinfo/gnome-i18nhttps://mail.gnome.org/mailman/listinfo/gnome-i18n -- Dimitris Glezos Founder CEO, Transifex https://www.transifex.com/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Please add in 'Brazilian portuguese' (pt_BR) into Switching Languages button
I observed that the behaviour associated to the 'Switching Languages' button has changed in GNOME webpage, but my locale, Brazilian Portuguese (pt_BR), is not an option available in the list of languages. Actualy only English, Spanish, German and Chinese are available. Brazilian Portuguese have a good number of documentations translated but, please, let us know if we can even improve our translations in order to make it available in this list too. Thank you all, Enrico. ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Please add in 'Brazilian portuguese' (pt_BR) into Switching Languages button
On Wed, 2013-09-04 at 12:42 -0300, Enrico Nicoletto wrote: I observed that the behaviour associated to the 'Switching Languages' button has changed in GNOME webpage, but my locale, Brazilian Portuguese (pt_BR), is not an option available in the list of languages. Actualy only English, Spanish, German and Chinese are available. Brazilian Portuguese have a good number of documentations translated but, please, let us know if we can even improve our translations in order to make it available in this list too. You probably want to talk to the maintainers of www.gnome.org instead (not sure how translators on gnome-i18n@ could help with this). Maybe file a ticket on https://bugzilla.gnome.org/enter_bug.cgi?product=website ? Thanks, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Please add in 'Brazilian portuguese' (pt_BR) into Switching Languages button
Thanks Andre for clarify it. Regards, Enrico. __ Em 04/09/2013 13:27, Andre Klapper escreveu: On Wed, 2013-09-04 at 12:42 -0300, Enrico Nicoletto wrote: I observed that the behaviour associated to the 'Switching Languages' button has changed in GNOME webpage, but my locale, Brazilian Portuguese (pt_BR), is not an option available in the list of languages. Actualy only English, Spanish, German and Chinese are available. Brazilian Portuguese have a good number of documentations translated but, please, let us know if we can even improve our translations in order to make it available in this list too. You probably want to talk to the maintainers of www.gnome.org instead (not sure how translators on gnome-i18n@ could help with this). Maybe file a ticket on https://bugzilla.gnome.org/enter_bug.cgi?product=website ? Thanks, andre ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'gtk+.master'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'gtk+.master': + Cannot create file as the filename is too long Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. http://git.gnome.org/browse/gtk+/log/?h=master ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
