Re: Remove INT64_FORMAT in translatable strings
Japin Li <japinli@hotmail.com>
From: Japin Li <japinli@hotmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2022-03-18T23:40:43Z
Lists: 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.
Commits
-
Remove workarounds for avoiding [U]INT64_FORMAT in translatable strings.
- d914eb347fcd 15.0 landed