[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#28423] gnu: Add imb-openmpi.

From: Ludovic Courtès
Subject: [bug#28423] gnu: Add imb-openmpi.
Date: Tue, 03 Oct 2017 14:47:58 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)

Hi Dave,

Dave Love <address@hidden> skribis:

> Ludovic Courtès <address@hidden> 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

  (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).


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:
+  ;; @dots{}
+  (synopsis "This is translatable")
+  (description (string-append "This is " "*not*" " translatable.")))
address@hidden 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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]