From: ludo@gnu.org (Ludovic Courtès)
To: Dave Love <fx@gnu.org>
Cc: 28423@debbugs.gnu.org
Subject: [bug#28423] gnu: Add imb-openmpi.
Date: Tue, 03 Oct 2017 14:47:58 +0200 [thread overview]
Message-ID: <87k20c8kjl.fsf@gnu.org> (raw)
In-Reply-To: <87bmlpffd3.fsf@albion.it.manchester.ac.uk> (Dave Love's message of "Mon, 02 Oct 2017 21:45:44 +0100")
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
Hi Dave,
Dave Love <fx@gnu.org> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Ping! :-)
>>
> I think I was waiting for an explanation
You didn’t ask though, did you? ;-)
> of the doc string rules for translation, and why they seem to be
> different from what gettext say in terms of placeholders in format
> strings. I think that needs documenting anyhow.
In po/packages/Makevars, we define only two keywords for translatable
strings: ‘synopsis’ and ‘description’. Thus, xgettext will extract this
string:
(synopsis "This is translatable")
but it will not extract this:
(synopsis (string-append "This is " "not translatable"))
I’ve added a note in the manual (below).
HTH,
Ludo’.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 933 bytes --]
diff --git a/doc/guix.texi b/doc/guix.texi
index c57c0bab6..9e301d007 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -19147,6 +19147,18 @@ Translation Project} so that as many users as possible can read them in
their native language. User interfaces search them and display them in
the language specified by the current locale.
+To allow @command{xgettext} to extract them as translatable strings,
+synopses and descriptions @emph{must be literal strings}. This means
+that you cannot use @code{string-append} or @code{format} to construct
+these strings:
+
+@lisp
+(package
+ ;; @dots{}
+ (synopsis "This is translatable")
+ (description (string-append "This is " "*not*" " translatable.")))
+@end lisp
+
Translation is a lot of work so, as a packager, please pay even more
attention to your synopses and descriptions as every change may entail
additional work for translators. In order to help them, it is possible
next prev parent reply other threads:[~2017-10-03 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 20:40 [bug#28423] gnu: Add imb-openmpi Dave Love
2017-09-11 20:47 ` Dave Love
2017-09-12 13:06 ` Ludovic Courtès
2017-09-28 20:09 ` Ludovic Courtès
2017-10-02 20:45 ` Dave Love
2017-10-03 12:47 ` Ludovic Courtès [this message]
2017-10-03 16:57 ` Dave Love
2017-10-03 19:51 ` Ludovic Courtès
2017-10-04 15:32 ` Dave Love
2017-10-05 9:24 ` bug#28423: " Ludovic Courtès
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=87k20c8kjl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28423@debbugs.gnu.org \
--cc=fx@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 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).