| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Japin Li <japinli(at)hotmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Cannot find a working 64-bit integer type on Illumos |
| Date: | 2024-07-22 14:39:13 |
| Message-ID: | 8488652c-afe6-4627-8f9a-945d5a32d7bc@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 14.07.24 16:51, Tom Lane wrote:
> Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
>> On 04.07.24 03:55, Thomas Munro wrote:
>>>> Personally, I find "PRId64" pretty unreadable. "INT64_MODIFIER" wasn't
>>>> nice either, though, and following standards is good, so I'm sure I'll
>>>> get used to it.
>
>> Using PRId64 would be very beneficial because gettext understands it,
>> and so we would no longer need the various workarounds for not putting
>> INT64_FORMAT into the middle of a translated string.
>
> Uh, really? The translated strings live in /usr/share, which is
> expected to be architecture-independent, so how would they make
> that work?
Gettext has some special run-time support for this. See here:
<https://www.gnu.org/software/gettext/manual/html_node/Preparing-Strings.html#No-string-concatenation>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-07-22 14:46:29 | Re: pg_upgrade and logical replication |
| Previous Message | Alastair Turner | 2024-07-22 14:31:50 | Re: Send duration output to separate log files |