[opensuse-translation] Strings for webyast are obsolete.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! The strings for webyast are obsolete, they are dated from last May. It is pointless to translate a project with obsolete strings. See: webyast-activedirectory-ui.pot:"POT-Creation-Date: 2011-05-30 16:17+0200\n" webyast-base-ui.pot:"POT-Creation-Date: 2010-05-27 11:01+0200\n" webyast-custom-services-ui.pot:"POT-Creation-Date: 2010-05-26 17:28+0200\n" webyast-firewall-ui.pot:"POT-Creation-Date: 2011-05-30 16:17+0200\n" webyast-kerberos-ui.pot:"POT-Creation-Date: 2011-05-30 16:17+0200\n" webyast-ldap-ui.pot:"POT-Creation-Date: 2011-05-30 16:17+0200\n" webyast-licenses-ui.pot:"POT-Creation-Date: 2011-05-30 16:17+0200\n" webyast-mail-ui.pot:"POT-Creation-Date: 2011-05-30 16:17+0200\n" webyast-mail-ws.pot:"POT-Creation-Date: 2011-03-04 11:25+0100\n" webyast-network-ui.pot:"POT-Creation-Date: 2011-05-30 16:16+0200\n" webyast-reboot-ui.pot:"POT-Creation-Date: 2011-05-30 16:16+0200\n" webyast-registration-ui.pot:"POT-Creation-Date: 2011-05-30 16:16+0200\n" webyast-registration-ws.pot:"POT-Creation-Date: 2010-05-31 12:46+0200\n" webyast-roles-ui.pot:"POT-Creation-Date: 2011-05-30 16:17+0200\n" webyast-root-user-ui.pot:"POT-Creation-Date: 2011-05-30 16:16+0200\n" webyast-samba-server-ui.pot:"POT-Creation-Date: 2010-05-03 16:31+0200\n" webyast-security-ui.pot:"POT-Creation-Date: 2010-04-23 11:01+0200\n" webyast-services-ui.pot:"POT-Creation-Date: 2011-05-30 16:16+0200\n" webyast-software-ui.pot:"POT-Creation-Date: 2011-05-30 16:16+0200\n" webyast-software-ws.pot:"POT-Creation-Date: 2011-03-04 11:25+0100\n" webyast-status-ui.pot:"POT-Creation-Date: 2011-05-30 16:16+0200\n" webyast-status-ws.pot:"POT-Creation-Date: 2011-03-04 11:25+0100\n" webyast-time-ui.pot:"POT-Creation-Date: 2011-05-30 16:16+0200\n" webyast-users-ui.pot:"POT-Creation-Date: 2011-05-30 16:16+0200\n" Do I have to open a Bugzilla for this? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6Hq8AACgkQtTMYHG2NR9Vx8gCfQNbNJpMpeyBVcE77kq6EfUPW h1wAmgKtv2RInZP8pYI8roQrHfDXS+lF =bIqb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2011-10-02 at 02:09 +0200, Carlos E. R. wrote:
Hi!
The strings for webyast are obsolete, they are dated from last May. It is pointless to translate a project with obsolete strings.
Bug 722425 - Webyast .pot files are obsolete - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6M+OMACgkQtTMYHG2NR9U6SgCfYDoZcvsOtCsL7dxtyi2p4SI0 1jQAn2iuu1WuVyEwPo3mI0IpaJQFT5qs =Ndes -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

"Carlos E. R." <carlos.e.r@opensuse.org> writes:
On Sunday, 2011-10-02 at 02:09 +0200, Carlos E. R. wrote:
The strings for webyast are obsolete, they are dated from last May. It is pointless to translate a project with obsolete strings.
Bug 722425 - Webyast .pot files are obsolete
Thanks for the reminder. We now have updated webyast files in the trunk. They are basically the same as in the SLE11 branch. You are strongly encouraged to make use of the existing translations from the branch (if your language exists there):: https://svn.berlios.de/svnroot/repos/opensuse-i18n/branches/SLE11/webyast If the existing translations do not match your expectations resp. if they are different from your style, it would help a lot, if you'd report your findings (either in bugzilla or via mail to me or Shane). In the near future, we want to get rid of the artificial separation (SUSE/Novell vs. community). Webyast is one of these product where we can try this first, esp. because webyast is kind of an add-on product where the same version (trunk) often also works on released distributions such as, say, SLE 11 SP2 or 11.4 or Factory. -- 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

