Return-Path: X-Original-To: apmail-httpd-docs-archive@www.apache.org Delivered-To: apmail-httpd-docs-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B8BC09D18 for ; Fri, 4 May 2012 01:02:44 +0000 (UTC) Received: (qmail 28250 invoked by uid 500); 4 May 2012 01:02:44 -0000 Delivered-To: apmail-httpd-docs-archive@httpd.apache.org Received: (qmail 28079 invoked by uid 500); 4 May 2012 01:02:44 -0000 Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: docs@httpd.apache.org List-Id: Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 28071 invoked by uid 99); 4 May 2012 01:02:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 May 2012 01:02:44 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.160.173] (HELO mail-gy0-f173.google.com) (209.85.160.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 May 2012 01:02:37 +0000 Received: by ghrr14 with SMTP id r14so3147013ghr.18 for ; Thu, 03 May 2012 18:02:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer:x-gm-message-state; bh=UdDZEV8vo1MQAAff07eQWLs5S0vrdStWkHm8ul2o/x4=; b=I0NvAM1R4PtwOtbzJDxMRgOzjaukRzDHZrQAbC0ngi+8woku3YerdYSR9tXKF8c2Cf bDoayoXjRvG4MvE1wcCvX8ADrmcU+R/WTupsnPnXOA0T93Rqhe8M/cAWVKXO1eD6xNac QFpmQcH01uu/OUwTkxT3qi++CTaWuYz+WJ2W3yVYJDmM7g8taxQUgjBkqO6Q3kMA5nvA PKJ/+8i9fIRHLpg+Td2DifMpn5kVKP+5lH1vBxDYF7qtLdHMWEOsHHLgKAhP0cTUEZuK 28/PK64StUgQPgwjocL3cJjzvXTdmebxxiBv2pFRJPpcsVcUvqivRCDvUhCN7IATd5Mv +LmA== Received: by 10.50.189.200 with SMTP id gk8mr1823464igc.57.1336093336279; Thu, 03 May 2012 18:02:16 -0700 (PDT) Received: from [192.168.0.198] (74-131-224-250.dhcp.insightbb.com. [74.131.224.250]) by mx.google.com with ESMTPS id dl10sm394622igb.5.2012.05.03.18.02.14 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 03 May 2012 18:02:15 -0700 (PDT) From: Rich Bowen Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: multipart/alternative; boundary="Apple-Mail=_BB550A17-30CD-413F-9F68-4F50CFE1EE20" Subject: Re: Comments in docs Date: Thu, 3 May 2012 21:02:13 -0400 In-Reply-To: To: docs@httpd.apache.org References: <66CBEEE9-9F7A-4B57-B218-EE68F01725A0@rcbowen.com> Message-Id: <14A53A7A-1B5B-4846-BD39-C384ECFD70D9@rcbowen.com> X-Mailer: Apple Mail (2.1257) X-Gm-Message-State: ALoCoQkZ3YhBlIIwO4IcSer4jV8GrOBOCZhOUklLSGwgSoRA43Zb8RwnCuhSFoRM8AYGUaWmUlrA X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_BB550A17-30CD-413F-9F68-4F50CFE1EE20 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On May 3, 2012, at 8:13 PM, Kyle Hamilton wrote: >=20 > On Thu, May 3, 2012 at 1:17 PM, Rich Bowen wrote: >>=20 >>>=20 >>> Is it possible to integrate different languages? (And how do we = moderate >>> those?) >>>=20 >>=20 >> I expect people can post in any language. We can then use google = translate >> to moderate them. That usually works well enough to understand the = intent. >=20 > The best way to ensure that one has a useful Google translation is to = substitute to the intended language, then translate back from the = intended to the original language. If the idea translated back out is = close to the intended statement, it's probably fine. If not, there will = likely be major communications issues, and should be reworded. >=20 > To put this in practice while writing documentation comments, perhaps = have a secondary window/iframe/whatever that shows the output of = translating xx -> en -> xx. When the writer accepts it, save/post both = the original xx and the en transform. The comments are not part of the documentation. They are comments. They = may eventually result in changes to the documentation, but as a comment, = they serve merely to start the conversation. That's why I thought that, = in this context, an exact and grammatical translation wasn't critical. -- Rich Bowen rbowen@rcbowen.com :: @rbowen rbowen@apache.org --Apple-Mail=_BB550A17-30CD-413F-9F68-4F50CFE1EE20 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

On Thu, May 3, 2012 at 1:17 PM, Rich Bowen <rbowen@rcbowen.com> = wrote:


Is it possible to integrate = different languages? (And how do we = moderate
those?)


I expect people = can post in any language. We can then use google = translate
to moderate them. = That usually works well enough to understand the = intent.

The best way to ensure that one has a useful = Google translation is to substitute to the intended language, then = translate back from the intended to the original language.  If the = idea translated back out is close to the intended statement, it's = probably fine.  If not, there will likely be major communications = issues, and should be reworded.

To put this in practice while = writing documentation comments, perhaps have a secondary = window/iframe/whatever that shows the output of translating xx -> en = -> xx.  When the writer accepts it, save/post both the original = xx and the en transform.

The comments = are not part of the documentation. They are comments. They may = eventually result in changes to the documentation, but as a comment, = they serve merely to start the conversation. That's why I thought that, = in this context, an exact and grammatical translation wasn't = critical.

--
Rich Bowen
rbowen@rcbowen.com :: = @rbowen
rbowen@apache.org

= --Apple-Mail=_BB550A17-30CD-413F-9F68-4F50CFE1EE20--