Refresh pot and po files after changings in en

1 files changed, 36 insertions, 49 deletions

diff --git a/po/fr/boot-installer.po b/po/fr/boot-installer.po
index 2be6ff507..855d51264 100644
--- a/po/fr/boot-installer.po
+++ b/po/fr/boot-installer.po
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: boot-installer\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2015-05-04 18:16+0000\n"
+"POT-Creation-Date: 2015-05-07 17:01+0000\n"
 "PO-Revision-Date: 2015-05-06 20:25+0100\n"
 "Last-Translator: Baptiste Jammet <baptiste@mailoo.org>\n"
 "Language-Team: debian-l10n-french <debian-l10n-french@lists.debian.org>\n"
@@ -80,14 +80,6 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:48
 #, no-c-format
-#| msgid ""
-#| "uImage/uInitrd are image formats designed for the U-Boot firmware that is "
-#| "used on many ARM-based systems{+ (mostly 32-bit ones)+}. Older U-Boot "
-#| "versions can only boot files in uImage/uInitrd format, so these are often "
-#| "used on older armel systems. Newer U-Boot versions can - besides booting "
-#| "uImages/uInitrds - also boot standard Linux kernels and ramdisk images, "
-#| "but the command syntax to do that is slightly different from that for "
-#| "booting uImages."
 msgid ""
 "uImage/uInitrd are image formats designed for the U-Boot firmware that is "
 "used on many ARM-based systems (mostly 32-bit ones). Older U-Boot versions "
@@ -108,13 +100,6 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:57
 #, no-c-format
-#| msgid ""
-#| "For systems using a multiplatform kernel, besides kernel and initial "
-#| "ramdisk a so-called device-tree file (or device-tree blob, <quote>dtb</"
-#| "quote>) is needed. It is specific to each supported system and contains a "
-#| "description of the particular hardware.{+ The dtb should be supplied on "
-#| "the device by the firmware, but in practice a newer one often needs to be "
-#| "loaded.+}"
 msgid ""
 "For systems using a multiplatform kernel, besides kernel and initial ramdisk "
 "a so-called device-tree file (or device-tree blob, <quote>dtb</quote>) is "
@@ -138,14 +123,6 @@ msgstr "Configuration de la console"
 #. Tag: para
 #: boot-installer.xml:69
 #, no-c-format
-#| msgid ""
-#| "The netboot tarball (<xref linkend=\"boot-armhf-netboot.tar.gz\"/>), {-"
-#| "the hd-media tarball (<xref linkend=\"boot-hd-media\"/>) -}and the "
-#| "installer SD-card images (<xref linkend=\"boot-installer-sd-image\"/>) "
-#| "use the (platform-specific) default console that is defined by U-Boot in "
-#| "the <quote>console</quote> variable. In most cases that is a serial "
-#| "console, so on those platforms you by default need a serial console cable "
-#| "to use the installer."
 msgid ""
 "The netboot tarball (<xref linkend=\"boot-armhf-netboot.tar.gz\"/>), and the "
 "installer SD-card images (<xref linkend=\"boot-installer-sd-image\"/>) use "
@@ -175,12 +152,19 @@ msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:87
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "The graphical installer is not enabled on the arm64 &d-i; images for "
+#| "jessie so the serial console is used. The console device should be "
+#| "detected automatically from the firmware, but if it is not then after you "
+#| "boot linux from the GRUB menu you will see a 'Booting Linux' message then "
+#| "nothing more."
 msgid ""
 "The graphical installer is not enabled on the arm64 &d-i; images for jessie "
 "so the serial console is used. The console device should be detected "
 "automatically from the firmware, but if it is not then after you boot linux "
-"from the GRUB menu you will see a 'Booting Linux' message then nothing more."
+"from the GRUB menu you will see a <quote>Booting Linux</quote> message, then "
+"nothing more."
 msgstr ""
 "L'installateur graphique n'est pas activé dans les images de l'installateur "
 "de Jessie pour l'architecture arm64. La console série est utilisée à la "
