Re: Georgian translation - initial

Hello,
Here are initial translation files for v15 and v14 in Georgian.
Hepefully, update will follow soon.

Temuri

On 06.07.22 10:47, Temuri Doghonadze wrote:
> Here are initial translation files for v15 and v14 in Georgian.
> Hepefully, update will follow soon.

I have committed the v15 set for now.

We don't usually put entirely new translations into stable branches.
But we could consider that at some point. Let's work on the v15 first.

Hi,

Sure, I still got a lot of work to do.
Thanks for submit.
Will come back once I'll have new files.

Temuri

On Wed, Jul 6, 2022 at 3:15 PM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>
> On 06.07.22 10:47, Temuri Doghonadze wrote:
> > Here are initial translation files for v15 and v14 in Georgian.
> > Hepefully, update will follow soon.
>
> I have committed the v15 set for now.
>
> We don't usually put entirely new translations into stable branches.
> But we could consider that at some point. Let's work on the v15 first.

Hi,
Update for Georgian translation is here. Finished some, another 7% of
postgres.po is done.

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?

Temuri

On Wed, Jul 6, 2022 at 3:46 PM Temuri Doghonadze
<temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>
> Hi,
>
> Sure, I still got a lot of work to do.
> Thanks for submit.
> Will come back once I'll have new files.
>
> Temuri
>
> On Wed, Jul 6, 2022 at 3:15 PM Peter Eisentraut
> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> >
> > On 06.07.22 10:47, Temuri Doghonadze wrote:
> > > Here are initial translation files for v15 and v14 in Georgian.
> > > Hepefully, update will follow soon.
> >
> > I have committed the v15 set for now.
> >
> > We don't usually put entirely new translations into stable branches.
> > But we could consider that at some point. Let's work on the v15 first.

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/

Hi!,
Now, that's beautiful!
Thank you for hint!

Temuri

On Fri, Jul 8, 2022 at 4:36 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> 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/

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?

On Fri, Jul 8, 2022 at 4:49 PM Temuri Doghonadze
<temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>
> Hi!,
> Now, that's beautiful!
> Thank you for hint!
>
> Temuri
>
> On Fri, Jul 8, 2022 at 4:36 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> >
> > 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/

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 each
argument. This is probably documented somewhere ... ah, right:
/docs/15/nls-translator.html#id-1.10.7.2.6

Also, I think if you use the $ designator for any argument in a message,
then all arguments have to use it in that message. This appears in the
printf(3) manpage, at least glibc's.

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/

Thans for info.

On Fri, Jul 8, 2022 at 9:54 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> 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 each
> argument. This is probably documented somewhere ... ah, right:
> /docs/15/nls-translator.html#id-1.10.7.2.6
>
> Also, I think if you use the $ designator for any argument in a message,
> then all arguments have to use it in that message. This appears in the
> printf(3) manpage, at least glibc's.
>
> --
> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/

Hello,
Here's another update for PostgreSQL 15 Georgian translation.

Temuri

On Fri, Jul 8, 2022 at 10:13 PM Temuri Doghonadze
<temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>
> Thans for info.
>
> On Fri, Jul 8, 2022 at 9:54 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> 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 each
> > argument. This is probably documented somewhere ... ah, right:
> > /docs/15/nls-translator.html#id-1.10.7.2.6
> >
> > Also, I think if you use the $ designator for any argument in a message,
> > then all arguments have to use it in that message. This appears in the
> > printf(3) manpage, at least glibc's.
> >
> > --
> > Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/

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
> <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>>
>> Thans for info.
>>
>> On Fri, Jul 8, 2022 at 9:54 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> 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 each
>>> argument. This is probably documented somewhere ... ah, right:
>>> /docs/15/nls-translator.html#id-1.10.7.2.6
>>>
>>> Also, I think if you use the $ designator for any argument in a message,
>>> then all arguments have to use it in that message. This appears in the
>>> printf(3) manpage, at least glibc's.
>>>
>>> --
>>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/

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.

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
<peter(dot)eisentraut(at)enterprisedb(dot)com> 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
> > <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> >>
> >> Thans for info.
> >>
> >> On Fri, Jul 8, 2022 at 9:54 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> 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 each
> >>> argument. This is probably documented somewhere ... ah, right:
> >>> /docs/15/nls-translator.html#id-1.10.7.2.6
> >>>
> >>> Also, I think if you use the $ designator for any argument in a message,
> >>> then all arguments have to use it in that message. This appears in the
> >>> printf(3) manpage, at least glibc's.
> >>>
> >>> --
> >>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
>

>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=table&langID=350&Source=true&productid=0

