Both good points. I can only speak for the German side, but keeping the original terms makes sense. But if other programming communities are used to full translations (French comes to mind, but I am not sure), we should go with whatever is best for the particular language and culture.
Best Jan -- On 21 Nov 2013, at 18:16 , Facundo Farias <[email protected]> wrote: > 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 <[email protected]> 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 >>
signature.asc
Description: Message signed with OpenPGP using GPGMail
