Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oL119-00056e-0A for pgsql-translators@arkaria.postgresql.org; Mon, 08 Aug 2022 11:33:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oL117-0007fg-Ph for pgsql-translators@arkaria.postgresql.org; Mon, 08 Aug 2022 11:33:53 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oL116-0007fX-So for pgsql-translators@lists.postgresql.org; Mon, 08 Aug 2022 11:33:53 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oL114-0008KM-8U for pgsql-translators@postgresql.org; Mon, 08 Aug 2022 11:33:51 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 178A95C00A5; Mon, 8 Aug 2022 07:33:49 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 08 Aug 2022 07:33:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1659958429; x=1660044829; bh=o dpr9s66xftHF00CwvRHDGifaT9gGXKJmhnjTEDxCgs=; b=s6AnjzFGTw9B1P7iR vbXO8xigpLc6wPkK35xI2Us1Z39n2qqY2yIwnPlEjGgdjkGxKgwXwP9cYFIkqPCg JDUODBp+L3BwNEJQNp9Czi7LTbNdXCWHzLvVG8PvgccPnPLV98k+c2RBPXVbk6k0 1yOLozvciyosH9wMqK/a+hpXGhApLGiY2fSEQkIXdnwpxFvLkN9oykIP4B8dQMjm EuI3UokIlWE+WDcRmchtLzrt/TkwfdExV60Q0iDX1ntcLSpaltwNSbAtqtY/QULi iVC0PejU1zjbliLlh8+G0QaOddZaFqdHkvy6s5CfEhNhtlfyMh5qAj84ZXJsBBwp gzLkA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdefkedggeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvvefukfggtggugfgjsehtke ertddttdejnecuhfhrohhmpeetlhhvrghrohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhr vgesrghlvhhhrdhnohdqihhprdhorhhgqeenucggtffrrghtthgvrhhnpedvkedtffduff dtffffheffhfejjefhgfeiueeukeejkeffgfdufffhudffffeuveenucffohhmrghinhep vghnthgvrhhprhhishgvuggsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrg hrrghmpehmrghilhhfrhhomheprghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhr gh X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 8 Aug 2022 07:33:48 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 599EB373; Mon, 8 Aug 2022 13:34:01 +0200 (CEST) Date: Mon, 8 Aug 2022 13:34:01 +0200 From: Alvaro Herrera To: Kyotaro Horiguchi Cc: harukat@sraoss.co.jp, pgsql-translators@postgresql.org Subject: Re: BUG #17508: ja.po for pg_ctl has an obvious mistake Message-ID: <20220808113401.ld5joqsffsapy5ta@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <568B0753-B4A7-4CF6-86BD-C8621AE84D7C@yesql.se> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello Horiguchi-san, I happened to notice that this mistake has not been corrected: > > On 2 Jun 2022, at 04:02, PG Bug reporting form wrote: > > > > "ja.po" for pg_ctl has an obvious error. > > "停止" in the following entry must be "開始" or "起動". > > > > src/bin/pg_ctl/po/ja.po: > > #: pg_ctl.c:996 > > #, c-format > > msgid "%s: server did not start in time\n" > > msgstr "%s: サーバは時間内に停止しませんでした\n" Thanks -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/