GNOME.org
 

[gnome-devel-docs] [l10n] Updated German doc translation

commit a7aef66a5ab33817aab7b64b6fef5dcf79b61b28
Author: Mario BlÃttermann <mario blaettermann gmail com>
Date:   Sat Feb 18 22:26:58 2012 +0100

    [l10n] Updated German doc translation

 optimization-guide/de/de.po |   72 +++++++++++++++++++++---------------------
 1 files changed, 36 insertions(+), 36 deletions(-)
---
diff --git a/optimization-guide/de/de.po b/optimization-guide/de/de.po
index 2d7b603..a03b666 100644
--- a/optimization-guide/de/de.po
+++ b/optimization-guide/de/de.po
@@ -1,15 +1,15 @@
 # German translation for gnome-devel-docs (accessibility handbook).
 # Copyright (C) 2009 gnome-devel-docs's COPYRIGHT HOLDER
 # This file is distributed under the same license as the gnome-devel-docs package.
-# Mario BlÃttermann <mariobl gnome org>, 2009, 2010.
+# Mario BlÃttermann <mario blaettermann gmail com>, 2009, 2010, 2012.
 # Christian Kirbach <Christian Kirbach googlemail com>, 2010.
 #
 msgid ""
 msgstr ""
 "Project-Id-Version: gnome-devel-docs master\n"
-"POT-Creation-Date: 2010-10-25 08:50+0000\n"
-"PO-Revision-Date: 2011-02-05 08:26+0100\n"
-"Last-Translator: Mario BlÃttermann <mariobl gnome org>\n"
+"POT-Creation-Date: 2012-02-10 19:19+0000\n"
+"PO-Revision-Date: 2012-02-18 22:13+0100\n"
+"Last-Translator: Mario BlÃttermann <mario blaettermann gmail com>\n"
 "Language-Team: Deutsch <gnome-de gnome org>\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -480,13 +480,13 @@ msgstr ""
 msgid ""
 "This article describes how to use the <application>Massif</application> heap "
 "profiler with GNOME applications. We describe how to invoke, interpret, and "
-"act on the output of <application>Massif</application>. The <application>Same "
-"GNOME</application> game is used as an example."
+"act on the output of <application>Massif</application>. The "
+"<application>Swell Foop</application> game is used as an example."
 msgstr ""
 "Dieser Artikel beschreibt, wie Sie den Heap-Profiler <application>Massif</"
 "application> mit GNOME-Anwendungen verwenden. Wir beschreiben den Aufruf, die "
 "Interpretation und die MÃglichkeiten, die Ausgaben von <application>Massif</"
-"application> richtig zu nutzen. Das Spiel <application>Same GNOME</"
+"application> richtig zu nutzen. Das Spiel <application>Swell Foop</"
 "application> wird als Beispiel verwendet."
 
 #: C/optimization-massif.xml:10(title)
@@ -593,21 +593,21 @@ msgstr "Ihre Befehlszeile sollte daher so aussehen:"
 msgid ""
 "\n"
 "valgrind --tool=massif --depth=5  --alloc-fn=g_malloc --alloc-fn=g_realloc --alloc-fn=g_try_malloc \\\n"
-"         --alloc-fn=g_malloc0 --alloc-fn=g_mem_chunk_alloc same-gnome\n"
+"         --alloc-fn=g_malloc0 --alloc-fn=g_mem_chunk_alloc swell-foop\n"
 "        "
 msgstr ""
 "\n"
 "valgrind --tool=massif --depth=5  --alloc-fn=g_malloc --alloc-fn=g_realloc --alloc-fn=g_try_malloc \\\n"
-"         --alloc-fn=g_malloc0 --alloc-fn=g_mem_chunk_alloc same-gnome\n"
+"         --alloc-fn=g_malloc0 --alloc-fn=g_mem_chunk_alloc swell-foop\n"
 "        "
 
 #: C/optimization-massif.xml:36(para)
 msgid ""
-"<application>Same GNOME</application> is the program we will be using as an "
+"<application>Swell Foop</application> is the program we will be using as an "
 "example. Be warned that, since valgrind emulates the CPU, it will run "
 "<emphasis>very</emphasis> slowly. You will also need a lot of memory."
 msgstr ""
-"Das Programm <application>Same GNOME</application> werden wir als Beispiel "
+"Das Programm <application>Swell Foop</application> werden wir als Beispiel "
 "verwenden. Seien Sie gewarnt: <application>Valgrind</application> emuliert "
 "den Prozessor, wodurch es <emphasis>ÃuÃerst</emphasis> langsam lÃuft. "
 "AuÃerdem wird sehr viel Speicher benÃtigt."
@@ -647,34 +647,34 @@ msgstr ""
 #: C/optimization-massif.xml:49(title)
 msgid ""
 "<application>Massif</application> output for the unoptimized version of the "
-"<application>Same GNOME</application> program."
+"<application>Swell Foop</application> program."
 msgstr ""
 "<application>Massif</application>-Ausgabe fÃr die nicht optimierte Version "
