Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 36C7810854 for ; Sat, 9 Nov 2013 19:54:18 +0000 (UTC) Received: (qmail 89350 invoked by uid 500); 9 Nov 2013 19:54:17 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 89313 invoked by uid 500); 9 Nov 2013 19:54:17 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 89301 invoked by uid 99); 9 Nov 2013 19:54:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Nov 2013 19:54:17 +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 ipad.wenk@gmail.com designates 209.85.217.179 as permitted sender) Received: from [209.85.217.179] (HELO mail-lb0-f179.google.com) (209.85.217.179) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Nov 2013 19:54:13 +0000 Received: by mail-lb0-f179.google.com with SMTP id w6so2314869lbh.24 for ; Sat, 09 Nov 2013 11:53:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=e75StWY8pCzF0PDT6zftPZsCTU//zaOnUGHn3fLy4VI=; b=TEvv+16GVKLnd+zfqrpuOYdKiyXJBmzn1a/BvBXTofYkTPXYjWxgy+SJe5GgKZ3Dml 1m9/2984qLLA5m8xPd/VevQZH5SGO/TGIEi6MQpdAcKbnwk+mqaOZ+6gzu5GKhIYguUH 0eSt58+tyQS+0bkwYd6eIAKCeZKASCpsgt4dg3nVkg02bwp95+jrVcDGeSaxrpFzSXgD NByw/DGHlHME5P4ObgPjdtfYZgzPkMY2DX639sTPuxjnE7WOssilX6X79SP6eeluQ6sy 4IO/xCmTakJ/Z8lbyzCKFX9QfJB6QbvUMt+j6/d9pKATfTvJCRRHim4Z5adOsQdLWKh8 34FA== X-Received: by 10.152.3.42 with SMTP id 10mr16135218laz.22.1384026831030; Sat, 09 Nov 2013 11:53:51 -0800 (PST) MIME-Version: 1.0 Reply-To: andywenk@apache.org Sender: ipad.wenk@gmail.com Received: by 10.112.65.97 with HTTP; Sat, 9 Nov 2013 11:53:30 -0800 (PST) In-Reply-To: References:

From: Andy Wenk Date: Sat, 9 Nov 2013 20:53:30 +0100 X-Google-Sender-Auth: mallRW5TI9Hd1ziugj-AT42YiWk Message-ID: Subject: Re: INFRA: Pootle translation service for CouchDB questions To: janI Cc: "infrastructure@apache.org" , "dev@couchdb.apache.org" , l10n@couchdb.apache.org Content-Type: multipart/alternative; boundary=089e013d14b29f8fb204eac3dbb1 X-Virus-Checked: Checked by ClamAV on apache.org --089e013d14b29f8fb204eac3dbb1 Content-Type: text/plain; charset=UTF-8 Hi Jan, a huge thanks for your reply and all the insights. This already helps very very much. I now need to find some time to see how we proceed here. We need to integrate the creation and extraction of the .pot and .po files. I did that already manually but it should be done automatically in the build scripts. I would like to come back to you when things are even clearer. Thanks again very much! Cheers Andy On 9 November 2013 11:55, janI wrote: > Hi Andy. > > thanks for your mail, I have added infra@ since others might also want to > read the answers. > > > > On 8 November 2013 22:53, Andy Wenk wrote: > >> Hi Jan, >> >> I have read https://issues.apache.org/jira/browse/INFRA-6888 and would >> like to get a better understanding, of how we can integrate the pootle >> service into the CouchDB CI. In your first comment, you mentioned that you >> have written some tools. What are the for? Can they help us? >> > > The tools I have made is a set of C++ classes with a main, that extract > the original (typical en-US) messages from from source files and generates > template files (.pot). The tool is made is made so that it is very simple > to add new source type (e.g. .java). > > If you use Sphinx that is a good alternative. > > >> >> We will be able to create .po files with Sphinx. I am now wondering, how >> these files can be uploaded to >> https://translate.apache.org/projects/couchdb/ . Is there an API we can >> use? As far as I understood, it is also possible to update existing files - >> what is for sure essential. >> > > There are no api, you do it via the UI. > > >> It would be great if there are some scenario descriptions or experience >> reports. Maybe the folks from the Apache OpenOffice project have some? Or >> can you just give some info? That would be awesome ;-). >> > > I am one of those folks (actually, probably one of two that knows most > about this process) :-) > > Let me first shortly present the normal work pattern, and then show how > you can get started: > > The normal workflow are (please see some of the things as being able to > happen in parallel) > > 1) Write source that contain new/changes en-US messages > 2) extract messages from source files to 1 or more template files (many > projects prefer to group the template files after function, e.g. > help/ui/errors, but you can also have a 1-1 with source files). > 3) Upload changed .pot files (template files, same format as .po just > another name) to pootle using the UI. > 4) Run "update languages against templates" in the UI. This will do the > following: > a) Add new messages to all language files (for each .pot file, you have 1 > .po file pr language), leaving translation empty > b) Mark changes messages as "fuzzy" so the translations can be corrected. > 5) Let translators do their magic online (remark translators can be but > need not be committers) > 6) Run "sync database to po files" > 7) Download po files (as zip) using th UI > 8) Merge po files into the source, as pr your code requirement (in AOO, > the source files is expanded with all languages, so users can switch > online). > 9) Compile and test. > > In order to bootstrap your project, you need to: > 1) define the languages you want to have (UI) > 2) Upload the first set of templates (its a bit tricky, I can do that for > you if you mail me a zip file) > 3) Upload any translatations you may already have > 4) use the above workflow. > > I have some spare cycles and can help you in 2 different ways if you want > it: > a) help setup/load the initial database > > or > b) join the project and help design a workflow fitting for your needs and > of course be there to get it working. > > Please if something is unclear or you need more information, please ask. > > rgds > jan I. > > > >> >> Thanks a lot for your help! >> >> Cheers >> >> Andy >> >> -- >> Andy Wenk >> Hamburg - Germany >> RockIt! >> >> http://www.couchdb-buch.de >> >> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 >> > > -- Andy Wenk Hamburg - Germany RockIt! http://www.couchdb-buch.de GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 --089e013d14b29f8fb204eac3dbb1--