From: Jiang Xin <worldhello.net@gmail.com>
To: "Christopher Díaz" <christopher.diaz.riv@gmail.com>,
"Jean-Noël Avila" <jn.avila@free.fr>,
"Peter Krefting" <peter@softwolves.pp.se>,
"Yi-Jyun Pan" <pan93412@gmail.com>,
"Andrei Rybak" <rybak.a.v@gmail.com>,
"Git List" <git@vger.kernel.org>
Cc: Jiang Xin <worldhello.net@gmail.com>
Subject: [L10N] l10n: fixed tripple-letter typos
Date: Mon, 21 Jun 2021 10:07:40 +0800 [thread overview]
Message-ID: <20210621020740.25577-1-worldhello.net@gmail.com> (raw)
Andrei found that the word "shallow" has an extra letter "l" in
"po/zh_CN.po". There are similar typos in other l10n files.
Reported-by: Andrei Rybak <rybak.a.v@gmail.com>
Signed-off-by: Jiang Xin <worldhello.net@gmail.com>
---
po/README.md | 2 +-
po/es.po | 4 ++--
po/fr.po | 2 +-
po/sv.po | 2 +-
po/zh_CN.po | 6 +++---
po/zh_TW.po | 6 +++---
6 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/po/README.md b/po/README.md
index 2fd92cca04..a7e6f2014c 100644
--- a/po/README.md
+++ b/po/README.md
@@ -392,7 +392,7 @@ additional conventions:
git-po-helper init --core <your-language>
3. Add a new entry in the "po/TEAMS" file with proper format, and check
- the syntax of "po/TEAMS" by runnning the following command:
+ the syntax of "po/TEAMS" by running the following command:
git-po-helper team --check
diff --git a/po/es.po b/po/es.po
index c1c26138f0..ea15180c65 100644
--- a/po/es.po
+++ b/po/es.po
@@ -14897,7 +14897,7 @@ msgstr "extraer de todos los remotos"
#: builtin/fetch.c:147 builtin/pull.c:245
msgid "set upstream for git pull/fetch"
-msgstr "configurar upstream para git pulll/fetch"
+msgstr "configurar upstream para git pull/fetch"
#: builtin/fetch.c:149 builtin/pull.c:188
msgid "append to .git/FETCH_HEAD instead of overwriting"
@@ -19567,7 +19567,7 @@ msgstr "recibir programa de paquete"
#: builtin/push.c:573
msgid "set upstream for git pull/status"
-msgstr "configurar upstream para git pulll/status"
+msgstr "configurar upstream para git pull/status"
#: builtin/push.c:576
msgid "prune locally removed refs"
diff --git a/po/fr.po b/po/fr.po
index 336dc606b2..6c3630cbd4 100644
--- a/po/fr.po
+++ b/po/fr.po
@@ -25124,7 +25124,7 @@ msgid ""
" * Saying \"./%s\" if you mean a file; or\n"
" * Giving --format-patch option if you mean a range.\n"
msgstr ""
-"Le fichier '%s' existe mais ce pourrait aussi être la plage de commmits\n"
+"Le fichier '%s' existe mais ce pourrait aussi être la plage de commits\n"
"pour lequel les patches sont à produire. Veuillez préciser...\n"
"\n"
" * en indiquant \"./%s\" si vous désignez un fichier, ou\n"
diff --git a/po/sv.po b/po/sv.po
index 4a9f2f3aca..d5bf6f530e 100644
--- a/po/sv.po
+++ b/po/sv.po
@@ -17352,7 +17352,7 @@ msgstr "kopiera Message-ID till slutet av incheckningsmeddelandet"
#: builtin/mailinfo.c:64
msgid "re-code metadata to i18n.commitEncoding"
-msgstr "koda om metadata till i18n.commmitEncoding"
+msgstr "koda om metadata till i18n.commitEncoding"
#: builtin/mailinfo.c:67
msgid "disable charset re-coding of metadata"
diff --git a/po/zh_CN.po b/po/zh_CN.po
index 446c601a70..d6f61eae5c 100644
--- a/po/zh_CN.po
+++ b/po/zh_CN.po
@@ -4162,7 +4162,7 @@ msgstr "服务器支持 %s"
#: fetch-pack.c:1029
msgid "Server does not support shallow clients"
-msgstr "服务器不支持 shalllow 客户端"
+msgstr "服务器不支持浅客户端"
#: fetch-pack.c:1089
msgid "Server does not support --shallow-since"
@@ -4204,7 +4204,7 @@ msgstr "服务器不支持算法 '%s'"
#: fetch-pack.c:1279
msgid "Server does not support shallow requests"
-msgstr "服务器不支持 shalllow 请求"
+msgstr "服务器不支持浅克隆请求"
#: fetch-pack.c:1286
msgid "Server supports filter"
@@ -23864,7 +23864,7 @@ msgstr "预期仍然需要 %d 个字节的正文"
#: remote-curl.c:1132
msgid "dumb http transport does not support shallow capabilities"
-msgstr "哑 http 传输不支持 shalllow 能力"
+msgstr "哑 http 传输不支持浅克隆能力"
#: remote-curl.c:1147
msgid "fetch failed."
diff --git a/po/zh_TW.po b/po/zh_TW.po
index 77a5d57ed8..cb5db0abfa 100644
--- a/po/zh_TW.po
+++ b/po/zh_TW.po
@@ -4291,7 +4291,7 @@ msgstr "伺服器支援 %s"
#: fetch-pack.c:1029
msgid "Server does not support shallow clients"
-msgstr "伺服器不支援 shalllow 用戶端"
+msgstr "伺服器不支援 shallow 用戶端"
#: fetch-pack.c:1089
msgid "Server does not support --shallow-since"
@@ -4333,7 +4333,7 @@ msgstr "伺服器不支援「%s」算法"
#: fetch-pack.c:1279
msgid "Server does not support shallow requests"
-msgstr "伺服器不支援 shalllow 請求"
+msgstr "伺服器不支援 shallow 請求"
#: fetch-pack.c:1286
msgid "Server supports filter"
@@ -23992,7 +23992,7 @@ msgstr "預期仍要有 %d 位元組的本文 (body)"
#: remote-curl.c:1132
msgid "dumb http transport does not support shallow capabilities"
-msgstr "啞 http 傳輸不支援 shalllow 能力"
+msgstr "啞 http 傳輸不支援 shallow 能力"
#: remote-curl.c:1147
msgid "fetch failed."
--
2.32.0.rc0.27.g7b1e85181b
next reply other threads:[~2021-06-21 2:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 2:07 Jiang Xin [this message]
2021-06-21 19:36 ` [L10N] l10n: fixed tripple-letter typos Peter Krefting
2021-06-22 0:24 ` Jiang Xin
2021-06-29 1:32 ` Junio C Hamano
2021-07-03 11:18 ` [L10N] fixed mismatched variable names Jiang Xin
2021-07-03 11:43 ` Ævar Arnfjörð Bjarmason
2021-07-03 14:33 ` Jiang Xin
2021-07-03 13:54 ` Jiang Xin
2021-07-05 1:55 ` [PATCH] [l10n] po/id.po: fix " Bagas Sanjaya
2021-06-22 6:57 ` [L10N] l10n: fixed tripple-letter typos Jean-Noël Avila
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210621020740.25577-1-worldhello.net@gmail.com \
--to=worldhello.net@gmail.com \
--cc=christopher.diaz.riv@gmail.com \
--cc=git@vger.kernel.org \
--cc=jn.avila@free.fr \
--cc=pan93412@gmail.com \
--cc=peter@softwolves.pp.se \
--cc=rybak.a.v@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.