{"thread":{"id":"9877","subject":"RFC: German translation vocabulary","startedAt":"2007-09-16T12:38:37Z","lastAt":"2007-09-17T19:56:55Z","messageCount":18,"participants":["Christian Stimming","David Soria","David Kastrup","Alexander Wuerstlein","Michele Ballabio","Simon Richter","Florian Weimer","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"53186","messageId":"200709161438.37733.stimming@tuhh.de","threadId":"9877","inReplyTo":null,"subject":"RFC: German translation vocabulary","fromName":"Christian Stimming","fromEmail":"stimming@tuhh.de","sentAt":"2007-09-16T12:38:37Z","receivedAt":"2007-09-16T12:38:37Z","isPatch":false,"sender":{"key":"stimming@tuhh.de","avatar":"https://avatars.githubusercontent.com/u/227778?v=4"},"body":"Dear all,\n\nas git-gui has now picked up the i18n features and the initial German \ntranslation has been included as well, it is about time to discuss and \nfinalize the actual translation wordings of git terminology in German. \n\nIn particular, for all keywords of git and git-gui one needs to find \ncorresponding keywords in German, which will then be used consistently \nthroughout all of git-gui translations. Those keywords and (for some of them) \ntheir english definition are contained in the \"glossary\" file, see [1]. I \nwould like to invite all German-speaking readers here to review the German \nkeyword translations that have been chosen in the glossary, and I'll denote \nthe most important ones below for immediate feedback. \n\n(I'll mostly stick to an english discussion so that other languages can use \nthis as a model on how to discuss this, if they want to.)\n\nOne word on the intended audience for the translated git-gui: The translated \nform of git-gui is *not for you* :-). In other words, it is not intended for \nthose who are reading this list and, by doing so, are completely familiar \nwith all the English terminology of git. Instead, the translation is intended \nfor German developers who know *some* English, but feel much more comfortable \nwith a fully German development environment and probably wouldn't touch an \nenglish-language git-gui anyway. Hence, the translation should try really \nhard to find German words wherever possible.\n\nAlso, other version control systems have worked on their German translation as \nwell. If you want to check the wordings that have been chosen there, I'd \nrecommend looking into their translations [2].\n\nI'll list the most important glossary terms here, starting with the easier \nones:\n\nrepository - Projektarchiv\nrevision - Version\nstaging area - Bereitstellung\nbranch [noun] - Zweig\nbranch  [verb] - verzweigen\nworking copy, working tree - Arbeitskopie\n[commit] message - Meldung (Nachricht?; Source Safe: Kommentar)\n\nFor some of them you can see alternatives considered in the glossary [1], but \noverall the above ones were rather easy. Now for the difficult ones:\n\ncommit [noun] \ncommit [verb]\ncheckout [noun]\ncheckout [verb]\n\nI'm still rather unsure what to do about them. One problem here is that both \nwords are used in several different meanings all at once. For example, \nthe \"commit [noun]\" is used interchangeably with \"revision\". I'm actually \ninclined to translate it with \"Version\" for exactly that reason. And \nthen \"checkout\": The noun is probably used interchangeably with \"working \ncopy\". Hence, it could be translated as such. OTOH the verb means \"to update \nthe working copy\", and it could be translated as such instead of one single \nword. This would leave only \"commit [verb]\" as the last tricky issue for \nwhich a single-word translation must be found. \"übertragen\" is my current \nfavorite but I'm absolutely open for further proposals here.\n\nAs you can see in the glossary file, I'm still unhappy with the translations \nfor those, but anyway here's the current status (not taking into account the \ndiscussion of the previous paragraph so far):\n\nmsgid \"checkout [noun]\"\nmsgstr \"Auscheck? Ausspielung? Abruf? (Source Safe: Auscheckvorgang)\"\n\nmsgid \"checkout [verb]\"\nmsgstr \"auschecken? ausspielen? abrufen? (Source Safe: auschecken)\"\n\nmsgid \"commit [noun]\"\nmsgstr \"Übertragung (Sendung?, Übergabe?, Einspielung?, Ablagevorgang?)\"\n\nmsgid \"commit [verb]\"\nmsgstr \"übertragen (TortoiseSVN: übertragen; Source Safe: einchecken; senden?, \nübergeben?, einspielen?, einpflegen?, ablegen?)\"\n\nRegards,\n\nChristian Stimming\n\n\n[1] http://repo.or.cz/w/git-gui.git?a=blob_plain;f=po/glossary/de.po;hb=HEAD \n(note: the file is in UTF-8, but repo.or.cz's webserver claims it is latin1, \nhence the messed-up Umlauts)\n\n[2] \n* http://tortoisesvn.net/docs/release/TortoiseSVN_de/index.html (very good)\n* http://msdn.microsoft.com/de-de/library/ms181038(vs.80).aspx (MS Visual \nSource Safe, commercial)\n* http://cvsbook.red-bean.com/translations/german/Kap_06.html (not so good)\n* \nhttp://tortoisecvs.cvs.sourceforge.net/tortoisecvs/po/TortoiseCVS/de_DE.po?view=markup \n(not so good)\n* http://rapidsvn.tigris.org/svn/rapidsvn/trunk/src/locale/de/rapidsvn.po \n(username=guest, password empty, quite bad)\n"},{"id":"53187","messageId":"fcjgfg$56m$1@sea.gmane.org","threadId":"9877","inReplyTo":"200709161438.37733.stimming@tuhh.de","subject":"Re: RFC: German translation vocabulary","fromName":"David Soria","fromEmail":"sn_@gmx.net","sentAt":"2007-09-16T15:01:04Z","receivedAt":"2007-09-16T15:01:04Z","isPatch":false,"sender":{"key":"sn_@gmx.net","avatar":"https://gravatar.com/avatar/b1075ecdd33ea094cbc23798fe8b95c73ec1ccf7bb213ac8260c719e2dd97b55?d=mp&s=160"},"body":"Am Sun, 16 Sep 2007 14:38:37 +0200 schrieb Christian Stimming:\n\n\n\nHi Christian,\n\nthank you for bringing up the topic, it's really worth discussing it.\n\n> [commit] message - Meldung (Nachricht?; Source Safe: Kommentar)\nI prefer \"Kommentar\" here. It describes better what the commit message is\nabout. \"Meldung\" has some co-notations that don't fit (like e.g.\n\"Meldung\" often involes other people, like you \"meldest\" something to\nsomebody).\n \n> I'm still rather unsure what to do about them. One problem here is that\n> both words are used in several different meanings all at once. For\n> example, the \"commit [noun]\" is used interchangeably with \"revision\".\n> I'm actually inclined to translate it with \"Version\" for exactly that\n> reason. And then \"checkout\": The noun is probably used interchangeably\n> with \"working copy\". Hence, it could be translated as such. OTOH the\n> verb means \"to update the working copy\", and it could be translated as\n> such instead of one single word. This would leave only \"commit [verb]\"\n> as the last tricky issue for which a single-word translation must be\n> found. \"übertragen\" is my current favorite but I'm absolutely open for\n> further proposals here.\n> \n> As you can see in the glossary file, I'm still unhappy with the\n> translations for those, but anyway here's the current status (not taking\n> into account the discussion of the previous paragraph so far):\n> \nReally hard. I would prefer some larger explanations if they fit into the\napplication and make sense on every label in the gui.\n\n\n> msgid \"commit [noun]\"\n> msgstr \"Übertragung (Sendung?, Übergabe?, Einspielung?, Ablagevorgang?)\"\nÜbertragung fits well, but for me it has a co-notation that something is\ntransfered from one point to another (e.g. using an internet connection)\nSo this translation would fit perfectly for centralized versioning\nsystems, where the changeset is really \"transfered\" to somewhere. I would\nprefer the term \"Einspielung\" as I think it reflects better, that the\ncommit is locally.\n\nDavid\n"},{"id":"53188","messageId":"85bqc24pjg.fsf@lola.goethe.zz","threadId":"9877","inReplyTo":"fcjgfg$56m$1@sea.gmane.org","subject":"Re: RFC: German translation vocabulary","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2007-09-16T15:07:31Z","receivedAt":"2007-09-16T15:07:31Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"David Soria <sn_@gmx.net> writes:\n\n> Am Sun, 16 Sep 2007 14:38:37 +0200 schrieb Christian Stimming:\n>\n> Hi Christian,\n>\n> thank you for bringing up the topic, it's really worth discussing it.\n>\n>> [commit] message - Meldung (Nachricht?; Source Safe: Kommentar)\n> I prefer \"Kommentar\" here. It describes better what the commit message is\n> about. \"Meldung\" has some co-notations that don't fit (like e.g.\n> \"Meldung\" often involes other people, like you \"meldest\" something to\n> somebody).\n\n\"Beschreibung\"?\n\n-- \nDavid Kastrup, Kriemhildstr. 15, 44793 Bochum\n"},{"id":"53189","messageId":"857imq4pi0.fsf@lola.goethe.zz","threadId":"9877","inReplyTo":"85bqc24pjg.fsf@lola.goethe.zz","subject":"Re: RFC: German translation vocabulary","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2007-09-16T15:08:23Z","receivedAt":"2007-09-16T15:08:23Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"David Kastrup <dak@gnu.org> writes:\n\n> David Soria <sn_@gmx.net> writes:\n>\n>> Am Sun, 16 Sep 2007 14:38:37 +0200 schrieb Christian Stimming:\n>>\n>> Hi Christian,\n>>\n>> thank you for bringing up the topic, it's really worth discussing it.\n>>\n>>> [commit] message - Meldung (Nachricht?; Source Safe: Kommentar)\n>> I prefer \"Kommentar\" here. It describes better what the commit message is\n>> about. \"Meldung\" has some co-notations that don't fit (like e.g.\n>> \"Meldung\" often involes other people, like you \"meldest\" something to\n>> somebody).\n>\n> \"Beschreibung\"?\n\nOder \"Zusammenfassung\"?\n\n-- \nDavid Kastrup, Kriemhildstr. 15, 44793 Bochum\n"},{"id":"53190","messageId":"fcjh5i$56m$2@sea.gmane.org","threadId":"9877","inReplyTo":"857imq4pi0.fsf@lola.goethe.zz","subject":"Re: RFC: German translation vocabulary","fromName":"David Soria","fromEmail":"sn_@gmx.net","sentAt":"2007-09-16T15:12:50Z","receivedAt":"2007-09-16T15:12:50Z","isPatch":false,"sender":{"key":"sn_@gmx.net","avatar":"https://gravatar.com/avatar/b1075ecdd33ea094cbc23798fe8b95c73ec1ccf7bb213ac8260c719e2dd97b55?d=mp&s=160"},"body":"> Oder \"Zusammenfassung\"?\n>\n\nprobably the best translation yet\n"},{"id":"53205","messageId":"20070916172341.GA17021@cip.informatik.uni-erlangen.de","threadId":"9877","inReplyTo":"200709161438.37733.stimming@tuhh.de","subject":"Re: RFC: German translation vocabulary","fromName":"Alexander Wuerstlein","fromEmail":"snalwuer@cip.informatik.uni-erlangen.de","sentAt":"2007-09-16T17:23:42Z","receivedAt":"2007-09-16T17:23:42Z","isPatch":false,"sender":{"key":"snalwuer@cip.informatik.uni-erlangen.de","avatar":null},"body":"On 070916 14:46, Christian Stimming <stimming@tuhh.de> wrote:\n> msgid \"commit [noun]\"\n> msgstr \"?bertragung (Sendung?, ?bergabe?, Einspielung?, Ablagevorgang?)\"\n\n\"Vorgang\"? (think Beamtendeutsch)\n\n\n\nCiao,\n\nAlexander Wuerstlein.\n"},{"id":"53211","messageId":"46ED8789.4010208@hogyros.de","threadId":"9877","inReplyTo":"200709161438.37733.stimming@tuhh.de","subject":"Re: RFC: German translation vocabulary","fromName":"Simon Richter","fromEmail":"simon.richter@hogyros.de","sentAt":"2007-09-16T19:44:09Z","receivedAt":"2007-09-16T19:44:09Z","isPatch":false,"sender":{"key":"simon.richter@hogyros.de","avatar":"https://gravatar.com/avatar/1192aa9fa5dd19ce258b12b044cc27111dd7cdb58d920dc2123a02a24f55b5c5?d=mp&s=160"},"body":"Hallo,\n\nChristian Stimming wrote:\n\n> repository - Projektarchiv\n\nJust \"Archiv\" would be fine as well in most places, I think.\n\n> revision - Version\n> staging area - Bereitstellung\n\nThe Windows world uses this word as a translation for \"deployment\", i.e. \nmaking binaries available to end users.\n\nMaybe \"Vorbereitung\" would be better here.\n\n> commit [noun] \n> commit [verb]\n\n\"einspielen\"? Problem is that this cannot be properly turned into a noun.\n\n> checkout [noun]\n> checkout [verb]\n\n\"Erstellung einer Arbeitskopie\" (gets less awkward when you make proper \nsentences from it).\n\n    Simon\n"},{"id":"53210","messageId":"200709162211.16872.barra_cuda@katamail.com","threadId":"9877","inReplyTo":"200709161438.37733.stimming@tuhh.de","subject":"RFC: Italian translation vocabulary","fromName":"Michele Ballabio","fromEmail":"barra_cuda@katamail.com","sentAt":"2007-09-16T20:11:16Z","receivedAt":"2007-09-16T20:11:16Z","isPatch":false,"sender":{"key":"barra_cuda@katamail.com","avatar":"https://avatars.githubusercontent.com/u/16371673?v=4"},"body":"[Thank you, Christian. I'll use your mail as a template for the\nItalian speakers, as most issues apply here as well. For those\ninterested, s/German/Italian/ :). Appended there's a draft of the\nItalian glossary.]\n\nOn Sunday 16 September 2007, Christian Stimming wrote:\n> Dear all,\n> \n> as git-gui has now picked up the i18n features and the initial German \n> translation has been included as well, it is about time to discuss and \n> finalize the actual translation wordings of git terminology in German. \n> \n> In particular, for all keywords of git and git-gui one needs to find \n> corresponding keywords in German, which will then be used consistently \n> throughout all of git-gui translations. Those keywords and (for some of them) \n> their english definition are contained in the \"glossary\" file, see [1]. I \n> would like to invite all German-speaking readers here to review the German \n> keyword translations that have been chosen in the glossary, and I'll denote \n> the most important ones below for immediate feedback. \n> \n> (I'll mostly stick to an english discussion so that other languages can use \n> this as a model on how to discuss this, if they want to.)\n> \n> One word on the intended audience for the translated git-gui: The translated \n> form of git-gui is *not for you* :-). In other words, it is not intended for \n> those who are reading this list and, by doing so, are completely familiar \n> with all the English terminology of git. Instead, the translation is intended \n> for German developers who know *some* English, but feel much more comfortable \n> with a fully German development environment and probably wouldn't touch an \n> english-language git-gui anyway. Hence, the translation should try really \n> hard to find German words wherever possible.\n> \n> Also, other version control systems have worked on their German translation as \n> well. If you want to check the wordings that have been chosen there, I'd \n> recommend looking into their translations [2].\n> \n> I'll list the most important glossary terms here, starting with the easier \n> ones:\n\nThese are the terms currently used in it.po:\n\nrepository - archivio, repository\nrevision - revisione\nstaging area - area di preparazione\nbranch [noun] - ramo\nbranch [verb] - creare ramo (well, git-gui never uses \"branch\" as a verb,\n                actually)\nworking copy, working tree - directory di lavoro (git-gui uses the espression\n                             \"working directory\")\n[commit] message - messaggio\nfetch - recuperare, prelevare\n\nNote: in it.po, \"repository\" is sometimes left untranslated and sometimes\ntraslated as \"archivio\". Also, git-gui uses the term \"database\" too.\nShould it be translated in the same way? Currently is left unchanged. We\nprobably should use the same term throughout all the translation. The\nsame applies to \"fetch\"; which one is better: \"recuperare\" or \"prelevare\"\n(we currently use both)?\n\n> For some of them you can see alternatives considered in the glossary [1], but \n> overall the above ones were rather easy. Now for the difficult ones:\n>\n> commit [noun] \n> commit [verb]\n> checkout [noun]\n> checkout [verb]\n\nThese are currently left untranslated in it.po. \"commit [verb]\" becomes\n\"effettuare un commit\". Other SCM suggest \"depositare\" or \"inviare\". If we\ntranslate \"repository\" with \"archivio\" we may as well translate\n\"commit [verb]\" with \"archiviare\".\n\n> I'm still rather unsure what to do about them. One problem here is that both \n> words are used in several different meanings all at once. For example, \n> the \"commit [noun]\" is used interchangeably with \"revision\". I'm actually \n> inclined to translate it with \"Version\" for exactly that reason. And \n> then \"checkout\": The noun is probably used interchangeably with \"working \n> copy\". Hence, it could be translated as such. OTOH the verb means \"to update \n> the working copy\", and it could be translated as such instead of one single \n> word. This would leave only \"commit [verb]\" as the last tricky issue for \n> which a single-word translation must be found. \"übertragen\" is my current \n> favorite but I'm absolutely open for further proposals here.\n\nFollowing these advices, \"commit [noun]\" will be \"revisione\",\n\"checkout [noun]\" \"revisione attiva\", and \"checkout [verb]\"\n\"attivare revisione\".\n\n> As you can see in the glossary file, I'm still unhappy with the translations \n> for those, but anyway here's the current status (not taking into account the \n> discussion of the previous paragraph so far):\n\nI've highlighted like *this* the terms currently used in it.po:\n\nmsgid \"checkout [noun]\"\nmsgstr \"*checkout*, revisione attiva, prelievo (TortoiseCVS)?\"\n\nmsgid \"checkout [verb]\"\nmsgstr \"effettuare un checkout, attivare revisione, prelevare (TortoiseCVS),\nritirare (TSVN)?\"\n\nmsgid \"commit [noun]\"\nmsgstr \"*commit*, revisione, deposito (TortoiseCVS), invio (TSVN)?\"\n\nmsgid \"commit [verb]\"\nmsgstr \"*effettuare un commit*, archiviare, depositare (nel server),\nfare un deposito (TortoiseCVS), inviare (TSVN)?\"\n\n\nThen, I think there are some problems regarding English terms\nvs Git terms vs Italian terms.\n\nE.g. these are the current translations:\n\nreset - *ripristinare*, *annullare* (reset is used as a Git term,\n        but with different meanings)\nrevert - *annullare* (Git term)\nundo - *annullare* (English term)\n\nI.e. there's an overlap: the same Italian word is used in three\ndifferent contexts (and two of them with different Git commands).\nWe should try to have an 1:1 relationship here. Or, at least,\nmore different terms in Italian than in Gittish :)\n\n\n> [1]\n\nSee below an Italian glossary proposal.\n \n> [2]\n\n* http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/Languages/Tortoise_it.po\n  (username=guest, password empty)\n* http://tortoisecvs.cvs.sourceforge.net/tortoisecvs/po/TortoiseCVS/it_IT.po?view=markup\n* http://rapidsvn.tigris.org/svn/rapidsvn/trunk/src/locale/it_IT/rapidsvn.po\n  (username=guest, password empty)\n\n---\n# Translation of git-gui glossary to Italian\n# Copyright (C) 2007 Shawn Pearce, et al.\n# This file is distributed under the same license as the git package.\n# Christian Stimming <stimming@tuhh.de>, 2007\n#\nmsgid \"\"\nmsgstr \"\"\n\"Project-Id-Version: git-gui glossary\\n\"\n\"PO-Revision-Date: 2007-07-29 16:24+0200\\n\"\n\"Last-Translator: Michele Ballabio <barra_cuda@katamail.com>\\n\"\n\"Language-Team: Italian \\n\"\n\"MIME-Version: 1.0\\n\"\n\"Content-Type: text/plain; charset=UTF-8\\n\"\n\"Content-Transfer-Encoding: 8bit\\n\"\n\n#. \"English Definition (Dear translator: This file will never be visible to the user! It should only serve as a tool for you, the translator. Nothing more.)\"\nmsgid \"\"\n\"English Term (Dear translator: This file will never be visible to the user!)\"\nmsgstr \"\"\n\"Traduzione italiana.\\n\"\n\"Altri SCM in italiano:\\n\"\n\"  http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/Languages/Tortoise_it.po (username=guest, password empty),\\n\"\n\"  http://tortoisecvs.cvs.sourceforge.net/tortoisecvs/po/TortoiseCVS/it_IT.po?view=markup ,\\n\"\n\"  http://rapidsvn.tigris.org/svn/rapidsvn/trunk/src/locale/it_IT/rapidsvn.po (username=guest, password empty)\"\n\"Le traduzioni evidenziate con '*' sono quelle correntemente utilizzate.\"\n\n#. \"\"\nmsgid \"amend\"\nmsgstr \"correggere, correzione\"\n\n#. \"\"\nmsgid \"annotate\"\nmsgstr \"annotare, annotazione\"\n\n#. \"A 'branch' is an active line of development.\"\nmsgid \"branch [noun]\"\nmsgstr \"*ramo*, diramazione, ramificazione\"\n\n#. \"\"\nmsgid \"branch [verb]\"\nmsgstr \"creare ramo, ramificare, diramare\"\n\n#. \"\"\nmsgid \"checkout [noun]\"\nmsgstr \"*checkout*, revisione attiva, prelievo (TortoiseCVS)?\"\n\n#. \"The action of updating the working tree to a revision which was stored in the object database.\"\nmsgid \"checkout [verb]\"\nmsgstr \"effettuare un checkout, attivare revisione, prelevare (TortoiseCVS), ritirare (TSVN)?\"\n\n#. \"A single point in the git history.\"\nmsgid \"commit [noun]\"\nmsgstr \"*commit*, revisione, deposito (TortoiseCVS), invio (TSVN)?\"\n\n#. \"The action of storing a new snapshot of the project's state in the git history.\"\nmsgid \"commit [verb]\"\nmsgstr \"*effettuare un commit*, archiviare, depositare (nel server), fare un deposito (TortoiseCVS), inviare (TSVN)?\"\n\n#. \"\"\nmsgid \"diff [noun]\"\nmsgstr \"*differenza*, confronto, comparazione, raffronto\"\n\n#. \"\"\nmsgid \"diff [verb]\"\nmsgstr \"confronta, mostra le differenze\"\n\n#. \"A fast-forward is a special type of merge where you have a revision and you are merging another branch's changes that happen to be a descendant of what you have.\"\nmsgid \"fast forward merge\"\nmsgstr \"*fusione in 'fast-forward'*, fusione in avanti veloce\"\n\n#. \"Fetching a branch means to get the branch's head from a remote repository, to find out which objects are missing from the local object database, and to get them, too.\"\nmsgid \"fetch\"\nmsgstr \"*recuperare*, *prelevare*, prendere da, recuperare (TSVN)\"\n\n#. \"A collection of files. The index is a stored version of your working tree.\"\nmsgid \"index (in git-gui: staging area)\"\nmsgstr \"*indice*\"\n\n#. \"A successful merge results in the creation of a new commit representing the result of the merge.\"\nmsgid \"merge [noun]\"\nmsgstr \"*fusione*, unione\"\n\n#. \"To bring the contents of another branch into the current branch.\"\nmsgid \"merge [verb]\"\nmsgstr \"*effettuare la fusione*, unire, fondere, eseguire la fusione\"\n\n#. \"\"\nmsgid \"message\"\nmsgstr \"*messaggio*, commento\"\n\n#. \"Pulling a branch means to fetch it and merge it.\"\nmsgid \"pull\"\nmsgstr \"prendi (recupera) e fondi (unisci)? (in pratica una traduzione di fetch + merge)\"\n\n#. \"Pushing a branch means to get the branch's head ref from a remote repository, and ... (well, can someone please explain it for mere mortals?)\"\nmsgid \"push\"\nmsgstr \"*propaga*\"\n\n#. \"\"\nmsgid \"redo\"\nmsgstr \"*ripeti*, rifai\"\n\n#. \"A collection of refs (?) together with an object database containing all objects which are reachable from the refs... (oops, you've lost me here. Again, please an explanation for mere mortals?)\"\nmsgid \"repository\"\nmsgstr \"*archivio*, *repository*, database? deposito (rapidsvn)?\"\n\n#. \"\"\nmsgid \"reset\"\nmsgstr \"*ripristinare*, *(annullare)*, azzerare, ripristinare\"\n\n#. \"\"\nmsgid \"revert\"\nmsgstr \"*annullare*, inverti (rapidsvn), ritorna allo stato precedente, annulla le modifiche della revisione\"\n\n#. \"A particular state of files and directories which was stored in the object database.\"\nmsgid \"revision\"\nmsgstr \"*revisione* (TortoiseSVN)\"\n\n#. \"\"\nmsgid \"sign off\"\nmsgstr \"*sign off*, firma\"\n\n#. \"\"\nmsgid \"staging area\"\nmsgstr \"*area di preparazione*, zona di preparazione, modifiche in preparazione? modifiche in allestimento?\"\n\n#. \"\"\nmsgid \"status\"\nmsgstr \"stato\"\n\n#. \"A ref pointing to a tag or commit object\"\nmsgid \"tag [noun]\"\nmsgstr \"*etichetta*, etichettatura (TortoiseCVS)\"\n\n#. \"\"\nmsgid \"tag [verb]\"\nmsgstr \"etichettare\"\n\n#. \"A regular git branch that is used to follow changes from another repository.\"\nmsgid \"tracking branch\"\nmsgstr \"*ramo in 'tracking'*, ramo inseguitore? ramo di {inseguimento,allineamento,rilevamento,puntamento}?\"\n\n#. \"\"\nmsgid \"undo\"\nmsgstr \"*annulla*\"\n\n#. \"\"\nmsgid \"update\"\nmsgstr \"*aggiornamento*, *aggiornare*\"\n\n#. \"\"\nmsgid \"verify\"\nmsgstr \"*verifica*, *verificare*\"\n\n#. \"The tree of actual checked out files.\"\nmsgid \"working copy, working tree\"\nmsgstr \"*directory di lavoro*, copia di lavoro\"\n"},{"id":"53214","messageId":"87y7f6fjjl.fsf@mid.deneb.enyo.de","threadId":"9877","inReplyTo":"200709161438.37733.stimming@tuhh.de","subject":"Re: RFC: German translation vocabulary","fromName":"Florian Weimer","fromEmail":"fw@deneb.enyo.de","sentAt":"2007-09-16T20:21:34Z","receivedAt":"2007-09-16T20:21:34Z","isPatch":false,"sender":{"key":"fw@deneb.enyo.de","avatar":null},"body":"* Christian Stimming:\n\n> repository - Projektarchiv\n\n\"Projekt\" or \"Archiv\" should suffice.\n\n> revision - Version\n\n\"Versionsangabe\", probably.  I think \"revision\" is most used as a\nshort form of \"revision specifier\".\n\n> staging area - Bereitstellung\n\n\"Index\"?\n\n> branch [noun] - Zweig\n> branch  [verb] - verzweigen\n\nOr \"abzweigen\", if it's used transitive.\n\n> [commit] message - Meldung (Nachricht?; Source Safe: Kommentar)\n\nI came up with David's \"Beschreibung\" independently.  It fits better\nto \"Sammlung\" below than \"Zusammenfassung\", IMHO.\n\n> For some of them you can see alternatives considered in the glossary [1], but \n> overall the above ones were rather easy. Now for the difficult ones:\n>\n> commit [noun] \n> commit [verb]\n\n\"Sammlung\" and \"sammeln\".\n\n> checkout [noun]\n> checkout [verb]\n\nHow's a checkout different from a working copy?\n\nBut to be honest, I wouldn't translate \"repository\" and \"commit\", at\nleast if they are used as nouns.\n"},{"id":"53220","messageId":"851wcy47n4.fsf@lola.goethe.zz","threadId":"9877","inReplyTo":"20070916172341.GA17021@cip.informatik.uni-erlangen.de","subject":"Re: RFC: German translation vocabulary","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2007-09-16T21:34:07Z","receivedAt":"2007-09-16T21:34:07Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"Alexander Wuerstlein <snalwuer@cip.informatik.uni-erlangen.de> writes:\n\n> On 070916 14:46, Christian Stimming <stimming@tuhh.de> wrote:\n>> msgid \"commit [noun]\"\n>> msgstr \"?bertragung (Sendung?, ?bergabe?, Einspielung?, Ablagevorgang?)\"\n>\n> \"Vorgang\"? (think Beamtendeutsch)\n\nBuchung, Einbuchung, Verbuchung, Registrierung?\n\n-- \nDavid Kastrup, Kriemhildstr. 15, 44793 Bochum\n"},{"id":"53221","messageId":"85wsuq2sza.fsf@lola.goethe.zz","threadId":"9877","inReplyTo":"46ED8789.4010208@hogyros.de","subject":"Re: RFC: German translation vocabulary","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2007-09-16T21:36:09Z","receivedAt":"2007-09-16T21:36:09Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"Simon Richter <Simon.Richter@hogyros.de> writes:\n\n> Hallo,\n>\n> Christian Stimming wrote:\n>\n>> repository - Projektarchiv\n>\n> Just \"Archiv\" would be fine as well in most places, I think.\n\nAgreed.\n\n-- \nDavid Kastrup, Kriemhildstr. 15, 44793 Bochum\n"},{"id":"53222","messageId":"85sl5e2sx5.fsf@lola.goethe.zz","threadId":"9877","inReplyTo":"87y7f6fjjl.fsf@mid.deneb.enyo.de","subject":"Re: RFC: German translation vocabulary","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2007-09-16T21:37:26Z","receivedAt":"2007-09-16T21:37:26Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"Florian Weimer <fw@deneb.enyo.de> writes:\n\n>> commit [noun] \n>> commit [verb]\n>\n> \"Sammlung\" and \"sammeln\".\n\nDoesn't fit because \"sammeln\" is what you do _before_ committing.\n\n-- \nDavid Kastrup, Kriemhildstr. 15, 44793 Bochum\n"},{"id":"53264","messageId":"20070917075433.GF17021@cip.informatik.uni-erlangen.de","threadId":"9877","inReplyTo":"851wcy47n4.fsf@lola.goethe.zz","subject":"Re: RFC: German translation vocabulary","fromName":"Alexander Wuerstlein","fromEmail":"snalwuer@cip.informatik.uni-erlangen.de","sentAt":"2007-09-17T07:54:33Z","receivedAt":"2007-09-17T07:54:33Z","isPatch":false,"sender":{"key":"snalwuer@cip.informatik.uni-erlangen.de","avatar":null},"body":"On 070916 23:34, David Kastrup <dak@gnu.org> wrote:\n> Alexander Wuerstlein <snalwuer@cip.informatik.uni-erlangen.de> writes:\n> \n> > On 070916 14:46, Christian Stimming <stimming@tuhh.de> wrote:\n> >> msgid \"commit [noun]\"\n> >> msgstr \"?bertragung (Sendung?, ?bergabe?, Einspielung?, Ablagevorgang?)\"\n> >\n> > \"Vorgang\"? (think Beamtendeutsch)\n> \n> Buchung, Einbuchung, Verbuchung, Registrierung?\n\nTransaktion?\n\n\nCiao,\n\nAlexander Wuerstlein.\n"},{"id":"53277","messageId":"Pine.LNX.4.64.0709171013230.28586@racer.site","threadId":"9877","inReplyTo":"20070917075433.GF17021@cip.informatik.uni-erlangen.de","subject":"Re: RFC: German translation vocabulary","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-09-17T09:17:55Z","receivedAt":"2007-09-17T09:17:55Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Mon, 17 Sep 2007, Alexander Wuerstlein wrote:\n\n> On 070916 23:34, David Kastrup <dak@gnu.org> wrote:\n> > Alexander Wuerstlein <snalwuer@cip.informatik.uni-erlangen.de> writes:\n> > \n> > > On 070916 14:46, Christian Stimming <stimming@tuhh.de> wrote:\n> > >> msgid \"commit [noun]\"\n> > >> msgstr \"?bertragung (Sendung?, ?bergabe?, Einspielung?, Ablagevorgang?)\"\n> > >\n> > > \"Vorgang\"? (think Beamtendeutsch)\n> > \n> > Buchung, Einbuchung, Verbuchung, Registrierung?\n> \n> Transaktion?\n\nThe real problem is that we use \"commit\" in two senses:\n\n- the action (\"to commit\", but also, \"to do a commit\") of making a new \n  revision, but also\n\n- the revision in the revision graph (\"is this in the commit abcdef?\").\n\nSo I do not think that any proposals reflect the ambiguity of \"a commit\".\nI actually talk about \"Revision\" in German, when I refer to a commit.\n\nCiao,\nDscho\n"},{"id":"53302","messageId":"86myvlmpiy.fsf@lola.quinscape.zz","threadId":"9877","inReplyTo":"20070917075433.GF17021@cip.informatik.uni-erlangen.de","subject":"Re: RFC: German translation vocabulary","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2007-09-17T12:42:45Z","receivedAt":"2007-09-17T12:42:45Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"Alexander Wuerstlein <snalwuer@cip.informatik.uni-erlangen.de> writes:\n\n> On 070916 23:34, David Kastrup <dak@gnu.org> wrote:\n>> Alexander Wuerstlein <snalwuer@cip.informatik.uni-erlangen.de> writes:\n>> \n>> > On 070916 14:46, Christian Stimming <stimming@tuhh.de> wrote:\n>> >> msgid \"commit [noun]\"\n>> >> msgstr \"?bertragung (Sendung?, ?bergabe?, Einspielung?, Ablagevorgang?)\"\n>> >\n>> > \"Vorgang\"? (think Beamtendeutsch)\n>> \n>> Buchung, Einbuchung, Verbuchung, Registrierung?\n>\n> Transaktion?\n\nWell, I might be biased against anything not from myself, but\n\"Transaktion\" is anything with a permanent effect, so I find this term\ntoo unspecific: it would equally well cover resetting, tagging,\nand a number of other things.\n\n-- \nDavid Kastrup\n"},{"id":"53339","messageId":"200709172109.18539.stimming@tuhh.de","threadId":"9877","inReplyTo":"Pine.LNX.4.64.0709171013230.28586@racer.site","subject":"Re: RFC: German translation vocabulary","fromName":"Christian Stimming","fromEmail":"stimming@tuhh.de","sentAt":"2007-09-17T19:09:17Z","receivedAt":"2007-09-17T19:09:17Z","isPatch":false,"sender":{"key":"stimming@tuhh.de","avatar":"https://avatars.githubusercontent.com/u/227778?v=4"},"body":"Am Montag, 17. September 2007 11:17 schrieb Johannes Schindelin:\n> > > >> msgid \"commit [noun]\"\n> > > >> msgstr \"?bertragung (Sendung?, ?bergabe?, Einspielung?,\n> > > >> Ablagevorgang?)\"\n> > > >\n> > > > \"Vorgang\"? (think Beamtendeutsch)\n> > >\n> > > Buchung, Einbuchung, Verbuchung, Registrierung?\n> >\n> > Transaktion?\n>\n> The real problem is that we use \"commit\" in two senses:\n>\n> - the action (\"to commit\", but also, \"to do a commit\") of making a new\n>   revision, but also\n>\n> - the revision in the revision graph (\"is this in the commit abcdef?\").\n\nThis is exactly the noun vs. the verb ambiguity. This is exactly why those are \nmentioned as two different entries in the glossary.\n\n> So I do not think that any proposals reflect the ambiguity of \"a commit\".\n> I actually talk about \"Revision\" in German, when I refer to a commit.\n\nYes, that's what I am leaning towards as well. Let's see.\n\nChristian\n"},{"id":"53343","messageId":"200709172145.26291.stimming@tuhh.de","threadId":"9877","inReplyTo":"87y7f6fjjl.fsf@mid.deneb.enyo.de","subject":"Re: RFC: German translation vocabulary","fromName":"Christian Stimming","fromEmail":"stimming@tuhh.de","sentAt":"2007-09-17T19:45:26Z","receivedAt":"2007-09-17T19:45:26Z","isPatch":false,"sender":{"key":"stimming@tuhh.de","avatar":"https://avatars.githubusercontent.com/u/227778?v=4"},"body":"Thanks for the replies so far. I'll summarize the proposals below, and I'll \ntake the freedom to reply to them directly.  (Note: Please CC: me on replies \nas I'm not subscribed to this list - too much traffic for me.)\n\nOne thing to keep in mind (one reader proposed to use \"commit\" \nand \"repository\" in untranslated form): This translation is really about \ntranslating the program, and the intended audience are those people who are \n*not* familiar with the English git terminology. Hence, I really really want \nto try hard to avoid untranslated terminology here. German really has enough \nwords to choose from (just like every other language), so that it should be \npossible to avoid using untranslated English words just because we couldn't \ncome up with German ones that fir.\n\n> repository - Projektarchiv\n\nSimon Richter thinks just \"Archiv\" would be fine as well in most places. \nFlorian Weimar says \"Projekt\" or \"Archiv\" should suffice. David Kastrup \nagrees to this.\n\nI think \"Archiv\" sounds quite unspecific, because it can be another room, or \nanother harddisk, or another directory. Whereas a git repository is \nparticular to this single git project. Also, when reading through the \nTortoiseSVN docs, \"Projektarchiv\" worked quite nicely. I'd still stick to \nthis.\n\n> revision - Version\n\nFlorian Weimar proposes \"Versionsangabe\". He thinks \"revision\" is most used as \na short form of \"revision specifier\".\n\nI think in sentences like \"let's switch the working copy from revision xyz to \nrevision abc\" the word \"Version\" would work much better than any longer form. \nI'd stick to this, especially since this proposal came here from the mailing \nlist already :-)\n\n> staging area - Bereitstellung\n\nSimon Richter remarks this German word is being used a translation \nfor \"deployment\", i.e. making binaries available to end users (however, this \nis probably specific to some particular development environment, isn't it?). \nHe thinks \"Vorbereitung\" would be better here. Florian Weimar \nproposes \"Index\".\n\nI think the word should have a connotation of \"another place which is \nseparated from the working copy\". The military term \"Bereitstellung\" IMHO \ngives this rather nicely. I haven't seen that term in the ambiguous meaning \nSimon pointed out; is this a problem? As for \"Index\": As mentioned above it \nshould be possible to find a German word here. \n\n> branch [noun] - Zweig\n\nNo comments to this one; it seems to be just fine.\n\n> branch  [verb] - verzweigen\n\nFlorian Weimar mentiones \"abzweigen\", if it's used transitive.\n\nIn itself \"abzweigen\" is a nice word, but \"verzweigen\" gives more of the \n(desired) connotation of a tree's branches (uh oh! Linas will beat me for \nthis! Of course this isn't a tree, it's a graph!) and hence for consistency I \nwould stick to \"verzweigen\".\n\n> working copy, working tree - Arbeitskopie\n\nNo comments to this one (or did I miss anyone); it seems to be just fine.\n\n> [commit] message - Meldung (Nachricht?; Source Safe: Kommentar)\n\nDavid Soria first preferred \"Kommentar\". David Kastrup \nproposes \"Beschreibung\", or later instead \"Zusammenfassung\", which then David \nSoria thinks is the best so far.\n\nI think \"Zusammenfassung\" would rather describe what the diffstat is about, as \nthis summarizes the actual commit. As we're naming \"the short text that \ndescribes what this is about\", I think actually \"Beschreibung\" is probably \nbest so far.\n\n> msgid \"checkout [noun]\"\n> msgstr \"Auscheck? Ausspielung? Abruf? (Source Safe: Auscheckvorgang)\"\n>\n> msgid \"checkout [verb]\"\n> msgstr \"auschecken? ausspielen? abrufen? (Source Safe: auschecken)\"\n\nSimon Richter proposed the long translation \"Erstellung einer Arbeitskopie\" \n(gets less awkward when you make proper sentences from it). Florian Weimar \nasks how's a checkout different from a working copy? But he wouldn't \ntranslate \"repository\" and \"commit\", at least if they are used as nouns.\n\nI agree with Simon Richter here, just as I've already explained in my initial \nemail: The noun should probably simply be the working copy, \"Arbeitskopie\", \nand the verb should be something with \"Arbeitskopie erstellen\". However, we \nhave strings like \"Checkout this branch...\", and those need yet another word. \nMaybe \"Arbeitskopie umstellen\"? I'm still unsure.\n\n> msgid \"commit [noun]\"\n> msgstr \"Übertragung (Sendung?, Übergabe?, Einspielung?, Ablagevorgang?)\"\n\nAlexander Wuerstlein proposed \"Vorgang\" (think governmental German). Florian \nWeimar proposes \"Sammlung\" and \"sammeln\", to which David Kastrup replied it \ndoesn't fit because \"sammeln\" is what you do _before_ committing. In addition \nDavid Kastrup proposes Buchung, Einbuchung, Verbuchung, Registrierung. \nAlexander Wuerstlein proposes \"Transaktion\", to which David replied he \nthinks \"Transaktion\" is anything with a permanent effect, so he finds this \nterm too unspecific: it would equally well cover resetting, tagging, and a \nnumber of other things. (Also, it wouldn't work as a verb.)\n\nI think we should try to replace this (the noun!) with \"revision\" and hence \ntranslate it as \"Version\". However, this needs to be checked in actual \nstrings in the program.\n\n> msgid \"commit [verb]\"\n> msgstr \"übertragen (TortoiseSVN: übertragen; Source Safe: einchecken;\n> senden?, übergeben?, einspielen?, einpflegen?, ablegen?)\"\n\nDavid Soria prefers \"Einspielung\" as he think it reflects better, that the\ncommit is locally. Simon Richter proposes \"einspielen\"? Problem is that this \ncannot be properly turned into a noun.\n\nThis verb appears on the one-word button \"commit\", which is obviously the most \nimportant button in git-gui. I think both \"einspielen\" and \"übertragen\" would \nwork in that context, but David Kastrup's proposals of \"buchen\" \nor \"verbuchen\" and the others of \"einpflegen\", \"ablegen\" might also work. Yet \nmore proposals, or other hints which one of these would work best?\n\nThanks for all the suggestions. This should be thought about for a few more \ndays, and then I'll prepare an updated German glossary file to be committed \nto the repository.\n\nRegards,\n\nChristian\n"},{"id":"53347","messageId":"87fy1dhxq0.fsf@mid.deneb.enyo.de","threadId":"9877","inReplyTo":"200709172145.26291.stimming@tuhh.de","subject":"Re: RFC: German translation vocabulary","fromName":"Florian Weimer","fromEmail":"fw@deneb.enyo.de","sentAt":"2007-09-17T19:56:55Z","receivedAt":"2007-09-17T19:56:55Z","isPatch":false,"sender":{"key":"fw@deneb.enyo.de","avatar":null},"body":"* Christian Stimming:\n\n> This verb appears on the one-word button \"commit\", which is\n> obviously the most important button in git-gui. I think both\n> \"einspielen\" and \"übertragen\" would work in that context,\n\nBy the way, what about \"eintragen\"?  It's got the advantage that\n\"Eintrag\" is a nicen oun.\n"}]}