>
>
>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
><peter(dot)eisentraut(at)enterprisedb(dot)com> 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
>> > <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>> >>
>> >> Thans for info.
>> >>
>> >> On Fri, Jul 8, 2022 at 9:54 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> 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 each
>> >>> argument. This is probably documented somewhere ... ah, right:
>> >>> /docs/15/nls-translator.html#id-1.10.7.2.6
>> >>>
>> >>> Also, I think if you use the $ designator for any argument in a message,
>> >>> then all arguments have to use it in that message. This appears in the
>> >>> printf(3) manpage, at least glibc's.
>> >>>
>> >>> --
>> >>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
>>

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 <pavlo(dot)golub(at)gmail(dot)com> 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=table&langID=350&Source=true&productid=0
>
> >
> >
> >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
> ><peter(dot)eisentraut(at)enterprisedb(dot)com> 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
> >> > <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> >> >>
> >> >> Thans for info.
> >> >>
> >> >> On Fri, Jul 8, 2022 at 9:54 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> 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 each
> >> >>> argument. This is probably documented somewhere ... ah, right:
> >> >>> /docs/15/nls-translator.html#id-1.10.7.2.6
> >> >>>
> >> >>> Also, I think if you use the $ designator for any argument in a message,
> >> >>> then all arguments have to use it in that message. This appears in the
> >> >>> printf(3) manpage, at least glibc's.
> >> >>>
> >> >>> --
> >> >>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
> >>
>

@Pavlo Golub
Could you please add Georgian on crowdin PostgreSQL project page, so
I'll stop asking for uploading files every second week?

Temuri

On Fri, Aug 12, 2022 at 5:49 PM Temuri Doghonadze
<temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>
> 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 <pavlo(dot)golub(at)gmail(dot)com> 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=table&langID=350&Source=true&productid=0
> >
> > >
> > >
> > >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
> > ><peter(dot)eisentraut(at)enterprisedb(dot)com> 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
> > >> > <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> > >> >>
> > >> >> Thans for info.
> > >> >>
> > >> >> On Fri, Jul 8, 2022 at 9:54 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> 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 each
> > >> >>> argument. This is probably documented somewhere ... ah, right:
> > >> >>> /docs/15/nls-translator.html#id-1.10.7.2.6
> > >> >>>
> > >> >>> Also, I think if you use the $ designator for any argument in a message,
> > >> >>> then all arguments have to use it in that message. This appears in the
> > >> >>> printf(3) manpage, at least glibc's.
> > >> >>>
> > >> >>> --
> > >> >>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
> > >>
> >

On Sun, Aug 14, 2022, 13:05 Temuri Doghonadze <temuri(dot)doghonadze(at)gmail(dot)com>
wrote:

> @Pavlo Golub
> Could you please add Georgian on crowdin PostgreSQL project page, so
> I'll stop asking for uploading files every second week?
>

Sure, i can add it. But the thing is there is no automatic updates from
crowdin to babel still.

