[gnome-devel-docs] Updated Spanish translation

[Daniel Mustieles García <dmustieles src gnome org>]

commit 579fa42c53e8eabbec27af5e9bae237123970350
Author: Daniel Mustieles <daniel mustieles gmail com>
Date:   Mon Jan 27 13:56:39 2014 +0100

    Updated Spanish translation

 optimization-guide/es/es.po |  163 ++++---------------------------------------
 1 files changed, 14 insertions(+), 149 deletions(-)
---
diff --git a/optimization-guide/es/es.po b/optimization-guide/es/es.po
index 481d881..c89e5fb 100644
--- a/optimization-guide/es/es.po
+++ b/optimization-guide/es/es.po
@@ -3,14 +3,14 @@
 # Copyright (C) 2009 gnome-devel-docs's COPYRIGHT HOLDER
 # This file is distributed under the same license as the gnome-devel-docs package.
 # Jorge González <jorgegonz svn gnome org>, 2009, 2010.
-# Daniel Mustieles <daniel mustieles gmail com>, 2011, 2012, 2013.
+# Daniel Mustieles <daniel mustieles gmail com>, 2011, 2012, 2013, 2014.
 #
 msgid ""
 msgstr ""
 "Project-Id-Version: gnome-devel-docs.optimization-guide.master\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2013-09-22 18:36+0000\n"
-"PO-Revision-Date: 2013-09-23 10:42+0200\n"
+"POT-Creation-Date: 2014-01-26 13:22+0000\n"
+"PO-Revision-Date: 2014-01-27 13:50+0100\n"
 "Last-Translator: Daniel Mustieles <daniel mustieles gmail com>\n"
 "Language-Team: Español <gnome-es-list gnome org>\n"
 "Language: \n"
@@ -18,27 +18,17 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=2; plural=(n!=1);\n"
-"X-Generator: KBabel 1.11.4\n"
+"X-Generator: Gtranslator 2.91.5\n"
 
 #. Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
 msgctxt "_"
 msgid "translator-credits"
 msgstr ""
-"Daniel Mustieles <daniel mustieles gmail com>, 2012\n"
+"Daniel Mustieles <daniel mustieles gmail com>, 2012 - 2014\n"
 "Jorge González <jorgegonz svn gnome org>, 2009-2010"
 
 #. (itstool) path: license/p
 #: C/index.page:7
-#| msgid ""
-#| "Permission is granted to copy, distribute and/or modify this document "
-#| "under the terms of the <citetitle>GNU Free Documentation License</"
-#| "citetitle>, Version 1.1 or any later version published by the Free "
-#| "Software Foundation with no Invariant Sections, no Front-Cover Texts, and "
-#| "no Back-Cover Texts. You may obtain a copy of the <citetitle>GNU Free "
-#| "Documentation License</citetitle> from the Free Software Foundation by "
-#| "visiting <ulink type=\"http\" url=\"http://www.fsf.org\";>their Web site</"
-#| "ulink> or by writing to: Free Software Foundation, Inc., 59 Temple Place "
-#| "- Suite 330, Boston, MA 02111-1307, USA."
 msgid ""
 "Permission is granted to copy, distribute and/or modify this document under "
 "the terms of the GNU Free Documentation License, Version 1.1 or any later "
@@ -56,8 +46,8 @@ msgstr ""
 "Cubierta Trasera. Puede encontrar una copia de la licencia Licencia de "
 "Documentación Libre de GNU de la Free Software Foundation visitando <link "
 "href=\"http://www.fsf.org\";>su página web</link> o escribiendo a: Free "
-"Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-"
-"1307, EE. UU."
+"Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA "
+"02111-1307, EE. UU."
 
 #. (itstool) path: license/p
 #: C/index.page:16
@@ -101,7 +91,6 @@ msgstr ""
 
 #. (itstool) path: page/title
 #: C/index.page:35
-#| msgid "Doing the Optimization"
 msgid "Optimization Guide"
 msgstr "Guía de optimización"
 
@@ -112,10 +101,6 @@ msgstr "Introducción"
 
 #. (itstool) path: section/p
 #: C/index.page:39
