Re: Remove INT64_FORMAT in translatable strings - Mailing list pgsql-hackers

From Japin Li
Subject Re: Remove INT64_FORMAT in translatable strings
Date
Msg-id MEYP282MB1669B6076C4D1E9421E4E8ADB6139@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Remove INT64_FORMAT in translatable strings  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, 19 Mar 2022 at 01:12, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Japin Li <japinli@hotmail.com> writes:
>> we can rely on %lld/%llu and we decided to use them in translatable strings.
>
> Seems like good cleanup, so pushed.  I think though that project style
> is to use "long long" or "unsigned long long", without the unnecessary
> "int" --- it certainly makes little sense to do it both ways in the
> same patch.
>
>> However, I am not sure how to update the *.po files under the pg_dump/po
>> directory. Any suggestions?
>
> The translation team manages those files.  We don't normally touch them
> during code development.
>

Thank you for pushing the patch.


--
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.



pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Re: Support logical replication of DDLs
Next
From: Andres Freund
Date:
Subject: Re: pg_walinspect - a new extension to get raw WAL data and WAL stats