So the uploading task is still on the translator :-(

> Temuri
>
> On Fri, Aug 12, 2022 at 5:49 PM Temuri Doghonadze
> <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> >
> > 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 <pavlo(dot)golub(at)gmail(dot)com>
> 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=table&langID=350&Source=true&productid=0
> > >
> > > >
> > > >
> > > >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
> > > ><peter(dot)eisentraut(at)enterprisedb(dot)com> 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
> > > >> > <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> > > >> >>
> > > >> >> Thans for info.
> > > >> >>
> > > >> >> On Fri, Jul 8, 2022 at 9:54 PM Alvaro Herrera <
> alvherre(at)alvh(dot)no-ip(dot)org> 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
> each
> > > >> >>> argument. This is probably documented somewhere ... ah, right:
> > > >> >>>
> /docs/15/nls-translator.html#id-1.10.7.2.6
> > > >> >>>
> > > >> >>> Also, I think if you use the $ designator for any argument in a
> message,
> > > >> >>> then all arguments have to use it in that message. This
> appears in the
> > > >> >>> printf(3) manpage, at least glibc's.
> > > >> >>>
> > > >> >>> --
> > > >> >>> Álvaro Herrera PostgreSQL Developer —
> https://www.EnterpriseDB.com/
> > > >>
> > >
>

no problem at all, will do.

On Sun, Aug 14, 2022 at 1:15 PM Pavlo Golub <pavlo(dot)golub(at)gmail(dot)com> wrote:
>
>
>
> On Sun, Aug 14, 2022, 13:05 Temuri Doghonadze <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>>
>> @Pavlo Golub
>> Could you please add Georgian on crowdin PostgreSQL project page, so
>> I'll stop asking for uploading files every second week?
>
>
> Sure, i can add it. But the thing is there is no automatic updates from crowdin to babel still.
>
> So the uploading task is still on the translator :-(
>
>
>>
>> Temuri
>>
>> On Fri, Aug 12, 2022 at 5:49 PM Temuri Doghonadze
>> <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>> >
>> > 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 <pavlo(dot)golub(at)gmail(dot)com> 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=table&langID=350&Source=true&productid=0
>> > >
>> > > >
>> > > >
>> > > >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
>> > > ><peter(dot)eisentraut(at)enterprisedb(dot)com> 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
>> > > >> > <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>> > > >> >>
>> > > >> >> Thans for info.
>> > > >> >>
>> > > >> >> On Fri, Jul 8, 2022 at 9:54 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> 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 each
>> > > >> >>> argument. This is probably documented somewhere ... ah, right:
>> > > >> >>> /docs/15/nls-translator.html#id-1.10.7.2.6
>> > > >> >>>
>> > > >> >>> Also, I think if you use the $ designator for any argument in a message,
>> > > >> >>> then all arguments have to use it in that message. This appears in the
>> > > >> >>> printf(3) manpage, at least glibc's.
>> > > >> >>>
>> > > >> >>> --
>> > > >> >>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
>> > > >>
>> > >

@Alvaro Herrera Could you please submit files from prev. email, please?

Thanks.

Temuri

On Sun, Aug 14, 2022 at 1:17 PM Temuri Doghonadze
<temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>
> no problem at all, will do.
>
> On Sun, Aug 14, 2022 at 1:15 PM Pavlo Golub <pavlo(dot)golub(at)gmail(dot)com> wrote:
> >
> >
> >
> > On Sun, Aug 14, 2022, 13:05 Temuri Doghonadze <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> >>
> >> @Pavlo Golub
> >> Could you please add Georgian on crowdin PostgreSQL project page, so
> >> I'll stop asking for uploading files every second week?
> >
> >
> > Sure, i can add it. But the thing is there is no automatic updates from crowdin to babel still.
> >
> > So the uploading task is still on the translator :-(
> >
> >
> >>
> >> Temuri
> >>
> >> On Fri, Aug 12, 2022 at 5:49 PM Temuri Doghonadze
> >> <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> >> >
> >> > 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 <pavlo(dot)golub(at)gmail(dot)com> 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=table&langID=350&Source=true&productid=0
> >> > >
> >> > > >
> >> > > >
> >> > > >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
> >> > > ><peter(dot)eisentraut(at)enterprisedb(dot)com> 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
> >> > > >> > <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> >> > > >> >>
> >> > > >> >> Thans for info.
> >> > > >> >>
> >> > > >> >> On Fri, Jul 8, 2022 at 9:54 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> 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 each
> >> > > >> >>> argument. This is probably documented somewhere ... ah, right:
> >> > > >> >>> /docs/15/nls-translator.html#id-1.10.7.2.6
> >> > > >> >>>
> >> > > >> >>> Also, I think if you use the $ designator for any argument in a message,
> >> > > >> >>> then all arguments have to use it in that message. This appears in the
> >> > > >> >>> printf(3) manpage, at least glibc's.
> >> > > >> >>>
> >> > > >> >>> --
> >> > > >> >>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
> >> > > >>
> >> > >

On 2022-Aug-17, Temuri Doghonadze wrote:

> @Alvaro Herrera Could you please submit files from prev. email, please?

Done. I also updated the file headers, naming you as first translator,
and copying the "Language-Team: Georgian <nothing>" from your psql.po.
Do you want to find another email address to use as language team? It
could be this list, pgsql-translators(at)lists(dot)postgresql(dot)org, if you don't
have anything better.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"La persona que no quería pecar / estaba obligada a sentarse
en duras y empinadas sillas / desprovistas, por cierto
de blandos atenuantes" (Patricio Vogel)

Thanks. Yep, suggested email is OK.

Temuri

On Wed, Aug 17, 2022 at 8:33 AM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> On 2022-Aug-17, Temuri Doghonadze wrote:
>
> > @Alvaro Herrera Could you please submit files from prev. email, please?
>
> Done. I also updated the file headers, naming you as first translator,
> and copying the "Language-Team: Georgian <nothing>" from your psql.po.
> Do you want to find another email address to use as language team? It
> could be this list, pgsql-translators(at)lists(dot)postgresql(dot)org, if you don't
> have anything better.
>
> --
> Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
> "La persona que no quería pecar / estaba obligada a sentarse
> en duras y empinadas sillas / desprovistas, por cierto
> de blandos atenuantes" (Patricio Vogel)

On 2022-Jul-06, Temuri Doghonadze wrote:

> Hello,
> Here are initial translation files for v15 and v14 in Georgian.
> Hepefully, update will follow soon.

Hello. Did you have time for more? Tomorrow the RC1 for 15 is tagged,
so if you have an update, this is a great time to submit it.

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"La conclusión que podemos sacar de esos estudios es que
no podemos sacar ninguna conclusión de ellos" (Tanenbaum)

Hello,
Here's latest update.

BR, Temuri

On Sun, Sep 25, 2022 at 5:35 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> On 2022-Jul-06, Temuri Doghonadze wrote:
>
> > Hello,
> > Here are initial translation files for v15 and v14 in Georgian.
> > Hepefully, update will follow soon.
>
> Hello. Did you have time for more? Tomorrow the RC1 for 15 is tagged,
> so if you have an update, this is a great time to submit it.
>
> --
> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
> "La conclusión que podemos sacar de esos estudios es que
> no podemos sacar ninguna conclusión de ellos" (Tanenbaum)

On 2022-Sep-25, Temuri Doghonadze wrote:

> Hello,
> Here's latest update.

Cool, thanks, applied.

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/

Hi,
I've applied latest pot files and made small corrections in files attached.
Sorry for inconvinence.

Temuri

On Sun, Sep 25, 2022 at 9:36 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> On 2022-Sep-25, Temuri Doghonadze wrote:
>
> > Hello,
> > Here's latest update.
>
> Cool, thanks, applied.
>
>
> --
> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/

On 25.09.22 22:24, Temuri Doghonadze wrote:
> Hi,
> I've applied latest pot files and made small corrections in files attached.
> Sorry for inconvinence.

committed

>
> Temuri
>
> On Sun, Sep 25, 2022 at 9:36 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>>
>> On 2022-Sep-25, Temuri Doghonadze wrote:
>>
>>> Hello,
>>> Here's latest update.
>>
>> Cool, thanks, applied.
>>
>>
>> --
>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/

Hello,
Here's complete translations for plpgsql.po, pg_upgrade.po and
pg_dump.po to Georgian

Temuri

On Mon, Sep 26, 2022 at 8:54 AM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>
> On 25.09.22 22:24, Temuri Doghonadze wrote:
> > Hi,
> > I've applied latest pot files and made small corrections in files attached.
> > Sorry for inconvinence.
>
> committed
>
> >
> > Temuri
> >
> > On Sun, Sep 25, 2022 at 9:36 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> >>
> >> On 2022-Sep-25, Temuri Doghonadze wrote:
> >>
> >>> Hello,
> >>> Here's latest update.
> >>
> >> Cool, thanks, applied.
> >>
> >>
> >> --
> >> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
>

kind reminder :)

On Sat, Oct 15, 2022 at 8:13 PM Temuri Doghonadze
<temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>
> Hello,
> Here's complete translations for plpgsql.po, pg_upgrade.po and
> pg_dump.po to Georgian
>
> Temuri
>
> On Mon, Sep 26, 2022 at 8:54 AM Peter Eisentraut
> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> >
> > On 25.09.22 22:24, Temuri Doghonadze wrote:
> > > Hi,
> > > I've applied latest pot files and made small corrections in files attached.
> > > Sorry for inconvinence.
> >
> > committed
> >
> > >
> > > Temuri
> > >
> > > On Sun, Sep 25, 2022 at 9:36 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> > >>
> > >> On 2022-Sep-25, Temuri Doghonadze wrote:
> > >>
> > >>> Hello,
> > >>> Here's latest update.
> > >>
> > >> Cool, thanks, applied.
> > >>
> > >>
> > >> --
> > >> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
> >

On 04.11.22 02:25, Temuri Doghonadze wrote:
> kind reminder :)

committed

>
> On Sat, Oct 15, 2022 at 8:13 PM Temuri Doghonadze
> <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>>
>> Hello,
>> Here's complete translations for plpgsql.po, pg_upgrade.po and
>> pg_dump.po to Georgian
>>
>> Temuri
>>
>> On Mon, Sep 26, 2022 at 8:54 AM Peter Eisentraut
>> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>>>
>>> On 25.09.22 22:24, Temuri Doghonadze wrote:
>>>> Hi,
>>>> I've applied latest pot files and made small corrections in files attached.
>>>> Sorry for inconvinence.
>>>
>>> committed
>>>
>>>>
>>>> Temuri
>>>>
>>>> On Sun, Sep 25, 2022 at 9:36 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>>>>>
>>>>> On 2022-Sep-25, Temuri Doghonadze wrote:
>>>>>
>>>>>> Hello,
>>>>>> Here's latest update.
>>>>>
>>>>> Cool, thanks, applied.
>>>>>
>>>>>
>>>>> --
>>>>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
>>>
>
>

Hello,
Here's update for Georgian translation.

Temuri

On Fri, Nov 4, 2022 at 4:35 PM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>
> On 04.11.22 02:25, Temuri Doghonadze wrote:
> > kind reminder :)
>
> committed
>
> >
> > On Sat, Oct 15, 2022 at 8:13 PM Temuri Doghonadze
> > <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> >>
> >> Hello,
> >> Here's complete translations for plpgsql.po, pg_upgrade.po and
> >> pg_dump.po to Georgian
> >>
> >> Temuri
> >>
> >> On Mon, Sep 26, 2022 at 8:54 AM Peter Eisentraut
> >> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> >>>
> >>> On 25.09.22 22:24, Temuri Doghonadze wrote:
> >>>> Hi,
> >>>> I've applied latest pot files and made small corrections in files attached.
> >>>> Sorry for inconvinence.
> >>>
> >>> committed
> >>>
> >>>>
> >>>> Temuri
> >>>>
> >>>> On Sun, Sep 25, 2022 at 9:36 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> >>>>>
> >>>>> On 2022-Sep-25, Temuri Doghonadze wrote:
> >>>>>
> >>>>>> Hello,
> >>>>>> Here's latest update.
> >>>>>
> >>>>> Cool, thanks, applied.
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
> >>>
> >
> >
>

