[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#65424: Guix doesn't use positional arguments in translated formatted
From: |
Maxime Devos |
Subject: |
bug#65424: Guix doesn't use positional arguments in translated formatted messages |
Date: |
Mon, 21 Aug 2023 14:09:14 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 |
Consider, e.g.,
(format #t (G_ "~0@*~a should be set to ~1@*~a instead of ~2@*~a~%")
"CC" "(cc-for-target)" "gcc")
->
CC should be set to (cc-for-target) instead of gcc
By using positional arguments like this, translators can reorder the
sentence to:
(format #t (G_ "It's not ~2@*~a that ~0@*~a should be set to, but
~1@*~a~%") "CC" (cc-for-target) "gcc"))
~0@*~a should be set to ~1@*~a instead of ~2@*~a~%") "CC"
"(cc-for-target)" "gcc")
->
It's not gcc that CC should be set to, but (cc-for-target).
CC should be set to (cc-for-target) instead of gcc
Such reorderings are occasionally useful, yet AFAIK nowhere (except
po/guix/ta.po, the mcron service and de.po) is this used.
Sure, you could as translator add these ~N@* afterwards, but you need to
know that's possible in the first place (and if you know it's possible,
you still need to remember or rediscover what exactly to write), and it
would be much simpler and more discoverable if they were included from
the start. Also, IIRC, Weblate complains if you add these.
p.s.: I'm writing a new linter, this particular example doesn't occur
yet in Guix.
OpenPGP_0x49E3EE22191725EE.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
- bug#65424: Guix doesn't use positional arguments in translated formatted messages,
Maxime Devos <=