Feedback-ID: ia2694551:Fastmail
Date: Fri, 8 Jul 2022 16:36:31 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Temuri Doghonadze <temuri.doghonadze@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
	pgsql-translators@lists.postgresql.org
Subject: Re: Georgian translation - initial
Message-ID: <20220708143631.ojyniyu54443nbxn@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAJapyA-WgXeV66DXUEa+f4x9Quh=LCnBakG+ofPCJCk2ge2a8w@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/20220708143631.ojyniyu54443nbxn%40alvherre.pgsql>
Precedence: bulk

On 2022-Jul-07, Temuri Doghonadze wrote:

> P.S. My only question, which will negative answer anyways, but I have to ask.
> Would it be possible to switch from "%s" style translations to
> $0-$1-$n-like one?
> It would give me opportunty to rearranle words in sentence to give it
> more meaning.
> I understand it's almost impossible, but anyways, is it even planned?

You can use %n$s in the translation already, even if the original
strings don't do it.  For example, we do it to rearrange phrases in this
one:

msgid "operator family \"%s\" of access method %s is missing operator(s) for types %s and %s"
msgstr "el/los operador(es) para los tipos %3$s y %4$s faltan de la familia de operadores «%1$s» de método de acceso %2$s"

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/