Hello,
Kind reminder.

Temuri

On Mon, Mar 27, 2023 at 7:22 AM Temuri Doghonadze
<temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>
> Hello,
> Here's update for Georgian translation.
>
> Temuri
>
> On Fri, Nov 4, 2022 at 4:35 PM Peter Eisentraut
> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> >
> > On 04.11.22 02:25, Temuri Doghonadze wrote:
> > > kind reminder :)
> >
> > committed
> >
> > >
> > > On Sat, Oct 15, 2022 at 8:13 PM Temuri Doghonadze
> > > <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> > >>
> > >> Hello,
> > >> Here's complete translations for plpgsql.po, pg_upgrade.po and
> > >> pg_dump.po to Georgian
> > >>
> > >> Temuri
> > >>
> > >> On Mon, Sep 26, 2022 at 8:54 AM Peter Eisentraut
> > >> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> > >>>
> > >>> On 25.09.22 22:24, Temuri Doghonadze wrote:
> > >>>> Hi,
> > >>>> I've applied latest pot files and made small corrections in files attached.
> > >>>> Sorry for inconvinence.
> > >>>
> > >>> committed
> > >>>
> > >>>>
> > >>>> Temuri
> > >>>>
> > >>>> On Sun, Sep 25, 2022 at 9:36 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> > >>>>>
> > >>>>> On 2022-Sep-25, Temuri Doghonadze wrote:
> > >>>>>
> > >>>>>> Hello,
> > >>>>>> Here's latest update.
> > >>>>>
> > >>>>> Cool, thanks, applied.
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
> > >>>
> > >
> > >
> >

