guix-devel
[Top][All Lists]
Advanced

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

(i18n) msgid feedback for shepherd-1.0.1rc1


From: Andrej Kacian
Subject: (i18n) msgid feedback for shepherd-1.0.1rc1
Date: Wed, 22 Jan 2025 23:48:03 +0100

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 via email to

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