Op dinsdag 20 januari 2015 13:41:29 schreef Guillaume Gardet:

Done for french.

Guillaume

Same for Dutch.

Le 20/01/2015 12:37, Ancor Gonzalez Sosa a écrit :

...

It has been decided to update the project's landing page including a call for collaboration for oSC'15.

I have just updated opensuse-org.pot in the svn. It would be nice if we can get some translations before publishing the changes.

Thanks in advance.

-- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

Lithuanian also

Done for catalan.

El dt 20 de 01 de 2015 a les 17:26 +0100, en/na Freek de Kruijf va escriure:

...

Op dinsdag 20 januari 2015 13:41:29 schreef Guillaume Gardet:

...

Done for french.

Guillaume

Same for Dutch.

...

Le 20/01/2015 12:37, Ancor Gonzalez Sosa a écrit :

...

It has been decided to update the project's landing page including a call for collaboration for oSC'15.

I have just updated opensuse-org.pot in the svn. It would be nice if

we

...

...

can get some translations before publishing the changes.

Thanks in advance.

-- fr.gr.

Freek de Kruijf

-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

-- 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: SHA1 On 2015-01-21 13:51, Guillaume Gardet wrote:

Hi,

Le 21/01/2015 08:35, David a écrit :

...

Hello, What has happened with vertaal.tk? Will it be back online soon?

I don't know the message shown seems to indicate it won't be back soon. :(

Maybe someone have more information? Gabriel? Luiz?

He said in the Spanish translation mail list that the supplier (hosting service?) can't keep it up, too many service failures, and there is no short term solution :-( - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlS/ovMACgkQtTMYHG2NR9VFLgCeIgH3RujwWiBRXSEQyX4PdFsB VxUAnRnLeTzisLog86DktVP6W7NhBIYQ =thpm -----END PGP SIGNATURE----- -- 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: SHA1 On 2015-01-21 15:30, Guillaume Gardet wrote:

Le 21/01/2015 14:00, Carlos E. R. a écrit :

...

On 2015-01-21 13:51, Guillaume Gardet wrote:

...

...

Maybe someone have more information? Gabriel? Luiz? He said in the Spanish translation mail list that the supplier (hosting service?) can't keep it up, too many service failures, and there is no short term solution :-(

Maybe we could transfer Vertaal to an openSUSE server? What would be the requirement?

I don't know... - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlS//T8ACgkQtTMYHG2NR9VDyACbBSj9FGaQtrCt6pW2Mu2P0Uyv fQ4AnRV3xTP2a1ISC2sHXlSEhrGygvZh =Eizd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

On 01/21/2015 11:46 PM, Gabriel wrote:

El 21 de enero de 2015 4:26:04 PM "Carlos E. R." escribio:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2015-01-21 15:30, Guillaume Gardet wrote:

...

Le 21/01/2015 14:00, Carlos E. R. a écrit :

...

On 2015-01-21 13:51, Guillaume Gardet wrote:

...

...

...

Maybe someone have more information? Gabriel? Luiz? He said in the Spanish translation mail list that the supplier (hosting service?) can't keep it up, too many service failures, and there is no short term solution :-(

Maybe we could transfer Vertaal to an openSUSE server? What would be the requirement?

I don't know...

Requirements are Python 2.6+, MySQL, wsgi server (pref apache), mail server, and disk space to hold the repository cache

Maybe is enough to open a ticket for the sysadmins team by sending a mail to admin@opensuse.org. But maybe it's better to open the discussion first at opensuse-project, specially since there was already some discussion about tools for coordinating translations in the past. http://lists.opensuse.org/opensuse-translation/2013-04/msg00009.html Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

Le 22/01/2015 14:24, Carlos E. R. a écrit :

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2015-01-22 12:23, Ancor Gonzalez Sosa wrote:

...

Maybe is enough to open a ticket for the sysadmins team by sending a mail to admin@opensuse.org. But maybe it's better to open the discussion first at opensuse-project, specially since there was already some discussion about tools for coordinating translations in the past. But they (admin) are very slow. I opened a ticked, on another issue, by the end of November, after being told to do so on the project list, and I only got an automated response. No activity, no comments. On other occasion I reported a server down, and got a response a week or two later, after the server had been brought up. The person that responded complained that he learned about the server failure by chance, not because of my report.

Maybe Karl could help us here to accelerate things? Guillaume -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

Hello, I just wanted to let you know I uploaded Vertaal to openshift. You can access using http://vertaal.tk, if you want/need ssl, use the following url instead https://vertaal-sgtdev.rhcloud.com, as ssl for custom domains is not supported. Be aware that, if you use openid, and use the rhcloud.com domain, you will be requested to associate your account again. This won't work with google, as they removed openid support, it's only available for already registered domains, vertaal.tk (non ssl) will still work, at least, until the migration period ends, in april. I recommend you to set a Vertaal password if you use google to sign in. If you don't remember/don't have a password, try the forgot password function. Please, let me know if you find any issue, or better, open a tkt https://github.com/dahool/vertaal/issues Regards. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

On 01/24/2015 05:19 AM, Andrea Turrini wrote:

2015-01-23 22:41 GMT+08:00 Ancor Gonzalez Sosa :

...

I hope we will have translations for the missing languages (cs, el, it, pt_BR, zh_CN and zh_TW) soon. If you contribute one of those (or any other I'm overlooking), please ping me so I don't forget to deploy the translation in the server.

it done.

Indeed, Italian was already included in the original deploy, so it's available since Friday. I overlooked it when counting the present translations. Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

pt_BR done! You could update all the .po files not leave this job to the translators :) 2015-01-26 14:13 GMT-02:00 Ramax Lo :

zh_TW done.

2015-01-23 22:41 GMT+08:00 Ancor Gonzalez Sosa :

...

On 01/20/2015 12:37 PM, Ancor Gonzalez Sosa wrote:

...

It has been decided to update the project's landing page including a call for collaboration for oSC'15.

I have just updated opensuse-org.pot in the svn. It would be nice if we can get some translations before publishing the changes.

I deployed the change today with the contributed translations for ca, de, es, fr, ja, nl, ru, and uk. Thanks all.

A page reload could be needed to see the changes.

I hope we will have translations for the missing languages (cs, el, it, pt_BR, zh_CN and zh_TW) soon. If you contribute one of those (or any other I'm overlooking), please ping me so I don't forget to deploy the translation in the server.

Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

Hi, I have near zero developer skills but you can ask keichwa how we does it - how he update all po files when a new pot arrive at SVN, but I guess is this script: https://svn.opensuse.org/viewvc/opensuse-i18n/trunk/lcn/50-tools/lcn-merge.sh?view=markup&revision=78152 Or we could use something similar to Scripty in KDE (at least in the automatic update .po files part). Because right now, for people using Tumbleweed, some things aren't translated, eg. zypper - although pt_BR are 100% translated on trunk, in TW zypper are a mix of pt_BR and English, probably because in SVN we have a outdated .pot. Maybe we should automatize this process a little bit (of creating .pot files and putting them on trunk) Regards, Luiz 2015-01-28 4:18 GMT-02:00 Ancor Gonzalez Sosa :

On 01/27/2015 11:36 AM, Luiz Fernando Ranghetti wrote:

...

pt_BR done!

Deployed the pt_BR and zw_TW translations. Thanks.

...

You could update all the .po files not leave this job to the translators :)

Feel free to improve the make_* scripts at [1] ;)

