-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2015-09-21 a las 09:19 +0800, Andrea Turrini escribió:

Well, you can translate the Factory trunk, if you desire, hoping that it is used for some part of Leap.

Only if they pull the package after the translation is pushed into factory devel's tree.

To me, it is rather unclear from where the packages are taken (some from SLE almost surely, some from Factory? or from TW?) and it is completely unclear from where the translations are taken.

So far, nowhere. It would have to be taken from whatever repository holds the Leap sources (Leap:42?). Where they take them from, it does not really matter to us :-) That is; a developer copies (branches or whatever is the OBS parlance) a package source tree from somwhere. That tree will contain .c files, or some other language, but also the translation tree for that program, in some directories. He, or someone, has to give those directories (pot and po) to us. And better if it is some automated process, integrated with OBS. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlX/XckACgkQja8UbcUWM1zTIgD+K6sfDKDq4pXbVQjnRN6ak8Fo S/HpKfyTiSuhiGFXFZwA/3ijM+G+8UGBILYE5E3zqUDrJ/yje7lP4AsdXUQaNU+L =vki5 -----END PGP SIGNATURE-----

Op donderdag 1 oktober 2015 12:40:29 schreef Karl Eichwalder:

Andrea Turrini writes:

...

On 21/09/15 03:40, Javier Llorente wrote:

...

According to [1], we have till the 30th of October to translate it, and well, I would like to start translating it :)

Well, you can translate the Factory trunk, if you desire, hoping that it is used for some part of Leap.

Yes, that's the plan currently. For yast, I'll add the "missing" translations from factory ("trunk") to the SLE yast2-trans bundle. Then Leap can inherit it from SLE 12 SP1 and all languages are covered in openSUSE Leap.

I would be great, if community translators of the official SLE languages (en_US, ar, cs, de, es, fr, hu, it, ja, ko, nl, pl, pt_BR, ru, sv, zh_CN, and zh_TW) would compare current factory translations with the variants in the SLE12-SP1 branch and report issues via bugzilla. Please, do not change translations in the SLE12-SP1 branch directly.

'lcn' translations we will probably handly in a similar manner.

Soon after the SLE12-SP1 SVN repository became available I have been translating yast and lcn po files in that repository. I have a common Translation Memory in lokalize for all openSUSE versions, so I believe there are not much differences between the po files for yast and lcn for the different versions of openSUSE. Most of the different versions are at 100% translated, except SLE12-SP1 which currently has only 175 untranslated messages. Should I really stop doing that? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

On 01/10/15 18:40, Karl Eichwalder wrote:

I would be great, if community translators of the official SLE languages (en_US, ar, cs, de, es, fr, hu, it, ja, ko, nl, pl, pt_BR, ru, sv, zh_CN, and zh_TW) would compare current factory translations with the variants in the SLE12-SP1 branch and report issues via bugzilla.

So you are saying that we should compare slightly less than 17k strings to find differences, aren't you? Sorry, but I think this is not feasible, also because it is enough to have a different wrapping of the strings to break the use of diff.

Please, do not change translations in the SLE12-SP1 branch directly.

'lcn' translations we will probably handly in a similar manner.

And here other 17k strings to compare? BTW, there are 4 strings that can not be translated in the just updated lcn/update-desktop-files-kde-services.pot since they are not in English (they refer to QNapi). Best, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2015-10-01 a las 18:02 +0200, Karl Eichwalder escribió:

Andrea Turrini <> writes:

...

So you are saying that we should compare slightly less than 17k strings to find differences, aren't you?

Why not? But with tools' support, of course ;) (for example, with msgcat.) If there are too many difference we should find the reason for this. I'll try to send more details next week.

Many translators (in my group, for instance) use vertaal, without access to the SVN. I don't see how this can work out. We really need a separate Leap branch. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlYNeE4ACgkQja8UbcUWM1ycjAEAoRGPEA2YxIh0XsP3Igvs3JoM 1Ld5LH9pxlDyrhAGi4EA/1qGQ4Ucij6WbSrgnbqYo+ryyVgWTgxniES6KpBhpgR7 =eVRG -----END PGP SIGNATURE-----

Den 01. okt. 2015 12:40, Karl Eichwalder skreiv:

...

...

Well, you can translate the Factory trunk, if you desire, hoping that it is used for some part of Leap. Yes, that's the plan currently. For yast, I'll add the "missing" translations from factory ("trunk") to the SLE yast2-trans bundle. Then Leap can inherit it from SLE 12 SP1 and all languages are covered in openSUSE Leap.

But won’t the application versions in factory/trunk be different from the ones for SLE 12 SP? And in particular, some strings will be different. Isn’t that the whole point of SLE12/Leap vs. factory/trunk/Tumbleweed, that SLE12/Leap contains *stable* versions of applications?

I would be great, if community translators of the official SLE languages (en_US, ar, cs, de, es, fr, hu, it, ja, ko, nl, pl, pt_BR, ru, sv, zh_CN, and zh_TW) would compare current factory translations with the variants in the SLE12-SP1 branch and report issues via bugzilla. Please, do not change translations in the SLE12-SP1 branch directly.

How about translations of *non-offical* SLE languages? Can/should these be submitted to the SLE12-SP1 branch https://svn.opensuse.org/svn/opensuse-i18n/branches/SLE12-SP1/? -- Karl Ove Hufthammer -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

Den 01. okt. 2015 19:39, Karl Eichwalder wrote:

This has to be decided case by case. Yast, zypper, snapper and probably some more will be identical. At least, for the moment. Maybe, we will need a Leap branch in the future.

If some tools are taken from trunk and some from SLE12-SP1 (and in the future other SPs), wouldn’t it be simplest if the translations were taken from the same (i.e. corresponding) branches? Then there would be stable (SLE12-SP1) and development versions of translations as well as of the tools, and everything would be in sync? So whenever Leap would change from using a SLE12-SP1 version to a trunk version of a tool, the source of the translation would change along with it.

coolo is working on the desktop files to get it right.

Are you talking about the problem that the KDE .desktop files were being stripped of translations (and the translations stored in the .po files weren’t being used)? If so, that good! -- Karl Ove Hufthammer -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org