From: Karel Zak <kzak@redhat.com>
To: Petr Pisar <petr.pisar@atlas.cz>
Cc: util-linux@vger.kernel.org
Subject: Re: Mistakes in message strings
Date: Tue, 4 Jun 2019 13:10:35 +0200 [thread overview]
Message-ID: <20190604111035.45rdqrl5pce4pcsu@ws.net.home> (raw)
In-Reply-To: <20190601142701.GL3522@album.bayer.uni.cx>
On Sat, Jun 01, 2019 at 04:27:02PM +0200, Petr Pisar wrote:
> while updating Czech translation for util-linux-2.34-rc2 I spotted these
> issues in the message strings:
Thanks for your feedback!
I have always doubts when fix messages issues -- before the release it
means that some already translated strings will be untranslated; and
after the release it means we will release with known mistakes.
Anyway, after release it seems as better from my point of view.
Karel
>
> # FIXME: Remove a trailing period
> #: login-utils/lslogins.c:1345
> msgid ""
> " -p, --pwd display information related to login by password.\n"
>
> # FIXME "user" should read "group"
> #: sys-utils/setpriv.c:139
> msgid " --rgid <gid|user> set real gid\n"
>
> # FIXME: Missing a comma between options
> #: term-utils/agetty.c:2352
> msgid " -J --noclear do not clear the screen before prompt\n"
>
> # FIXME: Missing a comma between options
> #: term-utils/agetty.c:2357
> msgid " -N --nonewline do not print a newline before issue\n"
>
> # FIXME: typo in "is possible", should be "if possible"
> #: misc-utils/findmnt.c:1246
> msgid " --tree enable tree format output is possible\n"
>
>
> Moreover, I have difficulies in translating this message:
>
> #: misc-utils/hardlink.c:363 text-utils/pg.c:1263
> msgid "saved"
>
> because each of the location requires a different translation in Czech
> language ("stored" versus "spared"). Please either add a gettext context or,
> better, duplicate the messages:
>
> # First argument is "Would link" or "Linked".
> #: misc-utils/hardlink.c:354
> #, c-format
> msgid " %s %s to %s\n"
>
> into:
>
> msgid " Would link %s to %s\n"
> msgid " Linked %s to %s\n"
>
> and duplicate this:
>
> # First argument is "Would link" or "Linked".
> # Second and third ones are file names.
> # Fourth one is "would save" or "saved".
> #: misc-utils/hardlink.c:360
> #, c-format
> msgid " %s %s to %s, %s %jd\n"
>
> into:
>
> msgid " Would link %s to %s, would save %jd\n"
> msgid " Linked %s to %s, saved %jd\n"
>
> I believe it will make the messages more undestandible and easier to
> translate also in other languages.
>
> -- Petr
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2019-06-04 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 14:27 Mistakes in message strings Petr Pisar
2019-06-04 11:10 ` Karel Zak [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190604111035.45rdqrl5pce4pcsu@ws.net.home \
--to=kzak@redhat.com \
--cc=petr.pisar@atlas.cz \
--cc=util-linux@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox