From: Jiang Xin <worldhello.net@gmail.com>
To: Jacques Viviers <jacques.viviers@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [L10N] af.po: New translation workflow
Date: Mon, 17 Jul 2017 23:53:57 +0800 [thread overview]
Message-ID: <CANYiYbFF380s2T_TUJ8Wa3pA_zkZc+L7=E-QhyFr4hycqMdmCA@mail.gmail.com> (raw)
In-Reply-To: <CAA=CdW25uWyZA_7RVnr35dNuK06=8_+fk_tBMt5OSf_xY4LWFA@mail.gmail.com>
2017-07-17 1:37 GMT+08:00 Jacques Viviers <jacques.viviers@gmail.com>:
> 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.
> 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
prev parent reply other threads:[~2017-07-17 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 17:37 [L10N] af.po: New translation workflow Jacques Viviers
2017-07-17 15:53 ` Jiang Xin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANYiYbFF380s2T_TUJ8Wa3pA_zkZc+L7=E-QhyFr4hycqMdmCA@mail.gmail.com' \
--to=worldhello.net@gmail.com \
--cc=git@vger.kernel.org \
--cc=jacques.viviers@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).