-#| msgid ""
-#| "This is a brief introduction to optimization, both the hows and the whys. "
-#| "Details of individual tools and techniques are left for later articles, "
-#| "but a collection of hints and tricks is provided."
 msgid ""
 "This is a brief introduction to optimization, both the hows and thewhys. "
 "Details of individual tools and techniques are left for later articles, but "
@@ -134,11 +119,6 @@ msgstr "Massif"
 #. (itstool) path: section/p
 #. (itstool) path: page/p
 #: C/index.page:46 C/massif.page:9
-#| 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>Swell Foop</application> game is used as an example."
 msgid ""
 "This article describes how to use the <app>Massif</app> heap profiler with "
 "GNOME applications. We describe how to invoke, interpret, and act on the "
@@ -196,9 +176,13 @@ msgstr ""
 
 #. (itstool) path: item/p
 #: C/harmful.page:28
+#| msgid ""
+#| "Doing the above on files that are in different directories, so as to "
+#| "ensure that they are in different cylinder groups and and cause even more "
+#| "seeking."
 msgid ""
 "Doing the above on files that are in different directories, so as to ensure "
-"that they are in different cylinder groups and and cause even more seeking."
+"that they are in different cylinder groups and cause even more seeking."
 msgstr ""
 "Realizar lo siguiente sobre archivos que están en diferentes carpetas, para "
 "asegurarse de que están en grupos de cilindros diferentes y pueden causar "
@@ -332,14 +316,6 @@ msgstr ""
 
 #. (itstool) path: section/p
 #: C/introduction.page:22
-#| msgid ""
-#| "Optimization is the process of measurement, refinement and re-"
-#| "measurement. So the first thing you must do is find a way to measure what "
-#| "you are optimizing. Ideally this measurement is a single number, for "
-#| "example: the time taken to perform a task. This is your benchmark, it is "
-#| "the only way to tell if you are winning or losing. There is a big "
-#| "difference between a program that <emphasis>should</emphasis> be fast and "
-#| "a program that <emphasis>is</emphasis> fast."
 msgid ""
 "Optimization is the process of measurement, refinement and re-measurement. "
 "So the first thing you must do is find a way to measure what you are "
@@ -604,12 +580,6 @@ msgstr ""
 
 #. (itstool) path: item/p
 #: C/introduction.page:124
-#| msgid ""
-#| "Give the compiler as many hints as possible. Use the const keyword. Use "
-#| "<envar>G_INLINE_FUNC</envar> for short, frequently called, functions. "
-#| "Look up <envar>G_GNUC_PURE</envar>, <envar>G_LIKELY</envar> and the other "
-#| "glib miscellaneous macros. Use the macros instead of gcc-specific "
-#| "keywords to ensure portability."
 msgid ""
 "Give the compiler as many hints as possible. Use the const keyword. Use "
 "<code>G_INLINE_FUNC</code> for short, frequently called, functions. Look up "
@@ -751,9 +721,6 @@ msgstr ""
 
 #. (itstool) path: page/title
 #: C/massif.page:7
-#| msgid ""
-#| "Using <application>Massif</application> for Profiling Memory Use in GNOME "
-#| "Software"
 msgid "Using <app>Massif</app> for Profiling Memory Use in GNOME Software"
 msgstr ""
 "Usar <app>Massif</app> para el Perfilado del uso de memoria en software de "
@@ -761,12 +728,6 @@ msgstr ""
 
 #. (itstool) path: section/p
 #: C/massif.page:13
-#| msgid ""
-#| "<application>Massif</application> is a member of the <ulink type=\"http\" "
-#| "url=\"http://valgrind.org/\";>valgrind</ulink> suite of memory-profiling "
-#| "tools. Its purpose is to give a detailed view of dynamic memory usage "
-#| "during the lifetime of the program. Specifically it records the memory "
-#| "use of the heap and the stack."
 msgid ""
 "<app>Massif</app> is a member of the <link href=\"http://valgrind.org/";
 "\">valgrind</link> suite of memory-profiling tools. Its purpose is to give a "
