From: Ralf Thielow <ralf.thielow@gmail.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: jk@jk.gs, stimming@tuhh.de, git@vger.kernel.org,
worldhello.net@gmail.com
Subject: Re: [RFC] l10n: de.po: translate 76 new messages
Date: Fri, 3 Aug 2012 14:28:54 +0200 [thread overview]
Message-ID: <CAN0XMOJJ=B-Uq+hv6fkTtA0vNs=XRf03_+dgymV8ESXA4tw0+A@mail.gmail.com> (raw)
In-Reply-To: <874nok5fxk.fsf@thomas.inf.ethz.ch>
On Fri, Aug 3, 2012 at 2:16 PM, Thomas Rast <trast@student.ethz.ch> wrote:
>>>
>>> KONFLIKT (rename/delete): foo gelöscht in bar und renamed in quux. Stand ...
>>
>> Gah, I misunderstood the values of the placeholders. The reason why I haven't
>> translate "delete" or "rename" is because they're part of the
>> "KONFLIKT (%s/delete)"
>> messages, aren't they? Translate it all would solve the problem. Thanks
>
> Well, it's a bit confusing. AFAICS the verb (rename/modify) goes into
> the parens at the start, and the participle (renamed/modified) goes into
> the fourth %s. So if you decided to *not* translate the
> "(rename/delete)" conflict description, you would have to translate
> "renamed" (to fit it into the sentence) but not "rename".
>
> Which would be really hard to maintain. So let's not do that. I think
> it's better if you translate them all.
>
That's what i meant. Sorry if I was unclear.
next prev parent reply other threads:[~2012-08-03 12:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 17:12 [RFC] l10n: de.po: translate 76 new messages Ralf Thielow
2012-08-03 8:59 ` Thomas Rast
2012-08-03 10:41 ` Ralf Thielow
2012-08-03 12:16 ` Thomas Rast
2012-08-03 12:28 ` Ralf Thielow [this message]
2012-08-05 7:13 ` [RFCv2] " Ralf Thielow
2012-08-03 12:16 ` [PATCH 1/2] diff_setup_done(): return void Thomas Rast
2012-08-03 12:16 ` [PATCH 2/2] merge-recursive: eliminate flush_buffer() in favor of write_in_full() Thomas Rast
2012-08-03 12:17 ` [PATCH 1/2] diff_setup_done(): return void Thomas Rast
2012-08-03 16:26 ` [RFC] l10n: de.po: translate 76 new messages Ralf Thielow
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN0XMOJJ=B-Uq+hv6fkTtA0vNs=XRf03_+dgymV8ESXA4tw0+A@mail.gmail.com' \
--to=ralf.thielow@gmail.com \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
--cc=stimming@tuhh.de \
--cc=trast@student.ethz.ch \
--cc=worldhello.net@gmail.com \
/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://80x24.org/mirrors/git.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).