From: "Ludovic Courtès" <ludo@gnu.org>
To: "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com>
Cc: guix-devel@gnu.org, Vagrant Cascadian <vagrant@debian.org>
Subject: Re: u-boot for beagleboard
Date: Mon, 05 Oct 2020 15:55:38 +0200 [thread overview]
Message-ID: <87eemcydyd.fsf@gnu.org> (raw)
In-Reply-To: <878sclgdtj.fsf@gmail.com> ("Miguel Ángel Arruga Vivas"'s message of "Mon, 05 Oct 2020 12:35:52 +0200")
Hi,
Miguel Ángel Arruga Vivas <rosen644835@gmail.com> skribis:
> I see two main possibilities for the "translation units" in these cases:
>
> - When the extra data is a "non-localizable string", I'd rather use a
> format string for the template, and insert the data through the format
> specifier, possibly with a message to the translators to make clearer
> the inserted data if it isn't clearly deduced from the message:
> ----------------------8<----------------------
> (let ((desc (format #f
> ;; TRANSLATORS: ~a is substituted by the board ids.
> (_ "Description.~{~% - Board: ~a~}~%")
> (list "id1" "id2" ... "idn"))))
> ...)
> ---------------------->8----------------------
>
> - In any other case, I'd concatenate them as two separate paragraphs[2]
> and let the translators face them up separately:
>
> ----------------------8<----------------------
> (let ((desc (format #f
> "~s~%~%~s" ; Translating this may be an overkill...
> (_ "First paragraph(s).")
> (_ "Other paragraph(s)."))))
> ...)
> ---------------------->8----------------------
Seconded.
See also the ‘--keyword’ options in po/guix/Makevars for the list of
keywords picked up for translation in Guix.
Ludo’.
prev parent reply other threads:[~2020-10-05 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 9:07 How to build Guix to send a patch when Guix build fails? Denis 'GNUtoo' Carikli
2020-10-01 13:54 ` zimoun
2020-10-01 23:19 ` Denis 'GNUtoo' Carikli
2020-10-02 8:08 ` zimoun
2020-10-01 17:15 ` u-boot for beagleboard Vagrant Cascadian
2020-10-04 18:34 ` Danny Milosavljevic
2020-10-05 10:35 ` Miguel Ángel Arruga Vivas
2020-10-05 13:55 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eemcydyd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rosen644835@gmail.com \
--cc=vagrant@debian.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).