Thread: Typo in chinese translations

Typo in chinese translations

From
Daniel Gustafsson
Date:
When accidentally typoing a git grep I got two hits in the chinese translations
for said typo.  I’m not comfortable in submitting a chinese translation file
via the normal patch tracker since I can’t see if I messed anything up (perhaps
unlikely, but still) so below is a patch suggestion instead.  If anyone feels
like picking this up then below are the changes.

cheers ./daniel

diff --git a/src/interfaces/libpq/po/zh_CN.po b/src/interfaces/libpq/po/zh_CN.po
index ec2268b..1953226 100644
--- a/src/interfaces/libpq/po/zh_CN.po
+++ b/src/interfaces/libpq/po/zh_CN.po
@@ -698,13 +698,13 @@ msgstr "无法判断函数 lowrite 的 OID\n"
 #: fe-misc.c:295
 #, c-format
 msgid "integer of size %lu not supported by pqGetInt"
-msgstr "pgGetInt 不支持大小为 %lu 的整数"
+msgstr "pqGetInt 不支持大小为 %lu 的整数"

 # fe-misc.c:341
 #: fe-misc.c:331
 #, c-format
 msgid "integer of size %lu not supported by pqPutInt"
-msgstr "pgPutInt 不支持大小为 %lu 的整数"
+msgstr "pqPutInt 不支持大小为 %lu 的整数"

 # fe-misc.c:450 fe-misc.c:642 fe-misc.c:798
 #: fe-misc.c:642 fe-misc.c:843
diff --git a/src/interfaces/libpq/po/zh_TW.po b/src/interfaces/libpq/po/zh_TW.po
index 7d90c9e..e14e6ef 100644
--- a/src/interfaces/libpq/po/zh_TW.po
+++ b/src/interfaces/libpq/po/zh_TW.po
@@ -650,13 +650,13 @@ msgstr "無法判斷函式 lowrite 的 OID\n"
 #: fe-misc.c:270
 #, c-format
 msgid "integer of size %lu not supported by pqGetInt"
-msgstr "pgGetInt 不支援大小為 %lu 的整數 "
+msgstr "pqGetInt 不支援大小為 %lu 的整數 "

 # fe-misc.c:264
 #: fe-misc.c:306
 #, c-format
 msgid "integer of size %lu not supported by pqPutInt"
-msgstr "pgPutInt 不支援大小為 %lu 的整數"
+msgstr "pqPutInt 不支援大小為 %lu 的整數"

 # fe-misc.c:544
 # fe-misc.c:748

Re: Typo in chinese translations

From
Peter Eisentraut
Date:
On 9/22/16 8:06 AM, Daniel Gustafsson wrote:
> When accidentally typoing a git grep I got two hits in the chinese translations
> for said typo.  I’m not comfortable in submitting a chinese translation file
> via the normal patch tracker since I can’t see if I messed anything up (perhaps
> unlikely, but still) so below is a patch suggestion instead.  If anyone feels
> like picking this up then below are the changes.

Fixed, thanks.

--
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services