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 1oMWuy-0001kY-Ig for pgsql-translators@arkaria.postgresql.org; Fri, 12 Aug 2022 15:49:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oMWux-0000q5-1w for pgsql-translators@arkaria.postgresql.org; Fri, 12 Aug 2022 15:49:47 +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 1oMWuw-0000pw-QD for pgsql-translators@lists.postgresql.org; Fri, 12 Aug 2022 15:49:46 +0000 Received: from mail-yw1-x1135.google.com ([2607:f8b0:4864:20::1135]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oMWuq-0000CX-2E for pgsql-translators@lists.postgresql.org; Fri, 12 Aug 2022 15:49:45 +0000 Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-3246910dac3so13734647b3.12 for ; Fri, 12 Aug 2022 08:49:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc; bh=epwlGSkaKcm98jGXJBcKeo6t3chB5mo82si2rl7AJus=; b=O797dplddaXtDjzHpfA/wJJJcAZ4EvU6bVatjHAzoJrMaAPQ0L7ViJkPY4oRrAjKgv ESg+4C3ZXR+hNOJLRsEfKunSgrES03rffG3t9BUm4kOxGJpmP0rdmYXATfP2O8nS8Rju xhpIkEaNkhur4KXX8MtAncVtMbO93x5ULRXsZpjN7PpH/vilIWHEnqNUwt1SJGJfP0lb t2ojTH0tj0IvE0Ss3N9bo2rXxBbZs+6KDqu1xVFWLBs5dfJ/U4X1cdLJwY/j2i4LHEMs v/mlN5o67Dqn3SJgkMHAom2oPSLCtzl+soO8q+zbBkuQBsDO+bzKDK6tbjRAXst6VvoS XlaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc; bh=epwlGSkaKcm98jGXJBcKeo6t3chB5mo82si2rl7AJus=; b=qAiaCqGZzk+D6eWhbWmPEL8hiCpxqa6J8BGviJC0i1vJ1jssa8FiCCIieGpQzbFFed PbTX3nKr9CmvlTFj0ZYK+B9uLMZZVh+0syncSUNi9yF2gTjCZz0a7ew6zHIhBa72hvbo CI3j/lOiQD+odNy6IpVlUZjGtj0kyReLeZRRxxexNUCTj37soycGkk9KB5cpfAwgjl50 VQuSrVTAx04LCw7pfOBNTVO5G/Np41JlVmzX41zsoutQaBWzClRFBIcTAkSFjEyjvm6l xL5YhT9N5uU5Z2U/L0d9qWf9RkrH2ap7g5UjbqzP3VIyAEVeIaBRgZ5UIg+MrM9CP00N vJtw== X-Gm-Message-State: ACgBeo0y9K2JPMzX4pzpZyGHuNw5LYAoO0L9vwzT7f46nBOORbAA7Bcd AiCeC0LDtpo2hDXRt8ZGy7prI6h6YWhtBDMlP5E= X-Google-Smtp-Source: AA6agR640HtrJqd29TAtza1TR3abwiONCXKJNZcT4pnGkQXApee/Nz3p0hX/k1UDhvt39MX7rwpo7doEhc7Kfb/4tyw= X-Received: by 2002:a81:b655:0:b0:328:316c:6916 with SMTP id h21-20020a81b655000000b00328316c6916mr4601403ywk.66.1660319379240; Fri, 12 Aug 2022 08:49:39 -0700 (PDT) MIME-Version: 1.0 References: <20220708195445.4geva763r5vbpglo@alvherre.pgsql> <50a488b1-aea8-5934-85a0-95a532f73800@enterprisedb.com> In-Reply-To: From: Temuri Doghonadze Date: Fri, 12 Aug 2022 17:49:27 +0200 Message-ID: Subject: Re: Re[2]: Georgian translation - initial To: Pavlo Golub Cc: Peter Eisentraut , Ekaterine Papava , Alvaro Herrera , pgsql-translators@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, it's not about wording, it's abut several words having the same meaning in Georgian, to express it as simple as I can. There are a lot of dictionaries which I use, but it's simple not there, or has different meaning. P.S. For some reason I somehow managed to buy poedit license, so MS translate/dictionary are available. You don't want to know how much nonsense it's putting on table.. Temuri On Fri, Aug 12, 2022 at 5:43 PM Pavlo Golub wrote: > > >Hello, > >Here's another update to Georgian translation, did my best to bring > >all files (except postgres.po) to 80+% . > >Since there are not much technical words in Georgian, I don't want to > >go further for now, until I'll get clue how to translate remaining > >files. > If you have any difficulties during translation I would recommend to use > Microsoft Terminology Search. It has a great vocabulary and not only for > database terms, e.g. > "table" in Georgian would be: > https://www.microsoft.com/en-us/language/Search?&searchTerm=3Dtable&langI= D=3D350&Source=3Dtrue&productid=3D0 > > > > > > >Including Ekaterine, since she's the only one (that I know) who can > >help if there will be anything wrong and I'll be unavailable. > > > >BR, Temuri > > > >On Tue, Jul 19, 2022 at 7:04 AM Peter Eisentraut > > wrote: > >> > >>On 18.07.22 15:43, Temuri Doghonadze wrote: > >> > Hello, > >> > Here's another update for PostgreSQL 15 Georgian translation. > >> > >>committed > >> > >> > > >> > Temuri > >> > > >> > On Fri, Jul 8, 2022 at 10:13 PM Temuri Doghonadze > >> > wrote: > >> >> > >> >> Thans for info. > >> >> > >> >> On Fri, Jul 8, 2022 at 9:54 PM Alvaro Herrera wrote: > >> >>> > >> >>> On 2022-Jul-08, Temuri Doghonadze wrote: > >> >>> > >> >>>> Quick question. How does it work with different types of output? = Is > >> >>>> %Ns for "%s" only or does it apply to all kind of printf output? > >> >>> > >> >>> It applies to all of them. You need to match the type used for ea= ch > >> >>> argument. This is probably documented somewhere ... ah, right: > >> >>> https://www.postgresql.org/docs/15/nls-translator.html#id-1.10.7.2= .6 > >> >>> > >> >>> Also, I think if you use the $ designator for any argument in a me= ssage, > >> >>> then all arguments have to use it in that message. This appears i= n the > >> >>> printf(3) manpage, at least glibc's. > >> >>> > >> >>> -- > >> >>> =C3=81lvaro Herrera PostgreSQL Developer =E2=80=94 https= ://www.EnterpriseDB.com/ > >> >