committed

On 11.04.23 15:39, Temuri Doghonadze wrote:
> Hello,
> Kind reminder.
>
> Temuri
>
> On Mon, Mar 27, 2023 at 7:22 AM Temuri Doghonadze
> <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>>
>> Hello,
>> Here's update for Georgian translation.
>>
>> Temuri
>>
>> On Fri, Nov 4, 2022 at 4:35 PM Peter Eisentraut
>> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>>>
>>> On 04.11.22 02:25, Temuri Doghonadze wrote:
>>>> kind reminder :)
>>>
>>> committed
>>>
>>>>
>>>> On Sat, Oct 15, 2022 at 8:13 PM Temuri Doghonadze
>>>> <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>>>>>
>>>>> Hello,
>>>>> Here's complete translations for plpgsql.po, pg_upgrade.po and
>>>>> pg_dump.po to Georgian
>>>>>
>>>>> Temuri
>>>>>
>>>>> On Mon, Sep 26, 2022 at 8:54 AM Peter Eisentraut
>>>>> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>>>>>>
>>>>>> On 25.09.22 22:24, Temuri Doghonadze wrote:
>>>>>>> Hi,
>>>>>>> I've applied latest pot files and made small corrections in files attached.
>>>>>>> Sorry for inconvinence.
>>>>>>
>>>>>> committed
>>>>>>
>>>>>>>
>>>>>>> Temuri
>>>>>>>
>>>>>>> On Sun, Sep 25, 2022 at 9:36 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>>>>>>>>
>>>>>>>> On 2022-Sep-25, Temuri Doghonadze wrote:
>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>> Here's latest update.
>>>>>>>>
>>>>>>>> Cool, thanks, applied.
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
>>>>>>
>>>>
>>>>
>>>
>
>

Hi,
Here's translation update for master branch, Georgian language

Temuri

On Tue, Apr 11, 2023 at 3:39 PM Temuri Doghonadze
<temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>
> Hello,
> Kind reminder.
>
> Temuri
>
> On Mon, Mar 27, 2023 at 7:22 AM Temuri Doghonadze
> <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> >
> > Hello,
> > Here's update for Georgian translation.
> >
> > Temuri
> >
> > On Fri, Nov 4, 2022 at 4:35 PM Peter Eisentraut
> > <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> > >
> > > On 04.11.22 02:25, Temuri Doghonadze wrote:
> > > > kind reminder :)
> > >
> > > committed
> > >
> > > >
> > > > On Sat, Oct 15, 2022 at 8:13 PM Temuri Doghonadze
> > > > <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> > > >>
> > > >> Hello,
> > > >> Here's complete translations for plpgsql.po, pg_upgrade.po and
> > > >> pg_dump.po to Georgian
> > > >>
> > > >> Temuri
> > > >>
> > > >> On Mon, Sep 26, 2022 at 8:54 AM Peter Eisentraut
> > > >> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> > > >>>
> > > >>> On 25.09.22 22:24, Temuri Doghonadze wrote:
> > > >>>> Hi,
> > > >>>> I've applied latest pot files and made small corrections in files attached.
> > > >>>> Sorry for inconvinence.
> > > >>>
> > > >>> committed
> > > >>>
> > > >>>>
> > > >>>> Temuri
> > > >>>>
> > > >>>> On Sun, Sep 25, 2022 at 9:36 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> > > >>>>>
> > > >>>>> On 2022-Sep-25, Temuri Doghonadze wrote:
> > > >>>>>
> > > >>>>>> Hello,
> > > >>>>>> Here's latest update.
> > > >>>>>
> > > >>>>> Cool, thanks, applied.
> > > >>>>>
> > > >>>>>
> > > >>>>> --
> > > >>>>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
> > > >>>
> > > >
> > > >
> > >

