Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openoffice.apache.org
Message-ID: <5946928F.2040702@apache.org>
Date: Sun, 18 Jun 2017 16:47:43 +0200
From: Andrea Pescetti <pescetti@apache.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: dev@openoffice.apache.org
Subject: Re: Release Manager for 4.2.0?
References: <56AAAD10.7040409@apache.org> <56F83ED7.9010207@apache.org> <86f1c66a-129f-9e89-6026-2156488a9d60@hamburg.de>
In-Reply-To: <86f1c66a-129f-9e89-6026-2156488a9d60@hamburg.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Sun, 18 Jun 2017 14:47:52 -0000

Matthias Seidel wrote:
> Bouncing up your mail from march...

Not only from March, but from March 2016!

> Am 27.03.2016 um 22:13 schrieb Andrea Pescetti:
>> 2) Localization. I got shell access to the Pootle server a few days
>> ago. I'm still looking around, and if someone else want to join this
>> is an important part. We need to have a solid process for updating
>> translations (the full route: new strings in code -> Pootle -> back to
>> code -> in localized builds) in place.
>
> This is the part I would be interested to help!
> Pootle synchronisation is essential for 4.2.0 and beyond.

Good! So the first step would be that you try exporting a language 
(likely German in you case) from Pootle to SDF and check how it looks.

While I assumed Pootle was aligned with 4.1.x (no strings are added 
within the 4.1.x series) Ariel did some work in early 2017 and found out 
that actually Pootle reflects some other, not perfectly clear, status of 
code.

Anyway, the first action I suggest is:

1) Download German PO files from https://translate.apache.org/de/ (you 
will need to login; I've just given you permission to download the PO 
files in case you didn't have them)

2) Convert the PO files to SDF; search "sdf" in 
https://wiki.openoffice.org for documentation

3) Compare the files you obtain with those at
http://svn.apache.org/viewvc/openoffice/branches/AOO413/extras/l10n/source/de/
(note: it's a huge text file, use some reliable editor)

4) You can also build the AOO414 branch -or trunk- with the new SDF if 
you want to have some fun.

This is a first check to understand how stuff works and the translation 
status. Feel free to open a new dedicated discussion for follow-up if 
you need some more information. Note that I only know the high-level 
steps but I'm not familiar with details, so some documentation digging 
will still be needed.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org