On Thu, Nov 06, 2008 at 09:28:32AM -0300, Domingo Becker wrote:
2008/11/6 Noriko Mizumoto <noriko(a)redhat.com>:
> Magnus Larsson さんは書きました:
>>
>> It doesn't destroy it. If it did, you would have to re-translate all
>> strings, every time you update a POT file...
>> One thing to be careful about is the msgmerge and msgfmt commands. They
>> will
>> destroy your po files if it cannot merge. So I wrote a simple script to
>> "backup" my po file before I merge it. Se below.
>>
>> The only problem with updating the POT file, is when you update too early
>> (not completely finished release notes). Then translators will translate
>> things that maybe will be deleted in later versions and waste time. So I
>> say, if the doc is almost finished (and only minor fixes are made) then
>> update the POT file as often as possible.
>
> I found (I think) that Transifex does not warn any conflict but accept the
> commit, thus it can override latest file with older file.
>
http://git.fedorahosted.org/git/?p=docs/release-notes.git;a=history;f=po/...
>
If I commit with an older file, it will replace the new one.
But the new one was obtained from merging the .po file with the .pot file.
So, in the next merge of the .po file with the .pot file, the new
strings will appear again.
The only lost translation work would be the strings removed by the merge.
This is how I understood it to work too, which is why I was so
surprised earlier. Looks like we have the issues resolved.
I just fixed some minor typos in a file. If I update the POT with
that new string, are we agreed that this will not be a major problem?
--
Paul W. Frields
http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - -
http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug