[SILENT_COMMIT] Update of POT and PO files for the manual

1 files changed, 20 insertions, 7 deletions

diff --git a/po/es/boot-installer.po b/po/es/boot-installer.po
index d78bb8340..ae1a1efd7 100644
--- a/po/es/boot-installer.po
+++ b/po/es/boot-installer.po
@@ -38,7 +38,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: \n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2016-11-25 19:03+0000\n"
+"POT-Creation-Date: 2017-01-24 19:01+0000\n"
 "PO-Revision-Date: 2015-03-21 18:05+0100\n"
 "Last-Translator: Javier Fernández-Sanguino <jfs@debian.org>\n"
 "Language-Team: Debian l10n Spanish <debian-l10n-spanish@lists.debian.org>\n"
@@ -3401,7 +3401,19 @@ msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:2481
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "In order to ensure the terminal type used by the installer matches your "
+#| "terminal emulator, the parameter <userinput>TERM=<replaceable>type</"
+#| "replaceable></userinput> can be added. Note that the installer only "
+#| "supports the following terminal types: <literal>linux</literal>, "
+#| "<literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</"
+#| "literal> and <literal>dumb</literal>. The default for serial console in "
+#| "&d-i; is <userinput>vt102</userinput>. If you are using a virtualization "
+#| "tool which does not provide conversion into such terminals types itself, "
+#| "e.g. QEMU/KVM, you can start it inside a <command>screen</command> "
+#| "session. That will indeed perform translation into the <literal>screen</"
+#| "literal> terminal type, which is very close to <literal>vt102</literal>."
 msgid ""
 "In order to ensure the terminal type used by the installer matches your "
 "terminal emulator, the parameter <userinput>TERM=<replaceable>type</"
@@ -3409,11 +3421,12 @@ msgid ""
 "the following terminal types: <literal>linux</literal>, <literal>bterm</"
 "literal>, <literal>ansi</literal>, <literal>vt102</literal> and "
 "<literal>dumb</literal>. The default for serial console in &d-i; is "
-"<userinput>vt102</userinput>. If you are using a virtualization tool which "
-"does not provide conversion into such terminals types itself, e.g. QEMU/KVM, "
-"you can start it inside a <command>screen</command> session. That will "
-"indeed perform translation into the <literal>screen</literal> terminal type, "
-"which is very close to <literal>vt102</literal>."
+"<userinput>vt102</userinput>. If you are using an IPMI console, or a "
+"virtualization tool which does not provide conversion into such terminals "
+"types itself, e.g. QEMU/KVM, you can start it inside a <command>screen</"
+"command> session. That will indeed perform translation into the "
+"<literal>screen</literal> terminal type, which is very close to "
+"<literal>vt102</literal>."
 msgstr ""
 "Puede añadir el parámetro <userinput>TERM=<replaceable>tipo</replaceable></"
 "userinput> para asegurar que el tipo de terminal usado por el instalador "