git-gui: updated translator README for current procedures.
We do not have a mob branch and the i18n fork is no longer used. Suggest translators simply send patches as per other contributors. Reported-by: Rodrigo Rosenfeld <rr.rosas@gmail.com> Signed-off-by: Pat Thoyts <patthoyts@users.sourceforge.net>
Pat Thoyts committed
Mar 31, 2011 at 16:24 UTC
8c0bf68353ed3394039ca04c01ded39a4f5643ea
1 file changed
+19
-20
po/README
+19
-20
@@ -18,28 +18,23 @@ specialized so-called "po file editors" (e.g. emacs po-mode, KBabel,
18
poedit, GTranslator --- any of them would work well). Please install
19
them.
20
21
-You would then need to clone the git-gui internationalization project
22
-repository, so that you can work on it:
21
+You would then need to clone the git-gui project repository and create
22
+a feature branch to begin working:
23
24
- $ git clone mob@repo.or.cz:/srv/git/git-gui/git-gui-i18n.git/
25
- $ cd git-gui-i18n
26
- $ git checkout --track -b mob origin/mob
27
- $ git config remote.origin.push mob
24
+ $ git clone git://repo.or.cz/git-gui.git
25
+ $ cd git-gui.git
26
+ $ git checkout -b my-translation
27
29
-The "git checkout" command creates a 'mob' branch from upstream's
30
-corresponding branch and makes it your current branch. You will be
31
-working on this branch.
32
-
33
-The "git config" command records in your repository configuration file
34
-that you would push "mob" branch to the upstream when you say "git
35
-push".
28
+The "git checkout" command creates a new branch to keep your work
29
+isolated and to make it simple to post your patch series when
30
+completed. You will be working on this branch.
31
32
33
2. Starting a new language.
34
40
-In the git-gui-i18n directory is a po/ subdirectory. It has a
41
-handful files whose names end with ".po". Is there a file that has
42
-messages in your language?
35
+In the git-gui directory is a po/ subdirectory. It has a handful of
36
+files whose names end with ".po". Is there a file that has messages
37
+in your language?
38
39
If you do not know what your language should be named, you need to find
40
it. This currently follows ISO 639-1 two letter codes:
@@ -149,15 +144,18 @@ There is a trick to test your translation without first installing:
144
$ make
145
$ LANG=af ./git-gui.sh
146
152
-When you are satisfied with your translation, commit your changes, and
153
-push it back to the 'mob' branch:
147
+When you are satisfied with your translation, commit your changes then submit
148
+your patch series to the maintainer and the Git mailing list:
149
150
$ edit po/af.po
151
... be sure to update Last-Translator: and
152
... PO-Revision-Date: lines.
153
$ git add po/af.po
159
- $ git commit -m 'Started Afrikaans translation.'
160
- $ git push
154
+ $ git commit -s -m 'git-gui: added Afrikaans translation.'
155
+ $ git send-email --to 'git@vger.kernel.org' \
156
+ --cc 'Pat Thoyts <patthoyts@users.sourceforge.net>' \
157
+ --subject 'git-gui: Afrikaans translation' \
158
+ master..
159
160
161
3. Updating your translation.
@@ -169,6 +167,7 @@ itself was updated and there are new messages that need translation.
167
168
In any case, make sure you are up-to-date before starting your work:
169
170
+ $ git checkout master
171
$ git pull
172
173
In the former case, you will edit po/af.po (again, replace "af" with