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 257D1907E for ; Tue, 3 Apr 2012 04:24:51 +0000 (UTC) Received: (qmail 5883 invoked by uid 500); 3 Apr 2012 04:24:50 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 5813 invoked by uid 500); 3 Apr 2012 04:24:49 -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 5786 invoked by uid 99); 3 Apr 2012 04:24:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Apr 2012 04:24:48 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jogischmidt@googlemail.com designates 209.85.214.47 as permitted sender) Received: from [209.85.214.47] (HELO mail-bk0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Apr 2012 04:24:42 +0000 Received: by bkcjg15 with SMTP id jg15so3048610bkc.6 for ; Mon, 02 Apr 2012 21:24:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:x-mailer :mime-version:content-type; bh=d+4vrFW8rl3EducjrFDeXtotT4xT5Ul8uJwthg9N0MI=; b=cOoGCyWGkPUkqLZN66x4mz5iM4RxEykXGMO4jNC1wM4Y32hcwYd1B3l3NKq/ng5T0r wD/vs8kqOpCpj2sdO7SA36w5doToZsGxrCV96hPmIi374jPNgTaITJWdOlI9Bj/vV3xQ ynNwpybNC1jA60QFnBUjKAFGPFMDrE1HkayrAZv/dWqA3Tn3XwogWZiDqSRAIzBeXB45 dlVe09E/nNVSyL+iwTyE889OE8+tyWw9qkzylbNbaKCXTk3O/TtncZ8nRusrvXHcbrfY 9u/5T2tkEYJyuJV6daT59vpkWN7dP9grvE8qGxLzSlJorKwA4PzTSvjYAx0iJMoWl+Jw 3rYQ== Received: by 10.205.117.15 with SMTP id fk15mr4585836bkc.133.1333427061214; Mon, 02 Apr 2012 21:24:21 -0700 (PDT) Received: from JogiPhone (e177142222.adsl.alicedsl.de. [85.177.142.222]) by mx.google.com with ESMTPS id z17sm42698481bkw.12.2012.04.02.21.24.19 (version=SSLv3 cipher=OTHER); Mon, 02 Apr 2012 21:24:20 -0700 (PDT) Date: Tue, 3 Apr 2012 06:24:18 +0200 From: Juergen Schmidt To: ooo-dev@incubator.apache.org Message-ID: <7296C737F88941F3B0020354038F02C2@googlmail.com> In-Reply-To: <20120402215920.GB24168@localhost> References: <4F74467C.4060505@googlemail.com> <20120329141237.GC22316@localhost> <4F7475C2.30406@googlemail.com> <4F7485E2.1050803@googlemail.com> <20120402215920.GB24168@localhost> Subject: Re: [TRANSLATION]: Current status X-Mailer: sparrow 1.0.1 (build 424) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="4f7a7b72_6b94764_27f1" X-Virus-Checked: Checked by ClamAV on apache.org --4f7a7b72_6b94764_27f1 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday, 2. April 2012 at 23:59, Ariel Constenla-Haile wrote: > Hi J=C3=BCrgen, > =20 > On Thu, Mar 29, 2012 at 05:55:14PM +0200, J=C3=BCrgen Schmidt wrote: > > Ariel, you can find a new sdf file here > > http://people.apache.org/=7Ejsc/sdf/new=5Fes.sdf > > =20 > > I haven't tested it so far but keep me informed when you start a > > build using it. But the last time I tired it with pt-BR and de it > > worked. > > =20 > =20 > =20 > Please note that I've found some build breakers, and I committed the > changes directly on the localize.sdf file (yes, I read the warning 'DO > NOT EDIT', but as it was a build breaker committing the changes directl= y > was the fastest solution). > =20 > http://svn.apache.org/viewvc=3Fview=3Drevision&revision=3D1308020 > =20 > Build breakers where due to errors in the XML mark up syntax in help > files. > =20 > =20 I will check it... =20 > =20 > Another question related to the ES translation: now that the translatio= n > is 100% complete (both UI and Help), how should be applied the > modifications made by QA=3F Can changes be made on the Pootle server, o= r > better off-line and submit the changes in a issue=3F If the later, what= > should be the format, single modified po files or an sdf file=3F > =20 > =20 I would say the changes should be made on the pootle server. To have for = now one source with the latest translations. But documenting the changes = in an issue is necessary as well that we can track it and know that we ha= ve to update. I will always update the language completely from pootle. I will to do it= somewhat automated ... As I mentioned earlier long term goal is to have a continuous integration= process once a week or so. =20 We will find out what will work best. Juergen > =20 > =20 > =20 > Regards > -- =20 > Ariel Constenla-Haile > La Plata, Argentina > =20 > =20 --4f7a7b72_6b94764_27f1--