Cheers.

[1] https://github.com/openSUSE/landing-page

...

2015-01-26 14:13 GMT-02:00 Ramax Lo :

...

zh_TW done.

2015-01-23 22:41 GMT+08:00 Ancor Gonzalez Sosa :

...

On 01/20/2015 12:37 PM, Ancor Gonzalez Sosa wrote:

...

It has been decided to update the project's landing page including a call for collaboration for oSC'15.

I have just updated opensuse-org.pot in the svn. It would be nice if we can get some translations before publishing the changes.

I deployed the change today with the contributed translations for ca, de, es, fr, ja, nl, ru, and uk. Thanks all.

A page reload could be needed to see the changes.

I hope we will have translations for the missing languages (cs, el, it, pt_BR, zh_CN and zh_TW) soon. If you contribute one of those (or any other I'm overlooking), please ping me so I don't forget to deploy the translation in the server.

Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

-- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

2015-01-28 9:28 GMT-02:00 Carlos E. R. :

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2015-01-28 12:10, Luiz Fernando Ranghetti wrote:

...

Hi,

I have near zero developer skills but you can ask keichwa how we does it - how he update all po files when a new pot arrive at SVN, but I guess is this script:

https://svn.opensuse.org/viewvc/opensuse-i18n/trunk/lcn/50-tools/lcn-merge.sh?view=markup&revision=78152

Or we could use something similar to Scripty in KDE (at least in the automatic update .po files part). Because right now, for people using Tumbleweed, some things aren't translated, eg. zypper - although pt_BR are 100% translated on trunk, in TW zypper are a mix of pt_BR and English, probably because in SVN we have a outdated .pot. Maybe we should automatize this process a little bit (of creating .pot files and putting them on trunk)

Creating/updating the "pot" file is up to the developers of each package; it typically is one "make" target.

Creating/updating the "po" file, however, is up to the translators, and has to be done at a moment when the translator of that language is not working on that file, or he will commit his version destroying the merge. So an automated merge is not desirable.

An script can exist, but you have to call it at the appropriate moment for you. Vertaal has that feature, but vertaal is not working now.

An automated "po" update on every "pot" update is possible, but you have to be aware of the collision danger. The hope is that collisions are minimal.

Thats why I suggest the KDE scripty. In theirs case this script do the magic (it runs everyday), If you commit an outdated version on .po, it will do the merge - in fact it read the codes, creates the .pot, update .po And before vertaal I don't remember having to update my .po files by hand, I remember keichwa doing these for all languages. We can see this looking who is the last commiter on many files: https://svn.opensuse.org/viewvc/opensuse-i18n/trunk/yast/pt_BR/po/ Regards, Luiz -- 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: SHA1 On 2015-01-28 13:13, Karl Eichwalder wrote:

I think these scripts still work, but often they are overkill these days.

I use my own script, simple, with ideas taken from those scripts. Mine is not generic. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlTI3CwACgkQtTMYHG2NR9U/MwCgkUCee83mmxunMcT+eEj5N6/T 3+EAn2cDmc2dUUpvYVNfEmSHw8xWphpI =qCVA -----END PGP SIGNATURE----- -- 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: SHA1 On 2015-01-28 13:01, Luiz Fernando Ranghetti wrote:

2015-01-28 9:28 GMT-02:00 Carlos E. R. <>:

...

An automated "po" update on every "pot" update is possible, but you have to be aware of the collision danger. The hope is that collisions are minimal.

Thats why I suggest the KDE scripty. In theirs case this script do the magic (it runs everyday), If you commit an outdated version on .po, it will do the merge - in fact it read the codes, creates the .pot, update .po

I like the idea. That way we could automatically merge all pots, translators would see working pending, and collisions would be handled automatically. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlTI3OoACgkQtTMYHG2NR9X1MgCfYEh4mHYm5OqdRJyJ6YpBEEi6 ThQAnilTf7pymt1iW5xy8nCfiIwLtv/D =72gP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

2015-01-28 10:16 GMT-02:00 Michael Skiba :

Am Mittwoch, 28. Januar 2015, 07:18:00 schrieb Ancor Gonzalez Sosa:

...

On 01/27/2015 11:36 AM, Luiz Fernando Ranghetti wrote:

...

You could update all the .po files not leave this job to the translators :)

