list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Jiang Xin <>
To: "Git List" <>,
	"Git l10n discussion group" <>,
	"Alexander Shopov" <>,
	"Jordi Mas" <>,
	"Ralf Thielow" <>,
	"Jimmy Angelakos" <>,
	"Christopher Díaz" <>,
	"Jean-Noël Avila" <>,
	"Bagas Sanjaya" <>,
	"Alessandro Menti" <>,
	"Gwan-gyeong Mun" <>, Arusekk <>,
	"Daniel Santos" <>,
	"Dimitriy Ryazantcev" <>,
	"Peter Krefting" <>,
	"Emir SARI" <>,
	"Trần Ngọc Quân" <>,
	"Fangyi Zhou" <>, "Yi-Jyun Pan" <>
Cc: Jiang Xin <>
Subject: [L10N] Kickoff for Git 2.38.0 round #2
Date: Thu, 22 Sep 2022 08:50:24 +0800	[thread overview]
Message-ID: <> (raw)


Additional 8 new translatable messages were found in the just-released
Git v2.38.0-rc1. Let's start a new round of git l10n. Please send your
pull request to the l10n coordinator's repository below before this
update window closes on Sun, Oct 02, 2022.

As of git 2.37, we (git l10n contributors) have a new l10n workflow. The
following description of the new l10n workflow is from the "po/"

## The "po/git.pot" file is a generated file, no longer in the repository

The l10n coordinator does not need to generate the "po/git.pot" file every
time to start a new l10n workflow, and there is no "po/git.pot" file at all.

Everyone can generate the "po/git.pot" file with the command below:

    make po/git.pot

But we can also forget about it. By updating our corresponding "po/XX.po"
file, the "po/git.pot" file is automatically generated.

## Update the "po/XX.po" file, and start to translate

Before updating the "po/XX.po" file, l10n contributors should pull the latest
commits from the master branch of "git.git". E.g.:

    git pull --rebase master

Then update the cooresponding "po/XX.po" file using the following command:

    make po-update PO_FILE=po/XX.po

Translate the uptodate "po/XX.po" file, and create a new commit.

## Refine your commits, send pull requests

In the "po/XX.po" file, there are location lines in comments like below:

    #: add-interactive.c:535 add-interactive.c:836 reset.c:136 sequencer.c:3505
    #: sequencer.c:3970 sequencer.c:4127 builtin/rebase.c:1261
    #: builtin/rebase.c:1671

These comments with file locations are useful for l10n contributors to locate
the context easily during translation. But these file locations introduce a
lot of noise and will consume a lot of repository storage. Therefore, we
should remove these file locations from the "po/XX.po" file.

To remove file locations in the "po/XX.po" file, you can use one of the
following two ways, but don't switch back and forth.

 * Keep the filenames, only remove locations (need gettext 0.19 and above):

        msgcat --add-location=file po/XX.po >po/
        mv po/ po/XX.po

 * Remove both filenames and locations:

        msgcat --no-location po/XX.po >po/
        mv po/ po/XX.po

After squashing trivial commits and removing file locations in the "po/XX.po"
file, send pull request to the l10n coordinator's repository below:

## Resolve errors found by the l10n CI pipeline for the pull request

A helper program hosted on "" can
help git l10n coordinator and git l10n contributors to check the conventions
of git l10n contributions, and it is also used in GitHub actions as l10n CI
pipeline to validate each pull request in the "git-l10n/git-po" repository.
Please fix the issues found by the helper program.

** Please note: The update window will close on Sun, Oct 02, 2022. **

Jiang Xin

                 reply	other threads:[~2022-09-22  0:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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

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).