diff options
Diffstat (limited to 'po')
| -rw-r--r-- | po/fr/boot-installer.po | 17 | ||||
| -rw-r--r-- | po/fr/hardware.po | 19 | ||||
| -rw-r--r-- | po/fr/install-methods.po | 15 | ||||
| -rw-r--r-- | po/fr/installation-howto.po | 13 | ||||
| -rw-r--r-- | po/fr/partitioning.po | 8 | ||||
| -rw-r--r-- | po/fr/preparing.po | 103 | ||||
| -rw-r--r-- | po/fr/preseed.po | 91 |
7 files changed, 0 insertions, 266 deletions
diff --git a/po/fr/boot-installer.po b/po/fr/boot-installer.po index 63f16c582..51ac3c8d0 100644 --- a/po/fr/boot-installer.po +++ b/po/fr/boot-installer.po @@ -696,14 +696,6 @@ msgstr "" #. Tag: para #: boot-installer.xml:339 #, no-c-format -#| msgid "" -#| "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 " -#| "entering the <quote>run bootcmd_usb0</quote> command." msgid "" "The autoboot framework in modern U-Boot versions works similar to the boot " "ordering options in a PC BIOS/UEFI, i.e. it checks a list of possible boot " @@ -1135,11 +1127,6 @@ msgstr "Carte réseau ou carte mère avec PXE" #. Tag: para #: boot-installer.xml:755 #, no-c-format -#| msgid "" -#| "It could be that your Network Interface Card or Motherboard provides PXE " -#| "boot functionality. This is a <trademark class=\"trade\">Intel</" -#| "trademark> re-implementation of TFTP boot. If so, you may be able to " -#| "configure your BIOS to boot from the network." msgid "" "It could be that your Network Interface Card or Motherboard provides PXE " "boot functionality. This is a <trademark class=\"trade\">Intel</trademark> " @@ -4059,10 +4046,6 @@ msgstr "" #. Tag: para #: boot-installer.xml:2936 #, no-c-format -#| msgid "" -#| "Check that your BIOS actually supports booting from optical disc (only an " -#| "issue for very old systems) and that booting from such media is enabled " -#| "in the BIOS." msgid "" "Check that your BIOS/UEFI actually supports booting from optical disc (only " "an issue for very old systems) and that booting from such media is enabled " diff --git a/po/fr/hardware.po b/po/fr/hardware.po index ddc95a29a..188d59f8f 100644 --- a/po/fr/hardware.po +++ b/po/fr/hardware.po @@ -488,15 +488,6 @@ msgstr "" #. Tag: para #: hardware.xml:285 #, no-c-format -#| msgid "" -#| "The ARM architecture is used mainly in so-called <quote>system-on-chip</" -#| "quote> (SoC) designs. These SoCs are designed by many different companies " -#| "with vastly varying hardware components even for the very basic " -#| "functionality required to bring the system up. System firmware interfaces " -#| "have been increasingly standardised over time, but especially on older " -#| "hardware firmware/boot interfaces vary a great deal, so on these systems " -#| "the Linux kernel has to take care of many system-specific low-level " -#| "issues which would be handled by the mainboard's BIOS in the PC world." msgid "" "The ARM architecture is used mainly in so-called <quote>system-on-chip</" "quote> (SoC) designs. These SoCs are designed by many different companies " @@ -2226,16 +2217,6 @@ msgstr "Types de machine zSeries et System z" #. Tag: para #: hardware.xml:1416 #, no-c-format -#| msgid "" -#| "Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. " -#| "Your machine needs to support the z/Architecture, 64-bit support is " -#| "mandatory. The userland of the S/390 port is still compiled for ESA/390, " -#| "though. All zSeries and System z hardware is fully supported. &arch-" -#| "title; support software is included from the kernel 4.3 development " -#| "stream. The most current information about IBM's Linux support can be " -#| "found at the <ulink url=\"http://www.ibm.com/developerworks/linux/" -#| "linux390/development_technical.html\"> Linux on <trademark class=" -#| "\"registered\">System z</trademark> page on developerWorks</ulink>." msgid "" "The minimum required z/Architecture processor type is z196. The most current " "information about IBM's Linux support can be found at the <ulink url=" diff --git a/po/fr/install-methods.po b/po/fr/install-methods.po index 19edd59b3..c9f8a38f0 100644 --- a/po/fr/install-methods.po +++ b/po/fr/install-methods.po @@ -339,17 +339,6 @@ msgstr "Préparation des fichiers pour un amorçage avec une clé USB" #. Tag: para #: install-methods.xml:240 #, no-c-format -#| msgid "" -#| "To prepare the USB stick, you will need a system where GNU/Linux is " -#| "already running and where USB is supported. With current GNU/Linux " -#| "systems the USB stick should be automatically recognized when you insert " -#| "it. If it is not you should check that the usb-storage kernel module is " -#| "loaded. When the USB stick is inserted, it will be mapped to a device " -#| "named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a " -#| "letter in the range a-z. You should be able to see to which device the " -#| "USB stick was mapped by running the command <command>dmesg</command> " -#| "after inserting it. To write to your stick, you may have to turn off its " -#| "write protection switch." msgid "" "To prepare the USB stick, we recommend to use a system where GNU/Linux is " "already running and where USB is supported. With current GNU/Linux systems " @@ -1010,10 +999,6 @@ msgstr "Préparer les fichiers pour amorcer depuis un disque dur" #. Tag: para #: install-methods.xml:644 #, no-c-format -#| msgid "" -#| "The installer may be booted using boot files placed on an existing hard " -#| "drive partition, either launched from another operating system or by " -#| "invoking a boot loader directly from the BIOS." msgid "" "The installer may be booted using boot files placed on an existing hard " "drive partition, either launched from another operating system or by " diff --git a/po/fr/installation-howto.po b/po/fr/installation-howto.po index ec3d1cfa4..02e838f2e 100644 --- a/po/fr/installation-howto.po +++ b/po/fr/installation-howto.po @@ -144,13 +144,6 @@ msgstr "" #. Tag: para #: installation-howto.xml:77 #, no-c-format -#| msgid "" -#| "Download whichever type you prefer and burn it to an optical disc. " -#| "<phrase arch=\"any-x86\">To boot the disc, you may need to change your " -#| "BIOS configuration, as explained in <xref linkend=\"bios-setup\"/>.</" -#| "phrase> <phrase arch=\"powerpc\"> To boot a PowerMac from CD, press the " -#| "<keycap>c</keycap> key while booting. See <xref linkend=\"boot-cd\"/> for " -#| "other ways to boot from CD. </phrase>" msgid "" "Download whichever type you prefer and burn it to an optical disc. <phrase " "arch=\"any-x86\">To boot the disc, you may need to change your BIOS/UEFI " @@ -238,12 +231,6 @@ msgstr "" #. Tag: para #: installation-howto.xml:123 #, no-c-format -#| msgid "" -#| "Some BIOSes can boot USB storage directly, and some cannot. You may need " -#| "to configure your BIOS to enable <quote>USB legacy support</quote>. The " -#| "boot device selection menu should show <quote>removable drive</quote> or " -#| "<quote>USB-HDD</quote> to get it to boot from the USB device. For helpful " -#| "hints and details, see <xref linkend=\"usb-boot-x86\"/>." msgid "" "While booting from USB storage is quite common on UEFI systems, this is " "somewhat different in the older BIOS world. Some BIOSes can boot USB storage " diff --git a/po/fr/partitioning.po b/po/fr/partitioning.po index 55b423908..44a35af14 100644 --- a/po/fr/partitioning.po +++ b/po/fr/partitioning.po @@ -1025,14 +1025,6 @@ msgstr "" #. Tag: para #: partitioning.xml:586 #, no-c-format -#| msgid "" -#| "The PC BIOS generally adds additional constraints for disk partitioning. " -#| "There is a limit to how many <quote>primary</quote> and <quote>logical</" -#| "quote> partitions a drive can contain. Additionally, with pre " -#| "1994–98 BIOSes, there are limits to where on the drive the BIOS can " -#| "boot from. More information can be found in the <ulink url=\"&url-" -#| "partition-howto;\">Linux Partition HOWTO</ulink>, but this section will " -#| "include a brief overview to help you plan most situations." msgid "" "While modern UEFI systems don't have such limitations as listed below, the " "old PC BIOS generally adds additional constraints for disk partitioning. " diff --git a/po/fr/preparing.po b/po/fr/preparing.po index 28caf3a92..a3607d49f 100644 --- a/po/fr/preparing.po +++ b/po/fr/preparing.po @@ -566,13 +566,6 @@ msgstr "les manuels accompagnant chaque élément ;" #. Tag: para #: preparing.xml:391 #, no-c-format -#| msgid "" -#| "The BIOS setup screens of your computer. You can view these screens when " -#| "you start your computer by pressing a combination of keys. Check your " -#| "manual for the combination. Often, it is the <keycap>Delete</keycap> or " -#| "the <keycap>F2</keycap> key, but some manufacturers use other keys or key " -#| "combinations. Usually upon starting the computer there will be a message " -#| "stating which key to press to enter the setup screen." msgid "" "The BIOS/UEFI setup screens of your computer. You can view these screens " "when you start your computer by pressing a combination of keys. Check your " @@ -840,12 +833,6 @@ msgstr "" #. Tag: para #: preparing.xml:553 #, no-c-format -#| msgid "" -#| "On Linux systems, these IDs can be read with the <command>lsusb</command> " -#| "command for USB devices and with the <command>lspci -nn</command> command " -#| "for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are " -#| "usually given in the form of two hexadecimal numbers, seperated by a " -#| "colon, such as <quote>1d6b:0001</quote>." msgid "" "On Linux systems, these IDs can be read with the <command>lsusb</command> " "command for USB devices and with the <command>lspci -nn</command> command " @@ -1700,13 +1687,6 @@ msgstr "Configuration matérielle et système avant l'installation" #. Tag: para #: preparing.xml:1117 #, no-c-format -#| msgid "" -#| "This section will walk you through pre-installation hardware setup, if " -#| "any, that you will need to do prior to installing &debian;. Generally, " -#| "this involves checking and possibly changing BIOS/system firmware " -#| "settings for your system. The <quote>BIOS</quote> or <quote>system " -#| "firmware</quote> is the core software used by the hardware; it is most " -#| "critically invoked during the bootstrap process (after power-up)." msgid "" "This section will walk you through pre-installation hardware setup, if any, " "that you will need to do prior to installing &debian;. Generally, this " @@ -1726,22 +1706,12 @@ msgstr "" #. Tag: title #: preparing.xml:1132 #, no-c-format -#| msgid "Invoking the BIOS Set-Up Menu" msgid "Invoking the BIOS/UEFI Set-Up Menu" msgstr "Le menu de configuration du BIOS ou de l'UEFI" #. Tag: para #: preparing.xml:1134 #, no-c-format -#| msgid "" -#| "The BIOS provides the basic functions needed to boot your machine and to " -#| "allow your operating system to access your hardware. Your system provides " -#| "a BIOS setup menu, which is used to configure the BIOS. To enter the BIOS " -#| "setup menu you have to press a key or key combination after turning on " -#| "the computer. Often it is the <keycap>Delete</keycap> or the <keycap>F2</" -#| "keycap> key, but some manufacturers use other keys. Usually upon starting " -#| "the computer there will be a message stating which key to press to enter " -#| "the setup screen." msgid "" "The BIOS/UEFI provides the basic functions needed to boot your machine and " "to allow your operating system to access your hardware. Your system provides " @@ -1770,13 +1740,6 @@ msgstr "Sélection du périphérique d'amorçage" #. Tag: para #: preparing.xml:1150 #, no-c-format -#| msgid "" -#| "Within the BIOS setup menu, you can select which devices shall be checked " -#| "in which sequence for a bootable operating system. Possible choices " -#| "usually include the internal harddisks, the CD/DVD-ROM drive and USB mass " -#| "storage devices such as USB sticks or external USB harddisks. On modern " -#| "systems there is also often a possibility to enable network booting via " -#| "PXE." msgid "" "Within the BIOS/UEFI setup menu, you can select which devices shall be " "checked in which sequence for a bootable operating system. Possible choices " @@ -1806,17 +1769,6 @@ msgstr "" #. Tag: para #: preparing.xml:1164 #, no-c-format -#| msgid "" -#| "Most BIOS versions allow you to call up a boot menu on system startup in " -#| "which you select from which device the computer should start for the " -#| "current session. If this option is available, the BIOS usually displays a " -#| "short message like <quote>press <keycap>F12</keycap> for boot menu</" -#| "quote> on system startup. The actual key used to select this menu varies " -#| "from system to system; commonly used keys are <keycap>F12</keycap>, " -#| "<keycap>F11</keycap> and <keycap>F8</keycap>. Choosing a device from this " -#| "menu does not change the default boot order of the BIOS, i.e. you can " -#| "start once from a USB stick while having configured the internal harddisk " -#| "as the normal primary boot device." msgid "" "Most BIOS/UEFI versions allow you to call up a boot menu on system startup " "in which you select from which device the computer should start for the " @@ -1842,11 +1794,6 @@ msgstr "" #. Tag: para #: preparing.xml:1178 #, no-c-format -#| msgid "" -#| "If your BIOS does not provide you with a boot menu to do ad-hoc choices " -#| "of the current boot device, you will have to change your BIOS setup to " -#| "make the device from which the &d-i; shall be booted the primary boot " -#| "device." msgid "" "If your BIOS/UEFI does not provide you with a boot menu to do ad-hoc choices " "of the current boot device, you will have to change your BIOS/UEFI setup to " @@ -1859,20 +1806,6 @@ msgstr "" #. Tag: para #: preparing.xml:1184 #, no-c-format -#| msgid "" -#| "Unfortunately some computers contain buggy BIOS versions. Booting &d-i; " -#| "from a USB stick might not work even if there is an appropriate option in " -#| "the BIOS setup menu and the stick is selected as the primary boot device. " -#| "On some of these systems using a USB stick as boot medium is impossible; " -#| "others can be tricked into booting from the stick by changing the device " -#| "type in the BIOS setup from the default <quote>USB harddisk</quote> or " -#| "<quote>USB stick</quote> to <quote>USB ZIP</quote> or <quote>USB CDROM</" -#| "quote>. <phrase condition=\"isohybrid-supported\"> In particular if you " -#| "use an isohybrid installation image on a USB stick (see <xref linkend=" -#| "\"usb-copy-isohybrid\"/>), changing the device type to <quote>USB CDROM</" -#| "quote> helps on some BIOSes which will not boot from a USB stick in USB " -#| "harddisk mode.</phrase> You may need to configure your BIOS to enable " -#| "<quote>USB legacy support</quote>." msgid "" "Unfortunately some computers may contain buggy BIOS/UEFI versions. Booting " "&d-i; from a USB stick might not work even if there is an appropriate option " @@ -1907,12 +1840,6 @@ msgstr "" #. Tag: para #: preparing.xml:1200 #, no-c-format -#| msgid "" -#| "If you cannot manipulate the BIOS to boot directly from a USB stick you " -#| "still have the option of using an ISO copied to the stick. Boot &d-i; " -#| "using <xref linkend=\"boot-drive-files\"/> and, after scanning the hard " -#| "drives for an installer ISO image, select the USB device and choose an " -#| "installation image." msgid "" "If you cannot manipulate the BIOS/UEFI to boot directly from a USB stick you " "still have the option of using an ISO copied to the stick. Boot &d-i; using " @@ -3031,20 +2958,6 @@ msgstr "" #. Tag: para #: preparing.xml:1837 #, no-c-format -#| msgid "" -#| "The latter becomes important when booting &d-i; on a UEFI system with CSM " -#| "because &d-i; checks whether it was started on a BIOS- or on a native " -#| "UEFI system and installs the corresponding bootloader. Normally this " -#| "simply works but there can be a problem in multi-boot environments. On " -#| "some UEFI systems with CSM the default boot mode for removable devices " -#| "can be different from what is actually used when booting from hard disk, " -#| "so when booting the installer from a USB stick in a different mode from " -#| "what is used when booting another already installed operating system from " -#| "the hard disk, the wrong bootloader might be installed and the system " -#| "might be unbootable after finishing the installation. When choosing the " -#| "boot device from a firmware boot menu, some systems offer two seperate " -#| "choices for each device, so that the user can select whether booting " -#| "shall happen in CSM or in native UEFI mode." msgid "" "The latter becomes important when booting &d-i; on a UEFI system with CSM " "because &d-i; checks whether it was started on a BIOS- or on a native UEFI " @@ -3125,7 +3038,6 @@ msgstr "" #. Tag: title #: preparing.xml:1879 #, no-c-format -#| msgid "Disabling the Windows 8 <quote>fast boot</quote> feature" msgid "" "Disabling the Windows <quote>fast boot</quote>/<quote>fast startup</quote> " "feature" @@ -3136,21 +3048,6 @@ msgstr "" #. Tag: para #: preparing.xml:1880 #, no-c-format -#| msgid "" -#| "Windows 8 offers a feature called <quote>fast boot</quote> to cut down " -#| "system startup time. Technically, when this feature is enabled, Windows 8 " -#| "does not do a real shutdown and a real cold boot afterwards when ordered " -#| "to shut down, but instead does something resembling a partial suspend to " -#| "disk to reduce the <quote>boot</quote> time. As long as Windows 8 is the " -#| "only operating system on the machine, this is unproblematic, but it can " -#| "result in problems and data loss when you have a dual boot setup in which " -#| "another operating system accesses the same filesystems as Windows 8 does. " -#| "In that case the real state of the filesystem can be different from what " -#| "Windows 8 believes it to be after the <quote>boot</quote> and this could " -#| "cause filesystem corruption upon further write accesses to the " -#| "filesystem. Therefore in a dual boot setup, to avoid filesystem " -#| "corruption the <quote>fast boot</quote> feature has to be disabled within " -#| "Windows." msgid "" "Windows offers a feature (called <quote>fast boot</quote> in Windows 8, " "<quote>fast startup</quote> in Windows 10) to cut down system startup time. " diff --git a/po/fr/preseed.po b/po/fr/preseed.po index 1e8773625..ab9079fd9 100644 --- a/po/fr/preseed.po +++ b/po/fr/preseed.po @@ -2228,97 +2228,6 @@ msgstr "Exemples de partitionnement" #. Tag: screen #: preseed.xml:974 #, no-c-format -#| msgid "" -#| "# If the system has free space you can choose to only partition that " -#| "space.\n" -#| "# This is only honoured if partman-auto/method (below) is not set.\n" -#| "#d-i partman-auto/init_automatically_partition select biggest_free\n" -#| "\n" -#| "# Alternatively, you may specify a disk to partition. If the system has " -#| "only\n" -#| "# one disk the installer will default to using that, but otherwise the " -#| "device\n" -#| "# name must be given in traditional, non-devfs format (so e.g. /dev/sda\n" -#| "# and not e.g. /dev/discs/disc0/disc).\n" -#| "# For example, to use the first SCSI/SATA hard disk:\n" -#| "#d-i partman-auto/disk string /dev/sda\n" -#| "# In addition, you'll need to specify the method to use.\n" -#| "# The presently available methods are:\n" -#| "# - regular: use the usual partition types for your architecture\n" -#| "# - lvm: use LVM to partition the disk\n" -#| "# - crypto: use LVM within an encrypted partition\n" -#| "d-i partman-auto/method string lvm\n" -#| "\n" -#| "# You can define the amount of space that will be used for the LVM " -#| "volume\n" -#| "# group. It can either be a size with its unit (eg. 20 GB), a percentage " -#| "of\n" -#| "# free space or the 'max' keyword.\n" -#| "d-i partman-auto-lvm/guided_size string max\n" -#| "\n" -#| "# If one of the disks that are going to be automatically partitioned\n" -#| "# contains an old LVM configuration, the user will normally receive a\n" -#| "# warning. This can be preseeded away...\n" -#| "d-i partman-lvm/device_remove_lvm boolean true\n" -#| "# The same applies to pre-existing software RAID array:\n" -#| "d-i partman-md/device_remove_md boolean true\n" -#| "# And the same goes for the confirmation to write the lvm partitions.\n" -#| "d-i partman-lvm/confirm boolean true\n" -#| "d-i partman-lvm/confirm_nooverwrite boolean true\n" -#| "\n" -#| "# You can choose one of the three predefined partitioning recipes:\n" -#| "# - atomic: all files in one partition\n" -#| "# - home: separate /home partition\n" -#| "# - multi: separate /home, /var, and /tmp partitions\n" -#| "d-i partman-auto/choose_recipe select atomic\n" -#| "\n" -#| "# Or provide a recipe of your own...\n" -#| "# If you have a way to get a recipe file into the d-i environment, you " -#| "can\n" -#| "# just point at it.\n" -#| "#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n" -#| "\n" -#| "# If not, you can put an entire recipe into the preconfiguration file in " -#| "one\n" -#| "# (logical) line. This example creates a small /boot partition, suitable\n" -#| "# swap, and uses the rest of the space for the root partition:\n" -#| "#d-i partman-auto/expert_recipe string \\\n" -#| "# boot-root :: \\\n" -#| "# 40 50 100 ext3 \\\n" -#| "# $primary{ } $bootable{ } \\\n" -#| "# method{ format } format{ } \\\n" -#| "# use_filesystem{ } filesystem{ ext3 } \\\n" -#| "# mountpoint{ /boot } \\\n" -#| "# . \\\n" -#| "# 500 10000 1000000000 ext3 \\\n" -#| "# method{ format } format{ } \\\n" -#| "# use_filesystem{ } filesystem{ ext3 } \\\n" -#| "# mountpoint{ / } \\\n" -#| "# . \\\n" -#| "# 64 512 300% linux-swap \\\n" -#| "# method{ swap } format{ } \\\n" -#| "# .\n" -#| "\n" -#| "# The full recipe format is documented in the file partman-auto-recipe." -#| "txt\n" -#| "# included in the 'debian-installer' package or available from D-I " -#| "source\n" -#| "# repository. This also documents how to specify settings such as file\n" -#| "# system labels, volume group names and which physical devices to " -#| "include\n" -#| "# in a volume group.\n" -#| "\n" -#| "# This makes partman automatically partition without confirmation, " -#| "provided\n" -#| "# that you told it what to do using one of the methods above.\n" -#| "d-i partman-partitioning/confirm_write_new_label boolean true\n" -#| "d-i partman/choose_partition select finish\n" -#| "d-i partman/confirm boolean true\n" -#| "d-i partman/confirm_nooverwrite boolean true\n" -#| "\n" -#| "# When disk encryption is enabled, skip wiping the partitions " -#| "beforehand.\n" -#| "#d-i partman-auto-crypto/erase_disks boolean false" msgid "" "# If the system has free space you can choose to only partition that space.\n" "# This is only honoured if partman-auto/method (below) is not set.\n" |