Re: Remove INT64_FORMAT in translatable strings

From: Japin Li <japinli(at)hotmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Remove INT64_FORMAT in translatable strings
Date: 2022-03-18 23:40:43
Message-ID: MEYP282MB1669B6076C4D1E9421E4E8ADB6139@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Sat, 19 Mar 2022 at 01:12, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Japin Li <japinli(at)hotmail(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-03-18 23:48:28 Re: pg_walinspect - a new extension to get raw WAL data and WAL stats
Previous Message Japin Li 2022-03-18 23:33:29 Re: Support logical replication of DDLs