From: "Ludovic Courtès" <ludo@gnu.org>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: guix-devel@gnu.org, Zhu Zihao <all_but_last@163.com>
Subject: Re: Word order in Guix l10n
Date: Tue, 22 Dec 2020 16:00:35 +0100 [thread overview]
Message-ID: <871rfh28do.fsf@gnu.org> (raw)
In-Reply-To: <878s9vf0vc.fsf@systemreboot.net> (Arun Isaac's message of "Fri, 18 Dec 2020 23:33:03 +0530")
Hi,
Arun Isaac <arunisaac@systemreboot.net> skribis:
>> This looks like a real issue. I’m surprised this isn’t already
>> addressed though: after all, ‘printf’ format strings have the same
>> problem, right? How does everyone else deal with that?
>
> For C's printf format strings, gettext supports special syntax to
> specify argument order. See
> https://www.gnu.org/software/gettext/manual/html_node/c_002dformat-Flag.html
Oh, I see.
> A German example is provided on that page.
>
> "%2$d Zeichen lang ist die Zeichenkette `%1$s'"
With (ice-9 format), as has been suggested before, we should be able to
do away with the “argument jumping” syntax (info "(guile) Formatted
Output"):
(format #f "~1@*~d Zeichen lang ist die Zeichenkette `~0@*~a'" "ab" 2)
It’s a bit awkward though, in particular because we have to jump to the
previous argument (0 and 1 here instead of 1 and 2).
Does xgettext support that syntax? We’ve had troubles before with ~*.
If it does, where should we use this syntax in lieu of the simpler
forms? Everywhere?
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-12-22 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 10:53 Word order in Guix l10n Zhu Zihao
2020-12-15 12:25 ` Julien Lepiller
2020-12-18 15:04 ` Ludovic Courtès
2020-12-18 18:03 ` Arun Isaac
2020-12-22 15:00 ` Ludovic Courtès [this message]
2020-12-22 15:06 ` Julien Lepiller
2020-12-23 12:22 ` Miguel Ángel Arruga Vivas
2020-12-27 22:13 ` Ludovic Courtès
2020-12-22 15:45 ` Miguel Ángel Arruga Vivas
2020-12-15 13:11 ` Arun Isaac
2020-12-15 13:51 ` Zhu Zihao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rfh28do.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=all_but_last@163.com \
--cc=arunisaac@systemreboot.net \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.