June 2016 - openSUSE Translation - openSUSE Mailing Lists

[opensuse-translation] [Attention]YaST Software Management GTK broken because gtk.pot is broken!
by Marguerite Su 11 Nov '24

11 Nov '24

Hi, Karl and all other local translators: Please watch bug 801311: https://bugzilla.novell.com/show_bug.cgi?id=801311 (There's also a software bug in it and has been assigned, so I can't assign it to Karl at the same time) Our yast/50-pot/gtk.pot is now only 48 strings, comparing to 321 strings in qt-pkg.pot Some former commit before 12.3 destroyed all strings for the GTK interface. (ViewVC is currently broken, so I can't tell which commit) So we may have to re-do the work for a big update. Just reserve some time in your schedule, or your locale will be broken for the entire 12.3 life cycle! Greetings Marguerite -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

4 5

[opensuse-translation] New console keymaps needs testing in variety of languages
by opensuse.lietuviu.kalba 29 Aug '16

29 Aug '16

Hi, As https://features.opensuse.org/318355 is in progress, openSUSE will use console keymaps, that are convert from X keyboard layouts. Console keymaps are highly dependent on settings in /etc/sysconfig/console. Regular openSUSE releases use complicated rules to define different console fonts. In future, it is suggested to use eurlatgr for countries with Latin and Greek alphabets, LatArCyrHeb (e.g. LatArCyrHeb-14) for other, like Arabic, Cyrilic... So please test console keyboards for your country in openSUSE Tumbleweed, after applying https://github.com/yast/yast-country/pull/61 patch. Please report at http://bugzilla.suse.com/show_bug.cgi?id=942896 -- Regards -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

1 1

Re: [opensuse-translation] SLE translation team in Weblate
by Stanislav Brabec 28 Jun '16

28 Jun '16

Luiz Fernando Ranghetti wrote: > For libzypp and zypper, using pt_BR as an example, contracted > translators and comunity ones uses different terms for translations, And this is something that sounds very wrong. One system, identical software, two different translations. > probably this means that in this phase, they will erase all our comunity > translations and re-apply the SLE Merge Robot which now are just > suggestions to make the zypper translation on next SLE like it always > was in SLE. No. The openSUSE translation was took as a default one. SLE Merge Robot changes were sent only as unapproved suggestions. Anybody from the community still can go through the suggestions, and solve them: https://l10n.opensuse.org/translate/zypper/master/pt_BR/?type=suggestions https://l10n.opensuse.org/translate/libzypp/master/pt_BR/?type=suggestions If it will not be done by community, contracted translators will be paid to make it 100% translated (and with with no pending suggestions). They should not change terminology, only make a linguistic review of the translated part. I believe that they will work carefully and check suggestions one by one. However I am not a native speaker of these languages, so I have to trust that the best available translation will be used. > I saw this as a problem. Why? Right now zypper is 96,3% translated for > pt_BR. Will the contractors start with that or with the last version > they worked? (With that they will complain that the translation doesn't > comply with their standards. No, this time (SLE12 SP2 for these three projects, SLE13 for all projects) they will start on top of the last openSUSE version. > After they do their work and when zypper is available to translate again > we, the comunity translators, will have to revert all the changes > contracted translators made or, at least, review all work done and > update the terms we use different. Next round of translations, same > problems... Translators should use community translations, as the rest of the system uses it as well. If you find a problem, you can make suggestion or comment during the translation process. I hope that the word fight will not appear. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.com Křižíkova 148/34 (Corso IIa) tel: +49 911 7405384547 186 00 Praha 8-Karlín fax: +420 284 084 001 Czech Republic http://www.suse.cz/ PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76 -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

6 11

[opensuse-translation] SLE translation team in Weblate
by Stanislav Brabec 17 Jun '16

17 Jun '16

Dear translators. As you may know, SUSE is now working on SLE12 SP2. As part of this effort, contracted translators and reviewers will work on translation of 16 languages of selected projects. As we plan to completely migrate to Weblate, we selected three projects as a pilot for this migration. These projects also represent two working models: libzypp, zypper: These projects now have only one branch that will be deployed simultaneously on both Factory/Tumbleweed and SLE12 SP2. yast-slide-show: This project has a separate branch for SLE12 SP2 and master (Factory/Tumbleweed). Last month we started phase 1: Merge of SLE translations into openSUSE translations using SLE Merge Robot making suggestions. (Some of them seen hundreds of mails. I apologize for that. Weblate sent one mail per change.) Now phase 2 will start: Contracted translators will start to work on these translations, make them complete and reviewed. As part of this work, these three project will be locked for community translators. Community still could look into the progress and make suggestions and comments. Once SLE12 SP2 will be released, these projects will be open for community translation again. When this work will end, both SLE and openSUSE will use the same translation, and the work of contracted translators will be (automatically) inherited in the Tumbleweed project. Note: In case of yast-slide-show, both branches will be locked. Weblate does not yet support branch disconnection and locking only one branch, so we need to lock both at once. In future, it will be possible to lock only particular branch. The another branch will be open for community, and inherit work from SLE branch. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.com Křižíkova 148/34 (Corso IIa) tel: +49 911 7405384547 186 00 Praha 8-Karlín fax: +420 284 084 001 Czech Republic http://www.suse.cz/ PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76 -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

7 8

[opensuse-translation] Leap 42.2 branch
by Jonas Svensson 06 Jun '16

06 Jun '16

Hi! a short question, to correct translation errors in the upcoming Leap 42.2, is "master" the branch to edit? greetings from Sweden Jonas -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

2 1