Mailinglist Archive: opensuse-translation (148 mails)

< Previous Next >
Re: [opensuse-translation] Problem with the verification scripts.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2012-04-26 15:52, Karl Eichwalder wrote:
"Carlos E. R." <> writes:


In this case the error was because the English message had a new end of
line symbol, making the translation fuzzy. Nothing like missing quotes.

Something strange is going on on your side; we are doing this all the
time. I submitted the following change with an invalid, but fuzzy
message:

And it was accepted?


svn diff s390.de.po
Index: s390.de.po
===================================================================
--- s390.de.po (revision 73770)
+++ s390.de.po (working copy)
@@ -28,7 +28,6 @@
"#-#-#-#-# s390.de.po (s390) #-#-#-#-#\n"
"#-#-#-#-# s390.de.po (YaST (@memory@)) #-#-#-#-#\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
-"X-Generator: Lokalize 1.4\n"

#. Command line help text for the Xcontroller module
#: src/clients/dasd.ycp:48
@@ -54,7 +53,7 @@
#: src/clients/dump.ycp:49
#, fuzzy
#| msgid "Configuration of DMA mode for IDE devices"
-msgid "Creation of s390 dump devices"
+msgid "Creation of s390 dump devices\n"
msgstr "DMA-Modus-Konfiguration von IDE-Geräten"

#. Command line help text for the Xcontroller module

msgfmt --check s390.de.po

svn ci -mtesting s390.de.po
Sending s390.de.po
Transmitting file data .
Committed revision 73771.

To save us time, you could have told us the name of your file ;)

Didn't I? :-?

[...]

Yes, I did, in the first post, see:

cer@Telcontar:~/Projects/babel/SuSE/trunk/yast/es/po> svn commit --message
"translated some files, pending verification"
Sending po/bootloader.es.po
Sending po/multipath.es.po
Sending po/s390.es.po
Transmitting file data ...svn: Commit failed (details follow):
svn: Commit blocked by pre-commit hook (exit code 1) with output:
/srv/svn/opensuse-i18n-repos/hooks/verify-po.py:18: DeprecationWarning:
The popen2 module is deprecated. Use the subprocess module.
import popen2
<stdin>:314: `msgid' and `msgstr' entries do not both end with '\n'
<stdin>:333: `msgid' and `msgstr' entries do not both end with '\n'
<stdin>:544: `msgid' and `msgstr' entries do not both end with '\n'
/usr/bin/msgfmt: found 3 fatal errors
PO format check failed for 'trunk/yast/es/po/s390.es.po'

cer@Telcontar:~/Projects/babel/SuSE/trunk/yast/es/po>

The file was s390.es.po


I have done the same test as you, but with an editor, I'm not fluent with
diffs, and it worked. Why did it not work for me that time? I don't understand.


Maybe I'm confused and the messages were not fuzzy - that's the only
explanation remaining.

- --
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/

iEYEARECAAYFAk+ZiOgACgkQIvFNjefEBxqVJgCffp6FRXZ+smb2cwrQLBSdHpmQ
ncUAoLvVcHvo0PokNBqfXyhe1A8FAE9s
=BImZ
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-translation+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups