On 05.04.2016 11:21, tiansworld wrote:

On Tue, Apr 5, 2016 at 10:39 PM, Florian H. <postfuerflo@gmail.com> wrote:
Sorry for bothering this list again with my rookie questions.

I translated (part of) blivet-gui into German (de) and noticed that the
f24-branch also requests translations for de-DE. How can I upload the
.po file of de-translations to de-DE? Or is this maybe not even needed?
Will a system automatically default to de if de-DE is not available?

First you have to be the translator of de-DE. 
I forget that if there is a upload button in Zanata online editor. If it has, then you can try to upload it.

That's what I am looking for, an upload button or function. Couldn't find it. I can send the .po file to the developers though.
The other thing, sometimes I see a master branch, I assume that all
"release branches" (such as f24, devel, rhel7...) are forked from this
master. What's the strategy if there is no master? Will the next release
be forked from the latest version? What if the release branches all have
different progress of translation (say 41%, 48%, and 66%). What this
question basically means, that it isn't obvious to me to what branch to
contribute (even in the case that there is a master. So, what would be
of higher priority? A master or f-24? Will the changes to f-24 be merged
back to master?).

I think in the case of blivet-gui, the devel branch is the master one.
In my opinion, f24 branch should be translated first before it is released. However after the release, master branch should be in the highest priority. Because the master branch is the main branch for developers, they will add new features or fix bugs in it and fork other branches in future. It always moves forward. But while the other branches are not EOL(end of life), we may also keep maintaining their translations as well.  
OK, Thanks for the explanation.
Does that also mean that after a the Translation Deadline of a new Fedora release, it makes no sense to contribute to its trans branch?

The changes in f-24 will not be merged back to master, because the branch may already be behind the master a lot, i.e. they may have a lots of differences.
That unfortunately can mean that parts have to be translated twice. In case contribution has happened only to release-branches but not to master or devel, right? Or maybe just before translation deadline we should try to merge the two...



Tian Shixiong
Fedora Project Contributor

trans mailing list