public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Jochen Hein <jochen@jochen.org>
To: libc-alpha@sourceware.org
Subject: Re: New template for 'libc' made available
Date: Sun, 02 Aug 2015 20:25:00 -0000	[thread overview]
Message-ID: <87bnepigsb.fsf@echidna.jochen.org> (raw)
In-Reply-To: <E1ZL4aK-0002H2-FJ@duik.vrijschrift.org> (Translation Project Robot's message of "Fri, 31 Jul 2015 09:18:28 +0200")

Translation Project Robot <robot@translationproject.org> writes:

> A new POT file for textual domain 'libc' has been made available
> to the language teams for translation.  It is archived as:
>
>     http://translationproject.org/POT-files/libc-2.22-pre1.pot

I've just updated the german translation and noticed a couple of things.

There are some new strings with `%s` instead of the usual `%s'. Is this
intentional?

There are some messages that are constructed dynamically, which may or
may not be possible to use in translations.  And the dynamic strings are
not marked for translation.  For example:

,----
| #: nscd/connections.c:977
| #, c-format
| msgid "monitoring file `%s` (%d)"
`----

The corresponds to the following C code:
,----
| 	      dbg_log (_("monitored file `%s` was %s, removing watch"),
| 		       finfo->fname, moved ? "moved" : "deleted");
`----

Also for

,----
| #: nscd/connections.c:1968
| #, c-format
| msgid "monitored file `%s` was %s, removing watch"
| msgstr "monitored file `%s` was %s, removing watch"
`----

,----
| »#: nscd/connections.c:2015
| #, c-format
| msgid "monitored parent directory `%s` was %s, removing watch on `%s`"
| msgstr ""
`----

and

,----
| »#: nscd/connections.c:2041
| #, c-format
| msgid "monitored file `%s` was %s, adding watch"
| msgstr "monitored file `%s` was %s, adding watch"
`----

This should probably be changed for the next revisions.

Jochen

-- 
The only problem with troubleshooting is that the trouble shoots back.

  reply	other threads:[~2015-08-02 20:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31  7:18 Translation Project Robot
2015-08-02 20:25 ` Jochen Hein [this message]
2015-08-03 17:07   ` Joseph Myers
2015-08-03 18:50     ` Carlos O'Donell
2015-08-03 19:08       ` Paul Eggert
2015-08-03 20:34       ` Joseph Myers
2015-08-04 14:30         ` Carlos O'Donell
  -- strict thread matches above, loose matches on Subject: below --
2024-01-03 10:38 Translation Project Robot
2023-07-18 14:07 Translation Project Robot
2023-01-25 10:19 Translation Project Robot
2022-07-31  9:09 Translation Project Robot
2022-01-30 15:39 Translation Project Robot
2021-07-29  8:00 Translation Project Robot
2020-07-23  7:17 Translation Project Robot
2020-01-10  9:01 Translation Project Robot
2019-07-24 18:14 Translation Project Robot
2019-01-16 16:40 Translation Project Robot
2018-07-27 18:54 Translation Project Robot
2018-01-10 19:12 Translation Project Robot
2017-07-25 19:22 Translation Project Robot
2017-01-11 13:47 Translation Project Robot
2017-01-11 13:41 Translation Project Robot
2015-01-22 19:25 Translation Project Robot
2014-08-21  7:39 Translation Project Robot
2014-01-08 12:37 Translation Project Robot
2013-07-26  8:04 Translation Project Robot
2012-12-11  7:10 Translation Project Robot
2012-06-30 16:24 Translation Project Robot

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=87bnepigsb.fsf@echidna.jochen.org \
    --to=jochen@jochen.org \
    --cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).