diff options
Diffstat (limited to 'po/fr')
| -rw-r--r-- | po/fr/boot-installer.po | 32 | ||||
| -rw-r--r-- | po/fr/hardware.po | 2 | ||||
| -rw-r--r-- | po/fr/preparing.po | 2 | ||||
| -rw-r--r-- | po/fr/using-d-i.po | 4 |
4 files changed, 20 insertions, 20 deletions
diff --git a/po/fr/boot-installer.po b/po/fr/boot-installer.po index 0abe27953..166009a51 100644 --- a/po/fr/boot-installer.po +++ b/po/fr/boot-installer.po @@ -81,10 +81,10 @@ msgstr "" #: boot-installer.xml:47 #, no-c-format #| msgid "" -#| "uImage/uInitrd are image formats designed for the u-boot firmware that is " -#| "used on many ARM-based systems. Older u-boot versions can only boot files " +#| "uImage/uInitrd are image formats designed for the U-Boot firmware that is " +#| "used on many ARM-based systems. 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 " +#| "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 "" @@ -199,7 +199,7 @@ msgstr "" #. Tag: title #: boot-installer.xml:108 #, no-c-format -#| msgid "TFTP-booting in u-boot" +#| msgid "TFTP-booting in U-Boot" msgid "TFTP-booting in U-Boot" msgstr "Amorcer à partir de TFTP avec U-Boot" @@ -207,7 +207,7 @@ msgstr "Amorcer à partir de TFTP avec U-Boot" #: boot-installer.xml:109 #, no-c-format #| msgid "" -#| "Network booting on systems using the u-boot firmware consists of three " +#| "Network booting on systems using the U-Boot firmware consists of three " #| "steps: a) configuring the network, b) loading the images (kernel/initial " #| "ramdisk/dtb) into memory and c) actually executing the previosly loaded " #| "code." @@ -278,7 +278,7 @@ msgstr "" #: boot-installer.xml:132 #, no-c-format #| msgid "" -#| "On some systems, u-boot predefines a set of environment variables with " +#| "On some systems, U-Boot predefines a set of environment variables with " #| "suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. " #| "You can check whether they are defined by running " #| "<informalexample><screen>\n" @@ -402,7 +402,7 @@ msgstr "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}" #, no-c-format #| msgid "" #| "Note: When booting standard linux images, it is important to load the " -#| "initial ramdisk image after the kernel and the dtb as u-boot sets the " +#| "initial ramdisk image after the kernel and the dtb as U-Boot sets the " #| "filesize variable to the size of the last file loaded and the bootz " #| "command requires the size of the ramdisk image to work correctly. In case " #| "of booting a platform-specific kernel, i.e. a kernel without device-tree, " @@ -495,7 +495,7 @@ msgstr "" #. Tag: title #: boot-installer.xml:206 #, no-c-format -#| msgid "Booting from a USB stick in u-boot" +#| msgid "Booting from a USB stick in U-Boot" msgid "Booting from a USB stick in U-Boot" msgstr "Amorcer sur une clé USB avec U-Boot" @@ -503,7 +503,7 @@ msgstr "Amorcer sur une clé USB avec U-Boot" #: boot-installer.xml:207 #, no-c-format #| msgid "" -#| "Many modern u-boot versions have USB support and allow booting from USB " +#| "Many modern U-Boot versions have USB support and allow booting from USB " #| "mass storage devices such as USB sticks. Unfortunately the exact steps " #| "required to do that can vary quite a bit from device to device." msgid "" @@ -539,8 +539,8 @@ msgstr "" #| msgid "" #| "To build a bootable USB stick for installing &debian;, unpack the hd-" #| "media tarball (see <xref linkend=\"where-files\"/>) onto a USB stick " -#| "formatted with a filesystem supported by the u-boot version on your " -#| "device. For modern u-boot versions, any of FAT16 / FAT32 / ext2 / ext3 / " +#| "formatted with a filesystem supported by the U-Boot version on your " +#| "device. For modern U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / " #| "ext4 usually works. Then copy the ISO image file of the first &debian; " #| "installation CD or DVD onto the stick." msgid "" @@ -562,12 +562,12 @@ msgstr "" #: boot-installer.xml:233 #, no-c-format #| msgid "" -#| "The autoboot framework in modern u-boot versions works similar to the " +#| "The autoboot framework in modern U-Boot versions works similar to the " #| "boot ordering options in a PC BIOS, i.e. it checks a list of possible " #| "boot devices for a valid boot image and starts the first one it finds. If " #| "there is no operating system installed, plugging in the USB stick and " #| "powering up the system should result in starting the installer. You can " -#| "also initiate the USB-boot process any time from the u-boot prompt by " +#| "also initiate the USB-boot process any time from the U-Boot prompt by " #| "entering the <quote>run bootcmd_usb0</quote> command." msgid "" "The autoboot framework in modern U-Boot versions works similar to the boot " @@ -593,15 +593,15 @@ msgstr "" #| msgid "" #| "One problem that can come up when booting from a USB stick while using a " #| "serial console can be a console baudrate mismatch. If a console variable " -#| "is defined in u-boot, the &d-i; boot script automatically passes it to " +#| "is defined in U-Boot, the &d-i; boot script automatically passes it to " #| "the kernel to set the primary console device and, if applicable, the " #| "console baudrate. Unfortunately the handling of the console variable " #| "varies from platform to platform - on some platforms, the console " #| "variable includes the baudrate (as in <quote>console=ttyS0,115200</" #| "quote>), while on other platforms the console variable contains only the " #| "device (as in <quote>console=ttyS0</quote>). The latter case leads to a " -#| "garbled console output when the default baudrate differs between u-boot " -#| "and the kernel. Modern u-boot versions often use 115200 baud while the " +#| "garbled console output when the default baudrate differs between U-Boot " +#| "and the kernel. Modern U-Boot versions often use 115200 baud while the " #| "kernel still defaults to the traditional 9600 baud. If this happens, you " #| "should manually set the console variable to contain the correct baudrate " #| "for your system and then start the installer with the <quote>run " diff --git a/po/fr/hardware.po b/po/fr/hardware.po index 38d270840..017267d43 100644 --- a/po/fr/hardware.po +++ b/po/fr/hardware.po @@ -927,7 +927,7 @@ msgstr "" #| msgid "" #| "Using a local display is technically possible without native display " #| "drivers via the <quote>simplefb</quote> infrastructure in the mainline " -#| "kernel, which relies on the <quote>u-boot</quote> bootloader for " +#| "kernel, which relies on the <quote>U-Boot</quote> bootloader for " #| "initializing the display hardware, but this is not supported by the u-" #| "boot version in &debian; 8." msgid "" diff --git a/po/fr/preparing.po b/po/fr/preparing.po index 0ebb95de6..8ca0a6921 100644 --- a/po/fr/preparing.po +++ b/po/fr/preparing.po @@ -2679,7 +2679,7 @@ msgstr "" #. Tag: title #: preparing.xml:1706 #, no-c-format -#| msgid "Setting the ethernet MAC address in u-boot" +#| msgid "Setting the ethernet MAC address in U-Boot" msgid "Setting the ethernet MAC address in U-Boot" msgstr "Configurer l'adresse MAC Ethernet dans U-Boot" diff --git a/po/fr/using-d-i.po b/po/fr/using-d-i.po index 566f7b3da..8a0ca889a 100644 --- a/po/fr/using-d-i.po +++ b/po/fr/using-d-i.po @@ -5202,12 +5202,12 @@ msgstr "" #: using-d-i.xml:3118 #, no-c-format msgid "" -"For ARM systems that use u-boot as their system firmware and boot the kernel " +"For ARM systems that use U-Boot as their system firmware and boot the kernel " "and the initial ramdisk from external storage media (such as MMC/SD-cards, " "USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " "appropriate boot script to allow autobooting without user interaction." msgstr "" -"Pour les systèmes ARM qui utilisent u-boot comme microprogramme, et qui " +"Pour les systèmes ARM qui utilisent U-Boot comme microprogramme, et qui " "amorcent le noyau et la mémoire initiale depuis un périphérique de stockage " "externe (comme une carte MMC/SD, un périphérique de stockage de masse USB ou " "un disque dur IDE/SATA), flash-kernel génère un script d'amorçage approprié " |