unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34498@debbugs.gnu.org
Subject: bug#34498: Confusing msgid "  Running value is ~s.~%"
Date: Thu, 18 Apr 2019 17:41:56 +0200	[thread overview]
Message-ID: <20190418154155.cboionc4lwy6rzpx@pelzflorian.localdomain> (raw)
In-Reply-To: <87sgufsiuc.fsf@gnu.org>

On Thu, Apr 18, 2019 at 12:34:03PM +0200, Ludovic Courtès wrote:
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> 
> > I am fairly sure
> >
> > #: modules/shepherd/scripts/herd.scm:86
> > #, scheme-format
> > msgid "  Running value is ~s.~%"
> >
> > refers to the value of the #:running slot but translators don’t know
> > that and would translate it as a value that is running.  This should
> > be changed and a comment for TRANSLATORS should be added.
> 
> Done in Shepherd commit 5d418ff0de1ac0a5419344dfe70c08ed464f3797.
> 
> Thanks,
> Ludo’.

No, it is not done.  What the manual described as the @code{running}
value, i.e. the value of the #:running slot, was understood by at
least one translator not as the value of #:running but as a value
which runs.

> #. TRANSLATORS: The "~s" bit is most of the time a placeholder
> #. for the PID (an integer) of the running process, and
> #. occasionally for another Scheme object.

This is not the information that translators need.

Regards,
Florian

  reply	other threads:[~2019-04-18 15:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-16  6:10 bug#34498: Confusing msgid " Running value is ~s.~%" pelzflorian (Florian Pelz)
2019-04-18 10:34 ` Ludovic Courtès
2019-04-18 15:41   ` pelzflorian (Florian Pelz) [this message]
2019-04-18 16:37     ` Ludovic Courtès
2019-04-18 17:24       ` pelzflorian (Florian Pelz)
2019-04-19  8:06         ` 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=20190418154155.cboionc4lwy6rzpx@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=34498@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).