@@ -190,16 +174,25 @@ msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:94
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "If you hit this issue you will need to set a specific console config on "
+#| "the kernel command line. Hit <userinput>e</userinput> for 'Edit Kernel "
+#| "command-line' at the GRUB menu, and change <informalexample><screen>--- "
+#| "quiet</screen></informalexample> to <informalexample><screen>console=&lt;"
+#| "device&gt;,&lt;speed&gt;</screen></informalexample> e.g. "
+#| "<informalexample><screen>console=ttyAMA0,115200n8</screen></"
+#| "informalexample> When finished hit <keycombo><keycap>Control</keycap> "
+#| "<keycap>x</keycap></keycombo> to continue booting with new setting."
 msgid ""
 "If you hit this issue you will need to set a specific console config on the "
-"kernel command line. Hit <userinput>e</userinput> for 'Edit Kernel command-"
-"line' at the GRUB menu, and change <informalexample><screen>--- quiet</"
-"screen></informalexample> to <informalexample><screen>console=&lt;device&gt;,"
-"&lt;speed&gt;</screen></informalexample> e.g. "
-"<informalexample><screen>console=ttyAMA0,115200n8</screen></informalexample> "
-"When finished hit <keycombo><keycap>Control</keycap> <keycap>x</keycap></"
-"keycombo> to continue booting with new setting."
+"kernel command line. Hit <userinput>e</userinput> for <quote>Edit Kernel "
+"command-line</quote> at the GRUB menu, and change "
+"<informalexample><screen>--- quiet</screen></informalexample> to "
+"<informalexample><screen>console=&lt;device&gt;,&lt;speed&gt;</screen></"
+"informalexample> e.g. <informalexample><screen>console=ttyAMA0,115200n8</"
+"screen></informalexample>. When finished hit <keycombo><keycap>Control</"
+"keycap> <keycap>x</keycap></keycombo> to continue booting with new setting."
 msgstr ""
 "Si vous observez ce problème, vous devrez définir une configuration "
 "spécifique de la console sur la ligne de commande du noyau. Entrez "
@@ -214,7 +207,6 @@ msgstr ""
 #. Tag: title
 #: boot-installer.xml:108
 #, no-c-format
-#| msgid "{-Submitting-}{+Juno+} Installation{- Reports-}"
 msgid "Juno Installation"
 msgstr "Installation sur Juno"
 
@@ -321,12 +313,17 @@ msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:155
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "Run a serial console at 115200, 8bit no parity, and boot the machine. "
+#| "Reboot the machine and when you see \"Hit any key to stop autoboot:\" hit "
+#| "a key to get a Mustang# prompt. Then use U-Boot commands to load and boot "
+#| "the kernel, dtb and initrd."
 msgid ""
 "Run a serial console at 115200, 8bit no parity, and boot the machine. Reboot "
-"the machine and when you see \"Hit any key to stop autoboot:\" hit a key to "
-"get a Mustang# prompt. Then use U-Boot commands to load and boot the kernel, "
-"dtb and initrd."
+"the machine and when you see <quote>Hit any key to stop autoboot:</quote> "
+"hit a key to get a Mustang# prompt. Then use U-Boot commands to load and "
+"boot the kernel, dtb and initrd."
 msgstr ""
 "Exécutez une console série à 115200 bauds, 8 bits, aucun bit de parité, et "
 "amorcez la machine. Redémarrez la machine et lorsque vous lisez « Hit any "
@@ -636,22 +633,12 @@ msgstr ""
 #. Tag: title
 #: boot-installer.xml:288
 #, no-c-format
-#| msgid "Booting from USB Memory Stick{+ with UEFI+}"
 msgid "Booting from USB Memory Stick with UEFI"
 msgstr "Amorcer sur une clé USB avec UEFI"
 
 #. Tag: para
 #: boot-installer.xml:294 boot-installer.xml:553
 #, no-c-format
-#| msgid ""
-#| "If your computer will boot from USB, this will probably be the easiest "
-#| "route for installation. Assuming you have prepared everything from <xref "
-#| "linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>, "
-#| "just plug your USB stick into some free USB connector and reboot the "
-#| "computer. The system should boot up, and unless you have used the "
-#| "flexible way to build the stick and not enabled it, you should be "
-#| "presented with a graphical boot menu{+ (on hardware that supports it)+}. "
-#| "Here you can select various installer options, or just hit &enterkey;."
 msgid ""
 "If your computer will boot from USB, this will probably be the easiest route "
 "for installation. Assuming you have prepared everything from <xref linkend="