diff options
author | Mounir IDRASSI <mounir.idrassi@idrix.fr> | 2014-07-27 02:38:18 +0200 |
---|---|---|
committer | Mounir IDRASSI <mounir.idrassi@idrix.fr> | 2014-11-08 23:21:46 +0100 |
commit | 4d8d59c23d8f7ea0ad1f6dda0facd26dad1f7660 (patch) | |
tree | 23c4abacd70bebae8d953e2667adf3f6fa4d0f81 /Translations/Language.da.xml | |
parent | 1c11ee428d9e06be1440133f6d1163ce6c709410 (diff) | |
download | VeraCrypt-4d8d59c23d8f7ea0ad1f6dda0facd26dad1f7660.tar.gz VeraCrypt-4d8d59c23d8f7ea0ad1f6dda0facd26dad1f7660.zip |
Add description string for the new wipe mode WIPE_MODE_256 in language files.
Diffstat (limited to 'Translations/Language.da.xml')
-rw-r--r-- | Translations/Language.da.xml | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/Translations/Language.da.xml b/Translations/Language.da.xml index 5e670334..9412b082 100644 --- a/Translations/Language.da.xml +++ b/Translations/Language.da.xml @@ -1032,40 +1032,41 @@ <string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>
<string lang="da" key="RESCUE_DISK_BURN_NO_CHECK_WARN">ADVARSEL: Hvis du allerede har oprettet en VeraCrypt Nødhjælps Disk tidligere, kan den ikke genbruges til denne system partition/drev fordi den blev oprettet med en anden hoved nøgle! Hver gang du krypterer en system partition/drev, skal du oprette en ny VeraCrypt Nødhjælps Disk for den, selv om du anvender samme kodeord.</string>
<string lang="da" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Fejl: Kan ikke gemme system krypterings indstillinger.</string>
<string lang="da" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Kan ikke påbegynde system krypterings første test.</string>
<string lang="da" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Kan ikke påbegynde processen med at oprette det skjulte operativsystem.</string>
<string lang="da" key="WIPE_MODE_TITLE">Udviske Tilstand</string>
<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>
<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>
<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>
<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>
<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>
<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>
<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>
<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>
<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>
<string lang="da" key="WIPE_MODE_NONE">Ingen (hurtigst)</string>
<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>
<string lang="da" key="WIPE_MODE_3_DOD_5220">3-passager (US DoD 5220.22-M)</string>
<string lang="da" key="WIPE_MODE_7_DOD_5220">7-passager (US DoD 5220.22-M)</string>
<string lang="en" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>
+ <string lang="en" key="WIPE_MODE_256">256-pass</string>
<string lang="da" key="SYS_MULTI_BOOT_MODE_TITLE">Antal Operativsystemer</string>
<string lang="da" key="MULTI_BOOT_FOR_ADVANCED_ONLY">ADVARSEL: Uerfarne brugere bør aldrig forsøge at kryptere Windows i multi-boot konfigurationer.\n\nFortsæt?</string>
<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>
<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>
<string lang="da" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Boot Drev</string>
<string lang="da" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Er det nuværende kørende operativsystem installeret på boot drevet?\n\nBemærk: Nogle gange er Windows ikke installeret på samme drev som Windows boot loader (boot partition). Hvis dette er tilfældet, vælg 'Nej'.</string>
<string lang="da" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt supporterer for tiden ikke kryptering af operativsystemer der ikke booter fra drevet hvorpå det er installeret.</string>
<string lang="da" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Antal System Drev</string>
<string lang="da" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Hvor mange drev indeholder et operativsystem?\n\nBemærk: For eksempel, hvis du har et operativsystem (f.eks. Windows, Mac OS X, Linux, osv.) installeret på dit primære drev og et andet operativsystem installeret på dit sekundære drev, vælg '2 eller flere'.</string>
<string lang="da" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt supporterer for tiden ikke kryptering af et helt drev der indeholder flere operativsystemer.\n\nMulige løsninger:\n\n- Du kan stadig kryptere et af systemerne hvis du går tilbage og vælger kun at kryptere en enkelt system partition (sat op imod at vælge at kryptere hele system drevet).\n\n- Alternativt, vil du være i stand til at kryptere hele drevet hvis du flytter nogel af systemerne til andre drev og kun beholder et system på det drev du ønsker at kryptere.</string>
<string lang="da" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Flere Systemer på et Drev</string>
<string lang="da" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Er der andre operativsystemer installeret på drevet hvorfra det nu kørende operativsystem er installeret?\n\nBemærk: For eksempel, hvis det nu kørende operativsystem er installeret på drevet #0, som indeholder flere partitioner, og hvis en af partitionerne indeholder Windows og en anden partition indeholder et operativsystem yderligere (f.eks. Windows, Mac OS X, Linux, osv.), vælg 'Ja'.</string>
<string lang="da" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Ikke-Windows Boot Loader</string>
<string lang="da" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Er der installeret en ikke-Windows boot loader (eller boot manager) i master boot record (MBR)?\n\nBemærk: For eksempel, hvis det første spor på boot drevet indeholder GRUB, LILO, XOSL, eller en anden ikke-Windows boot manager (eller boot loader), vælg 'Ja'.</string>
<string lang="da" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>
<string lang="da" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt supporterer for tiden ikke multi-boot konfigurationer hvor en ikke-Windows boot loader er installeret i Master Boot Record.\n\nMulige løsninger:\n\n- Hvis du anvender en boot manager til at boote Windows og Linux, flyt da boot manageren (typisk, GRUB) fra Master Boot Record til en partition. Start da dette hjælpeprogram igen og krypter system partition/drev. Bemærk at VeraCrypt Boot Loader vil blive din primære boot manager og det vil tillade dig at opstarte den originale boot manager (f.eks. GRUB) som din sekundære boot manager (ved at trykke på Esc i VeraCrypt Boot Loader skærmbilledet) og således vil du være i stand til at boote Linux.</string>
<string lang="da" key="WINDOWS_BOOT_LOADER_HINTS">Hvis det nuværende kørende operativsystem er installeret på boot partitionen, så vil du efter at have krypteret det, være nødt til at indtaste korrekt kodeord selv om du ønsker at starte et andet ukrypteret Windows system(er) (da de vil dele en krypteret Windows boot loader/manager).\n\nDerimod, hvis det nuværende kørende operativsystem ikke er installeret på boot partitionen (eller hvis Windows boot loader/manager ikke bliver brugt at noget andet system), så vil du efter at have krypteret dette system, ikke skulle indtaste korrekt kodeord for at boote det andet ukrypterede system(er) -- du vil kun skulle trykke på Esc tasten for at starte det ukrypterede system (hvis der er flere ukrypterede systemer, vil du også skulle vælge hvilket system der skal startes i VeraCrypt Boot Manager menuen).\n\nBemærk: Typisk er det tidligst installerede Windows system installeret på boot partitionen.</string>
<string lang="da" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Kryptering af værts beskyttet område</string>
<string lang="da" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">Sidst på mange drev er der et område der normalt er skjult for operativsystemet (sådanne områder kaldes normalt Værts Beskyttede Områder). Det er dog muligt for nogle programmer at læse og skrive data til/fra disse områder.\n\nADVARSEL: Nogle computer fabrikanter kan bruge disse områder til at gemme værktøjer og data til RAID, system gendannelse, system setup, diagnostisering, eller andre formål. Hvis sådanne værtøjer eller data skal være tilgængelige før boot, bør det skjulte område IKKE krypteres (vælg 'Nej' ovenfor).\n\nØnsker du at VeraCrypt skal detektere og kryptere sådan et skjult område (hvis det findes) sidst på system drevet?</string>
<string lang="da" key="SYSENC_TYPE_PAGE_TITLE">Type af System Kryptering</string>
|