On 14.07.24 16:51, Tom Lane wrote:
Peter Eisentraut <pe...@eisentraut.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>