On 20.04.23 10:54, Temuri Doghonadze wrote:
> Hi,
> Here's translation update for master branch, Georgian language

committed

>
> Temuri
>
> On Tue, Apr 11, 2023 at 3:39 PM Temuri Doghonadze
> <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>>
>> Hello,
>> Kind reminder.
>>
>> Temuri
>>
>> On Mon, Mar 27, 2023 at 7:22 AM Temuri Doghonadze
>> <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>>>
>>> Hello,
>>> Here's update for Georgian translation.
>>>
>>> Temuri
>>>
>>> On Fri, Nov 4, 2022 at 4:35 PM Peter Eisentraut
>>> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>>>>
>>>> On 04.11.22 02:25, Temuri Doghonadze wrote:
>>>>> kind reminder :)
>>>>
>>>> committed
>>>>
>>>>>
>>>>> On Sat, Oct 15, 2022 at 8:13 PM Temuri Doghonadze
>>>>> <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
>>>>>>
>>>>>> Hello,
>>>>>> Here's complete translations for plpgsql.po, pg_upgrade.po and
>>>>>> pg_dump.po to Georgian
>>>>>>
>>>>>> Temuri
>>>>>>
>>>>>> On Mon, Sep 26, 2022 at 8:54 AM Peter Eisentraut
>>>>>> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>>>>>>>
>>>>>>> On 25.09.22 22:24, Temuri Doghonadze wrote:
>>>>>>>> Hi,
>>>>>>>> I've applied latest pot files and made small corrections in files attached.
>>>>>>>> Sorry for inconvinence.
>>>>>>>
>>>>>>> committed
>>>>>>>
>>>>>>>>
>>>>>>>> Temuri
>>>>>>>>
>>>>>>>> On Sun, Sep 25, 2022 at 9:36 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>>>>>>>>>
>>>>>>>>> On 2022-Sep-25, Temuri Doghonadze wrote:
>>>>>>>>>
>>>>>>>>>> Hello,
>>>>>>>>>> Here's latest update.
>>>>>>>>>
>>>>>>>>> Cool, thanks, applied.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
>>>>>>>
>>>>>
>>>>>
>>>>

Hello,
I think on https://babel.postgresql.org/ master branch is no longer
synced with real po/pot files.
Very first initdb.po file has 189 lines, while .pot file has 189 lines
too, makes .po file 100% translated, but website shows it in yellow
anyway.
Could you please advise where to get updated pot/po files?

Thanks you in advance.

On Fri, Apr 21, 2023 at 6:07 PM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>
> On 20.04.23 10:54, Temuri Doghonadze wrote:
> > Hi,
> > Here's translation update for master branch, Georgian language
>
> committed
>
> >
> > Temuri
> >
> > On Tue, Apr 11, 2023 at 3:39 PM Temuri Doghonadze
> > <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> >>
> >> Hello,
> >> Kind reminder.
> >>
> >> Temuri
> >>
> >> On Mon, Mar 27, 2023 at 7:22 AM Temuri Doghonadze
> >> <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> >>>
> >>> Hello,
> >>> Here's update for Georgian translation.
> >>>
> >>> Temuri
> >>>
> >>> On Fri, Nov 4, 2022 at 4:35 PM Peter Eisentraut
> >>> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> >>>>
> >>>> On 04.11.22 02:25, Temuri Doghonadze wrote:
> >>>>> kind reminder :)
> >>>>
> >>>> committed
> >>>>
> >>>>>
> >>>>> On Sat, Oct 15, 2022 at 8:13 PM Temuri Doghonadze
> >>>>> <temuri(dot)doghonadze(at)gmail(dot)com> wrote:
> >>>>>>
> >>>>>> Hello,
> >>>>>> Here's complete translations for plpgsql.po, pg_upgrade.po and
> >>>>>> pg_dump.po to Georgian
> >>>>>>
> >>>>>> Temuri
> >>>>>>
> >>>>>> On Mon, Sep 26, 2022 at 8:54 AM Peter Eisentraut
> >>>>>> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> >>>>>>>
> >>>>>>> On 25.09.22 22:24, Temuri Doghonadze wrote:
> >>>>>>>> Hi,
> >>>>>>>> I've applied latest pot files and made small corrections in files attached.
> >>>>>>>> Sorry for inconvinence.
> >>>>>>>
> >>>>>>> committed
> >>>>>>>
> >>>>>>>>
> >>>>>>>> Temuri
> >>>>>>>>
> >>>>>>>> On Sun, Sep 25, 2022 at 9:36 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> >>>>>>>>>
> >>>>>>>>> On 2022-Sep-25, Temuri Doghonadze wrote:
> >>>>>>>>>
> >>>>>>>>>> Hello,
> >>>>>>>>>> Here's latest update.
> >>>>>>>>>
> >>>>>>>>> Cool, thanks, applied.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
> >>>>>>>
> >>>>>
> >>>>>
> >>>>
>

