[latexila] Added Spanish translation

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

commit fd97f742039a0d9e872514a5b9a50fe47512ba7d
Author: Daniel Mustieles <daniel mustieles gmail com>
Date:   Sat Aug 6 12:47:17 2011 +0200

    Added Spanish translation

 help/Makefile.am |    2 +-
 help/es/es.po    |  305 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 306 insertions(+), 1 deletions(-)
---
diff --git a/help/Makefile.am b/help/Makefile.am
index 850b0c5..e09315a 100644
--- a/help/Makefile.am
+++ b/help/Makefile.am
@@ -6,4 +6,4 @@ HELP_FILES = \
 	build_tools.page \
 	index.page
 
-HELP_LINGUAS = de
+HELP_LINGUAS = de es
diff --git a/help/es/es.po b/help/es/es.po
new file mode 100644
index 0000000..f3c50d5
--- /dev/null
+++ b/help/es/es.po
@@ -0,0 +1,305 @@
+# Spanish translation for latexila.
+# Copyright (C) 2011 latexila's COPYRIGHT HOLDER
+# This file is distributed under the same license as the latexila package.
+# FIRST AUTHOR <EMAIL ADDRESS>, YEAR.
+# Daniel Mustieles <daniel mustieles gmail com>, 2011.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: latexila master\n"
+"POT-Creation-Date: 2011-08-05 15:17+0000\n"
+"PO-Revision-Date: 2011-08-05 18:17+0200\n"
+"Last-Translator: Daniel Mustieles <daniel mustieles gmail com>\n"
+"Language-Team: EspaÃol <gnome-es-list gnome org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+#: C/index.page:4(page/title)
+msgid "LaTeXila Help"
+msgstr "Ayuda de LaTeXila"
+
+#. Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
+msgctxt "_"
+msgid "translator-credits"
+msgstr "Daniel Mustieles <daniel mustieles gmail com>, 2011"
+
+#: C/build_tools.page:10(page/title)
+msgid "Build Tools"
+msgstr "Herramientas de construcciÃn"
+
+#: C/build_tools.page:13(synopsis/p)
+msgid ""
+"The purpose of the build tools is to generate a document in the PDF, DVI or "
+"PS format."
+msgstr ""
+"El propÃsito de las herramientas de construcciÃn es generar un documento en "
+"formato PDF, DVI o PS."
+
+#: C/build_tools.page:20(section/title)
+msgid "Introduction"
+msgstr "IntroducciÃn"
+
+#: C/build_tools.page:22(section/p)
+msgid ""
+"Several different tools can be used for a document compilation. There are "
+"some low-level commands, and two higher-level tools: Latexmk and Rubber."
+msgstr ""
+"Se pueden usar varias herramientas para compilar documentos. Hay algunos "
+"comandos de bajo nivel y dos herramientas de alto nivel: Latexmk y Rubber."
+
+#: C/build_tools.page:26(table/title)
+msgid "Low-level commands"
+msgstr "Comandos de bajo nivel"
+
+#: C/build_tools.page:29(td/p)
+msgid "Label"
+msgstr "Etiqueta"
+
+#: C/build_tools.page:30(td/p)
+msgid "Command"
+msgstr "Comando"
+
+#: C/build_tools.page:59(td/p)
+msgid "Bibliography"
+msgstr "BibliografÃa"
+
+#: C/build_tools.page:63(td/p)
+msgid "Index"
+msgstr "Ãndice"
+
+#: C/build_tools.page:69(section/p)
+msgid ""
+"Compiling a LaTeX document can involve to execute several low-level "
+"commands, in a certain order and a certain number of times. Here is an "
+"example:"
+msgstr ""
+"Compilar un documento LaTeX puede implicar tener que ejecutar varios "
+"comandos de bajo nivel, en determinado orden y cierto nÃmero de veces. Aquà "
+"hay un ejemplo:"
+
+#: C/build_tools.page:78(section/p)
+msgid ""
+"Using a higher-level tool such as Latexmk or Rubber simplify a lot all this "
+"process, since only one command is required. Indeed, these tools can detect "
+"how many times the <cmd>latex</cmd> or <cmd>pdflatex</cmd> command must be "
+"called, and whether <cmd>bibtex</cmd> or <cmd>makeindex</cmd> is required. "
+"By default, LaTeXila uses Latexmk."
+msgstr ""
+
+#: C/build_tools.page:86(section/title)
+msgid "Differences Between Latexmk and Rubber"
+msgstr "Diferencias entre Latexmk y Rubber"
+
+#: C/build_tools.page:87(section/p)
+msgid ""
+"<link href=\"http://www.phys.psu.edu/~collins/software/latexmk-jcc/";
+"\">Latexmk</link> and <link href=\"https://launchpad.net/rubber/\";>Rubber</"
+"link> have the same purpose: simplify the compilation process of a LaTeX "
+"document. Latexmk is written in Perl, while Rubber is written in Python."
+msgstr ""
+"<link href=\"http://www.phys.psu.edu/~collins/software/latexmk-jcc/";
+"\">Latexmk</link> y <link href=\"https://launchpad.net/rubber/\";>Rubber</"
+"link> tienen el mismo propÃsito: simplificar el proceso de compilaciÃn de un "
+"documento LaTeX. Latexmk està escrito en Perl, mientras que Rubber està "
+"escrito en Python."
+
+#: C/build_tools.page:92(section/p)
+msgid ""
+"The output of Latexmk contains more information: which commands are "
+"executed, how many times, their output, and the reasons why Latexmk executes "
+"(or doesn't execute) these commands. The output of Rubber, on the other "
+"hand, doesn't contain a lot of information. When an error occurs, it can be "
+"more difficult to diagnose."
+msgstr ""
+
+#: C/build_tools.page:97(section/p)
+msgid ""
+"Also, Rubber filter the output of the <cmd>latex</cmd> or <cmd>pdflatex</"
+"cmd> command. As a consequence, when Rubber prints an error, it's more "
+"difficult to know which type of error it is. If you use Latexmk, errors are "
+"categorized into three types: critical errors, simple warnings and bad-boxes "
+"(for example when a word exceed the margin). With Rubber, there is no "
+"distinction between critical errors and simple warnings. See <link xref="
+"\"#post-processors\"/> for more information."
+msgstr ""
+
+#: C/build_tools.page:104(section/p)
+msgid ""
+"Latexmk is more flexible. Each low-level command can be customized, for "
+"example for adding a parameter, or use a completely other tool. This can be "
+"done both from the command line and in configuration files (see the <cmd>-e</"
+"cmd> and <cmd>-r</cmd> options). Rubber is also configurable, but less than "
+"Latexmk."
+msgstr ""
+
+#: C/build_tools.page:109(section/p)
+msgid ""
+"Last, but not least: Rubber seems to have more bugs and is less actively "
+"maintained than Latexmk."
+msgstr ""
+
+#: C/build_tools.page:114(section/title)
+msgid "Execute a Build Tool"
+msgstr "Ejecutar una herramienta de construcciÃn"
+
+#: C/build_tools.page:116(section/p)
+msgid "There are several means to execute a build tool:"
+msgstr "Hay varias maneras de ejecutar una herramienta de construcciÃn:"
+
+#: C/build_tools.page:118(item/p)
+msgid "Open the <gui style=\"menu\">Build</gui> menu (first part)."
+msgstr "Abrir el menà <gui style=\"menu\">Construir</gui> (primera parte)."
+
+#: C/build_tools.page:119(item/p)
+msgid "Use the buttons in the main toolbar (last part)."
+msgstr "Usar los botones en la barra de herramientas principal (Ãltima parte)."
+
+#: C/build_tools.page:120(item/p)
+msgid "Use the shortcut: <key>F2</key> â <key>F11</key>."
+msgstr "Use el atajo de teclado: <key>F2</key> â <key>F11</key>."
+
+#: C/build_tools.page:123(section/p)
+msgid ""
+"The build tool is executed on the currently opened file. If the file belongs "
+"to a project, it is executed on the project's main file."
+msgstr ""
+"La herramienta de construcciÃn se ejecute sobre el archivo abierto "
+"actualmente. Si el archivo pertenece a un proyecto, se ejecuta sobre el "
+"archivo principal del proyecto."
+
+#: C/build_tools.page:127(note/title)
+msgid "Hidden Build Tools"
+msgstr "Herramientas de construcciÃn ocultas"
+
+#: C/build_tools.page:128(note/p)
+msgid ""
+"By default, a lot of build tools are hidden, so they can't be executed. To "
+"view the full list of build tools, activate or configure them, read the "
+"<link xref=\"#general_configuration\"/> section."
+msgstr ""
+"De manera predeterminada, hay muchas herramientas de construcciÃn ocultas. "
+"Para ver la lista completa de herramientas de construcciÃn, activarlas o "
+"configurarlas, consulte la <link xref=\"#general_configuration\"/>."
+
+#: C/build_tools.page:135(section/title)
+msgid "General Configuration"
+msgstr "ConfiguraciÃn general"
+
+#: C/build_tools.page:137(section/p)
+msgid ""
+"To configure the build tools, open the preferences dialog: <guiseq><gui "
+"style=\"menu\">Edit</gui><gui style=\"menu\">Preferences</gui><gui style="
+"\"tab\">LaTeX</gui></guiseq>"
+msgstr ""
+"Para configurar las herramientas de construcciÃn, abra el diÃlogo de "
+"preferencias: <guiseq><gui style=\"menu\">Editar</gui><gui style=\"menu"
+"\">Preferencias</gui><gui style=\"tab\">LaTeX</gui></guiseq>"
+
+#: C/build_tools.page:141(section/p)
+msgid ""
+"You will see a list with all the build tools. There are check buttons to "
+"show or hide them. When a build tool is hidden, it's not possible to execute "
+"it. You can perform some actions, like moving a tool up or down, open its "
+"properties, delete or copy it, create a new one, etc."
+msgstr ""
+
+#: C/build_tools.page:147(note/p)
+msgid "Double-click on a build tool will open its properties."
+msgstr ""
+"Una pulsaciÃn doble sobre una herramienta de construcciÃn mostrarà sus "
+"propiedades."
+
+#: C/build_tools.page:150(section/p)
+msgid ""
+"For an explanation of the option about the Latexmk post processor, see <link "
+"xref=\"#post-processors\"/>."
+msgstr ""
+"Para obtener una explicaciÃn de la opciÃn sobre el post-procesador Latexmk, "
+"consulte la <link xref=\"#post-processors\"/>."
+
+#: C/build_tools.page:155(section/title)
+msgid "Jobs of a Build Tool"
+msgstr "Tareas de una herramienta de construcciÃn"
+
+#: C/build_tools.page:157(section/p)
+msgid ""
+"In the properties of a build tool, the tricky part is to configure the jobs. "
+"A build tool can execute several jobs. Each job contains three pieces of "
+"information:"
+msgstr ""
+"En las propiedades de una herramienta de construcciÃn, la parte complicada "
+"es configurar las tareas. Una herramienta de construcciÃn puede ejecutar "
+"varias tareas. Cada tarea contiene tres fragmentos de informaciÃn:"
+
+#: C/build_tools.page:161(item/p)
+msgid "The command, which can use placeholders."
+msgstr "El comando, que puede usar marcadores de posiciÃn."
+
+#: C/build_tools.page:162(item/p)
+msgid ""
+"Whether the job must succeed. If this option is enabled, when an error "
+"occurs during the job execution, the next job is not executed."
+msgstr ""
+"Indica si la tarea debe terminar con Ãxito. Si esta opciÃn està activada, "
+"cuando ocurre un error durante la ejecuciÃn de la tarea, la siguiente tarea "
+"no se ejecuta."
+
+#: C/build_tools.page:164(item/p)
+msgid "The post processor (see <link xref=\"#post-processors\"/>)."
+msgstr "El post-procesador (consulte la <link xref=\"#post-processors\"/>)."
+
+#: C/build_tools.page:169(section/title)
+msgid "Post Processors"
+msgstr "Post-procesadores"
+
+#: C/build_tools.page:170(section/p)
+msgid ""
+"The purpose of a post processor is to filter the command output and extract "
+"the useful information. Five post processors are available:"
+msgstr ""
+"El propÃsito de un post-procesador es filtrar la informaciÃn de salida del "
+"comando y extraer la informaciÃn Ãtil. Hay cinco post-procesadores "
+"disponibles:"
+
+#: C/build_tools.page:176(item/p)
+msgid "The output is simply not displayed."
+msgstr "La salida simplemente no se muestra."
+
+#: C/build_tools.page:180(item/p)
+msgid "All the output is displayed, without filter."
+msgstr "Se muestra toda la salida, sin filtrar."
+
+#: C/build_tools.page:184(item/p)
+msgid ""
+"Filter the output of the <cmd>latex</cmd> or <cmd>pdflatex</cmd> commands. "
+"There can be three types of errors: critical errors, warnings, or bad-boxes. "
+"There are also some other useful information: the size of the document, the "
+"number of pages, and the number of errors."
+msgstr ""
+
+#: C/build_tools.page:191(item/p)
+msgid ""
+"Used for the <cmd>latexmk</cmd> command. Internally, this post processor "
+"uses other ones: <em>latex</em> and <em>all-output</em>."
+msgstr ""
+
+#: C/build_tools.page:194(item/p)
+msgid ""
+"In the <link xref=\"#general_configuration\"/>, there is an option for "
+"always showing all information of this post processor. If this option is "
+"disabled (which is the case by default), only the output of the last "
+"<cmd>latex</cmd> or <cmd>pdflatex</cmd> command is displayed, if no error "
+"occurred in another command. This allows to reduce the output showed in the "
+"bottom panel. But even if there are no errors, it can be useful to see "
+"exactly which commands are executed, with their output."
+msgstr ""
+
+#: C/build_tools.page:204(item/p)
+msgid ""
+"This is the post-processor used for the <cmd>rubber</cmd> command. The "
+"errors are categorized into two types: bad-boxes, and the others. So, unlike "
+"the <em>latex</em> post processor, there is no distinction between critical "
+"errors and simple warnings."
+msgstr ""