Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8312FD66F for ; Thu, 1 Nov 2012 20:25:09 +0000 (UTC) Received: (qmail 96740 invoked by uid 500); 1 Nov 2012 20:25:09 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 96646 invoked by uid 500); 1 Nov 2012 20:25:09 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 96633 invoked by uid 99); 1 Nov 2012 20:25:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 20:25:09 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of marcus.mail@wtnet.de designates 213.209.103.7 as permitted sender) Received: from [213.209.103.7] (HELO smtp2.wtnet.de) (213.209.103.7) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 20:25:03 +0000 X-WT-Originating-IP: 84.46.110.107 Received: from f9.linux (pop8-1636.catv.wtnet.de [84.46.110.107]) (authenticated bits=0) by smtp2.wtnet.de (8.14.4/8.14.4) with ESMTP id qA1KOdEi031514 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Thu, 1 Nov 2012 21:24:44 +0100 Message-ID: <5092DA84.9080103@wtnet.de> Date: Thu, 01 Nov 2012 21:24:36 +0100 From: "Marcus (OOo)" User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.2.20) Gecko/20110804 Thunderbird/3.1.12 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: extensions and translations. References: <508B15AA.20607@wtnet.de> <5091B6AB.8090503@wtnet.de> <50922A40.2060707@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Am 11/01/2012 01:17 PM, schrieb Rob Weir: > On Thu, Nov 1, 2012 at 3:52 AM, Jürgen Schmidt wrote: >> On 11/1/12 12:39 AM, Marcus (OOo) wrote: >>> Am 10/27/2012 01:17 AM, schrieb jan iversen: >>>> I see, I have to get used to this license issues (a long time ago I >>>> believed open source was just open source, then I joined an apache >>>> project). >>>> >>>> never mind. >>>> >>>> Would it be to our advantage if we offered third party developers >>>> (that is >>>> how I see extension developers) the possibility to register a language >>>> file >>>> and get it translated as part of the language packs ? >>> >>> Of course it would be to our advantage; or let's say for the project and >>> software. A lot of extensions would be available in many languages. >>> >>> However, I don't know where we should draw the line to set a limit. When >>> we select here and there some extensions, then the other developers will >>> ask why not their extensions. >> >> It's quite simple I would say, if people want develop extensions under >> ALv2 and want to contribute the code to the project. We can easy create >> a special section in our repo where we can host them. >> >> But this means they have to be handled in the same way as all other >> stuff here. Means a new release have to be voted... >> > > > +1 > > I think the important thing is this: We don't just want code. We > want communities. So if an extension author thinks that their > extension is generally useful and he/she wants to join the AOO > community and work on the extension here, and allow others to work on > it as well, then this is good. Of course, +1. > We can have a set of "standard extensions". So, we just need to define the standard. Marcus >>> And IMHO it's not possible to translate all strings for all extensions. >>> >>> But maybe others here have a great idea? >> >> we can't probably provide it and I think we have to do enough ;-). But I >> can think of an alternative service hosted somewhere else. >> >> Juergen >> >>> >>>> Or should we just say extension developers does not concern us (and help >>>> AOO get more used) so we just look the other way ? >>>> >>>> Maybe the right way is somewhere in the middle. >>> >>> Yeah, maybe. ;-) >>> >>> Marcus >>> >>> >>> >>>> On 27 October 2012 00:58, Marcus (OOo) wrote: >>>> >>>>> Am 10/27/2012 12:36 AM, schrieb jan iversen: >>>>> >>>>> While doing an update to the l10n workflow I think I found a slight >>>>>> problem. >>>>>> >>>>>> Extensions offers the capability to integrate/extend our UI. >>>>>> >>>>>> Assuming somebody writes an extension, and publishes it on >>>>>> http://www.openoffice.org/**extensions/how >>>>>> does that get integrated into the >>>>>> translation process ? >>>>>> >>>>> >>>>> Simply, not at all. >>>>> >>>>> >>>>> As far as I can see the sources are not integrated into our "build >>>>> --all >>>>>> --with-lang". >>>>>> >>>>> >>>>> Right. >>>>> >>>>> >>>>> If I am right that they are not part of the general translation, >>>>> then is >>>>>> that per design so or should it be different ? >>>>>> >>>>> >>>>> Yes, this is by design. >>>>> >>>>> Extensions are offered to extent your AOO install at any point of time. >>>>> These are developed by people that do not have to belong to our project >>>>> (when we put aside some exceptions). They can act independently. And >>>>> therefore they are allowed to (or have to ;-) ) do all on their own; >>>>> incl. >>>>> translation. >>>>> >>>>> That applies for all extensions and templates available on: >>>>> >>>>> - >>>>> http://extensions.services.**openoffice.org >>>>> >>>>> - >>>>> http://templates.services.**openoffice.org >>>>> >>>>> >>>>> >>>>> I might be following a wrong track here, but please forgive me for >>>>> trying >>>>>> to make the l10n process as complete as I can. >>>>>> >>>>> >>>>> Don't panic. That's a great goal and everybody is thankful to you for >>>>> doing this task. >>>>> >>>>> Marcus