GNOME.org
 

[gnome-devel-docs] Updated French doc translation

commit 14d502460eb2eae250cc50b99ef166a33dcb2706
Author: Bruno Brouard <annoa b gmail com>
Date:   Sun Feb 12 15:58:58 2012 +0100

    Updated French doc translation

 optimization-guide/fr/fr.po |   90 ++++++++++++++++++++-----------------------
 1 files changed, 42 insertions(+), 48 deletions(-)
---
diff --git a/optimization-guide/fr/fr.po b/optimization-guide/fr/fr.po
index aabcfeb..a1083a7 100644
--- a/optimization-guide/fr/fr.po
+++ b/optimization-guide/fr/fr.po
@@ -3,14 +3,14 @@
 # This file is distributed under the same license as the gnome-devel-docs package.
 #
 # Nicolas Repentin <nicolas repentin gmail com>, 2009.
-# Bruno Brouard <annoa b gmail com>, 2010.
+# Bruno Brouard <annoa b gmail com>, 2010,2012.
 # GÃrard Baylard <gerard b bbox fr>, 2010.
 msgid ""
 msgstr ""
 "Project-Id-Version: gnome-devel-docs master\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2010-10-24 16:27+0000\n"
-"PO-Revision-Date: 2011-03-22 12:06+0100\n"
+"POT-Creation-Date: 2012-02-10 19:19+0000\n"
+"PO-Revision-Date: 2012-02-12 15:57+0100\n"
 "Last-Translator: Bruno Brouard <annoa b gmail com>\n"
 "Language-Team: GNOME French Team <gnomefr traduc org>\n"
 "MIME-Version: 1.0\n"
@@ -492,13 +492,12 @@ 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."
+"<application>Swell Foop</application> game is used as an example."
 msgstr ""
 "Ce chapitre dÃcrit comment utiliser le profileur du tas mÃmoire "
 "<application>Massif</application> avec les applications GNOME. Nous allons "
 "montrer comment appeler, interprÃter et manipuler les sorties de "
-"<application>Massif</application>. Nous utiliserons le jeu <application>Same "
-"GNOME</application> en exemple."
+"<application>Massif</application>. Nous utiliserons le jeu <application>Swell Foop</application> en exemple."
 
 #: C/optimization-massif.xml:10(title)
 msgid "Introduction"
@@ -616,26 +615,21 @@ msgstr ""
 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  \\\n"
-"         --alloc-fn=g_malloc \\\n"
-"         --alloc-fn=g_realloc \\\n"
-"         --alloc-fn=g_try_malloc \\\n"
-"         --alloc-fn=g_malloc0 \\\n"
-"         --alloc-fn=g_mem_chunk_alloc \\\n"
-"                same-gnome\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 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 ""
-"<application>Same GNOME</application> est le programme que nous utilisons en "
+"<application>Swell Foop</application> est le programme que nous utilisons en "
 "exemple. Soyez averti que, comme <application>valgrind</application> Ãmule "
 "la CPU, il s'exÃcutera <emphasis>trÃs</emphasis> lentement. Vous aurez "
 "Ãgalement besoin de beaucoup de mÃmoire."
@@ -676,35 +670,35 @@ 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 ""
 "Sortie <application>Massif</application> pour la version non-optimisÃe de "
-"<application>Same GNOME</application>."
+"<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</application> (version 2.8.0) and then quitting. The postscript file "
+"the 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> "
+"different numbers, 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 ""
 "La <xref linkend=\"optimization-massif-FIG-output-unoptimized\"/> montre une "
 "sortie postscript typique de l'application <application>Massif</"
 "application>. Vous obtenez un rÃsultat de ce type en jouant une seule partie "
-"de <application>Same GNOME</application> (version 2.8.0) puis en quittant. "
+"de <application>Swell Foop</application> (version 2.8.0) puis en quittant. "
 "Le fichier postscript aura un nom du type <filename>massif.12345.ps</"
 "filename> et le fichier texte <filename>massif.12345.txt</filename>. Le "
 "nombre au milieu du nom est l'identifiant du processus correspondant au "
 "programme examinÃ. Si vous testez rÃellement cet exemple, vous trouverez "
 "deux versions de chacun de ces fichiers avec un numÃro d'identifiant "
-"diffÃrent, car <application>Same GNOME</application> lance un deuxiÃme "
+"diffÃrent, car <application>Swell Foop</application> lance un deuxiÃme "
 "processus que <application>Massif</application> analyse Ãgalement. Nous "
 "ignorerons ce deuxiÃme processus car il ne consomme que trÃs peu de mÃmoire."
 
@@ -725,7 +719,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"
@@ -741,7 +735,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"
@@ -749,12 +743,12 @@ msgstr ""
 "Called from:\n"
 "  28.8% : 0x6BF83A: gdk_pixbuf_new (in /usr/lib/libgdk_pixbuf-2.0.so.0.400.9)\n"
 "\n"
