From: Jiang Xin <worldhello.net@gmail.com>
To: Dimitriy Ryazantcev via GitGitGadget <gitgitgadget@gmail.com>
Cc: Git List <git@vger.kernel.org>,
Jiang Xin <zhiyou.jx@alibaba-inc.com>,
Junio C Hamano <gitster@pobox.com>,
Dimitriy Ryazantcev <dimitriy.ryazantcev@gmail.com>
Subject: Re: [PATCH] l10n: mark message helpers prefix for translation.
Date: Tue, 21 Jun 2022 22:27:38 +0800 [thread overview]
Message-ID: <CANYiYbFju5PBZdx4EpZzG8uNw120hXwG2iCsuCd4hrub28-8oQ@mail.gmail.com> (raw)
In-Reply-To: <pull.1279.git.git.1655819439775.gitgitgadget@gmail.com>
On Tue, Jun 21, 2022 at 10:13 PM Dimitriy Ryazantcev via GitGitGadget
<gitgitgadget@gmail.com> wrote:
>
> From: Dimitriy Ryazantcev <dimitriy.ryazantcev@gmail.com>
>
> Some messages prefixed like 'usage:'/'fatal:'/'warning:'/'error:'
> were not translated.
>
> Signed-off-by: Dimiytriy Ryazantcev <dimitriy.ryazantcev@gmail.com>
> ---
> l10n: mark message helpers prefix for translation.
1. The prefix of the subject should be "i18n", because your are
marking strings for translation.
2. The subject line should not end with a period.
> Some messages prefixes like 'usage:'/'fatal:'/'warning:'/'error:' were
> not translated.
>
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1279%2FDJm00n%2Fl10n-fixes-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1279/DJm00n/l10n-fixes-v1
> Pull-Request: https://github.com/git/git/pull/1279
prev parent reply other threads:[~2022-06-21 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 13:50 [PATCH] l10n: mark message helpers prefix for translation Dimitriy Ryazantcev via GitGitGadget
2022-06-21 13:57 ` [PATCH v2] i18n: " Dimitriy Ryazantcev via GitGitGadget
2022-06-22 8:12 ` Ævar Arnfjörð Bjarmason
2022-06-22 15:23 ` Junio C Hamano
2022-06-22 15:33 ` Ævar Arnfjörð Bjarmason
2022-06-21 14:27 ` 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=CANYiYbFju5PBZdx4EpZzG8uNw120hXwG2iCsuCd4hrub28-8oQ@mail.gmail.com \
--to=worldhello.net@gmail.com \
--cc=dimitriy.ryazantcev@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=zhiyou.jx@alibaba-inc.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).