From: "Torsten Bögershausen" <tboegi@web.de>
To: "Jeff King" <peff@peff.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Michael J Gruber" <git@drmicha.warpmail.net>,
"Torsten Bögershausen" <tboegi@web.de>,
"Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>,
"Git Mailing List" <git@vger.kernel.org>,
"Ralf Thielow" <ralf.thielow@gmail.com>
Subject: Re: Enhancement Request: "locale" git option
Date: Fri, 05 Dec 2014 16:45:15 +0100 [thread overview]
Message-ID: <5481D30B.2020104@web.de> (raw)
In-Reply-To: <20141204205527.GA19953@peff.net>
On 12/04/2014 09:55 PM, Jeff King wrote:
> On Thu, Dec 04, 2014 at 06:21:40PM +0100, Ævar Arnfjörð Bjarmason wrote:
>
>>> That is one of the many reasons why I proposed to have a dictionary of
>>> the main technical terms for each language before we even localise git
>>> in that language. In an ideal word, we would provide a simple solution
>>> for looking these terms up both ways. I don't think we're going to have
>>> localised man pages any time soon, are we?
>>
>> I think that's a great idea, and one that's only blocked on someone
>> (hint hint) sending patches for it.
>>
>> It would be neat-o to have something to make translating the docs
>> easier, i.e. PO files for sections of the man pages. There's tools to
>> help with that which we could use.
>>
>> But there's no reason for us not to have translated glossaries in the meantime.
>
> By the way, there has been fairly significant volunteer effort put into
> translating Pro Git (e.g., <http://git-scm.com/book/de/v1>). I have no
> idea if the terms they use are similar to the terms we use in the
> localized messages. It might make sense to:
>
> 1. Coordinate with those translators to make sure that the glossary
> terms are consistent.
>
> 2. Figure out how to harness those translators for manpage work. Why
> did Pro Git get so much volunteer translation done, and the
> manpages didn't? Did they advertise to the right people? Have an
> interface that made it easier for non-technical people to get
> involved?
>
> -Peff
(Thanks for the pointer, excellent book)
I do not know who was first, and who came later, but
<http://git-scm.com/book/de/v1/Git-Grundlagen-%C3%84nderungen-am-Repository-nachverfolgen>
uses "versioniert" as "tracked"
LANG=de_DE.UTF-8 git status
gives:
nichts zum Commit vorgemerkt, aber es gibt unbeobachtete Dateien (benutzen Sie "git add" zum Beobachten)
Does it make sense to replace "beobachten" with "versionieren" ?
next prev parent reply other threads:[~2014-12-05 15:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 7:32 Enhancement Request: "locale" git option Ulrich Windl
2014-12-04 8:29 ` Torsten Bögershausen
2014-12-04 9:55 ` Jeff King
2014-12-04 15:49 ` Ævar Arnfjörð Bjarmason
2014-12-04 16:12 ` Michael J Gruber
2014-12-04 16:53 ` Andreas Schwab
2014-12-04 17:21 ` Ævar Arnfjörð Bjarmason
2014-12-04 20:55 ` Jeff King
2014-12-05 15:45 ` Torsten Bögershausen [this message]
2014-12-06 19:28 ` Ralf Thielow
2014-12-08 7:50 ` Antw: " Ulrich Windl
2014-12-08 9:48 ` David Kastrup
2014-12-04 15:51 ` Ulrich Windl
2014-12-04 19:02 ` Ralf Thielow
2014-12-08 7:20 ` Antw: " Ulrich Windl
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=5481D30B.2020104@web.de \
--to=tboegi@web.de \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=avarab@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=ralf.thielow@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.
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 NNTP newsgroup(s).