Return-Path: X-Original-To: apmail-couchdb-l10n-archive@minotaur.apache.org Delivered-To: apmail-couchdb-l10n-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 542ED10338 for ; Thu, 21 Nov 2013 17:17:16 +0000 (UTC) Received: (qmail 60196 invoked by uid 500); 21 Nov 2013 17:17:16 -0000 Delivered-To: apmail-couchdb-l10n-archive@couchdb.apache.org Received: (qmail 60165 invoked by uid 500); 21 Nov 2013 17:17:16 -0000 Mailing-List: contact l10n-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: l10n@couchdb.apache.org Delivered-To: mailing list l10n@couchdb.apache.org Received: (qmail 60156 invoked by uid 99); 21 Nov 2013 17:17:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Nov 2013 17:17:15 +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 facundo.farias@gmail.com designates 209.85.160.54 as permitted sender) Received: from [209.85.160.54] (HELO mail-pb0-f54.google.com) (209.85.160.54) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Nov 2013 17:17:11 +0000 Received: by mail-pb0-f54.google.com with SMTP id un15so26340pbc.41 for ; Thu, 21 Nov 2013 09:16:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=NAA+/qCf6QugKUQzXpKdndIqcsWuEzB4dR00BhPjB2g=; b=B6Y6FYhiZGK/GXf91V6lfWwLfDDrmaJb3DzKSb9Jeh5c3H9S4/xeldEbgQlLH+ceN/ OvrGbmUH5kD54hrYWM6SyS+VAXvZOWtVbmnvucdG69fPM1zxGNpzFUYCXHjE25GIbbz7 sbtEf8ZwVBn+qylPY+KrWcetsuc9znni+7wGyPlFJFUN38uhVu98emYVp+aYKorruidP 75Ups9Lo28NTEpGjp5ZfxXvn1SEWWItHFwx5g6BlsK61DiGRQl7b4yCNNX/IdZLVbTRf gx0Hmvx3cc6I8hOxMN0gqa4JK4fZFQACLL/LvahUtWMCP/XYqG/l1Dlvy74A15e5qhDr yG6Q== X-Received: by 10.66.231.6 with SMTP id tc6mr7345419pac.68.1385054211040; Thu, 21 Nov 2013 09:16:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.68.6.104 with HTTP; Thu, 21 Nov 2013 09:16:30 -0800 (PST) In-Reply-To: References: From: Facundo Farias Date: Thu, 21 Nov 2013 15:16:30 -0200 Message-ID: Subject: Re: How to translate well known english words? To: l10n@couchdb.apache.org, andy@nms.de Content-Type: multipart/alternative; boundary=047d7b15a0813e6cdc04ebb3104d X-Virus-Checked: Checked by ClamAV on apache.org --047d7b15a0813e6cdc04ebb3104d Content-Type: text/plain; charset=ISO-8859-1 Agree, I think that this documentation will be used by developers and they already know what is a "request" or a "response". Good catch! Facundo. On Thu, Nov 21, 2013 at 2:12 PM, Andy Wenk wrote: > Hi all, > > I am asking myself how we translate well known english words in the context > of CouchDB. These words are for example: > > * view > * request > * response > > and furthermore > > * replication > * compaction > > and so on ... > > In my opinion, we should keep these words and do not translate them. When > we have sth. like > > "Request the database with the following URL" > > we could translate it to (in German): > > "Sende einen Request mit der folgenden URL an die Datenbank" > > What is your opinion here? When we found a solution, we should do that in > all languages - if possible. > > Please remember, that there is also the navigation point "Terminology" > where we should insert these decisions. > > 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 > --047d7b15a0813e6cdc04ebb3104d--