Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hR7QP-0005Qv-TP for pgsql-translators@arkaria.postgresql.org; Thu, 16 May 2019 03:51:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hR7QO-00029D-O9 for pgsql-translators@arkaria.postgresql.org; Thu, 16 May 2019 03:51:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hR7QO-000296-EX for pgsql-translators@lists.postgresql.org; Thu, 16 May 2019 03:51:20 +0000 Received: from mail-qk1-x730.google.com ([2607:f8b0:4864:20::730]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hR7QK-0002vb-Qm for pgsql-translators@lists.postgresql.org; Thu, 16 May 2019 03:51:19 +0000 Received: by mail-qk1-x730.google.com with SMTP id j20so1441326qke.1 for ; Wed, 15 May 2019 20:51:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=aUnAd9Cmcih5WSUwkBgzBxpdTyWggYRcocZ7F3XFJK4=; b=jN9g0etcqpLpLxmpQXvkQzdlmT5qkvROj+YonCG+JvYuPhTwnoXNLcne6BFWzYnkog 8rkwiAr7bkZ9Bk0cX6oT7I/1+JnPa3F8N5f9geRE0bjEBZpOacW/pF9xuYvTUDSxYFB9 kvGP+dorojv70WLma+bEzjg2vrkO33sC1ddPm/+hxA/3ESjOXxfnV0h8HUOQ9Xsg/nrn A5LXGix+fGUvB1HhcGOEc47wo6JoVuG40jPWiksXkqDjHM3ruKyCxKhr0G0iImCqUCRU 7azEHfHOH3eEfK/2y5C9OlBusLMNoosv9meLDnaVY41N+1zVZDWPodwMmdm4Ztoky0xB fZmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=aUnAd9Cmcih5WSUwkBgzBxpdTyWggYRcocZ7F3XFJK4=; b=OKp4XyiIsiGunzKbOYAewP4wQ0B66GTK4xJOWvx3b76e0nBCXf/QZYhAJN6KCQK5NN 1Wr7umn6B3hRBtWeW1zVTTmbglvKd8nILm4kzlySlttqNYoic/sJ6VuZSi8XwTeTW3mM 505hRIt/AVj1ktYMQHHzbVnYPliV+aScQHD2dpxK6A2GqG/g7c7sbFh3KIgzwmqi0hKA Emk+JVxVz0Oc4JRvzw21oHUmknzeEFHhekXVo2hjtdvxP2Fz/337LQKnNU8kqWqfoQ14 yT8qM7kD5uagCtQS/puR3LahWDQFNN5J34bR+EdPxjTfjgvu75BTktGRR/hAbXFMh+2h Eczg== X-Gm-Message-State: APjAAAWfQZyLu4Nuktr62WkHCujCOehlbk08hPeHS9tf2jtHw9Yy1Jr5 KMMmjZtePu71psbhb7U8a/CFim+Wn9ytwotF0ygqEXe9fpbM2YpehvlvKILn3aTW5xeKOkSGHdc bX4qeBIVAa42NPbtojXLCq7JBwt5ETwdyDhESOwh5djyLJD+Ep5Esgnq/SRYFYUvPHcrdabQYeW V/TrdpWZwpG1yVsRWvg1E= X-Google-Smtp-Source: APXvYqyoN740j9D7qKBC+BSQVu0P2ax+GQ4BcF0oasc5vW65KoM1iJPVgOGbB6HXq4qbJTJDiBSGLQ== X-Received: by 2002:a37:5444:: with SMTP id i65mr37040067qkb.263.1557978675799; Wed, 15 May 2019 20:51:15 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([179.56.48.227]) by smtp.gmail.com with ESMTPSA id t58sm2479741qtj.4.2019.05.15.20.51.14 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 15 May 2019 20:51:14 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id AC81A120CE5; Wed, 15 May 2019 23:51:12 -0400 (-04) Date: Wed, 15 May 2019 23:51:12 -0400 From: Alvaro Herrera To: Ioseph Kim Cc: pgsql-translators@lists.postgresql.org, Turkish , Yuwei Peng Subject: Re: inconsistent translations, or the language is like that? Message-ID: <20190516035112.GA27177@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <17734d60-3519-0895-2d27-658f3496ac9f@postgresql.kr> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-May-16, Ioseph Kim wrote: Hi, thanks for replying so quickly. > The exact Korean expression is 'INSERT RETURNING 구문을 수행할 수 없음'. > > perform has same meaming for '구성' and '수행'. > > and '없음' is abbreviated to '없습니다'. I see :-) > I'll change it in the next version. thanks. > > I am more curious why you are interested in this matter. :) Well, I'm considering changing the way those three error messages are emitted by the server, so that the three cases use the same code. So the translator would only get this string in the translation file: "cannot perform %s on relation \"%s\"" instead of getting three strings. Then the program would substitute the first %s by INSERT RETURNING, UPDATE RETURNING, or DELETE RETURNING depending on which case is hit. So I was searching for occurrences of those three messages in the existing translations, looking for any where the three translations were not identical, and Korean was the first I found. After sending, I realized that the translations for simplified Chinese and Turkish of the three phrases are also different! simplified Chinese: msgstr "无法在关系\"%s\"上执行INSERT RETURNING " msgstr "无法在关系\"%s\"执行UPDATE RETURNING" msgstr "无法在关系 \"%s\"上执行DELETE RETURNING" Turkish: msgstr "\"%s\" nesnesinde INSERT RETURNING yapılamaz" msgstr "\"%s\" nesnesinde UPDATE RETURNING yapılamaz" msgstr "\"%s\" nesnesi üzerinde DELETE RETURNING işlemi yapılamaz" I don't speak (or even read) either of these languages so can't tell whether the translations are just different because there are two ways of writing the same thing (so my proposed change would not cause a problem), or the languages have inflection or grammatical rules that make the phrases be different (which makes my proposed change not acceptable). My preliminary conclusion is that I shouldn't be changing this. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services