po/README: Update directions for l10n contributors
Some Linux distributions (such as Ubuntu) have their own l10n workflows, and their translations may be different. Add notes for this case for l10n translators. Signed-off-by: Philip Oakley <philipoakley@iee.org> Signed-off-by: Jiang Xin <worldhello.net@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Philip Oakley committed
Aug 16, 2015 at 15:56 UTC
a6926b837e22f69d9b800eb5f6d6c6d37285d8b6
1 file changed
+19
po/README
+19
@@ -10,10 +10,26 @@ coordinates our localization effort in the l10 coordinator repository:
10
11
https://github.com/git-l10n/git-po/
12
13
+The two character language translation codes are defined by ISO_639-1, as
14
+stated in the gettext(1) full manual, appendix A.1, Usual Language Codes.
15
+
16
+
17
+Contributing to an existing translation
18
+---------------------------------------
19
As a contributor for a language XX, you should first check TEAMS file in
20
this directory to see whether a dedicated repository for your language XX
21
exists. Fork the dedicated repository and start to work if it exists.
22
23
+Sometime, contributors may find that the translations of their Git
24
+distributions are quite different with the translations of the
25
+corresponding version from Git official. This is because some Git
26
+distributions (such as from Ubuntu, etc.) have their own l10n workflow.
27
+For this case, wrong translations should be reported and fixed through
28
+their workflows.
29
+
30
+
31
+Creating a new language translation
32
+-----------------------------------
33
If you are the first contributor for the language XX, please fork this
34
repository, prepare and/or update the translated message file po/XX.po
35
(described later), and ask the l10n coordinator to pull your work.
@@ -23,6 +39,9 @@ coordinate among yourselves and nominate the team leader for your
39
language, so that the l10n coordinator only needs to interact with one
40
person per language.
41
42
+
43
+Translation Process Flow
44
+------------------------
45
The overall data-flow looks like this:
46
47
+-------------------+ +------------------+