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 CE70990C6 for ; Tue, 6 Mar 2012 12:49:33 +0000 (UTC) Received: (qmail 41177 invoked by uid 500); 6 Mar 2012 12:49:33 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 41111 invoked by uid 500); 6 Mar 2012 12:49:33 -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 41097 invoked by uid 99); 6 Mar 2012 12:49:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Mar 2012 12:49:33 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [195.186.99.133] (HELO zhbdzmsp-smta17.bluewin.ch) (195.186.99.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Mar 2012 12:49:26 +0000 Received: from [195.186.227.130] ([195.186.227.130:35349] helo=zhhdzmsp-smta12.bluewin.ch) by zhbdzmsp-smta17.bluewin.ch (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id 68/07-24898-FB7065F4; Tue, 06 Mar 2012 12:49:03 +0000 Received: from Raphaels-iMac.local (92.104.246.139) by zhhdzmsp-smta12.bluewin.ch (8.5.142) (authenticated as rbircher_aoo) id 4F509CE9006D4E0D for ooo-dev@incubator.apache.org; Tue, 6 Mar 2012 12:49:03 +0000 Message-ID: <4F5607BE.1020507@bluewin.ch> Date: Tue, 06 Mar 2012 13:49:02 +0100 From: Raphael Bircher User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: Please do not work at Pootle atm References: <4F5120DC.4040402@gmx.ch> <4F547A6B.3020501@a-w-f.de> <4F55CFCB.2090807@a-w-f.de> In-Reply-To: <4F55CFCB.2090807@a-w-f.de> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Am 06.03.12 09:50, schrieb Andre Fischer: > On 06.03.2012 09:46, Paolo Pozzan wrote: >> 2012/3/5 Andre Fischer: >>> Hi Raphael, >>> >>> >>> On 02.03.2012 20:34, Raphael Bircher wrote: >>>> >>>> Hi at all >>>> >>>> No panic, I will make this night a new initial import. The reason is, >>>> that we are not sure if the data from the old pootle server are >>>> compleet. So we want to be sure, and so I will import the data from >>>> the >>>> SDF. >>>> >>>> I will import only the language wich we release for the moment. I >>>> hope, >>>> i can do this work util tomorrow >>> >>> >>> I am a bit confused. SDF seems to imply the current data in the >>> extras/l10n >>> module. For at least one language (zn-TW) we know that the data >>> from the >>> old pootle server is more up-to-date. How can we handle that? >> >> Usually previous translations will be merged into the newly extracted >> .po files, so there won't be any loss of data. > > When there are strings that are in both data sets then we have to > choose one, right? Is that done automatically? First at all. I have backups from the data. But yes, we have to merge changes. The problem is, that we have not realy a clean base. We have 3 different sources: - first the SDF in the Source - The backup from the old pootle Server - The Source it self (but the source has no translation, only the en-US strings) The SDF Files works in the build, so they are tecnical clean. But they are probabily not up to date with the localization. The SDF was created before Hamburg stopt working. So samewhat in the March 2011. The Pootle server works much longer, so there are probabily translation in the old Pootle backup wich are not in the SDF. But both include not the new AOO Strings. The Pootle server has a actual Backup from the translation, but this backup commes from a crushed HD. So we are not sure if this files are clean. Not clean po's are a big risk. The data from the source content the additional AOO strings but no translations. What I try to do is the following: debug the existing po from the old Pootle server. Broken language we can't use, the changes will be loost. If you have a actual local copy of the po files from the old Pootle server you can send me the directory in a Zip archive. Dreate new po files based on the AOO Source update pootle Greetings raphael