Translations by Akerbeltz
Akerbeltz has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| 1631. |
Please disable the swap space (e.g. by running swapoff) or configure an encrypted swap space and then run setup of encrypted volumes again. This program will now abort.
|
|
| 2013-09-07 |
Please disable the swap space (e.g. by running swapoff) or configure an encrypted swap space and then run setup of encrypted volumes again. This program will now abort.
|
|
| 1632. |
Encryption passphrase:
|
|
| 2013-09-07 |
Encryption passphrase:
|
|
| 1633. |
You need to choose a passphrase to encrypt ${DEVICE}.
|
|
| 2013-09-07 |
You need to choose a passphrase to encrypt ${DEVICE}.
|
|
| 1634. |
The overall strength of the encryption depends strongly on this passphrase, so you should take care to choose a passphrase that is not easy to guess. It should not be a word or sentence found in dictionaries, or a phrase that could be easily associated with you.
|
|
| 2013-09-07 |
The overall strength of the encryption depends strongly on this passphrase, so you should take care to choose a passphrase that is not easy to guess. It should not be a word or sentence found in dictionaries, or a phrase that could be easily associated with you.
|
|
| 1635. |
A good passphrase will contain a mixture of letters, numbers and punctuation. Passphrases are recommended to have a length of 20 or more characters.
|
|
| 2013-09-07 |
A good passphrase will contain a mixture of letters, numbers and punctuation. Passphrases are recommended to have a length of 20 or more characters.
|
|
| 1636. |
There is no way to recover this passphrase if you lose it. To avoid losing data, you should normally write down the passphrase and keep it in a safe place separate from this computer.
|
|
| 2013-09-07 |
There is no way to recover this passphrase if you lose it. To avoid losing data, you should normally write down the passphrase and keep it in a safe place separate from this computer.
|
|
| 1637. |
Re-enter passphrase to verify:
|
|
| 2013-09-07 |
Re-enter passphrase to verify:
|
|
| 1638. |
Please enter the same passphrase again to verify that you have typed it correctly.
|
|
| 2013-09-07 |
Please enter the same passphrase again to verify that you have typed it correctly.
|
|
| 1639. |
Passphrase input error
|
|
| 2013-09-07 |
Passphrase input error
|
|
| 1640. |
The two passphrases you entered were not the same. Please try again.
|
|
| 2013-09-07 |
The two passphrases you entered were not the same. Please try again.
|
|
| 1641. |
Empty passphrase
|
|
| 2013-09-07 |
Empty passphrase
|
|
| 1642. |
You entered an empty passphrase, which is not allowed. Please choose a non-empty passphrase.
|
|
| 2013-09-07 |
You entered an empty passphrase, which is not allowed. Please choose a non-empty passphrase.
|
|
| 1643. |
Use weak passphrase?
|
|
| 2013-09-07 |
Use weak passphrase?
|
|
| 1644. |
You entered a passphrase that consists of less than ${MINIMUM} characters, which is considered too weak. You should choose a stronger passphrase.
|
|
| 2013-09-07 |
You entered a passphrase that consists of less than ${MINIMUM} characters, which is considered too weak. You should choose a stronger passphrase.
|
|
| 1645. |
The encryption key for ${DEVICE} is now being created.
|
|
| 2013-09-07 |
The encryption key for ${DEVICE} is now being created.
|
|
| 1646. |
Key data has been created successfully.
|
|
| 2013-09-07 |
Key data has been created successfully.
|
|
| 1647. |
Keyfile creation failure
|
|
| 2013-09-07 |
Keyfile creation failure
|
|
| 1648. |
An error occurred while creating the keyfile.
|
|
| 2013-09-07 |
An error occurred while creating the keyfile.
|
|
| 1649. |
Encryption configuration failure
|
|
| 2013-09-07 |
Encryption configuration failure
|
|
| 1650. |
You have selected the root file system to be stored on an encrypted partition. This feature requires a separate /boot partition on which the kernel and initrd can be stored.
|
|
| 2013-09-07 |
You have selected the root file system to be stored on an encrypted partition. This feature requires a separate /boot partition on which the kernel and initrd can be stored.
|
|
| 1651. |
You should go back and setup a /boot partition.
|
|
| 2013-09-07 |
You should go back and setup a /boot partition.
|
|
| 1652. |
You have selected the /boot file system to be stored on an encrypted partition. This is not possible because the boot loader would be unable to load the kernel and initrd. Continuing now would result in an installation that cannot be used.
|
|
| 2013-09-07 |
You have selected the /boot file system to be stored on an encrypted partition. This is not possible because the boot loader would be unable to load the kernel and initrd. Continuing now would result in an installation that cannot be used.
|
|
| 1653. |
You should go back and choose a non-encrypted partition for the /boot file system.
|
|
| 2013-09-07 |
You should go back and choose a non-encrypted partition for the /boot file system.
|
|
| 1654. |
Are you sure you want to use a random key?
|
|
| 2013-09-07 |
Are you sure you want to use a random key?
|
|
| 1655. |
You have chosen a random key type for ${DEVICE} but requested the partitioner to create a file system on it.
|
|
| 2013-09-07 |
You have chosen a random key type for ${DEVICE} but requested the partitioner to create a file system on it.
|
|
| 1656. |
Using a random key type means that the partition data is going to be destroyed upon each reboot. This should only be used for swap partitions.
|
|
| 2013-09-07 |
Using a random key type means that the partition data is going to be destroyed upon each reboot. This should only be used for swap partitions.
|
|
| 1657. |
Failed to download crypto components
|
|
| 2013-09-07 |
Failed to download crypto components
|
|
| 1658. |
An error occurred trying to download additional crypto components.
|
|
| 2013-09-07 |
An error occurred trying to download additional crypto components.
|
|
| 1659. |
Proceed to install crypto components despite insufficient memory?
|
|
| 2013-09-07 |
Proceed to install crypto components despite insufficient memory?
|
|
| 1660. |
There does not seem to be sufficient memory available to install additional crypto components. If you choose to go ahead and continue anyway, the installation process could fail.
|
|
| 2013-09-07 |
There does not seem to be sufficient memory available to install additional crypto components. If you choose to go ahead and continue anyway, the installation process could fail.
|
|
| 1661. |
Activate existing encrypted volumes
|
|
| 2013-09-07 |
Activate existing encrypted volumes
|
|
| 1662. |
Create encrypted volumes
|
|
| 2013-09-07 |
Create encrypted volumes
|
|
| 1663. |
Encryption configuration actions
|
|
| 2013-09-07 |
Encryption configuration actions
|
|
| 1664. |
This menu allows you to configure encrypted volumes.
|
|
| 2013-09-07 |
This menu allows you to configure encrypted volumes.
|
|
| 1665. |
Devices to encrypt:
|
|
| 2013-09-07 |
Devices to encrypt:
|
|
| 1666. |
Please select the devices to be encrypted.
|
|
| 2013-09-07 |
Please select the devices to be encrypted.
|
|
| 1667. |
No devices selected
|
|
| 2013-09-07 |
No devices selected
|
|
| 1668. |
No devices were selected for encryption.
|
|
| 2013-09-07 |
No devices were selected for encryption.
|
|
| 1669. |
No LUKS devices found
|
|
| 2013-09-07 |
No LUKS devices found
|
|
| 1670. |
This partitioning program can only activate existing encrypted volumes that use the LUKS format (dm-crypt with a passphrase). No such volumes were found. If you have encrypted volumes using other formats, you may need to back up your data before continuing with installation.
|
|
| 2013-09-07 |
This partitioning program can only activate existing encrypted volumes that use the LUKS format (dm-crypt with a passphrase). No such volumes were found. If you have encrypted volumes using other formats, you may need to back up your data before continuing with installation.
|
|
| 1671. |
If you don't enter anything, the volume will not be activated.
|
|
| 2013-09-07 |
If you don't enter anything, the volume will not be activated.
|
|
| 1672. |
No partitions were found in your system. You may need to partition your hard drives or load additional kernel modules.
|
|
| 2013-09-07 |
No partitions were found in your system. You may need to partition your hard drives or load additional kernel modules.
|
|
| 1673. |
No file systems found
|
|
| 2013-09-07 |
No file systems found
|
|
| 1674. |
No usable file systems were found. You may need to load additional kernel modules.
|
|
| 2013-09-07 |
No usable file systems were found. You may need to load additional kernel modules.
|
|
| 1675. |
Abort
|
|
| 2013-09-07 |
Abort
|
|
| 1676. |
Select a partition
|
|
| 2013-09-07 |
Select a partition
|
|
| 1677. |
These are the partitions that were detected in your system. Please select a partition to configure. No actual changes will be made until you select "Finish". If you select "Abort", no changes will be made.
|
|
| 2013-09-07 |
These are the partitions that were detected in your system. Please select a partition to configure. No actual changes will be made until you select "Finish". If you select "Abort", no changes will be made.
|
|
| 1678. |
The information shown is, in order: device name, size, file system, and mount point.
|
|
| 2013-09-07 |
The information shown is, in order: device name, size, file system, and mount point.
|
|
| 1679. |
Leave the file system intact
|
|
| 2013-09-07 |
Leave the file system intact
|
|
| 1680. |
Create swap space
|
|
| 2013-09-07 |
Create swap space
|
|
