Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of Andre.Schnabel@gmx.net
 designates 213.165.64.22 as permitted sender)
Content-Type: text/plain; charset="utf-8"
Date: Mon, 20 Jun 2011 14:02:42 +0200
From: "Andre Schnabel" <Andre.Schnabel@gmx.net>
In-Reply-To: <BANLkTikzfc7muqphJvkxOPztrFgc2ETcKw@mail.gmail.com>
Message-ID: <20110620120242.320490@gmx.net>
MIME-Version: 1.0
References: <BANLkTinR1SyreyOB7HfaaGv1K67CSYVDLg@mail.gmail.com>
	<BANLkTimj67TUEcCpjRHUP_f0mY+VSn0VDg@mail.gmail.com>
	<C8C2B281-AAEB-49C4-8CC8-51C20CD7F064@gmail.com>
	<1308316065.3011.6.camel@localhost.localdomain>
	<4DFB7656.3090907@gmx-topmail.de>
 <BANLkTikzfc7muqphJvkxOPztrFgc2ETcKw@mail.gmail.com>
Subject: Re: Can we rationalize and formalize "a language project"?
To: ooo-dev@incubator.apache.org
Content-Transfer-Encoding: 8bit

Hi,

> Datum: Fri, 17 Jun 2011 22:43:24 +0100
> Von: Ross Gardler <rgardler@opendirective.com>
> An: ooo-dev@incubator.apache.org
> Betreff: Re: Can we rationalize and formalize "a language project"?


> 
> Non-English core development lists are not acceptable.

Well - what exactly is "core development"? :)

E.g. I consider localization for an end-user focused office application 
suite as core development.

> 
> I'm not sure if there is precedent for non-english dev lists for
> translation and the like. I imagine that they *might* be acceptable
> but only if all proposals that affect code (other than language
> specific items) would need to be brought to the core list. My gut
> feeling is that it would be best to avoid them if at all possible, but
> that's just instinct (i.e. not based on practical experience).


You might change your mind, as soon as you see 20 Mails focusing
just on the question if a certain string should be
"via Doppelklick" or "per Doppelklick" - and all the discussion
would be in German. There are lots of discussions within l10n teams
to find the correct(tm) wording - and all this discussion (or the
result of this discussion) is important for the product.

So - imho this kind of discussion belongs to the OOo project but needs
to be in the translator's native lang.

regards,

André