Feel free to improve the make_* scripts at [1] ;) Cheers. [1] https://github.com/openSUSE/landing-page

I think I can extend the script to update the .po files automaticly. However I know this is a very sensetive issue for many translators. So I wanted to discuss this particular case first.

First of all, it is important to state that this script affects only the opensuse-org.po, NOTHING else.

In my opinion it makes sense to automate this process, because the existing script that converts the openSUSE landing page into a pot file is only run, when there are significant changes to the landing page (i.e. not that often). But in the rare cases, when it is done, it makes sense to update all the affected po files as well.

Because the aggregation of the updated po files happens in a manual process, one has to specificly ask for/trigger. Therefore the risk of a file conflict is very low, since translators usually update the small changes as quickly as possible and notify the landing page coordinator to get them back on the page.

So unless someone strongly disagrees I'd try my luck and send in a patch via github.

-- Kind Regards, Michael

Hi, Maybe we can create some ideas for GSOC to automate the creation of yast pot files and others... -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

2015-02-20 9:59 GMT+01:00 Ancor Gonzalez Sosa :

On 02/14/2015 02:32 PM, Ferdinand Galko wrote:

...

Slovak language finished.

But I noticed that Slovak is not between supported languages.

I had removed it because it was heavily outdated (no announcement of the 13.2 release, for example).

...

Can you please add it there?

It's back now.

I also uploaded/updated the translations for cs, da, de and zh.

Cheers.

Thanks for Slovak. Ferdinand -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org