Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bRj5U-0008NA-OS for pgsql-translators@arkaria.postgresql.org; Mon, 25 Jul 2016 16:50:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bRj5U-0001Dn-BU for pgsql-translators@arkaria.postgresql.org; Mon, 25 Jul 2016 16:50:40 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bRj5T-0001Dh-Pu for pgsql-translators@postgresql.org; Mon, 25 Jul 2016 16:50:39 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bRj5Q-0008Pi-PL for pgsql-translators@postgresql.org; Mon, 25 Jul 2016 16:50:38 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id E420A206E4; Mon, 25 Jul 2016 12:50:35 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Mon, 25 Jul 2016 12:50:35 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=+HlNeeo6UvwGL5l hloLQOOGJuxQ=; b=LmimHOsAodK1GMCYT2pOLFdAQxkwc3H0kr9kslm7W7w33hR kXgJ4OjFoKS+5bkhAP+/iMuRenhLtcVzERFBRAUX7+xUlsL9ZHqrZHfv30+NsgNP GWH7SMSVTI7PvjsjIxTnnRzJ489bJyB80zHh6fl/OjJSPDEhepaOdORqWYzs= X-Sasl-enc: 3OKigT7I5euHPctjLPj9lhrL51BcaxE/U9g4x4AuE3gK 1469465435 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 07846CCD83; Mon, 25 Jul 2016 12:50:34 -0400 (EDT) Subject: Re: Problem with error messages To: Alexander Law , pgsql-translators@postgresql.org References: <337ce77f-4159-0f43-cdb7-fcac30e3e219@2ndquadrant.com> <578F1B63.5000301@gmail.com> <2177748d-ff90-535c-080c-5ee0f399f4af@2ndquadrant.com> <579064B8.3060205@gmail.com> Cc: Walter Willmertinger From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <459fa80e-4ea7-9340-fddf-fd2c0280dd78@2ndquadrant.com> Date: Mon, 25 Jul 2016 12:50:30 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <579064B8.3060205@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-translators Precedence: bulk Sender: pgsql-translators-owner@postgresql.org On 7/21/16 1:59 AM, Alexander Law wrote: >> Right, but we don't have that functionality in PostgreSQL. It would >> > have to be implemented, and the transliteration tables provided. >> > > It seems, that the gettext functionality could be used for that conversion. Well, that would be quite a change to have gettext do the conversion when everything else in protocol messages goes through the built-in conversion tables. The possible implications of that are not clear. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-translators mailing list (pgsql-translators@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-translators