I am starting with projects w/o much translations:
bastion : https://github.com/Katello/bastion/pull/72
katello: https://github.com/Katello/katello/pull/5334
I will start to work on the other projects next. I assume for foreman
core, the PR should go against 1.9. For the plugins and hammer, should
it go against the development branch… or the latest release?
Thanks!
– bk
> I am starting with projects w/o much translations:
>
> bastion : https://github.com/Katello/bastion/pull/72
> katello: https://github.com/Katello/katello/pull/5334
>
> I will start to work on the other projects next. I assume for foreman
> core, the PR should go against 1.9.
Note that we can't merge translations into the git repo, they have to be
sent to Transifex.
Now is also the worst time to try and merge in translated strings in
bulk, as translation is underway for 1.9. I'd suggest doing it once
it's quietened down, or after the first or second 1.9 release when we're
heading towards 1.10.
> For the plugins and hammer, should
> it go against the development branch… or the latest release?
Against the current .pot in their develop or master branches.
–
Dominic Cleal
Red Hat Engineering
>> I am starting with projects w/o much translations:
>>
>> bastion : https://github.com/Katello/bastion/pull/72
>> katello: https://github.com/Katello/katello/pull/5334
>>
>> I will start to work on the other projects next. I assume for foreman
>> core, the PR should go against 1.9.
>
> Note that we can't merge translations into the git repo, they have to be
> sent to Transifex.
I was assuming if I pull the latest down, and then merge in the
donstream changes, then on approval it could be a :
create a edit.po for each .poi file
tx push
would that work?
>
> Now is also the worst time to try and merge in translated strings in
> bulk, as translation is underway for 1.9. I'd suggest doing it once
> it's quietened down, or after the first or second 1.9 release when we're
> heading towards 1.10.
I will hold off a bit to the core ones, and try out the process on the
plugins which are not really changing. Some of them do not seem to have
changed for a few weeks.
>
>> For the plugins and hammer, should
>> it go against the development branch… or the latest release?
>
> Against the current .pot in their develop or master branches.
Will do for the plugins. For foreman-core, do you want it against 1.9 or
against develop?
– bk
>
>
>>> I am starting with projects w/o much translations:
>>>
>>> bastion : https://github.com/Katello/bastion/pull/72
>>> katello: https://github.com/Katello/katello/pull/5334
>>>
>>> I will start to work on the other projects next. I assume for foreman
>>> core, the PR should go against 1.9.
>>
>> Note that we can't merge translations into the git repo, they have to be
>> sent to Transifex.
>
> I was assuming if I pull the latest down, and then merge in the
> donstream changes, then on approval it could be a :
>
> create a edit.po for each .poi file
> tx push
>
> would that work?
If it's just new strings, that's fine. A while ago you had a thread
open about changing existing strings and reviewing that, do you still
plan to propose that?
>> Now is also the worst time to try and merge in translated strings in
>> bulk, as translation is underway for 1.9. I'd suggest doing it once
>> it's quietened down, or after the first or second 1.9 release when we're
>> heading towards 1.10.
>
> I will hold off a bit to the core ones, and try out the process on the
> plugins which are not really changing. Some of them do not seem to have
> changed for a few weeks.
The POT files may not have, but note that the strings in Transifex may
be changing still.
>>> For the plugins and hammer, should
>>> it go against the development branch… or the latest release?
>>
>> Against the current .pot in their develop or master branches.
>
> Will do for the plugins. For foreman-core, do you want it against 1.9 or
> against develop?
Currently we're translating 1.9, and usually only translate the latest
stable release, rarely develop.
–
Dominic Cleal
Red Hat Engineering
>>
>>
>>>> I am starting with projects w/o much translations:
>>>>
>>>> bastion : https://github.com/Katello/bastion/pull/72
>>>> katello: https://github.com/Katello/katello/pull/5334
>>>>
>>>> I will start to work on the other projects next. I assume for foreman
>>>> core, the PR should go against 1.9.
>>>
>>> Note that we can't merge translations into the git repo, they have to be
>>> sent to Transifex.
>>
>> I was assuming if I pull the latest down, and then merge in the
>> donstream changes, then on approval it could be a :
>>
>> create a edit.po for each .poi file
>> tx push
>>
>> would that work?
>
> If it's just new strings, that's fine. A while ago you had a thread
> open about changing existing strings and reviewing that, do you still
> plan to propose that?
Yes, I will call those out specifically in a seperate pastebin so that
those are easy to find. I will do a test run on a smaller plugin first
so that folks see the process before core.
>
>>> Now is also the worst time to try and merge in translated strings in
>>> bulk, as translation is underway for 1.9. I'd suggest doing it once
>>> it's quietened down, or after the first or second 1.9 release when we're
>>> heading towards 1.10.
>>
>> I will hold off a bit to the core ones, and try out the process on the
>> plugins which are not really changing. Some of them do not seem to have
>> changed for a few weeks.
>
> The POT files may not have, but note that the strings in Transifex may
> be changing still.
Yeah, I was checking the dates on the transifex website.
>
>>>> For the plugins and hammer, should
>>>> it go against the development branch… or the latest release?
>>>
>>> Against the current .pot in their develop or master branches.
>>
>> Will do for the plugins. For foreman-core, do you want it against 1.9 or
>> against develop?
>
> Currently we're translating 1.9, and usually only translate the latest
> stable release, rarely develop.
>
kk… will do a pr against 1.9 then once it settles down.
– bk