Mailinglist Archive: opensuse-translation (148 mails)

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

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

Which brings another point: Errors in fuzzy strings should not render a
file not "commitable". The file was correct in the reviewed strings, it was
incorrect in three fuzzy strings. That's a bug somewhere, IMO.

Which kind of errors do you have in mind? If there are syntax errors
(e.g., missing quote), you are not allowed to submit it even if this
message is marked fuzzy. But other issues such as the wrong number of
format specifiers (%1, %2) or newline mismatches (\n) at the end of the
strings, it is not fatal for fuzzy messages. Does it work this way?

No, it didn't.

Why check the fuzzy messages at all? It doesn't make sense to me.

Notice the sequence:

download the file
change, say, a single letter
uppload the file - rejected.

The downloaded file was incorrect already.

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.

And I didn't notice because I'm using lokalize this time. When I finish a
file, I then review it again in kbabel, but as this one is not finished,
and I had two other finished files, I needed to commit.

As others explained it, either submit your work file by file or first
fix the invalid file and then commit the set. If you are not interested
in the invalid file at all, you can simply revert your change with:

snv revert invalid_file.po

Yes, I understand.

- --
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 "Celadon" at Telcontar)
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with SUSE -

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

< Previous Next >
Follow Ups