From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Peter Krefting <peter@softwolves.pp.se>,
Robin Rosenberg <robin.rosenberg@dewire.com>,
Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
Git <git@vger.kernel.org>, Swedish <tp-sv@listor.tp-sv.se>
Subject: Re: [PATCH 2/2] Add Swedish translation.
Date: Thu, 16 Sep 2010 14:02:12 +0000 [thread overview]
Message-ID: <AANLkTim4M_KfuZoe5z_upPug5AT=P-_EfvPcxDe8-uPn@mail.gmail.com> (raw)
In-Reply-To: <4C92227B.70800@drmicha.warpmail.net>
On Thu, Sep 16, 2010 at 13:58, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> Ævar Arnfjörð Bjarmason venit, vidit, dixit 16.09.2010 13:41:
>> On Thu, Sep 16, 2010 at 11:23, Peter Krefting <peter@softwolves.pp.se> wrote:
>>> Robin Rosenberg:
>>>> (My comments are in swedish as it feels more natural in this context).
>>>
>>> While I do agree, I'm trying to reply in English since the Git list is in
>>> English.
>>
>> Usually yeah, but when a PO file is under discussion only people that
>> speak the language can contribute usefully anyway, so I think it's OK
>> if that discussion is not in English.
>
> How about "[L10N SE] etc." subject lines etc.? That way people can
> easily filter out all L10N posts but keep those relevant to them
> (including their language).
Sounds good, but convincing people to submit posts with those subjects
consistently is the hard part :)
> I'm trying to advocate "Marke" for DE ;)
> In fact, subversion seems to be a good source for inspiration - at least
> for the terms...
Yeah, languages that benefit from existing SCM translations should
definitely be looking at those, even if those SCM's aren't distributed
there's a lot of common vocabulary.
next prev parent reply other threads:[~2010-09-16 14:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 20:10 [PATCH 2/2] Add Swedish translation Peter Krefting
2010-09-12 23:03 ` Ævar Arnfjörð Bjarmason
2010-09-13 7:15 ` Peter Krefting
2010-09-13 12:47 ` [PATCH] Makefile: only add gettext tests on XGETTEXT_INCLUDE_TESTS=YesPlease Ævar Arnfjörð Bjarmason
2010-09-13 13:35 ` [PATCH 2/2] Add Swedish translation Ævar Arnfjörð Bjarmason
2010-09-13 13:45 ` Peter Krefting
2010-09-13 15:45 ` Ævar Arnfjörð Bjarmason
2010-09-14 8:25 ` Peter Krefting
2010-09-15 22:38 ` Ævar Arnfjörð Bjarmason
2010-09-13 10:12 ` Peter Kjellerstedt
2010-09-15 10:24 ` Peter Krefting
2010-09-15 15:31 ` Peter Kjellerstedt
2010-09-15 22:46 ` Robin Rosenberg
2010-09-16 7:49 ` Peter Kjellerstedt
2010-09-16 7:57 ` Jeremiah Foster
2010-09-16 11:23 ` Peter Krefting
2010-09-16 11:41 ` Ævar Arnfjörð Bjarmason
2010-09-16 13:58 ` Michael J Gruber
2010-09-16 14:02 ` Ævar Arnfjörð Bjarmason [this message]
2010-09-16 17:09 ` Peter Krefting
2010-09-16 19:18 ` [PATCH 2/2] Add Swedish translation. [in swedish] Robin Rosenberg
2010-09-16 10:41 ` [PATCH 2/2] Add Swedish translation Peter Krefting
2010-09-16 10:59 ` Ævar Arnfjörð Bjarmason
2010-09-18 16:46 ` [L10N SE] " Göran Uddeborg
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='AANLkTim4M_KfuZoe5z_upPug5AT=P-_EfvPcxDe8-uPn@mail.gmail.com' \
--to=avarab@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=peter.kjellerstedt@axis.com \
--cc=peter@softwolves.pp.se \
--cc=robin.rosenberg@dewire.com \
--cc=tp-sv@listor.tp-sv.se \
/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).