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 1F79F104FF for ; Sun, 17 Nov 2013 00:33:04 +0000 (UTC) Received: (qmail 47134 invoked by uid 500); 17 Nov 2013 00:33:03 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 47104 invoked by uid 500); 17 Nov 2013 00:33:03 -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 47096 invoked by uid 99); 17 Nov 2013 00:33:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Nov 2013 00:33:03 +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.215.52 as permitted sender) Received: from [209.85.215.52] (HELO mail-la0-f52.google.com) (209.85.215.52) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Nov 2013 00:32:59 +0000 Received: by mail-la0-f52.google.com with SMTP id ev20so3833837lab.39 for ; Sat, 16 Nov 2013 16:32:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:from:date:message-id:subject:to:cc :content-type; bh=Oda7Lu2PFyIhDyf7Jxe1jPwfo3zNTLgfRtH4ocAEkL8=; b=CJch3mkjsF0E+ykGAJlUkMXhe7bKMfULk6zN/XmatExluNU5qiRbbhSo9W/UgYjDU7 /9fFvCtp1G4LWVgcDLB9v1NVV/ct51m+q1aWajWrS7HzW1kFDYLSoY5djpq7+CseLuBR W+2AtjvaHD9o7ot/XpFKr360gvIoiR2AnTU8XFgdWypAQC0ExB6euGYrGpb7o3biOpfF biN8/AUkTrw1rRws+YDIpn+yJgrSWr8lID3xBv6rbMPnIwnZefppQv0I/+FdSzZR+w6B KUv5+CE1J1XH0SC61gcHpqejS8dKUqNxEExswK0tf2sTDViEWzBNJgSlP7oIBTiIxh7a HiBw== X-Received: by 10.152.120.73 with SMTP id la9mr8252323lab.3.1384648358129; Sat, 16 Nov 2013 16:32:38 -0800 (PST) MIME-Version: 1.0 Reply-To: andy@nms.de Sender: ipad.wenk@gmail.com Received: by 10.112.65.97 with HTTP; Sat, 16 Nov 2013 16:32:18 -0800 (PST) From: Andy Wenk Date: Sun, 17 Nov 2013 01:32:18 +0100 X-Google-Sender-Auth: kwCnGM6ZCJ3K0OijAW1K0PIO1so Message-ID: Subject: Let's start translating To: "dev@couchdb.apache.org" Cc: janI Content-Type: multipart/alternative; boundary=089e011766e586767604eb5491ef X-Virus-Checked: Checked by ClamAV on apache.org --089e011766e586767604eb5491ef Content-Type: text/plain; charset=UTF-8 Hi all, I would like to let the translators start their work. As of today, we have eleven languages setup at https://translate.apache.org/projects/CouchDB/ . There are around the same amount of people, who want to translate. That's pretty awesome imho ;-). I have clarified the process for adding translators to pootle as users with INFRA. A big thanks again to jan I. for setting everything up and for his help. I have now admin rights and am able (also Noah) to create users. The next step would be to create user accounts for the translators form the l10n-mailing-list. They will receive an email with instructions to confirm the creation of their account. But before that, I want to make sure that the created .pot files uploaded to pootle are correct and are usable. I created the files from share/doc/src. That means, that the translations would result in the translated versions of http://docs.couchdb.org/en/latest/. Here are some questions and discussion points: / we still have not integrated the creation of the .pot files to the build process. Is this a blocker? (Note: at this time, I would need help to do this) / there is no api for uploading (changed) .pot files to https://translate.apache.org/de/CouchDB/ . Is this a blocker? / there is also no api for downloading translated .po files for integration into the src. But it is possible to download a zip file like this (from my machine at least): wget -O couchdb-de.zip https://translate.apache.org/de/CouchDB/export/zip where de is interchangeable with the available languages and the zip archive is including all the .po files. Furthermore it is not clear to me, if we want to have the .po files in the source at all. I personally would integrate them in the way I proposed in another post. What is your opinion here? I think Alex started to grab into this already. / the process for generating the translated docs is not done yet. Here, I also need help from someone with more experience in the build process than I have today. / should we start with the translations or does it make more sense to wait until we have integrated the creation of the .pot files automatically? So as a summary the setup for starting with the translations at https://translate.apache.org/de/CouchDB/ is done. But the technical parts regarding the build process are not done yet. I appreciate your help in this point very much. Thanks a lot for your input and thoughts on this. Cheers Andy -- Andy Wenk Hamburg - Germany RockIt! http://www.couchdb-buch.de http://www.pg-praxisbuch.de GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 --089e011766e586767604eb5491ef--