threads / discuss / 46400

[L10N] af.po: New translation workflow

Subject: [L10N] af.po: New translation workflow

## tl;dr

2 messages between Jul 16, 2017 and Jul 17, 2017.

replies: 1people: 2as markdown or json

Jacques Viviers· Jul 16, 2017, 17:37 UTC · lore
Hi all,

I have started a new translation af.po at: (https://github.com/jbviviers/git-po)

The translation is far from complete. Should I wait until it is all done before I submit the patch, or is it better to submit as I go along?

Although it is unlikely that someone else is busy with the same thing, it would still be better to somehow notify other potential translators that this work is in progress.

There is a few of my colleagues that indicated they would help with this translation. How does that collaboration work? Do I merge everyone's contributions as I see fit and then send in the set of patches?

Some advice would be much appreciated.

Kind regards, Jacques

Jiang Xin· Jul 17, 2017, 15:53 UTC · re: Jacques Viviers · lore

Re: [L10N] af.po: New translation workflow

2017-07-17 1:37 GMT+08:00 Jacques Viviers <jacques.viviers@gmail.com>:
Show 9 quoted lines
> Hi all,
>
> I have started a new translation af.po at:
> (https://github.com/jbviviers/git-po)
>
> The translation is far from complete. Should I wait until it is all
> done before I submit the patch, or is it better to submit as I go
> along?
>

After you complete most of the translations, send a PR to the l10n coordinator's repo (git-l10n/git-po on GitHub).

> Although it is unlikely that someone else is busy with the same thing,
> it would still be better to somehow notify other potential translators
> that this work is in progress.
>

A work-in-progress (WIP) branch will be created to let other guys know that l10n on Afrikaans is working in progress.

Show 5 quoted lines
> There is a few of my colleagues that indicated they would help with
> this translation. How does that collaboration work? Do I merge
> everyone's contributions as I see fit and then send in the set of
> patches?
>

You can review contributions using pull requests on your GitHub repo (jbviviers/git-po), and squash them into one or several commits before send pull request to the l10n coordinator's repo (git-l10n/git-po on GitHub).

> Some advice would be much appreciated.
>
> Kind regards,
> Jacques
-- 
Jiang Xin

← back to recent threads