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 3E6709903 for ; Mon, 12 Dec 2011 23:37:34 +0000 (UTC) Received: (qmail 19600 invoked by uid 500); 12 Dec 2011 23:37:34 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 19529 invoked by uid 500); 12 Dec 2011 23:37:34 -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 19521 invoked by uid 99); 12 Dec 2011 23:37:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Dec 2011 23:37:34 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [212.227.17.8] (HELO moutng.kundenserver.de) (212.227.17.8) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Dec 2011 23:37:24 +0000 Received: from [192.168.1.71] (host-78-145-11-228.as13285.net [78.145.11.228]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0MbcUz-1RHtlV0Ew1-00Iw0N; Tue, 13 Dec 2011 00:37:04 +0100 Message-ID: <4EE69013.5050309@akerbeltz.org> Date: Mon, 12 Dec 2011 23:36:51 +0000 From: Michael Bauer Reply-To: fios@akerbeltz.org Organization: Akerbeltz User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: About the Former Native Language projects Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:9oZbB8HA/kKg8UXUa+n7PCT4aBk1i/Eb5M3bp6VcYXK 0bG07hyc/BZySzGWonZSod3ue+4Ucpixk581//ucx1TDj/R2AB 6WFxNrEdFstfny1YaipcMk+pHEnY0k+3mJob1qjgNdDESA7RjM HRWfWkFalVWj2+ozGbawotIWgkGvOZjXl81rRbfgbJPKTQ73gj LWLtah2Wi7Sn4e0+D2adVF1RO0M5GNp9/9RTDXL1XSwCwL/0m4 q642qcX1zxaderKnhO4UX4XARLPT7zvRBgmTeTh8zljbcer7uk kEae1oL0G25KCi+rQuWLyji2uW09irFg4bWgKR6N22igWJCwiH JLZPGFQLR9P3+qHg0udg= X-Virus-Checked: Checked by ClamAV on apache.org Hi folks, I admit to mostly lurking but kinda feel compelled to chip in at this point. First off, I'm "just a translator", I came to OO late in the day to resucitate the Scottish Gaelic localization which had fallen format. I have no coding skills, at least none at the level needed to contribute code, so I consider my skills in translation my contribution. As such, I usually have little interest in the direction projects such as OO, Mozilla w/e take, code-wise or politically, except for trying to promote translator-friendly localization processes. The impending rift and eventual split took me completely by surprise. Literally. One day I had been translating away in Pootle, the next day it was dead and it took a lot of googling to eventually figure out what had been going on. I'm just glad I had taken a backup the day before, I don't know how many nascent projects have had their entire work frozen on Pootle since. Which is why I felt a little irked by the suggestion someone made that interested NL projects could "come forward". If it hadn't been for someone's blog post I came across eventually, I *still* wouldn't know that OO had "shifted" to Apache. I suspect very few NL projects will have come forward because for a long time it was not obvious to people not hooked into the develpment mailing lists (conjecture, mylord) that that's what happened. Apart from spam, nothing has ever been posted on the l10n list which was the only list I had subscribed to for the above reasons. So if "we're" supposed to step forward, perhaps someone should let the l10n list subscribers know? My main concern are the Gaelic users, however few those may be, who are still stuck on 3.01 and who know nothing of this break, apart from the fact that the extensions site has been going offline regulary. So I'd like to find some way of completing the localization - which should be relatively easy as I completed it over on LO, so they can finally update to whatever version is next. Salude e trigu, Michael And incidentally, translation *is* a technical skill - it just doesn't involve code dancing across the screen ;)