On 07.06.23 05:40, Temuri Doghonadze wrote:
> I think onhttps://babel.postgresql.org/ master branch is no longer
> synced with real po/pot files.
> Very first initdb.po file has 189 lines, while .pot file has 189 lines
> too, makes .po file 100% translated, but website shows it in yellow
> anyway.

The reason for this is that the files on babel are processed so that
they automatically adapt identical translation from other catalogs. For
example ka/plpython.po had a few new strings, but the same strings
already have translations in ka/plperl.po, so the file you download
already has those in it. Then the file just needs to be committed.

To demonstrate this, I just downloaded ka/initdb.po and ka/plpython.po
and committed them. So when the processing is done, these two should be
at 100%.

Hello,
Thanks for explanation.
Here's another update for main branch.
BR, Temuri

On Wed, Jun 7, 2023 at 9:13 AM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>
> On 07.06.23 05:40, Temuri Doghonadze wrote:
> > I think onhttps://babel.postgresql.org/ master branch is no longer
> > synced with real po/pot files.
> > Very first initdb.po file has 189 lines, while .pot file has 189 lines
> > too, makes .po file 100% translated, but website shows it in yellow
> > anyway.
>
> The reason for this is that the files on babel are processed so that
> they automatically adapt identical translation from other catalogs. For
> example ka/plpython.po had a few new strings, but the same strings
> already have translations in ka/plperl.po, so the file you download
> already has those in it. Then the file just needs to be committed.
>
> To demonstrate this, I just downloaded ka/initdb.po and ka/plpython.po
> and committed them. So when the processing is done, these two should be
> at 100%.

On 05.07.23 14:57, Temuri Doghonadze wrote:
> Hello,
> Thanks for explanation.
> Here's another update for main branch.

committed

> On Wed, Jun 7, 2023 at 9:13 AM Peter Eisentraut
> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>>
>> On 07.06.23 05:40, Temuri Doghonadze wrote:
>>> I think onhttps://babel.postgresql.org/ master branch is no longer
>>> synced with real po/pot files.
>>> Very first initdb.po file has 189 lines, while .pot file has 189 lines
>>> too, makes .po file 100% translated, but website shows it in yellow
>>> anyway.
>>
>> The reason for this is that the files on babel are processed so that
>> they automatically adapt identical translation from other catalogs. For
>> example ka/plpython.po had a few new strings, but the same strings
>> already have translations in ka/plperl.po, so the file you download
>> already has those in it. Then the file just needs to be committed.
>>
>> To demonstrate this, I just downloaded ka/initdb.po and ka/plpython.po
>> and committed them. So when the processing is done, these two should be
>> at 100%.

Hello,
Here's another update of 16 branch.
Temuri

On Fri, Jul 7, 2023 at 2:47 PM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>
> On 05.07.23 14:57, Temuri Doghonadze wrote:
> > Hello,
> > Thanks for explanation.
> > Here's another update for main branch.
>
> committed
>
> > On Wed, Jun 7, 2023 at 9:13 AM Peter Eisentraut
> > <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> >>
> >> On 07.06.23 05:40, Temuri Doghonadze wrote:
> >>> I think onhttps://babel.postgresql.org/ master branch is no longer
> >>> synced with real po/pot files.
> >>> Very first initdb.po file has 189 lines, while .pot file has 189 lines
> >>> too, makes .po file 100% translated, but website shows it in yellow
> >>> anyway.
> >>
> >> The reason for this is that the files on babel are processed so that
> >> they automatically adapt identical translation from other catalogs. For
> >> example ka/plpython.po had a few new strings, but the same strings
> >> already have translations in ka/plperl.po, so the file you download
> >> already has those in it. Then the file just needs to be committed.
> >>
> >> To demonstrate this, I just downloaded ka/initdb.po and ka/plpython.po
> >> and committed them. So when the processing is done, these two should be
> >> at 100%.
>

On 07.08.23 10:07, Temuri Doghonadze wrote:
> Hello,
> Here's another update of 16 branch.
> Temuri

