unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Dave Love <fx@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28423@debbugs.gnu.org
Subject: [bug#28423] gnu: Add imb-openmpi.
Date: Tue, 03 Oct 2017 17:57:25 +0100	[thread overview]
Message-ID: <877ewcb24q.fsf@albion.it.manchester.ac.uk> (raw)
In-Reply-To: <87k20c8kjl.fsf@gnu.org> ("Ludovic \=\?iso-8859-1\?Q\?Court\=E8s\?\= \=\?iso-8859-1\?Q\?\=22's\?\= message of "Tue, 3 Oct 2017 14:47:58 +0200")

Ludovic Courtès <ludo@gnu.org> writes:

> You didn’t ask though, did you?  ;-)

I thought I had, twice.  Oh, well, sorry!

>> 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"))

The question would have been why

  (format-string #f ("Package variant ~a is not translatable" x))

when the sprintf equivalent would be, as I understand what the gettext
doc says.

  reply	other threads:[~2017-10-03 16:58 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
2017-10-03 16:57           ` Dave Love [this message]
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=877ewcb24q.fsf@albion.it.manchester.ac.uk \
    --to=fx@gnu.org \
    --cc=28423@debbugs.gnu.org \
    --cc=ludo@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).