@@ -781,16 +742,6 @@ msgstr ""
 
 #. (itstool) path: section/p
 #: C/massif.page:16
-#| msgid ""
-#| "The heap is the region of memory which is allocated with functions like "
-#| "malloc. It grows on demand and is usually the largest region of memory in "
-#| "a program. The stack is where all the local data for functions is stored. "
-#| "This includes the \"automatic\" variables in C and the return address for "
-#| "subroutines. The stack is typically a lot smaller and a lot more active "
-#| "than the heap. We won't consider the stack explicitly since "
-#| "<application>Massif</application> treats it as though it were just "
-#| "another part of the heap. <application>Massif</application> also gives "
-#| "information about how much memory is used to manage the heap."
 msgid ""
 "The heap is the region of memory which is allocated with functions like "
 "malloc. It grows on demand and is usually the largest region of memory in a "
@@ -813,9 +764,6 @@ msgstr ""
 
 #. (itstool) path: section/p
 #: C/massif.page:18
-#| msgid ""
-#| "<application>Massif</application> produces two output files: a graphical "
-#| "overview in a postscript file and a detailed breakdown in a text file."
 msgid ""
 "<app>Massif</app> produces two output files: a graphical overview in a "
 "postscript file and a detailed breakdown in a text file."
@@ -825,23 +773,11 @@ msgstr ""
 
 #. (itstool) path: section/title
 #: C/massif.page:23
-#| msgid "Using <application>Massif</application> with GNOME"
 msgid "Using <app>Massif</app> with GNOME"
 msgstr "Usar <app>Massif</app> con GNOME"
 
 #. (itstool) path: section/p
 #: C/massif.page:24
-#| msgid ""
-#| "<application>Massif</application> has very few options and for many "
-#| "programs does not need them. However for GNOME applications, where memory "
-#| "allocation might be buried deep in either glib or GTK, the number of "
-#| "levels down the call-stack Massif descends needs to be increased. This is "
-#| "achieved using the --depth parameter. By default this is 3; increasing it "
-#| "to 5 will guarantee the call-stack reaches down to your code. One or two "
-#| "more levels may also be desirable to provide your code with some context. "
-#| "Since the level of detail becomes quickly overwhelming it is best to "
-#| "start with the smaller depth parameter and only increase it when it "
-#| "becomes apparent that it isn't sufficient."
 msgid ""
 "<app>Massif</app> has very few options and for many programs does not need "
 "them. However for GNOME applications, where memory allocation might be "
@@ -867,13 +803,6 @@ msgstr ""
 
 #. (itstool) path: section/p
 #: C/massif.page:27
-#| msgid ""
-#| "It is also useful to tell <application>Massif</application> which "
-#| "functions allocate memory in glib. It removes an unnecessary layer of "
-#| "function calls from the reports and gives you a clearer idea of what code "
-#| "is allocating memory. The allocating functions in glib are g_malloc, "
-#| "g_malloc0, g_realloc, g_try_malloc, and g_mem_chunk_alloc. You use the --"
-#| "alloc-fn option to tell Massif about them."
 msgid ""
 "It is also useful to tell <app>Massif</app> which functions allocate memory "
 "in glib. It removes an unnecessary layer of function calls from the reports "
@@ -886,8 +815,8 @@ msgstr ""
 "glib. Quita una capa de llamadas de funciones innecesarias de los informes y "
 "le proporciona una idea más clara de qué código está reservando memoria. Las "
 "funciones de reserva de memoria en glib son «g_malloc», «g_malloc0», "
-"«g_realloc», «g_try_malloc», y «g_mem_chunk_alloc». Use la opción «--alloc-fn» "
-"para pasarle la opción a Massif."
+"«g_realloc», «g_try_malloc», y «g_mem_chunk_alloc». Use la opción «--alloc-"
+"fn» para pasarle la opción a Massif."
 
 #. (itstool) path: section/p
 #: C/massif.page:30
@@ -910,10 +839,6 @@ msgstr ""
 
 #. (itstool) path: section/p
 #: C/massif.page:37