committed

>
> On Fri, Jul 7, 2023 at 2:47 PM Peter Eisentraut
> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>>
>> On 05.07.23 14:57, Temuri Doghonadze wrote:
>>> Hello,
>>> Thanks for explanation.
>>> Here's another update for main branch.
>>
>> committed
>>
>>> On Wed, Jun 7, 2023 at 9:13 AM Peter Eisentraut
>>> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>>>>
>>>> On 07.06.23 05:40, Temuri Doghonadze wrote:
>>>>> I think onhttps://babel.postgresql.org/ master branch is no longer
>>>>> synced with real po/pot files.
>>>>> Very first initdb.po file has 189 lines, while .pot file has 189 lines
>>>>> too, makes .po file 100% translated, but website shows it in yellow
>>>>> anyway.
>>>>
>>>> The reason for this is that the files on babel are processed so that
>>>> they automatically adapt identical translation from other catalogs. For
>>>> example ka/plpython.po had a few new strings, but the same strings
>>>> already have translations in ka/plperl.po, so the file you download
>>>> already has those in it. Then the file just needs to be committed.
>>>>
>>>> To demonstrate this, I just downloaded ka/initdb.po and ka/plpython.po
>>>> and committed them. So when the processing is done, these two should be
>>>> at 100%.
>>

Hello,
Here's update for both 15 and 16 branches, Georgian translation.

Temuri

On Fri, Aug 11, 2023 at 8:00 PM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> On 07.08.23 10:07, Temuri Doghonadze wrote:
> > Hello,
> > Here's another update of 16 branch.
> > Temuri
>
> committed
>
> >
> > On Fri, Jul 7, 2023 at 2:47 PM Peter Eisentraut
> > <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> >>
> >> On 05.07.23 14:57, Temuri Doghonadze wrote:
> >>> Hello,
> >>> Thanks for explanation.
> >>> Here's another update for main branch.
> >>
> >> committed
> >>
> >>> On Wed, Jun 7, 2023 at 9:13 AM Peter Eisentraut
> >>> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> >>>>
> >>>> On 07.06.23 05:40, Temuri Doghonadze wrote:
> >>>>> I think onhttps://babel.postgresql.org/ master branch is no longer
> >>>>> synced with real po/pot files.
> >>>>> Very first initdb.po file has 189 lines, while .pot file has 189 lines
> >>>>> too, makes .po file 100% translated, but website shows it in yellow
> >>>>> anyway.
> >>>>
> >>>> The reason for this is that the files on babel are processed so that
> >>>> they automatically adapt identical translation from other catalogs. For
> >>>> example ka/plpython.po had a few new strings, but the same strings
> >>>> already have translations in ka/plperl.po, so the file you download
> >>>> already has those in it. Then the file just needs to be committed.
> >>>>
> >>>> To demonstrate this, I just downloaded ka/initdb.po and ka/plpython.po
> >>>> and committed them. So when the processing is done, these two should be
> >>>> at 100%.
> >>
>

On 24.08.23 11:54, Temuri Doghonadze wrote:
> Hello,
> Here's update for both 15 and 16 branches, Georgian translation.

committed

>
> Temuri
>
> On Fri, Aug 11, 2023 at 8:00 PM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>>
>> On 07.08.23 10:07, Temuri Doghonadze wrote:
>>> Hello,
>>> Here's another update of 16 branch.
>>> Temuri
>>
>> committed
>>
>>>
>>> On Fri, Jul 7, 2023 at 2:47 PM Peter Eisentraut
>>> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>>>>
>>>> On 05.07.23 14:57, Temuri Doghonadze wrote:
>>>>> Hello,
>>>>> Thanks for explanation.
>>>>> Here's another update for main branch.
>>>>
>>>> committed
>>>>
>>>>> On Wed, Jun 7, 2023 at 9:13 AM Peter Eisentraut
>>>>> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>>>>>>
>>>>>> On 07.06.23 05:40, Temuri Doghonadze wrote:
>>>>>>> I think onhttps://babel.postgresql.org/ master branch is no longer
>>>>>>> synced with real po/pot files.
>>>>>>> Very first initdb.po file has 189 lines, while .pot file has 189 lines
>>>>>>> too, makes .po file 100% translated, but website shows it in yellow
>>>>>>> anyway.
>>>>>>
>>>>>> The reason for this is that the files on babel are processed so that
>>>>>> they automatically adapt identical translation from other catalogs. For
>>>>>> example ka/plpython.po had a few new strings, but the same strings
>>>>>> already have translations in ka/plperl.po, so the file you download
>>>>>> already has those in it. Then the file just needs to be committed.
>>>>>>
>>>>>> To demonstrate this, I just downloaded ka/initdb.po and ka/plpython.po
>>>>>> and committed them. So when the processing is done, these two should be
>>>>>> at 100%.
>>>>
>>