¡Hola!
Miguel Ángel Arruga Vivas skribis:
> From 2615934a2c377858dce2a0410982287faed754a9 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Miguel=20=C3=81ngel=20Arruga=20Vivas?=
>
> Date: Wed, 23 Dec 2020 13:07:38 +0100
> Subject: [PATCH] nls: Add comment about format directives.
>
> * gnu.scm
Hi Julien,
Julien Lepiller writes:
> This specific syntax looks ok, but we need to limit ourself to the
> common syntax between guile and lisp, because that's what gettext
> supports.
The issue with Guile's format is explained here[1], as the used
implementation follows SRFI-28[2], but there
Hi Ludo,
Ludovic Courtès writes:
> 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
This specific syntax looks ok, but we need to limit ourself to the common
syntax between guile and lisp, because that's what gettext supports.
We should use this kind of syntax everywhere we have more than one argument.
Also thinking about rtl languages, it's probably important for them, though
Hi,
Arun Isaac 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
>
Hi,
> 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
Hi!
Julien Lepiller skribis:
> Even when translating to French, I sometimes feel the need to change
> word order, but I end up finding a slightly unnatural way to preserve
> the order of arguments. I don't have an example at hand though.
>
> I don't know enough about guile to know how best to
Arun Isaac writes:
> Hi Zhu Zihao,
>
> I faced the same problem while working on the Tamil localization. I used
> the ~* argument jumping supported by (ice-9 format) to work around
> this. So, for the message "could not find bootstrap binary '~a' for
> system '~a'", you could do something like
>
Hi Zhu Zihao,
I faced the same problem while working on the Tamil localization. I used
the ~* argument jumping supported by (ice-9 format) to work around
this. So, for the message "could not find bootstrap binary '~a' for
system '~a'", you could do something like
"无法找到用于引导 ~1@* 系统的二进制文件 ~0@*"
Even when translating to French, I sometimes feel the need to change word
order, but I end up finding a slightly unnatural way to preserve the order of
arguments. I don't have an example at hand though.
I don't know enough about guile to know how best to implement that (or if that
exists
Hi, Guix users!
Currently I'm putting my energy into Guix l10n(zh_CN). However, there's
a serious flaw in current implementation of l10n.
AFAFIK, Guix use format in (ice-9 format) to format the the template
string return by `G_`. The template string of (ice-9 format) looks
similar to the format
11 matches
Mail list logo