-"   6.1% : 0x5A32A5: g_strdup (in /usr/lib/libglib-2.0.so.0.400.6)\n"
+"    6.1% : 0x5A32A5: g_strdup (in /usr/lib/libglib-2.0.so.0.400.6)\n"
 "\n"
-"   5.9% : 0x510B3C: (within /usr/lib/libfreetype.so.6.3.7)\n"
+"    5.9% : 0x510B3C: (within /usr/lib/libfreetype.so.6.3.7)\n"
 "\n"
-"   3.5% : 0x2A4A6B: __gconv_open (in /lib/tls/libc-2.3.3.so)\n"
-" "
+"    3.5% : 0x2A4A6B: __gconv_open (in /lib/tls/libc-2.3.3.so)\n"
+"        "
 
 #: C/optimization-massif.xml:77(para)
 msgid ""
@@ -789,7 +783,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"
@@ -805,12 +799,12 @@ 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"
+"    0.9% : 0x3E8095E: (within /usr/lib/libgnomeui-2.so.0.792.0)\n"
 "\n"
 "  and 1 other insignificant place\n"
-" "
+"        "
 
 #: C/optimization-massif.xml:95(para)
 msgid ""
@@ -819,7 +813,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 "
+"to the <application>Swell Foop</application> code. From this listing, we can "
 "see instantly that the problem code is load_scenario."
 msgstr ""
 "La premiÃre ligne indique que nous nous trouvons au quatriÃme niveau dans la "
@@ -828,7 +822,7 @@ msgstr ""
 "liste des fonctions situÃes au niveau immÃdiatement infÃrieur appelant ces "
 "fonctions. Bien entendu, les entrÃes pour les niveaux 1, 2 et 3 existent, "
 "mais le 4 est le premier niveau qui arrive directement jusqu'au code GDK de "
-"<application>Same GNOME</application>. Ã partir de cette liste, nous voyons "
+"<application>Swell Foop</application>. Ã partir de cette liste, nous voyons "
 "instantanÃment que le problÃme se situe au niveau du code de "
 "<function>load_scenario</function>."
 
@@ -881,31 +875,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</"
+"of 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 ""
 "HÃlas, les choix d'une optimisation sont Ãgalement contraints par les "
 "besoins du programme. La taille des donnÃes de l'image <literal>pixbuf</"
-"literal> de <application>Same GNOME</application> est dÃterminÃe par la "
+"literal> de <application>Swell Foop</application> est dÃterminÃe par la "
 "taille des graphiques du jeu et ne peut pas Ãtre facilement rÃduite. "
 "Toutefois, la durÃe de chargement de l'image <literal>pixbuf</literal> en "
 "mÃmoire peut Ãtre rÃduite de maniÃre drastique. <xref linkend=\"optimization-"
 "massif-FIG-output-optimized\"/> affiche l'analyse par <application>Massif</"
-"application> de l'application <application>Same GNOME</application> modifiÃe "
+"application> de l'application <application>Swell Foop</application> modifiÃe "
 "pour se dÃbarrasser du <literal>pixbuf</literal> une fois que les images ont "
 "Ãtà chargÃes dans le serveur X."
 
 #: 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 ""
-"Sortie <application>Massif</application> pour <application>Same GNOME</"
+"Sortie <application>Massif</application> pour <application>Swell Foop</"
 "application> optimisÃ."
 
 #: C/optimization-massif.xml:118(para)
@@ -939,7 +933,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"
@@ -955,7 +949,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"
@@ -1054,7 +1048,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 "
+"<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-"
@@ -1067,7 +1061,7 @@ msgstr ""
 "D'autre part, <application>Massif</application> ne prend en compte que la "
 "mÃmoire utilisÃe par votre propre programme. Des ressources telles que les "
 "images sont stockÃes dans le serveur X et <application>Massif</application> "
-"ne les prend pas en considÃration. Dans l'exemple <application>Same GNOME</"
+"ne les prend pas en considÃration. Dans l'exemple <application>Swell Foop</"
 "application> nous avons en rÃalità seulement dÃplacà la consommation mÃmoire "
 "des images <literal>pixbufs</literal> cÃtà client vers les images "
 "<literal>pixmap</literal> cÃtà serveur. MÃme si c'est une tromperie, nous "
@@ -1278,4 +1272,4 @@ msgid "translator-credits"
 msgstr ""
 "Nicolas Repentin <nicolas repentin gmail com>, 2009\n"
 "GÃrard Baylard <Geodebay gmail com>, 2010\n"
-"Bruno Brouard <annoa b gmail com>, 2010"
+"Bruno Brouard <annoa b gmail com>, 2010,2012"
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]