2011/10/13 Karl Eichwalder <ke@suse.de>:
Thanks for the reminder. We now have updated webyast files in the trunk. They are basically the same as in the SLE11 branch. You are strongly encouraged to make use of the existing translations from the branch (if your language exists there)::
https://svn.berlios.de/svnroot/repos/opensuse-i18n/branches/SLE11/webyast
I have just checkout such repo and the first thing I can note is that files have different names, in "our" trunk there are files that are not in the branch and vice versa.
If the existing translations do not match your expectations resp. if they are different from your style, it would help a lot, if you'd report your findings (either in bugzilla or via mail to me or Shane).
Is there a simple way to compare strings that is not manually diff the files that are supposed to be the same? Anyway, I have also merged from updated pot files and nothing is changed, except for a new file (webyast-example-ui) with 5 strings. I find quite difficult to think that after about 5 months no string has been changed. Regards, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

Andrea Turrini <andrea.turrini@gmail.com> writes:
I have just checkout such repo and the first thing I can note is that files have different names, in "our" trunk there are files that are not in the branch and vice versa.
I see. They were renamed last year in May. I'm also a little bit confused about the ui/ws variants (e.g., webyast-mail-ui.pot and webyast-mail-ws.pot); I must check this.
Is there a simple way to compare strings that is not manually diff the files that are supposed to be the same?
I guess, lokalize can help you with this. Or try a simple mgscat, that will put different translations of the same string in one message and mark it as fuzzy: #: app/controllers/eulas_controller.rb:94 #, fuzzy msgid "You cannot reject a license once it has been accepted!" msgstr "" "#-#-#-#-# yast_webclient_eulas.it.po (yast_webclient_eulas) #-#-#-#-#\n" "Impossibile rifiutare una licenza una volta che è stata accettata.\n" "#-#-#-#-# webyast-licenses-ui.it.po (@PACKAGE@) #-#-#-#-#\n" "Non puoi rifiutare una licenza una volta che è stata accettata!" #: app/controllers/eulas_controller.rb:97 #: app/controllers/eulas_controller.rb:93 #, fuzzy msgid "You must accept all licences before using this product!" msgstr "" "#-#-#-#-# yast_webclient_eulas.it.po (yast_webclient_eulas) #-#-#-#-#\n" "Accettare tutte le licenze prima di utilizzare il prodotto.\n" "#-#-#-#-# webyast-licenses-ui.it.po (@PACKAGE@) #-#-#-#-#\n" "Si devono accettare tutte le licenze prima di usare questo prodotto!"
Anyway, I have also merged from updated pot files and nothing is changed, except for a new file (webyast-example-ui) with 5 strings. I find quite difficult to think that after about 5 months no string has been changed.
I think that's the way it is. -- 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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2011-10-13 at 12:33 +0200, Karl Eichwalder wrote:
"Carlos E. R." <> writes:
On Sunday, 2011-10-02 at 02:09 +0200, Carlos E. R. wrote:
The strings for webyast are obsolete, they are dated from last May. It is pointless to translate a project with obsolete strings.
Bug 722425 - Webyast .pot files are obsolete
Thanks for the reminder. We now have updated webyast files in the trunk. They are basically the same as in the SLE11 branch.
Thanks. I have downloaded them and aplied them to the Spanish .po files. There are absolutely no changes in strings since last May. Its very strange. The devs are not "deving"? There is just a new file: webyast-example-ui.pot And two have disapeared: webyast-language-ui.es.po and webyast-permissions-ui.es.po. I have done the appropiate changes in the svn. Gabriel: You have to do the changes to Vertaal, too.
You are strongly encouraged to make use of the existing translations from the branch (if your language exists there)::
https://svn.berlios.de/svnroot/repos/opensuse-i18n/branches/SLE11/webyast
If the existing translations do not match your expectations resp. if they are different from your style, it would help a lot, if you'd report your findings (either in bugzilla or via mail to me or Shane).
Hum! That will take a fair bit of work and time. I have to figure a way of doing it. I will have to download the SLE11 branch, them open both sides on two kbabel instances, then compare one by one... tedious. No, I don't use lokalize. Last time I tried it did not have verifications, besides not knowing how to use it. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6a6NoACgkQtTMYHG2NR9ULLQCcDOYRipAZGl28Tp1oetoouKnT m2QAn1IVEns0DSU6PZvGya3cS4bb2ZE0 =FtSD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

