[opensuse-translation] New pot files in yast
Hi, everyone! Recently there was a huge merge happening in yast, as you have probably noticed already. However, I still doubt it's validity, cause it's message said "Updated current pot files to the latest SLE12 state". My question to anyone with some knowledge: are these new lines and files coming only for SLE12 development (then why it is here in openSUSE trunk) or they are valid also for openSUSE and will stay, so we need to translate them all? -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Alexander Melentev <minton@opensuse.org> writes:
Recently there was a huge merge happening in yast, as you have probably noticed already. However, I still doubt it's validity, cause it's message said "Updated current pot files to the latest SLE12 state".
Oops, at least the commit message could cause confusion. Thanks for warning!
My question to anyone with some knowledge: are these new lines and files coming only for SLE12 development (then why it is here in openSUSE trunk) or they are valid also for openSUSE and will stay, so we need to translate them all?
I guess, ATM the same yast code base is in use for opensuse factory and SLE 12. But at least we must check that all these files are actually useful in the openSUSE context. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am Montag, 31. März 2014, 15:52:10 schrieb Karl Eichwalder:
I guess, ATM the same yast code base is in use for opensuse factory and SLE 12. But at least we must check that all these files are actually useful in the openSUSE context. Are there any news on this topic?
A translator of our team noticed that this merge by minton introduced russian headers, in example (more text after the header): # Russian translations for opensuse-i package # Английские переводы для пакета opensuse-i. # Copyright (C) 2014 SuSE Linux Products GmbH, Nuernberg # This file is distributed under the same license as the opensuse-i package. # Automatically generated, 2014. # msgid "" msgstr "" "Project-Id-Version: opensuse-i 18n\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2014-03-27 16:00+0100\n" "PO-Revision-Date: 2014-03-24 10:57+0100\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" "Language: ru\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" "%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" A few of this header fields will be overwritten automaticly by most .po- editors, others like the "Plural-Forms" are usualy not overwritten, but have to be adapted for the most non-russian languages. This leads me to the following questions: 1. Is it safe/sufficient to edit the Plural-Forms header field or do I have to involve some special gettext tool? 2. Can/Should we modify the introduction text? ("Russian translations for opensuse-i package" and the same in Cyrillic) 3. What is this opensuse-i package? As it further states that this file is distributed under the same license as the opensuse-i package. Kind Regards, Michael
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-05-18 17:04, Michael Skiba wrote:
Am Montag, 31. März 2014, 15:52:10 schrieb Karl Eichwalder:
I guess, ATM the same yast code base is in use for opensuse factory and SLE 12. But at least we must check that all these files are actually useful in the openSUSE context. Are there any news on this topic?
A translator of our team noticed that this merge by minton introduced russian headers, in example (more text after the header):
Is this a new .po file? If it is an old one, which has been modified by someone outside of your team, revert all the changes. You can simply upload your own local copy, and then merge yourself from the original .pot file - if using vertaal, it is a click. If it is a new file, then adapt all the entries for your own language. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlN51PoACgkQja8UbcUWM1wfjQD/VNKlZsoN8ZQbWG97e0/BJMGS d4egncHI9VKa62uSOWYBAJVnYqwQvQGiNFd7nLqDsBUoXQeMYGzkUEc3KBoYWYWA =EC1F -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
On 2014-05-18 17:04, Michael Skiba wrote:
Am Montag, 31. März 2014, 15:52:10 schrieb Karl Eichwalder:
I guess, ATM the same yast code base is in use for opensuse factory and SLE 12. But at least we must check that all these files are actually useful in the openSUSE context.
Are there any news on this topic?
A translator of our team noticed that this merge by minton introduced russian headers, in example (more text after the
header): Is this a new .po file? If it is an old one, which has been modified by someone outside of your team, revert all the changes. You can simply upload your own local copy, and then merge yourself from the original .pot file - if using vertaal, it is a click.
If it is a new file, then adapt all the entries for your own language. There are a few new files, uploaded/merged from pot by the user "minton", I've no clue if it's a legimate change or not (the content of the files look
Am Montag, 19. Mai 2014, 11:55:06 schrieb Carlos E. R.: plausable). A short notice would be appreciated :-) -- Kind Regards, Michael
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-05-19 23:34, Michael Skiba wrote:
There are a few new files, uploaded/merged from pot by the user "minton", I've no clue if it's a legimate change or not (the content of the files look plausable).
But the .po files should not be initialized with the wrong language. If you can not initialize all .po files, each one with their own language, then do none, and leave that job to each language team, which should know what settings they need (like plurals). I can not look at my language files now, not at my home office.
A short notice would be appreciated :-)
Indeed. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlN6iLQACgkQja8UbcUWM1yNBQD/W2Sb9gs9dkshD5QNkW0l8vFZ Lc9+NbiDd4AV9gn2yoMA/3GygWIpmR265FPM8TUWbmdibinSDU0Q4zQYRVwplsFp =Z4ra -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
On 20/05/14 06:41, Carlos E. R. wrote:
On 2014-05-19 23:34, Michael Skiba wrote:
There are a few new files, uploaded/merged from pot by the user "minton", I've no clue if it's a legimate change or not (the content of the files look plausable).
But the .po files should not be initialized with the wrong language. If you can not initialize all .po files, each one with their own language, then do none, and leave that job to each language team, which should know what settings they need (like plurals).
I can not look at my language files now, not at my home office.
I just checked and the Italian files auth-client.it.po, auth-server.it.po, ldap.it.po, services-manager.it.po, and support.it.po are all affected by the same problem (Russian plurals and opensuse-i project id). And they are all new files. Time to fix them... 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 On 2014-05-20 02:20, Andrea Turrini wrote:
Time to fix them...
Delete them entirely, and recreate them yourself. I don't remember the incantation, but I suppose it will be somewhere in my notes when I get back to my home.office. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlN6pcAACgkQja8UbcUWM1xO6wD/Vf0xeB2EFv8PBzx9Pbybxttp Iflhj83t8VCA/zegkk4A/Rv41sXM4P3Qvo4+GCC0zNTtrKCODlMDioIqMQK6wcuk =HOiD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
OK, that's exactly where good intentions can lead :) I used the same script that helps me with updating russian translations, but I forgot that msginit needs a corresponding --locale option. That is totally my fault and I am deeply sorry for that. Correct headers should be in 50-memory/head-info.<LANG>.po but sadly they also contain some incorrect comments with years and translators, using them right now would also cause some questions, so it was not an option for me. Right plurals expression is written automatically by msginit. I used this invocation: msginit --no-translator --no-wrap -i ?0-pot/$pot.pot -o $lang/po/$pot.$lang.po Without the --locale switch it works with your current locale, so this is the reason you see the russian plurals, sorry once more. I'll modify my merging script accordingly. I can fix current issue for you, it is a two lines patch, but I need some additional input: what locale is matched by your two-letters code. I've tested for Italian with it_IT, but this is not always the case. This should be fixed for all languages, so if you know where I can take a list of such matches it would be just perfect =) -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Op dinsdag 20 mei 2014 10:27:13 schreef Alexander Melentev:
I can fix current issue for you, it is a two lines patch, but I need some additional input: what locale is matched by your two-letters code. I've tested for Italian with it_IT, but this is not always the case.
I have nl_NL.utf8 for locale. No need to do anything for the Dutch language files. -- 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-05-20 08:27, Alexander Melentev wrote:
OK, that's exactly where good intentions can lead :) I used the same script that helps me with updating russian translations, but I forgot that msginit needs a corresponding --locale option. That is totally my fault and I am deeply sorry for that.
Oh, ok. I see how it happened. No big deal, then :-)
Correct headers should be in 50-memory/head-info.<LANG>.po but sadly they also contain some incorrect comments with years and translators, using them right now would also cause some questions, so it was not an option for me.
Ah, that file... I don't download that directory. Maybe we translators should have a go at keeping it updated. Unfortunately, that directory is large, which is why I don't keep it. I can't have a go at it till some days.
I can fix current issue for you, it is a two lines patch, but I need some additional input: what locale is matched by your two-letters code. I've tested for Italian with it_IT, but this is not always the case. This should be fixed for all languages, so if you know where I can take a list of such matches it would be just perfect =)
For Spanish: es_ES.UTF-8 - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlN7JQUACgkQja8UbcUWM1zHDQEAghyClx38E/wAproYnhJzOXt8 vfmdejddRelxafkBv3UA/RUqHdUi76wBbAxbs8LL+v2Q86pKS6ejtaqKGP/k37Va =oMxr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
On 20/05/14 14:27, Alexander Melentev wrote:
I can fix current issue for you, it is a two lines patch, but I need some additional input: what locale is matched by your two-letters code. I've tested for Italian with it_IT, but this is not always the case.
Actually, I do not know: the files are put in /usr/share/YaST2/locale/it/LC_MESSAGES/ and YaST is in Italian if I use as locale "it_IT.UTF-8" or "it_CH.UTF-8" (actually, ".UTF-8" doesn't matter). But if I try "it" only, YaST uses English. However, currently the it.po files contain "Language: it\n" but I do not know if this affects the resulting behavior. 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 On 2014-05-20 12:15, Andrea Turrini wrote:
Actually, I do not know: the files are put in /usr/share/YaST2/locale/it/LC_MESSAGES/ and YaST is in Italian if I use as locale "it_IT.UTF-8" or "it_CH.UTF-8" (actually, ".UTF-8" doesn't matter).
It may, because there are two lines: "Language: es\n" <--- "Content-Type: text/plain; charset=UTF-8\n" <--- "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n"
However, currently the it.po files contain
"Language: it\n"
but I do not know if this affects the resulting behavior.
If there are translation variants, yes. Portuguese can be for Portugal or for Brasil. Spanish can be for Spain or for the many different American countries (and maybe others, I have not checked if one exists for the "Filipinas"). As we don't have people enough to do separate translations, we try to do only a common one. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlN7OVYACgkQja8UbcUWM1winwD7Bd9qwpwbp4UBrdlW5lukuGK9 uSY1nmjYqWuJeAY5besA/jC0VhMYD9OB9KaYeUqKAULgDvauBKEwDYCNbXVW4P9R =a9Uj -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am Dienstag, 20. Mai 2014, 10:27:13 schrieb Alexander Melentev:
I can fix current issue for you, it is a two lines patch, but I need some additional input: what locale is matched by your two-letters code. I've tested for Italian with it_IT, but this is not always the case. 'de_DE' or just 'de' for us :-)
Thanks, Michael
Hopefully, everything is fixed now. Have not touched <nl> and <it> cause it was not needed, but had to manually fix pt_BR and zh_CN, cause automation failed on these two for unknown reason. Anyway, please re-check. Russian comments and plurals should not be in your files anymore. -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
participants (7)
-
Alexander Melentev
-
Andrea Turrini
-
Carlos E. R.
-
Carlos E. R.
-
Freek de Kruijf
-
Karl Eichwalder
-
Michael Skiba