Hi Paul and all,

thanks for doing the pot/po merge, it makes it much easier for the translators.

And thanks for the detailed explanation below. Appreciate it.

I've just finished another batch of translation more focused on untranslated and fuzzy strings.
Still I did some other stuff when relevant.

I'll continue that on Monday and Tuesday since I'll be AFK tomorrow pretty much all day.

Let's keep making Audacity translation much better for all languages !

Cheers,
Olivier


Le 2017-11-25 21:37, Paul Licameli a écrit :
Dear translators -- especially Olivier Humbert and Carmelo Battaglia,
who are completing fr and it right now:

I figured this out for myself, rather than requiring all translators
to do it, who might not know the gettext tools in detail:

At commit 101f6c7482a437956919a26d180597f280bdc717, all of the .po
files are now merged with the latest .pot file.

This means any new messages in the .pot not previously in the .po will
be there with empty msgstr for you to simply fill in.  Or, they might
be "fuzzy" matches.

That means msgmerge made a guess and copied a translation with an
inexact match of msgid.  But such places are marked with a comment
line starting

#, fuzzy

and the strings will not be used by Audacity unless you judge the
translation correct and remove that comment line.

The merge also means that messages no longer needed are commented out
in lines beginning

#~

And these seem to get collected at the end of the file.

The obsoletes may be useful references to you, supplying better
matches for some of the fuzzies, or maybe not.  I leave them there.
At your discretion, you can submit new versions of the .po file
without them, which is welcome to save a bit of space in the source
code tree.

At the command line you can eliminate all obsoletes at once with:

msgattrib --no-obsolete xx.po > xx1.po; mv xx1.po xx.po

I also removed all line numbers from comments in the .po files, but
still comment the original source code file.  I think this is good
enough to look up the string in the source, but saves a bit of space,
and in future will make the diffs between versions of each .po file
smaller and easier to review.

Lastly, if you go to the locale directory and type

msgcmp xx.po audacity.pot

then you get a list of errors describing where the translation is
incomplete and a summary count of errors.

The priority for translators should be to reduce that count of errors
to zero.  After that, you can review and improve translations that
were already present.

Paul Licameli
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-translation mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/audacity-translation

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-translation mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/audacity-translation

Reply via email to