Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openoffice.apache.org
MIME-Version: 1.0
Date: Sat, 31 Aug 2013 19:07:34 +0200
Message-ID: 
 <CAK2iWdSLm+Bp=5MrO4HoB5FtRMNwAv4sd1MpLfHUV1q5P+ba+w@mail.gmail.com>
Subject: [announce] genLang extract is ready.
From: janI <jani@apache.org>
To: dev <dev@openoffice.apache.org>
Content-Type: multipart/alternative; boundary=047d7b342d4a19c4c204e541602a

--047d7b342d4a19c4c204e541602a
Content-Type: text/plain; charset=ISO-8859-1

Hi

I am pleased to inform you, that I have reached a major milestone with
genLang.

genLang is now integrated in the build system (for extraction), and  I have
carefully tested that "genLang extract" (generation of .pot template files)
is 100% identical to the existing system (except for the approx 5 errors in
the old system).

Sources are in branches/l10n40 (based on trunk approx start august)
R1519182.

The work flow is:

1) run "build --all --genPO" or "build --genPO"
2) on pootle server:
      "cd aooGenLang; svn up"
      "pootle update_stores" (with parms as normal)
3) on translate.a.o
       "update against templates"
4) translate
5) on pootle server:
        "pootle sync_stores" (with parms as normal)
        "cd aooGenLang; svn commit"

Now translated files are available in our source tree.

I have tested all these steps. We can make a number of elegant
optimizations,
a) allow committers to commit directly in pootle (removes 5)
b) allow committers to run "svn up" (req. a simple php page and removes 2,3)

If someone could review the branch, it would be real nice. Also I need to
check build on windows/mac.

In the meantime I will integrate "genLang convert" so we can get all
current translations into the new system.

and finally integrate "genLang merge" that generates sources with languages.

rgds
jan I.

--047d7b342d4a19c4c204e541602a--