<tiansworld@fedoraproject.org>:
> On Tue, Apr 5, 2016 at 10:39 PM, Florian H. <postfuerflo@gmail.com>
> wrote:
>
>> Hi,
>> 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.
Hi,
There is a down arrow on the right pane, next to the "blivet-gui" label.
Click on it and choose "Upload translation".
As it was mentioned above, you should be member of the corresponding team
to be able to do this.
However, the duplication of locales seems useless (at least, for the pair
of default speeches de - de_DE).
Best regards,
Yuri
>
>
>> 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.
>
> 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.
--
trans mailing list
trans@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/trans@lists.fedoraproject.org
No comments:
Post a Comment