-"des Programms <application>Same GNOME</application>."
+"des Programms <application>Swell Foop</application>."
 
 #: C/optimization-massif.xml:56(para)
 msgid ""
 "<xref linkend=\"optimization-massif-FIG-output-unoptimized\"/> shows a "
 "typical postscript output from <application>Massif</application>. This is the "
-"result you would get from playing a single game of <application>Same GNOME</"
+"result you would get from playing a single game of <application>Swell Foop</"
 "application> (version 2.8.0) and then quitting. The postscript file will have "
 "a name like <filename>massif.12345.ps</filename> and the text file will be "
 "called <filename>massif.12345.txt</filename>. The number in the middle is the "
 "process ID of the program that was examined. If you actually try this example "
 "you will find two versions of each file, with slightly different numbers, "
-"this is because <application>Same GNOME</application> starts a second process "
+"this is because <application>Swell Foop</application> starts a second process "
 "and <application>Massif</application> follows that too. We will ignore this "
 "second process, it consumes very little memory."
 msgstr ""
 "<xref linkend=\"optimization-massif-FIG-output-unoptimized\"/> zeigt typische "
 "PostScript-Ausgaben von <application>Massif</application>. Dies ist das "
-"Ergebnis, wenn Sie eine einzige Runde <application>Same GNOME</application> "
+"Ergebnis, wenn Sie eine einzige Runde <application>Swell Foop</application> "
 "(Version 2.8.0) spielen und dann die Anwendung schlieÃen. Die PostScript-"
 "Datei hat einen Namen Ãhnlich wie <filename>massif.12345.ps</filename> und "
 "die Text-Datei <filename>massif.12345.txt</filename>. Die Zahl im Dateinamen "
 "entspricht der Prozesskennung des untersuchten Programms. Wenn Sie dieses "
 "Beispiel nachstellen, so werden Sie zwei Versionen jeder Datei mit leicht "
-"verschiedenen Nummern finden. Dies liegt daran, dass <application>Same GNOME</"
+"verschiedenen Nummern finden. Dies liegt daran, dass <application>Swell Foop</"
 "application> einen zweiten Prozess startet und <application>Massif</"
 "application> diesen ebenfalls protokolliert. Wie werden diesen zweiten "
 "Prozess ignorieren. Er verbraucht nur sehr wenig Speicher."
@@ -696,7 +696,7 @@ msgstr ""
 #, no-wrap
 msgid ""
 "\n"
-"Command: ./same-gnome \n"
+"Command: ./swell-foop\n"
 "\n"
 "== 0 ===========================\n"
 "Heap allocation functions accounted for 90.4% of measured spacetime\n"
@@ -712,7 +712,7 @@ msgid ""
 "        "
 msgstr ""
 "\n"
-"Command: ./same-gnome \n"
+"Command: ./swell-foop\n"
 "\n"
 "== 0 ===========================\n"
 "Heap allocation functions accounted for 90.4% of measured spacetime\n"
@@ -758,7 +758,7 @@ msgid ""
 "  0x6C285E: gdk_pixbuf_new_from_file (in /usr/lib/libgdk_pixbuf-2.0.so.0.400.9)\n"
 "\n"
 "Called from:\n"
-"  27.8% : 0x804C1A3: load_scenario (same-gnome.c:463)\n"
+"  27.8% : 0x804C1A3: load_scenario (swell-foop.c:463)\n"
 "\n"
 "    0.9% : 0x3E8095E: (within /usr/lib/libgnomeui-2.so.0.792.0)\n"
 "\n"
@@ -774,7 +774,7 @@ msgstr ""
 "  0x6C285E: gdk_pixbuf_new_from_file (in /usr/lib/libgdk_pixbuf-2.0.so.0.400.9)\n"
 "\n"
 "Called from:\n"
-"  27.8% : 0x804C1A3: load_scenario (same-gnome.c:463)\n"
+"  27.8% : 0x804C1A3: load_scenario (swell-foop.c:463)\n"
 "\n"
 "    0.9% : 0x3E8095E: (within /usr/lib/libgnomeui-2.so.0.792.0)\n"
 "\n"
@@ -788,7 +788,7 @@ msgid ""
 "Finally there is a list of functions that are at the next level down and call "
 "these functions. There are, of course, also entries for levels 1, 2, and 3, "
 "but this is the first level to reach right down through the GDK code to the "
-"<application>Same GNOME</application> code. From this listing, we can see "
+"<application>Swell Foop</application> code. From this listing, we can see "
 "instantly that the problem code is load_scenario."
 msgstr ""
 "Die erste Zeile besagt, dass wir uns nun vier Ebenen tief im Stapelspeicher "
@@ -796,8 +796,8 @@ msgstr ""
 "bis  gdk_pixbuf_new reichen. SchlieÃlich findet sich eine Liste von "
 "Funktionen, die sich eine Ebene darunter befinden und jene Funktionen "
 "aufrufen. es gibt natÃrlich auch EintrÃge fÃr die Ebenen 1 bis 3, aber dies "
