From: Bagas Sanjaya <bagasdotme@gmail.com>
To: git@vger.kernel.org
Cc: worldhello.net@gmail.com, Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 2/3] po/README: document "core translation"
Date: Thu, 11 Mar 2021 19:55:10 +0700 [thread overview]
Message-ID: <20210311125511.51152-3-bagasdotme@gmail.com> (raw)
In-Reply-To: <20210311125511.51152-1-bagasdotme@gmail.com>
We now expect new language translations to have core subset of 5000+
messages translated for these to be merged. If it hasn't been done yet,
do so by first generate core PO, then do translation work there, merge
it back to main PO (XX.po), and fix any "fuzzy" errors.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
po/README | 36 ++++++++++++++++++++++++++++++++++++
1 file changed, 36 insertions(+)
diff --git a/po/README b/po/README
index 9beffc2954..eda7edf4e6 100644
--- a/po/README
+++ b/po/README
@@ -39,6 +39,42 @@ coordinate among yourselves and nominate the team leader for your
language, so that the l10n coordinator only needs to interact with one
person per language.
+Because there are now over 5000 messages that needs to be translated,
+we expect to complete translation for core subset of messages before
+a new language translation can be merged. See "Core translation"
+below.
+
+
+Core translation
+----------------
+The core translation file, core-XX.po, covers some of commonly used
+commands:
+
+ - wt-status.c
+ - builtin/clone.c
+ - builtin/checkout.c
+ - builtin/index-pack.c
+ - builtin/push.c
+ - builtin/reset.c
+
+To generate core-XX.po, install the helper script (see "PO Helper")
+and check the main PO file:
+
+ cd po/
+ po-helper.sh check id.po
+
+This will generate po/core-XX.po and corresponding po/core-XX.pot
+template. Now complete the translation in po/core-XX.po.
+
+When it is completed, merge core translation back to main PO file:
+
+ msgcat core-XX.po XX.po -s -o /tmp/XX.po
+ mv /tmp/XX.po XX.po
+ msgmerge --add-location --backup=off -U XX.po git.pot
+
+Fix any "fuzzy" errors that occurs, such as misplaced translated
+messages and duplicate messages.
+
Translation Process Flow
------------------------
--
2.25.1
next prev parent reply other threads:[~2021-03-11 12:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 12:55 [PATCH 0/3] po/README: document miscellaneous topics mentioned by l10n coordinator Bagas Sanjaya
2021-03-11 12:55 ` [PATCH 1/3] po/README: document PO helper Bagas Sanjaya
2021-03-12 1:32 ` Jiang Xin
2021-03-12 6:03 ` Junio C Hamano
2021-03-12 11:56 ` Bagas Sanjaya
2021-05-13 15:40 ` Jiang Xin
2021-05-27 3:11 ` Jiang Xin
2021-03-11 12:55 ` Bagas Sanjaya [this message]
2021-03-12 1:32 ` [PATCH 2/3] po/README: document "core translation" Jiang Xin
2021-03-11 12:55 ` [PATCH 3/3] po/README: document l10n conventions Bagas Sanjaya
2021-03-11 13:13 ` Bagas Sanjaya
2021-03-12 1:33 ` Jiang Xin
2021-03-12 11:47 ` Bagas Sanjaya
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=20210311125511.51152-3-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=worldhello.net@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).