2011/10/16 Carlos E. R. <carlos.e.r@opensuse.org>:
I have downloaded them and aplied them to the Spanish .po files. There are absolutely no changes in strings since last May. Its very strange. The devs are not "deving"?
I had the same doubt, too, but this seems to be the case.
That will take a fair bit of work and time. I have to figure a way of doing it.
As proposed by Karl, I think you can use msgcat (for instance: msgcat -o wy.po webyast/po/*po webyast-sle/po/*po) and then have a look at the generated file wy.po. You'll find something like: #: app/views/activedirectory/index.html.erb:34 #: app/views/kerberos/index.html.erb:37 app/views/ldap/index.html.erb:35 #: app/views/users/new.html.erb:144 app/views/users/index.html.erb:119 #: app/views/users/index.html.erb:98 app/views/users/new.html.erb:108 #, fuzzy msgid "This field is required." msgstr "" "#-#-#-#-# webyast-activedirectory-ui.it.po (@PACKAGE@) #-#-#-#-#\n" "Questo campo è obbligatorio.\n" "#-#-#-#-# webyast-kerberos-ui.it.po (@PACKAGE@) #-#-#-#-#\n" "Questo campo è obbligatorio.\n" "#-#-#-#-# webyast-ldap-ui.it.po (@PACKAGE@) #-#-#-#-#\n" "Questo campo è obbligatorio.\n" "#-#-#-#-# webyast-users-ui.it.po (yast_webclient_users) #-#-#-#-#\n" "Questo campo è obbligatorio.\n" "#-#-#-#-# yast_webclient_users.it.po (yast_webclient_users) #-#-#-#-#\n" "Il campo è obbligatorio." If I have understood correctly, this means that there are different translations for the same msgid (don't care about the \n at the end of the sentences, they are not in the original msgstrs). If I change "Il campo è obbligatorio." to "Questo campo è obbligatorio." in yast_webclient_users.it.po, with the same msgcat command I obtain: #: app/views/activedirectory/index.html.erb:34 #: app/views/kerberos/index.html.erb:37 app/views/ldap/index.html.erb:35 #: app/views/users/new.html.erb:144 app/views/users/index.html.erb:119 #: app/views/users/index.html.erb:98 app/views/users/new.html.erb:108 msgid "This field is required." msgstr "Questo campo è obbligatorio." Now the only problem is to find a fast and automatic way to extract only the collisions (perl, python, bash? I have no idea on how to do this). Regards, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

Hi, There is a package called "translate-toolkit" (http://translate.sourceforge.net/wiki/toolkit/index) which is a set of programs for translators. One of them is poconflicts which extract only the conflicts, which is what you are looking at. I have it packages in my home repo as well as in the M17N repository. Regards, Luiz 2011/10/17 Andrea Turrini <andrea.turrini@gmail.com>:
2011/10/16 Carlos E. R. <carlos.e.r@opensuse.org>:
I have downloaded them and aplied them to the Spanish .po files. There are absolutely no changes in strings since last May. Its very strange. The devs are not "deving"?
I had the same doubt, too, but this seems to be the case.
That will take a fair bit of work and time. I have to figure a way of doing it.
As proposed by Karl, I think you can use msgcat (for instance: msgcat -o wy.po webyast/po/*po webyast-sle/po/*po) and then have a look at the generated file wy.po. You'll find something like:
#: app/views/activedirectory/index.html.erb:34 #: app/views/kerberos/index.html.erb:37 app/views/ldap/index.html.erb:35 #: app/views/users/new.html.erb:144 app/views/users/index.html.erb:119 #: app/views/users/index.html.erb:98 app/views/users/new.html.erb:108 #, fuzzy msgid "This field is required." msgstr "" "#-#-#-#-# webyast-activedirectory-ui.it.po (@PACKAGE@) #-#-#-#-#\n" "Questo campo è obbligatorio.\n" "#-#-#-#-# webyast-kerberos-ui.it.po (@PACKAGE@) #-#-#-#-#\n" "Questo campo è obbligatorio.\n" "#-#-#-#-# webyast-ldap-ui.it.po (@PACKAGE@) #-#-#-#-#\n" "Questo campo è obbligatorio.\n" "#-#-#-#-# webyast-users-ui.it.po (yast_webclient_users) #-#-#-#-#\n" "Questo campo è obbligatorio.\n" "#-#-#-#-# yast_webclient_users.it.po (yast_webclient_users) #-#-#-#-#\n" "Il campo è obbligatorio."
If I have understood correctly, this means that there are different translations for the same msgid (don't care about the \n at the end of the sentences, they are not in the original msgstrs). If I change "Il campo è obbligatorio." to "Questo campo è obbligatorio." in yast_webclient_users.it.po, with the same msgcat command I obtain:
#: app/views/activedirectory/index.html.erb:34 #: app/views/kerberos/index.html.erb:37 app/views/ldap/index.html.erb:35 #: app/views/users/new.html.erb:144 app/views/users/index.html.erb:119 #: app/views/users/index.html.erb:98 app/views/users/new.html.erb:108 msgid "This field is required." msgstr "Questo campo è obbligatorio."
Now the only problem is to find a fast and automatic way to extract only the collisions (perl, python, bash? I have no idea on how to do this).
Regards, Andrea -- 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 2011-10-17 11:39, Luiz Fernando Ranghetti wrote:
Hi,
There is a package called "translate-toolkit" (http://translate.sourceforge.net/wiki/toolkit/index) which is a set of programs for translators. One of them is poconflicts which extract only the conflicts, which is what you are looking at. I have it packages in my home repo as well as in the M17N repository.
Interesting. What is the difference between the M17N/ and the M17N:/ repos? Anyway, there is no "translate-toolkit" there. http://download.opensuse.org/repositories/M17N/openSUSE_11.4/x86_64/ Mmm... it looks complex to me: http://translate.sourceforge.net/wiki/toolkit/poconflicts +++*********************************** poconflicts poconflicts takes a PO file and creates an set of output PO files that contain messages that conflict. During any translation project that involves a large amount of work or a number of translators you will see message conflicts. A conflict is where the same English message has been translated differently (in some languages this may have been intentional). Conflicts occur due to different translation style or a shift in translations as the translators or project mature. poconflicts allows you to quickly identify these problem messages, investigate and correct them. To merge the files back, they have to be restructured into the correct directory structure using porestructure in order to enable merging using pomerge. Usage poconflicts [options] <po> <conflicts> Where: <po> -- is a directory of existing PO files or an individual PO file <conflicts> -- is a directory containing one PO file for each conflict ***********************************++- One file per conflict... it may be hundreds. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk6cDVwACgkQtTMYHG2NR9UDfwCgiYXpRbmyuZEMyQ6MlJfgJtTt H5IAn3TBjI4OhE01eE3MHBlVK09uendg =9XXF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

2011/10/17 Carlos E. R. <carlos.e.r@opensuse.org>:
What is the difference between the M17N/ and the M17N:/ repos? Anyway, there is no "translate-toolkit" there.
http://download.opensuse.org/repositories/M17N/openSUSE_11.4/x86_64/
I have found the package the the "oS:Tools" repo: http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.4/
One file per conflict... it may be hundreds.
Indeed: I applyed poconflicts to all po files (yast, lcn, packages, webyast and webyast-sle for a total of 225 files) and now I have more than 600 conflict files. And I need to check manually one file at a time... If I restrict myself to webyast and webyast-sle only (49 po files), I obtain 159 conflicts... Regards, 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: SHA1 On 2011-10-17 13:32, Andrea Turrini wrote:
2011/10/17 Carlos E. R. <>:
What is the difference between the M17N/ and the M17N:/ repos? Anyway, there is no "translate-toolkit" there.
http://download.opensuse.org/repositories/M17N/openSUSE_11.4/x86_64/
I have found the package the the "oS:Tools" repo: http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.4/
Ahá.
One file per conflict... it may be hundreds.
Indeed: I applyed poconflicts to all po files (yast, lcn, packages, webyast and webyast-sle for a total of 225 files) and now I have more than 600 conflict files. And I need to check manually one file at a time...
If I restrict myself to webyast and webyast-sle only (49 po files), I obtain 159 conflicts...
You could use xterm and mc (midnight commander). Press F4 to edit each file directly, it has an automatic .po mode. Or, if you use kbabel, the complementary utility "catalogmanager" loads the entire directory (you have to define a project first) and allows you to double click on each .po file to edit it with kbabel. Surely lokalize should have the equivalent thing, but I consider it an unfinished product, I don't know much about it. There is an example here: http://translate.sourceforge.net/wiki/toolkit/poconflicts#examples - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk6cKhEACgkQtTMYHG2NR9Vx3gCfbGILgTiNijckkp8Fat4F+0Ut PI4AnjlEzYjqiwhiMqiOBUQX9OKrHytj =wrWG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

2011/10/17 Carlos E. R. <carlos.e.r@opensuse.org>:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-10-17 11:39, Luiz Fernando Ranghetti wrote:
Hi,
There is a package called "translate-toolkit" (http://translate.sourceforge.net/wiki/toolkit/index) which is a set of programs for translators. One of them is poconflicts which extract only the conflicts, which is what you are looking at. I have it packages in my home repo as well as in the M17N repository.
Interesting.
What is the difference between the M17N/ and the M17N:/ repos? Anyway, there is no "translate-toolkit" there.
http://download.opensuse.org/repositories/M17N/openSUSE_11.4/x86_64/
Hi, You won't find it here because it's a noarch package: http://download.opensuse.org/repositories/M17N/openSUSE_11.4/noarch/ The :/ repos are subrepos, generally they use to test something or some changes before submitting to the root repo. And yes, it generate tons of conflicts ;-) I use it from time to time. 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 2011-10-17 11:31, Andrea Turrini wrote:
2011/10/16 Carlos E. R. <>:
That will take a fair bit of work and time. I have to figure a way of doing it.
As proposed by Karl, I think you can use msgcat (for instance: msgcat -o wy.po webyast/po/*po webyast-sle/po/*po) and then have a look at the generated file wy.po. You'll find something like:
Yes, I saw his post, but did not understood how to do it. Your explanation makes it clear, thanks.
Now the only problem is to find a fast and automatic way to extract only the collisions (perl, python, bash? I have no idea on how to do this).
Yes... - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk6cCiQACgkQtTMYHG2NR9X5TwCeKMKb1ZP+Oek039lZgI1NrWFd 480An3oFgTAM6ZiVm5fHmeYk7Fjkn+Fp =ztMH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

2011/10/17 Andrea Turrini <andrea.turrini@gmail.com>:
As proposed by Karl, I think you can use msgcat (for instance: msgcat -o wy.po webyast/po/*po webyast-sle/po/*po) and then have a look at the generated file wy.po. You'll find something like: -----skipped----- Now the only problem is to find a fast and automatic way to extract only the collisions (perl, python, bash? I have no idea on how to do this).
Regards, Andrea I believe that "msgcat *.<LANG_CODE>.po --more-than=1|msgattrib --only-fuzzy -o <SOME_NAME>.po" will be accurate enough in most scenarios. I understand this will not work for identical fuzzy translations, but this case is not so common (this can be avoided by using msggrep instead of msgattrib, filtering messages for #-#-#-#-# collision marker, but I wasn't able to compose a working command in five minutes) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

Alexander Melentyev <minton@opensuse.org> writes:
I believe that "msgcat *.<LANG_CODE>.po --more-than=1|msgattrib --only-fuzzy -o <SOME_NAME>.po" will be accurate enough in most scenarios. I understand this will not work for identical fuzzy translations, but this case is not so common (this can be avoided by using msggrep instead of msgattrib, filtering messages for #-#-#-#-# collision marker, but I wasn't able to compose a working command in five minutes)
This will probably work: msgcat ... | msggrep -T -e '^#-#-#-#-#' It is probably better to remove all fuzzy message from every .po file before you run the msgcat command with: msgattrib --no-fuzzy -- 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
participants (6)
-
Alexander Melentyev
-
Andrea Turrini
-
Carlos E. R.
-
Carlos E. R.
-
Karl Eichwalder
-
Luiz Fernando Ranghetti