{"thread":{"id":"30944","subject":"[RFC] l10n: de.po: translate 29 new messages","startedAt":"2012-07-03T17:04:46Z","lastAt":"2012-07-06T20:12:59Z","messageCount":10,"participants":["Ralf Thielow","Christian Stimming","Andreas Schwab","Michael J Gruber","Peter Baumann"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"194530","messageId":"1341335086-6767-1-git-send-email-ralf.thielow@gmail.com","threadId":"30944","inReplyTo":null,"subject":"[RFC] l10n: de.po: translate 29 new messages","fromName":"Ralf Thielow","fromEmail":"ralf.thielow@gmail.com","sentAt":"2012-07-03T17:04:46Z","receivedAt":"2012-07-03T17:04:46Z","isPatch":false,"sender":{"key":"ralf.thielow@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1275832?v=4"},"body":"Translate 29 new messages came from git.pot update\nin 11b9017 (l10n: Update git.pot (29 new messages)).\n\nSigned-off-by: Ralf Thielow <ralf.thielow@gmail.com>\n---\n\nHi German translation team,\n\nplease review this update of German translation.\nThis patch might not be applicable directly because\nit's based on a preparation commit which just contains\nchanges of \"msgmerge\". After this patch passed the\nreview, i'll merge them together.\n\nThanks,\nRalf\n\n po/de.po | 92 +++++++++++++++++++++++++++-------------------------------------\n 1 Datei geändert, 38 Zeilen hinzugefügt(+), 54 Zeilen entfernt(-)\n\ndiff --git a/po/de.po b/po/de.po\nindex 96b993b..0cbcd64 100644\n--- a/po/de.po\n+++ b/po/de.po\n@@ -71,9 +71,8 @@ msgstr[0] \"Das Paket enthält %d Referenz\"\n msgstr[1] \"Das Paket enthält %d Referenzen\"\n \n #: bundle.c:192\n-#, fuzzy\n msgid \"The bundle records a complete history.\"\n-msgstr \"Das Paket benötigt diese Referenz\"\n+msgstr \"Das Paket speichert eine komplette Historie.\"\n \n #: bundle.c:195\n #, c-format\n@@ -696,11 +695,8 @@ msgstr \"\"\n \"Bereitstellung)\"\n \n #: wt-status.c:174\n-#, fuzzy\n msgid \"  (use \\\"git add <file>...\\\" to mark resolution)\"\n-msgstr \"\"\n-\"  (benutze \\\"git add/rm <Datei>...\\\" um die Auflösung entsprechend zu \"\n-\"markieren)\"\n+msgstr \"  (benutze \\\"git add/rm <Datei>...\\\" um die Auflösung zu markieren)\"\n \n #: wt-status.c:176 wt-status.c:180\n msgid \"  (use \\\"git add/rm <file>...\\\" as appropriate to mark resolution)\"\n@@ -709,11 +705,8 @@ msgstr \"\"\n \"markieren)\"\n \n #: wt-status.c:178\n-#, fuzzy\n msgid \"  (use \\\"git rm <file>...\\\" to mark resolution)\"\n-msgstr \"\"\n-\"  (benutze \\\"git add/rm <Datei>...\\\" um die Auflösung entsprechend zu \"\n-\"markieren)\"\n+msgstr \"  (benutze \\\"git add/rm <Datei>...\\\" um die Auflösung zu markieren)\"\n \n #: wt-status.c:189\n msgid \"Changes to be committed:\"\n@@ -844,112 +837,104 @@ msgid \"bug: unhandled diff status %c\"\n msgstr \"Fehler: unbehandelter Differenz-Status %c\"\n \n #: wt-status.c:786\n-#, fuzzy\n msgid \"You have unmerged paths.\"\n-msgstr \"Nicht zusammengeführte Pfade:\"\n+msgstr \"Du hast nicht zusammengeführte Pfade.\"\n \n #: wt-status.c:789 wt-status.c:913\n-#, fuzzy\n msgid \"  (fix conflicts and run \\\"git commit\\\")\"\n-msgstr \" (benutze \\\"git add\\\" und/oder \\\"git commit -a\\\")\"\n+msgstr \" (behebe die Konflikte und führe \\\"git commit\\\" aus)\"\n \n #: wt-status.c:792\n msgid \"All conflicts fixed but you are still merging.\"\n-msgstr \"\"\n+msgstr \"Alle Konflikte sind behoben, aber du bist immer noch beim \"\n+\"Zusammenführen.\"\n \n #: wt-status.c:795\n-#, fuzzy\n msgid \"  (use \\\"git commit\\\" to conclude merge)\"\n-msgstr \"\"\n-\"Zusammenführung wurde nicht eingetragen; benutze 'git commit' um die \"\n-\"Zusammenführung abzuschließen.\\n\"\n+msgstr \"  (benutze \\\"git commit\\\" um die Zusammenführung abzuschließen)\"\n \n #: wt-status.c:805\n-#, fuzzy\n msgid \"You are in the middle of an am session.\"\n-msgstr \"Eine Zusammenführung ist im Gange -- kann nicht nachbessern.\"\n+msgstr \"Eine \\\"am\\\"-Sitzung ist im Gange.\"\n \n #: wt-status.c:808\n msgid \"The current patch is empty.\"\n-msgstr \"\"\n+msgstr \"Der aktuelle Patch ist leer.\"\n \n #: wt-status.c:812\n msgid \"  (fix conflicts and then run \\\"git am --resolved\\\")\"\n-msgstr \"\"\n+msgstr \"  (behebe die Konflikte und führe dann \\\"git am --resolved\\\" aus)\"\n \n #: wt-status.c:814\n-#, fuzzy\n msgid \"  (use \\\"git am --skip\\\" to skip this patch)\"\n-msgstr \" (benutze \\\"git add\\\" zum Beobachten)\"\n+msgstr \" (benutze \\\"git am --skip\\\" um diesen Patch auszulassen)\"\n \n #: wt-status.c:816\n msgid \"  (use \\\"git am --abort\\\" to restore the original branch)\"\n-msgstr \"\"\n+msgstr \"  (benutze \\\"git am --abort\\\" um den ursprünglichen Zweig \"\n+\"wiederherzustellen)\"\n \n #: wt-status.c:874 wt-status.c:884\n-#, fuzzy\n msgid \"You are currently rebasing.\"\n-msgstr \"Du befindest dich auf keinem Zweig.\"\n+msgstr \"Du bist gerade beim Neuaufbau.\"\n \n #: wt-status.c:877\n msgid \"  (fix conflicts and then run \\\"git rebase --continue\\\")\"\n-msgstr \"\"\n+msgstr \"  (behebe die Konflikte und führe dann \\\"git rebase --continue\\\" aus)\"\n \n #: wt-status.c:879\n-#, fuzzy\n msgid \"  (use \\\"git rebase --skip\\\" to skip this patch)\"\n-msgstr \"\"\n-\"  (benutze \\\"git reset %s <Datei>...\\\" zum Herausnehmen aus der \"\n-\"Bereitstellung)\"\n+msgstr \"  (benutze \\\"git rebase --skip\\\" um diesen Patch auszulassen)\"\n \n #: wt-status.c:881\n msgid \"  (use \\\"git rebase --abort\\\" to check out the original branch)\"\n-msgstr \"\"\n+msgstr \"  (benutze \\\"git rebase --abort\\\" um den ursprünglichen Zweig \"\n+\"auszuchecken)\"\n \n #: wt-status.c:887\n msgid \"  (all conflicts fixed: run \\\"git rebase --continue\\\")\"\n-msgstr \"\"\n+msgstr \"  (alle Konflikte behoben: führe \\\"git rebase --continue\\\" aus)\"\n \n #: wt-status.c:889\n msgid \"You are currently splitting a commit during a rebase.\"\n-msgstr \"\"\n+msgstr \"Du teilst gerade eine Version während eines Neuaufbaus auf.\"\n \n #: wt-status.c:892\n msgid \"  (Once your working directory is clean, run \\\"git rebase --continue\\\")\"\n-msgstr \"\"\n+msgstr \"  (Sobald dein Arbeitsverzeichnis sauber ist, führe \"\n+\"\\\"git rebase --continue\\\" aus)\"\n \n #: wt-status.c:894\n-#, fuzzy\n msgid \"You are currently editing a commit during a rebase.\"\n-msgstr \"\"\n-\"Kann keine partielle Eintragung durchführen, während eine Zusammenführung im \"\n-\"Gange ist.\"\n+msgstr \"Du editierst gerade eine Version während eines Neuaufbaus.\"\n \n #: wt-status.c:897\n msgid \"  (use \\\"git commit --amend\\\" to amend the current commit)\"\n-msgstr \"\"\n+msgstr \"  (benutze \\\"git commit --amend\\\" um die aktuelle Version \"\n+\"nachzubessern)\"\n \n #: wt-status.c:899\n msgid \"\"\n \"  (use \\\"git rebase --continue\\\" once you are satisfied with your changes)\"\n-msgstr \"\"\n+msgstr \"  (benutze \\\"git rebase --continue\\\" sobald deine Änderungen \"\n+\"abgeschlossen sind)\"\n \n #: wt-status.c:909\n msgid \"You are currently cherry-picking.\"\n-msgstr \"\"\n+msgstr \"Du führst gerade \\\"cherry-pick\\\" aus.\"\n \n #: wt-status.c:916\n msgid \"  (all conflicts fixed: run \\\"git commit\\\")\"\n-msgstr \"\"\n+msgstr \"  (alle Konflikte behoben: führe \\\"git commit\\\" aus)\"\n \n #: wt-status.c:925\n-#, fuzzy\n msgid \"You are currently bisecting.\"\n-msgstr \"Wir sind nicht beim Halbieren.\"\n+msgstr \"Du bist gerade beim Halbieren.\"\n \n #: wt-status.c:928\n msgid \"  (use \\\"git bisect reset\\\" to get back to the original branch)\"\n-msgstr \"\"\n+msgstr \"  (benutze \\\"git bisect reset\\\" um zum ursprünglichen Zweig \"\n+\"zurückzukehren)\"\n \n #: wt-status.c:979\n msgid \"On branch \"\n@@ -3175,9 +3160,9 @@ msgstr \"SHA1 KOLLISION MIT %s GEFUNDEN !\"\n \n #: builtin/index-pack.c:649 builtin/pack-objects.c:170\n #: builtin/pack-objects.c:262\n-#, fuzzy, c-format\n+#, c-format\n msgid \"unable to read %s\"\n-msgstr \"konnte %s nicht schreiben\"\n+msgstr \"kann %s nicht lesen\"\n \n #: builtin/index-pack.c:715\n #, c-format\n@@ -3228,9 +3213,8 @@ msgid \"pack has junk at the end\"\n msgstr \"Paketende enthält nicht verwendbaren Inhalt\"\n \n #: builtin/index-pack.c:1028\n-#, fuzzy\n msgid \"confusion beyond insanity in parse_pack_objects()\"\n-msgstr \"Fehler beim Auflösen der Unterschiede\"\n+msgstr \"Fehler beim Ausführen von \\\"parse_pack_objects()\\\"\"\n \n #: builtin/index-pack.c:1051\n msgid \"Resolving deltas\"\n@@ -4066,9 +4050,9 @@ msgid \"Unknown subcommand: %s\"\n msgstr \"Unbekanntes Unterkommando: %s\"\n \n #: builtin/pack-objects.c:183 builtin/pack-objects.c:186\n-#, fuzzy, c-format\n+#, c-format\n msgid \"deflate error (%d)\"\n-msgstr \"Fehler am anderen Ende: %s\"\n+msgstr \"Fehler beim Komprimieren (%d)\"\n \n #: builtin/pack-objects.c:2398\n #, c-format\n-- \n1.7.11.1\n"},{"id":"194557","messageId":"2021839.rMjHRWft8I@cs-pc","threadId":"30944","inReplyTo":"1341335086-6767-1-git-send-email-ralf.thielow@gmail.com","subject":"Re: [RFC] l10n: de.po: translate 29 new messages","fromName":"Christian Stimming","fromEmail":"stimming@tuhh.de","sentAt":"2012-07-03T20:03:50Z","receivedAt":"2012-07-03T20:03:50Z","isPatch":false,"sender":{"key":"stimming@tuhh.de","avatar":"https://avatars.githubusercontent.com/u/227778?v=4"},"body":"Hi Ralf,\n\nvery good. I have a few remarks, though, on particularly chosen word \ntranslations:\n\nAm Dienstag, 3. Juli 2012, 19:04:46 schrieb Ralf Thielow:\n>  #: wt-status.c:874 wt-status.c:884\n> -#, fuzzy\n>  msgid \"You are currently rebasing.\"\n> -msgstr \"Du befindest dich auf keinem Zweig.\"\n> +msgstr \"Du bist gerade beim Neuaufbau.\"\n\nIs \"rebase\" = \"Neuaufbau\"? My last thought on this wording was \"rebase\" = \n\"Umpflanzen\".\n\n>  #: wt-status.c:889\n>  msgid \"You are currently splitting a commit during a rebase.\"\n> -msgstr \"\"\n> +msgstr \"Du teilst gerade eine Version während eines Neuaufbaus auf.\"\n\nMaybe\n\"Du teilst gerade eine Version auf während eines Neuaufbaus.\"\n\n>  #: wt-status.c:909\n>  msgid \"You are currently cherry-picking.\"\n> -msgstr \"\"\n> +msgstr \"Du führst gerade \\\"cherry-pick\\\" aus.\"\n\nI thought \"cherry-pick\" = \"pflücken\", or is there a different glossary choice?\n\nThanks!\n\nChristian\n"},{"id":"194601","messageId":"CAN0XMO+R3+JiuHSZ0O46py2WbXVh8D2Z+f7t_xofsN6ZrFwnQQ@mail.gmail.com","threadId":"30944","inReplyTo":"2021839.rMjHRWft8I@cs-pc","subject":"Re: [RFC] l10n: de.po: translate 29 new messages","fromName":"Ralf Thielow","fromEmail":"ralf.thielow@gmail.com","sentAt":"2012-07-04T07:20:40Z","receivedAt":"2012-07-04T07:20:40Z","isPatch":false,"sender":{"key":"ralf.thielow@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1275832?v=4"},"body":"Hi Christian,\n\nthanks for your review.\n\nOn Tue, Jul 3, 2012 at 10:03 PM, Christian Stimming <stimming@tuhh.de> wrote:\n> Hi Ralf,\n\n> Am Dienstag, 3. Juli 2012, 19:04:46 schrieb Ralf Thielow:\n>>  #: wt-status.c:874 wt-status.c:884\n>> -#, fuzzy\n>>  msgid \"You are currently rebasing.\"\n>> -msgstr \"Du befindest dich auf keinem Zweig.\"\n>> +msgstr \"Du bist gerade beim Neuaufbau.\"\n>\n> Is \"rebase\" = \"Neuaufbau\"? My last thought on this wording was \"rebase\" =\n> \"Umpflanzen\".\n\nAccording to the current state of the glossary on GitHub, \"rebase\" as a\nverb is translated as \"neu aufbauen\". There are already translations using\nthis. For example:\n\n#: builtin/remote.c:998\n#, c-format\nmsgid \"rebases onto remote %s\"\nmsgstr \"baut neu auf externen Zweig %s auf\"\n\nIn this translation, \"rebase\" is used as a noun for the very first time.\nSo, I simply translate it with \"Neuaufbau\". In fact, we can use different\ntranslations for verbs and nouns. Not really sure whether we should do this\nfor \"rebase\".\n\nUsing \"Umpflanzen\" for \"rebase\" as a noun, would result in\nmsgstr \"Du bist gerade beim Umplanzen.\"\nUsing \"Umplanzen\" was a verb, would result in\nmsgstr \"Du planzt gerade um.\"\n\nFor me, \"Umpflanzen\" sounds a bit like \"working with plants\nin the garden\". I do not have a strong opinion on this, though.\n\nAre there thoughts from others?\n\n>>  #: wt-status.c:889\n>>  msgid \"You are currently splitting a commit during a rebase.\"\n>> -msgstr \"\"\n>> +msgstr \"Du teilst gerade eine Version während eines Neuaufbaus auf.\"\n>\n> Maybe\n> \"Du teilst gerade eine Version auf während eines Neuaufbaus.\"\n>\n\nI don't think that this is grammatically correct.\n\n>>  #: wt-status.c:909\n>>  msgid \"You are currently cherry-picking.\"\n>> -msgstr \"\"\n>> +msgstr \"Du führst gerade \\\"cherry-pick\\\" aus.\"\n>\n> I thought \"cherry-pick\" = \"pflücken\", or is there a different glossary choice?\n\nAt the moment we do not have a translation for \"cherry-pick\" in the glossary.\nIn older parts of the translation we left it as it is, and I prefer to\nfollow this\nfor now. If we decide to translate it, we should do this in the whole\ntranslation.\nI've added your suggestion to the glossary.\n\nThanks,\nRalf\n"},{"id":"194608","messageId":"m28vf0aqb8.fsf@igel.home","threadId":"30944","inReplyTo":"CAN0XMO+R3+JiuHSZ0O46py2WbXVh8D2Z+f7t_xofsN6ZrFwnQQ@mail.gmail.com","subject":"Re: [RFC] l10n: de.po: translate 29 new messages","fromName":"Andreas Schwab","fromEmail":"schwab@linux-m68k.org","sentAt":"2012-07-04T08:22:35Z","receivedAt":"2012-07-04T08:22:35Z","isPatch":false,"sender":{"key":"schwab@linux-m68k.org","avatar":"https://avatars.githubusercontent.com/u/2175493?v=4"},"body":"Ralf Thielow <ralf.thielow@gmail.com> writes:\n\n> Hi Christian,\n>\n> thanks for your review.\n>\n> On Tue, Jul 3, 2012 at 10:03 PM, Christian Stimming <stimming@tuhh.de> wrote:\n>> Hi Ralf,\n>\n>> Am Dienstag, 3. Juli 2012, 19:04:46 schrieb Ralf Thielow:\n>>>  #: wt-status.c:874 wt-status.c:884\n>>> -#, fuzzy\n>>>  msgid \"You are currently rebasing.\"\n>>> -msgstr \"Du befindest dich auf keinem Zweig.\"\n>>> +msgstr \"Du bist gerade beim Neuaufbau.\"\n>>\n>> Is \"rebase\" = \"Neuaufbau\"? My last thought on this wording was \"rebase\" =\n>> \"Umpflanzen\".\n\n\"Basisumbau\"?\n\nAndreas.\n\n-- \nAndreas Schwab, schwab@linux-m68k.org\nGPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5\n\"And now for something completely different.\"\n"},{"id":"194625","messageId":"1819393.sAuVItIfZO@cs-pc","threadId":"30944","inReplyTo":"CAN0XMO+R3+JiuHSZ0O46py2WbXVh8D2Z+f7t_xofsN6ZrFwnQQ@mail.gmail.com","subject":"Re: [RFC] l10n: de.po: translate 29 new messages","fromName":"Christian Stimming","fromEmail":"stimming@tuhh.de","sentAt":"2012-07-04T20:14:03Z","receivedAt":"2012-07-04T20:14:03Z","isPatch":false,"sender":{"key":"stimming@tuhh.de","avatar":"https://avatars.githubusercontent.com/u/227778?v=4"},"body":"Hi Ralf,\n\nAm Mittwoch, 4. Juli 2012, 09:20:40 schrieb Ralf Thielow:\n> >> -msgstr \"Du befindest dich auf keinem Zweig.\"\n> >> +msgstr \"Du bist gerade beim Neuaufbau.\"\n> > \n> > Is \"rebase\" = \"Neuaufbau\"? My last thought on this wording was \"rebase\"\n> > = \"Umpflanzen\".\n> \n> According to the current state of the glossary on GitHub, \"rebase\" as a\n> verb is translated as \"neu aufbauen\". There are already translations using\n> this. For example:\n> \n> #: builtin/remote.c:998\n> #, c-format\n> msgid \"rebases onto remote %s\"\n> msgstr \"baut neu auf externen Zweig %s auf\"\n> \n> In this translation, \"rebase\" is used as a noun for the very first time.\n> So, I simply translate it with \"Neuaufbau\". In fact, we can use different\n> translations for verbs and nouns. Not really sure whether we should do this\n> for \"rebase\".\n> \n> Using \"Umpflanzen\" for \"rebase\" as a noun, would result in\n> msgstr \"Du bist gerade beim Umplanzen.\"\n> Using \"Umplanzen\" was a verb, would result in\n> msgstr \"Du planzt gerade um.\"\n> \n> For me, \"Umpflanzen\" sounds a bit like \"working with plants\n> in the garden\". I do not have a strong opinion on this, though.\n\nThat's true. The wording goes very far into gardening, which is an argument \nagainst it. An argument for it is that it consequently re-uses the tree and \nbranch metaphor, which is indeed also related to gardening.\n\nI thought \"neu aufbauen\" is probably useful in the context of the gc or fsck \ncommand... no strong opinion on this, too, though.\n\nThanks for the reminder of the glossary - indeed I forgot to check that first.\n\nRegards,\n\nChristian\n"},{"id":"194666","messageId":"CAN0XMOJF8+iJqyiqvBxEHOVGMB17rPnO9Pnu29LY1fMDBopKGw@mail.gmail.com","threadId":"30944","inReplyTo":"m28vf0aqb8.fsf@igel.home","subject":"Re: [RFC] l10n: de.po: translate 29 new messages","fromName":"Ralf Thielow","fromEmail":"ralf.thielow@gmail.com","sentAt":"2012-07-05T18:16:49Z","receivedAt":"2012-07-05T18:16:49Z","isPatch":false,"sender":{"key":"ralf.thielow@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1275832?v=4"},"body":">>> Is \"rebase\" = \"Neuaufbau\"? My last thought on this wording was \"rebase\" =\n>>> \"Umpflanzen\".\n>\n> \"Basisumbau\"?\n>\n\nI have added both suggestions to the glossary that they don't get lost when\nwe discuss about non-optimal and/or missing parts within the glossary.\n\nRalf\n"},{"id":"194744","messageId":"4FF72C70.1010202@drmicha.warpmail.net","threadId":"30944","inReplyTo":"CAN0XMOJF8+iJqyiqvBxEHOVGMB17rPnO9Pnu29LY1fMDBopKGw@mail.gmail.com","subject":"Re: [RFC] l10n: de.po: translate 29 new messages","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2012-07-06T18:20:32Z","receivedAt":"2012-07-06T18:20:32Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Ralf Thielow venit, vidit, dixit 05.07.2012 20:16:\n>>>> Is \"rebase\" = \"Neuaufbau\"? My last thought on this wording was \"rebase\" =\n>>>> \"Umpflanzen\".\n>>\n>> \"Basisumbau\"?\n>>\n> \n> I have added both suggestions to the glossary that they don't get lost when\n> we discuss about non-optimal and/or missing parts within the glossary.\n\nNot the base is being reconstructed, but what's on top of it. So,\n\"Basiswechsel\" would be more appropriate.\n\nBut: \"Umpflanzen\" is really a great term which stays within the context\nof trees, roots and branches. Strictly speaking, \"Umpflanzen\" refers to\nsomething you do at the root level. The corresponding action for\nbranches would be \"Umpfropfen\". I think that also conveys the effort\nthat is sometimes necessary ;)\n\nMichael\n"},{"id":"194745","messageId":"CAN0XMO+wz-2EGcX+KoLQLYDsG7Kz1T7YujxdJTUo1Yvqx=A4tg@mail.gmail.com","threadId":"30944","inReplyTo":"4FF72C70.1010202@drmicha.warpmail.net","subject":"Re: [RFC] l10n: de.po: translate 29 new messages","fromName":"Ralf Thielow","fromEmail":"ralf.thielow@gmail.com","sentAt":"2012-07-06T18:58:21Z","receivedAt":"2012-07-06T18:58:21Z","isPatch":false,"sender":{"key":"ralf.thielow@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1275832?v=4"},"body":"On Fri, Jul 6, 2012 at 8:20 PM, Michael J Gruber\n<git@drmicha.warpmail.net> wrote:\n> Ralf Thielow venit, vidit, dixit 05.07.2012 20:16:\n>>>>> Is \"rebase\" = \"Neuaufbau\"? My last thought on this wording was \"rebase\" =\n>>>>> \"Umpflanzen\".\n>>>\n>>> \"Basisumbau\"?\n>>>\n>>\n>> I have added both suggestions to the glossary that they don't get lost when\n>> we discuss about non-optimal and/or missing parts within the glossary.\n>\n> Not the base is being reconstructed, but what's on top of it. So,\n> \"Basiswechsel\" would be more appropriate.\n>\n\nI agree with you. There is no question what it means, but what are\nthe best german words for it.\n\n> But: \"Umpflanzen\" is really a great term which stays within the context\n> of trees, roots and branches. Strictly speaking, \"Umpflanzen\" refers to\n> something you do at the root level. The corresponding action for\n> branches would be \"Umpfropfen\". I think that also conveys the effort\n> that is sometimes necessary ;)\n\n\"Neuaufbau\": it contains the concept of rebase\n\"Umpflanzen\": it contains the concept of rebase\n\"Umpfropfen\": Actually, this word isn't familiar to me. It's a bit\nunusual, isn't it?\n(but it might contains the concept of rebase)\n\nThe whole point is that the user needs to know what it actually meant\nin git-context.\nIf a user read \"sie pflanzen gerade um\" or \"sie pfropfen gerade um\", I\ndon't think that\nthis is the best solution. I haven't said that \"sie bauen gerade neu\nauf\" is the optimal one,\nfor me it's better, though.\n\nWe really need to discuss (and thats indeed also an issue on other\ntranslation teams), which\ngit (or SCM) related words we shouldn't translate at all.\n\nThanks,\nRalf\n"},{"id":"194747","messageId":"20120706191829.GA20919@m62s10.vlinux.de","threadId":"30944","inReplyTo":"CAN0XMO+wz-2EGcX+KoLQLYDsG7Kz1T7YujxdJTUo1Yvqx=A4tg@mail.gmail.com","subject":"Re: [RFC] l10n: de.po: translate 29 new messages","fromName":"Peter Baumann","fromEmail":"waste.manager@gmx.de","sentAt":"2012-07-06T19:18:29Z","receivedAt":"2012-07-06T19:18:29Z","isPatch":false,"sender":{"key":"waste.manager@gmx.de","avatar":null},"body":"On Fri, Jul 06, 2012 at 08:58:21PM +0200, Ralf Thielow wrote:\n> On Fri, Jul 6, 2012 at 8:20 PM, Michael J Gruber\n> <git@drmicha.warpmail.net> wrote:\n> > Ralf Thielow venit, vidit, dixit 05.07.2012 20:16:\n> >>>>> Is \"rebase\" = \"Neuaufbau\"? My last thought on this wording was \"rebase\" =\n> >>>>> \"Umpflanzen\".\n> >>>\n> >>> \"Basisumbau\"?\n> >>>\n> >>\n> >> I have added both suggestions to the glossary that they don't get lost when\n> >> we discuss about non-optimal and/or missing parts within the glossary.\n> >\n> > Not the base is being reconstructed, but what's on top of it. So,\n> > \"Basiswechsel\" would be more appropriate.\n> >\n> \n> I agree with you. There is no question what it means, but what are\n> the best german words for it.\n> \n> > But: \"Umpflanzen\" is really a great term which stays within the context\n> > of trees, roots and branches. Strictly speaking, \"Umpflanzen\" refers to\n> > something you do at the root level. The corresponding action for\n> > branches would be \"Umpfropfen\". I think that also conveys the effort\n> > that is sometimes necessary ;)\n> \n> \"Neuaufbau\": it contains the concept of rebase\n> \"Umpflanzen\": it contains the concept of rebase\n> \"Umpfropfen\": Actually, this word isn't familiar to me. It's a bit\n> unusual, isn't it?\n> (but it might contains the concept of rebase)\n> \n> The whole point is that the user needs to know what it actually meant\n> in git-context.\n> If a user read \"sie pflanzen gerade um\" or \"sie pfropfen gerade um\", I\n> don't think that\n> this is the best solution. I haven't said that \"sie bauen gerade neu\n> auf\" is the optimal one,\n> for me it's better, though.\n> \n> We really need to discuss (and thats indeed also an issue on other\n> translation teams), which\n> git (or SCM) related words we shouldn't translate at all.\n\nI have to agree with this last sentence. Most of the git gui terms are really\nnot understandable to me (and even the team I introduced it too). The only way to \nactually \"guess\" what it means is by knowing the position of the buttons and then\ngetting the actual command from the position. \n\nAFAIK it makes no senes to translate terms like \"commit\" to \"Abzeichen\" like it is used\nin git gui. I don't know *anybody* here in my IT business environment who uses this word\nor even would guess what it means.  Everyone is used to the Denglisch Version \"committen\" \nor \"einchecken\".\n\nBut in case you insist of translating this word (which I wouldn't!!!),\nmay I toss in another suggestion: \"Umsetzen\"\n\n-Peter\n"},{"id":"194756","messageId":"CAN0XMOLW_S0Py+zeWaNVcMm18OLG4Kx6vU+gvS5yrVn1nVxWBQ@mail.gmail.com","threadId":"30944","inReplyTo":"20120706191829.GA20919@m62s10.vlinux.de","subject":"Re: [RFC] l10n: de.po: translate 29 new messages","fromName":"Ralf Thielow","fromEmail":"ralf.thielow@gmail.com","sentAt":"2012-07-06T20:12:59Z","receivedAt":"2012-07-06T20:12:59Z","isPatch":false,"sender":{"key":"ralf.thielow@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1275832?v=4"},"body":"> AFAIK it makes no senes to translate terms like \"commit\" to \"Abzeichen\" like it is used\n> in git gui. I don't know *anybody* here in my IT business environment who uses this word\n> or even would guess what it means.  Everyone is used to the Denglisch Version \"committen\"\n> or \"einchecken\".\n\nAs far as i can see, \"Abzeichen\" is only used as translation for \"Sign off\".\n\"commit\" is translated as \"eintragen\". So i don't see what your\nproblem is, actually.\n\nIf you have a problem caused by translation, please send a bug-report\nto the GIT ML\nthat we are able to detect and fix them.\n\nThanks\n\nRalf\n"}]}