-#| msgid ""
-#| "<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."
 msgid ""
 "<app>Swell Foop</app> is the program we will be using as an example. Be "
 "warned that, since valgrind emulates the CPU, it will run <em>very</em> "
@@ -930,12 +855,6 @@ msgstr "Interpretar los resultados"
 
 #. (itstool) path: section/p
 #: C/massif.page:42
-#| msgid ""
-#| "The graphical output of <application>Massif</application> is largely self "
-#| "explanatory. Each band represents the memory allocated by one function "
-#| "over time. Once you identify which bands are using the most memory, "
-#| "usually the big thick ones at the top you will have to consult the text "
-#| "file for the details."
 msgid ""
 "The graphical output of <app>Massif</app> is largely self explanatory. Each "
 "band represents the memory allocated by one function over time. Once you "
@@ -965,9 +884,6 @@ msgstr ""
 
 #. (itstool) path: figure/title
 #: C/massif.page:49
-#| msgid ""
-#| "<application>Massif</application> output for the unoptimized version of "
-#| "the <application>Swell Foop</application> program."
 msgid ""
 "<app>Massif</app> output for the unoptimized version of the <app>Swell Foop</"
 "app> program."
@@ -977,19 +893,6 @@ msgstr ""
 
 #. (itstool) path: section/p
 #: C/massif.page:52
-#| 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>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>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."
 msgid ""
 "<link xref=\"optimization-massif-FIG-output-unoptimized\"/> shows a typical "
 "postscript output from <app>Massif</app>. This is the result you would get "
@@ -1121,15 +1024,6 @@ msgstr ""
 
 #. (itstool) path: section/p
 #: C/massif.page:103
-#| msgid ""
-#| "The first line tells us we are now four levels deep into the stack. Below "
-#| "it is a listing of the function calls that leads from here to "
-#| "gdk_pixbuf_new. 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>Swell Foop</application> code. "
-#| "From this listing, we can see instantly that the problem code is "
-#| "load_scenario."
 msgid ""
 "The first line tells us we are now four levels deep into the stack. Below it "
 "is a listing of the function calls that leads from here to gdk_pixbuf_new. "
@@ -1196,16 +1090,6 @@ msgstr ""
 
 #. (itstool) path: section/p
 #: C/massif.page:115
-#| msgid ""
-#| "Unfortunately, the choice of optimization is also constrained by the "
-#| "needs 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>Swell Foop</application> after "
-#| "being altered to dispose of the pixbufs once the images have been loaded "
-#| "into the X server."
 msgid ""
 "Unfortunately, the choice of optimization is also constrained by the needs "
 "of the program. The size of the pixbuf data in <app>Swell Foop</app> is "
@@ -1227,9 +1111,6 @@ msgstr ""
 
 #. (itstool) path: figure/title
 #: C/massif.page:124
-#| msgid ""
-#| "<application>Massif</application> output for the optimized "
-#| "<application>Swell Foop</application> program."
 msgid ""
 "<app>Massif</app> output for the optimized <app>Swell Foop</app> program."
 msgstr ""
@@ -1256,9 +1137,6 @@ msgstr ""
 
 #. (itstool) path: section/p
 #: C/massif.page:130
-#| msgid ""
-#| "Can we do better ? A quick examination of <application>Massif</"
-#| "application>'s text output reveals: g_strdup to be the new major offender."
 msgid ""
 "Can we do better ? A quick examination of <app>Massif</app>'s text output "
 "reveals: g_strdup to be the new major offender."
@@ -1386,19 +1264,6 @@ msgstr ""
 
 #. (itstool) path: section/p
 #: C/massif.page:176
-#| 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>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-process communication. Also, the pixmaps will be "
-#| "stored in a native graphics format which is often more compact than the "
-#| "32-bit RGBA format used by gdk_pixbuf. To measure the effect of pixmaps, "
-#| "and other X resources use the <ulink type=\"http\" url=\"http://www.";
-#| "freedesktop.org/Software/xrestop\">xrestop</ulink> program."
 msgid ""
 "Secondly, <app>Massif</app> only takes into account the memory used by your "
 "own program. Resources like pixmaps are stored in the X server and aren't "