написане Tue, 17 Apr 2012 17:12:29 +0300, Richard E. van der Luit
<nippur(a)fedoraproject.org>:
Op 17-04-12 12:03, Yuri Chornoivan schreef:
> Tue, 17 Apr 2012 12:53:12 +0300 було написано Kévin Raymond
> <shaiton(a)fedoraproject.org>:
>
>>>
>>> To be honest, I do not see the major problem here.
>>>
>>> 1. Download PO.
>>> 2. Fix it or if it's already fixed do nothing.
>>> 3. Upload fixed PO to every branch.
>> No, because the PO should be different between branches. If not, they
>> would only have master…
>> But it could be the same between branches, you need to ask the
>> maintainer or check by yourself.
>
> Strange. Works every time here. ;)
>
> Even with different templates, the system merges only the entries with
> the same msgid strings (it's polib feature, imho).
Won't work if you want to replace a translation of a term for
consistency with translations of that term in other programs or
documents of the Project, as i regularly have to do.
- how do you know that all strings in all branches are reached by
uploading one just one .po? --> manual check on all sources -> 2 minutes
won't do it.
If you want to work directly with git repo, I have bad news for you.
General Transifex workflow does not imply PO (or POT) files in repos at
all.
You reach exactly the branch that can be derived from the name of the
catalog branch in Transifex.
About manual check of sources. Once again Lotte is not reliable, it hides
the translation from translator as good as it can. The results can be very
unpredictable if string has some formatting in it. If you want to change
something globally use tx client and some consistency checking instrument,
i.e. Pology [1]. Then upload all at once with tx client (as it was
mentioned earlier by Kévin Raymond).
- which .po is clever to use? The one with the most strings? The
most
appearances? --> manual check --> pffff
We have not very wide field: 16/17 branch and current master (believe me
that the difference between them is negligible). The rest of translations
cannot be reached for us as source repositories should not contain POs now
(see above).
On the other hand, translations on Zanata have all necessary equipment to
change them in the branch needed from (and only from) web-interface.
- are there still strings left to be corrected in the other sources?
-->
manual check --> *sigh*, no 'search and replace' feature...
Use search in /usr/share/locale/<locale>/LC_MESSAGES for installed UI
translations (docs should be treated by tx client method explained by
Kévin Raymond). On the other hand, if you do not know if there a mistake
somewhere, how would you know that there is a mistake at all? ;)
Better open all sources and take Lottes history to check every line,
wereof deed.
I hope you are joking.
What i was looking for, actually, was that one source which has
*all*
the strings in it, and let the system sort it out. How 'master' is
master anyway?
If you are looking for Fedora only translations, it's tx client snapshot
of the project or web-only Fedora Zanata instance. We cannot reach
translations that are not there in a usual way (without bug reporting).
You can fix the files locally (grep or pology sieve can help you to find
the necessary files), then sort by day and upload them. But for the fixed
translations reach the users you have to file bugs against all the
versions of packages affected.
regards
Richard
regards,
Yuri
[1]
http://pology.nedohodnik.net/