Re: Re[2]: Georgian translation - initial

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:
>> > > >> >>> 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 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/
>> > > >>
>> > >