-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2011-10-31 at 00:21 -0200, Luiz Fernando Ranghetti wrote:

This messages are created with msgmerge using option --merge:

`--previous' Keep the previous msgids of translated messages, marked with `#|', when adding the fuzzy marker to such messages.

They are used in Lokalize to show us what exactly changes when a string is changed (in this screenshot you can see it: http://forums.wesnoth.org/download/file.php?id=21030&mode=view - the blue is the text added and the red is the text which is gone)

Ah. I assume that Lokalize then clears the comments when finished. Nice feature, but I still don't use Lokalize - no syntax checking, last time I tried. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6uoFIACgkQtTMYHG2NR9XQ5ACbBTQBOofOITEDiyAg/n7Klq0V /ycAnjz7G1bitLjfamywGWuFb/aPO4qX =nzEm -----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 Monday, 2011-10-31 at 17:34 +0400, Alexander Melentyev wrote:

Carlos, deleting those "comments" makes no sense as they are generated automatically. If you hate'em so much, just run the msgmerge without "--previous" flag

The merge was run already, and not by me.

ot use the above-mentioned grep trick (pointless anyway, these "comments" WILL appear again sometimes). Lokalize just visualizes the differences, it does not delete these lines (obviously, cause they are useful).

They are usefull while translating, but not after. When a string is no longer fuzzy, I do not need to see the old msgid. Thus, after I finish translating a file, I need remove manually those comments.

P.S. Syntax checking is performed by svn-hook scripts on every commit.

Which is a nuisance, having to reopen the files and search. On kbabel I just click on verify, then click on next error to see all of them. Much easier. Even if I could use lokalize, it segfaults. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6ups0ACgkQtTMYHG2NR9W/VACfdNvAJdL5oXCGUQpn6NVguIOf aUoAn2gkDtVhRkAYptaDeBy2upfuogVV =V7nt -----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/31 Elisio Catana :

According the portuguese translation how can I check how is the current status.

Best regards.

I use Vertaal http://www.vertaal.com.ar/releases/factory/ Hope it helps.

On 31 October 2011 14:46, Carlos E. R. wrote:

...

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

On Monday, 2011-10-31 at 17:34 +0400, Alexander Melentyev wrote:

...

Carlos, deleting those "comments" makes no sense as they are generated automatically. If you hate'em so much, just run the msgmerge without "--previous" flag

The merge was run already, and not by me.

...

ot use the above-mentioned grep trick (pointless anyway, these "comments" WILL appear again sometimes). Lokalize just visualizes the differences, it does not delete these lines (obviously, cause they are useful).

They are usefull while translating, but not after. When a string is no longer fuzzy, I do not need to see the old msgid. Thus, after I finish translating a file, I need remove manually those comments.

...

P.S. Syntax checking is performed by svn-hook scripts on every commit.

Which is a nuisance, having to reopen the files and search. On kbabel I just click on verify, then click on next error to see all of them. Much easier.

Even if I could use lokalize, it segfaults.

- -- Cheers,       Carlos E. R.       (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux)

iEYEARECAAYFAk6ups0ACgkQtTMYHG2NR9W/VACfdNvAJdL5oXCGUQpn6NVguIOf aUoAn2gkDtVhRkAYptaDeBy2upfuogVV =V7nt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

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

-- http://opensuse.gr http://amb.opensuse.gr http://own.opensuse.gr http://warlordfff.tk me I am not me ------- Time travel is possible, you just need to know the right aliens -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org

Andrea Turrini writes:

I think you can use grep instead of sed; something like

grep -v "^#|" file.po > temp.po; mv temp.po file.po

I never managed to force sed to remove also the line feed at the end of the removed string.

You are probably looking for sed -i.old '/^#.*/d' file.po It replaces in place and saves the old file as file.po.old (just in case something goes wrong). -- 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

On 11/03/2011 06:22 PM, Carlos E. R. wrote:

On Wednesday, 2011-11-02 at 09:56 +0100, Karl Eichwalder wrote:

...

sed -i.old '/^#.*/d' file.po

But that one would not remove any comment? #.* I understand is # followed by any char. I need just "#|".

I think you should use sed -i.old '/^#|.*/d' file.po In this case the dot stands for every character, not a real dot. Best, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org