-"ist die erste Ebene, die man Ãber den GDK-Code bis zum <application>Same "
-"GNOME</application>-Code erreichen kann. Aus der Auflistung kann man sofort "
+"ist die erste Ebene, die man Ãber den GDK-Code bis zum <application>Swell "
+"Foop</application>-Code erreichen kann. Aus der Auflistung kann man sofort "
 "erkennen, dass der problematische Code in load_scenario ist."
 
 #: C/optimization-massif.xml:98(para)
@@ -846,31 +846,31 @@ msgstr ""
 #: C/optimization-massif.xml:107(para)
 msgid ""
 "Unfortunately, the choice of optimization is also constrained by the needs of "
-"the program. The size of the pixbuf data in <application>Same GNOME</"
+"the program. The size of the pixbuf data in <application>Swell Foop</"
 "application> is determined by the size of the game's graphics and cannot be "
 "easily reduced. However, the amount of time it spends loaded into memory can "
 "be drastically reduced. <xref linkend=\"optimization-massif-FIG-output-"
 "optimized\"/> shows the <application>Massif</application> analysis of "
-"<application>Same GNOME</application> after being altered to dispose of the "
+"<application>Swell Foop</application> after being altered to dispose of the "
 "pixbufs once the images have been loaded into the X server."
 msgstr ""
 "UnglÃcklicherweise schrÃnken die Erfordernisse des Programms die Wahl der "
-"Optimierung ein. Die GrÃÃe der Pixbuf-Daten in <application>Same GNOME</"
+"Optimierung ein. Die GrÃÃe der Pixbuf-Daten in <application>Swell Foop</"
 "application> ist von der GrÃÃe der Grafiken im Spiel abhÃngig und kann nicht "
 "ohne Weiteres reduziert werden. Allerdings kann die Zeit zum Laden des "
 "Programms in den Speicher drastisch reduziert werden! <xref linkend="
 "\"optimization-massif-FIG-output-optimized\"/> zeigt die <application>Massif</"
-"application>-Analyse von <application>Same GNOME</application> nach den "
+"application>-Analyse von <application>Swell Foop</application> nach den "
 "Ãnderungen, die die Pixbufs entsorgen, sobald diese vom X-Server geladen "
 "wurden."
 
 #: C/optimization-massif.xml:111(title)
 msgid ""
-"<application>Massif</application> output for the optimized <application>Same "
-"GNOME</application> program."
+"<application>Massif</application> output for the optimized <application>Swell "
+"Foop</application> program."
 msgstr ""
 "<application>Massif</application>-Ausgaben fÃr das optimierte Programm "
-"<application>Same GNOME</application>."
+"<application>Swell Foop</application>."
 
 #: C/optimization-massif.xml:118(para)
 msgid ""
@@ -902,7 +902,7 @@ msgstr ""
 #, no-wrap
 msgid ""
 "\n"
-"Command: ./same-gnome \n"
+"Command: ./swell-foop\n"
 "\n"
 "== 0 ===========================\n"
 "Heap allocation functions accounted for 87.6% of measured spacetime\n"
@@ -918,7 +918,7 @@ msgid ""
 "        "
 msgstr ""
 "\n"
-"Command: ./same-gnome \n"
+"Command: ./swell-foop\n"
 "\n"
 "== 0 ===========================\n"
 "Heap allocation functions accounted for 87.6% of measured spacetime\n"
@@ -1016,7 +1016,7 @@ msgid ""
 "Secondly, <application>Massif</application> only takes into account the "
 "memory used by your own program. Resources like pixmaps are stored in the X "
 "server and aren't considered by <application>Massif</application>. In the "
-"<application>Same GNOME</application> example we have actually only moved the "
+"<application>Swell Foop</application> example we have actually only moved the "
 "memory consumption from client-side pixbufs to server-side pixmaps. Even "
 "though we cheated there are performance gains. Keeping the image data in the "
 "X server makes the graphics routines quicker and removes a lot of inter-"
@@ -1029,7 +1029,7 @@ msgstr ""
 "Zweitens: <application>Massif</application> erfasst nur die Speicherbelegung "
 "durch Ihr eigenes Programm. Ressourcen wie Pixmaps werden im X-Server "
 "gespeichert und werden nicht durch <application>Massif</application> "
-"berÃcksichtigt. In dem Beispiel mit <application>Same GNOME</application> "
+"berÃcksichtigt. In dem Beispiel mit <application>Swell Foop</application> "
 "haben wir tatsÃchlich nur den Speicherverbrauch von client-seitigen Pixbufs "
 "zu server-seitigen Pixmaps verlagert. Obwohl dies nur nach Schummeln "
 "aussieht, gab es dennoch Geschwindigkeitsgewinne. Bilddaten im X-Server "
@@ -1231,5 +1231,5 @@ msgstr ""
 #: C/optimization-guide.xml:0(None)
 msgid "translator-credits"
 msgstr ""
-"Mario BlÃttermann <mariobl gnome org>, 2009\n"
+"Mario BlÃttermann <mario blaettermann gmail com>, 2009, 2012\n"
 "Christian Kirbach <christian kirbach googlemail com>, 2010"
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]