unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrej Kacian via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: guix-devel@gnu.org
Subject: (i18n) msgid feedback for shepherd-1.0.1rc1
Date: Thu, 23 Jan 2025 02:27:56 +0100	[thread overview]
Message-ID: <2843101.ogcfADQ0N9@penny> (raw)

Hi, I am working on a translation for shepherd-1.0.1rc1, and I thought I'd 
give some msgid feedback on a few small issues that I noticed. Here goes:

There are several msgids with strings indented with two spaces at the 
beginning. Could these two spaces perhaps be placed outside of translated 
strings? Or maybe there are some languages where such indenting needs to be 
translated differently? Even then, a separate msgid containing just those 
indenting spaces could be made instead.

There is a msgid that is just "~a", without any explanation. Maybe there is a 
reason why this is translatable, but without at least a translators' comment, 
it seems unnecessary.

There are two msgids with the string "~:[~a~;~*local process~]", what exactly 
is the part in square brackets? should it be kept verbatim, or should "local 
process" be translated in a regular manner?

The software name "Shepherd" is mentioned in several msgids which look like 
help strings, but sometimes the starting letter is uppercase, sometimes 
lowercase. Seems inconsistent.

There are several msgids which need to take advantage of the multiple plural 
support of gettext:
  - "service names: ~a; heap: ~,2f MiB; file descriptors: ~a"
  - "Monitoring logging period changed to ~a seconds."
  - "Closing ~a system log ports."
  - "Process ~a of timer '~a' terminated with status ~a after ~a seconds."
  - "Terminating process ~a of timer '~a' after maximum duration of ~a 
seconds."
  - "warning: already ~a threads running, disabling 'signalfd' support"

Granted, the last one probably does not really need this change, since the 
number of threads is likely to be quite high, but still. :)

There are two or three msgids which start with "calendar-event:". Is that name 
of some subcomponent, and as such should be kept verbatim?

"Timer spec lacks 'at TIME'."
This one is tricky. I'm assuming the "at TIME" should be kept verbatim? Or 
perhaps just the "at" should be translated? The uppercase TIME seems like a 
symbolic parameter name, something like parameter names in help strings (FILE, 
PARAM, ACTION), but I can't see any other msgid where TIME is referenced. The 
help string for this only lists a concrete example (10:00). This makes it 
difficult to convey what is meant without the translation feeling awkward. Or 
maybe it's just a me-problem.

I hope I'm explaining myself clearly, and that the feedback is useful.

Cheers,
-- 
Andrej





             reply	other threads:[~2025-01-25 11:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23  1:27 Andrej Kacian via Development of GNU Guix and the GNU System distribution. [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-22 22:48 (i18n) msgid feedback for shepherd-1.0.1rc1 Andrej Kacian via Development of GNU Guix and the GNU System distribution.
2025-02-08 22:22 ` Ludovic Courtès
2025-02-09  1:20   ` pelzflorian (Florian Pelz)
2025-02-09 21:52     ` pelzflorian (Florian Pelz)
2025-02-10 19:59     ` Andrej Kacian via Development of GNU Guix and the GNU System distribution.

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=2843101.ogcfADQ0N9@penny \
    --to=guix-devel@gnu.org \
    --cc=andrej@kacian.sk \
    /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).