Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-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 BAF1AE832 for ; Thu, 17 Jan 2013 03:04:27 +0000 (UTC) Received: (qmail 39686 invoked by uid 500); 17 Jan 2013 03:04:27 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 39600 invoked by uid 500); 17 Jan 2013 03:04:26 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 39575 invoked by uid 99); 17 Jan 2013 03:04:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 03:04:25 +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: domain of olemis@gmail.com designates 209.85.223.177 as permitted sender) Received: from [209.85.223.177] (HELO mail-ie0-f177.google.com) (209.85.223.177) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 03:04:20 +0000 Received: by mail-ie0-f177.google.com with SMTP id k13so4014618iea.36 for ; Wed, 16 Jan 2013 19:04:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=LTg2wtDK6kbQE6Sr2xc8RbW2O34TmJVui9/dU5vhRxk=; b=HTGWKVJJLvvgs86KKiPAymH5nyzf2xOfWln3ZRk7qT9w7jatIpyvbOmypd1JZo2KsS rd621gZVmVuHpxxfiKMQ5fLtze3VRd+aG3Yn9kDYD5trovaLkOgUKYcf+0e6qohr4GPZ S7dDmAs2WunLgalyoDydhe5+W2gPYQbdVYqz26VkToQf7Ep8Kckuck6+ZEEyaOznNXCq Ia0hnvDU9n13hmnBheg404Voj2cw6/D5vBACiABKB5qA1dqmdGBRA+mbEYFO39UMjWhN spyDWTT3Wn1pzi5i2ZGAKVRlhBVis+liTPg9Hd0UIh0jvqxoNuNWAo+Z+TuswNDd9Wyl EJhw== MIME-Version: 1.0 X-Received: by 10.43.82.72 with SMTP id ab8mr2272490icc.33.1358391839968; Wed, 16 Jan 2013 19:03:59 -0800 (PST) Received: by 10.50.1.44 with HTTP; Wed, 16 Jan 2013 19:03:59 -0800 (PST) Date: Wed, 16 Jan 2013 22:03:59 -0500 Message-ID: Subject: Bloodhound i18n , translations , and alike ... From: Olemis Lang To: bloodhound-dev Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org As could be expected , after some successful installations there is interest in an issue tracker oriented to communities sharing common language and cultural characteristics . Nowadays Trac offers very good translations . Nonetheless , since the very moment Apache=99 Bloodhound changed / introduced different approaches to UX / UI , it turns out that such support is not as effective as it should . Therefore I'm putting this subject on the table for our consideration . 1. What shall be done about translations ? 2. Should something be started for Release 5 ? 3. What would be the translation workflow ? Like Trac's ? How does it work ? 4. Current resources about i18n for Trac extensions / plugins ? 5. Translators ... where are they ? ;) 6. Will such translations be included in ASF svn repos ? in trunk ? 7. What will be the impact on the release process ? 8. Is Apache=99 Bloodhound code base ready for translation ? 9. ... ? :P As you can see , many questions indeed . Please throw your $0.02 coins ... = ;) PS: More precisely we have received requests for Spanish and Portuguese translations . According to my skills I could contribute to Spanish and French translations . --=20 Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: