From de4a0393dfc8d12b042e9848c35e5371db3f78a6 Mon Sep 17 00:00:00 2001 From: wwj402 Date: Sun, 5 Nov 2017 11:39:48 +0800 Subject: Update Language.zh-cn.xml Chinese Simplified language 1.22-BETA3 translation update. --- Translations/Language.zh-cn.xml | 130 ++++++++++++++++++++-------------------- 1 file changed, 65 insertions(+), 65 deletions(-) (limited to 'Translations/Language.zh-cn.xml') diff --git a/Translations/Language.zh-cn.xml b/Translations/Language.zh-cn.xml index 0456131e..ea0caf65 100644 --- a/Translations/Language.zh-cn.xml +++ b/Translations/Language.zh-cn.xml @@ -1314,31 +1314,31 @@ 不能在VeraCrypt使用这个用TrueCrypt%x.%x创建的加密卷,VeraCrypt只支持TrueCrypt6.x/7.x创建的加密卷。 测试 密钥文件 - Backspace - Tab - Clear - Enter - Pause - Caps Lock + 退格键 + 跳格键 + 清除键 + 回车键 + 暂停键 + 大写锁定 空格键 - Page Up - Page Down - End - Home + 向上翻页 + 向下翻页 + 行尾 + 行首 左箭头 上箭头 右箭头 下箭头 选择键 打印键 - Execute Key - Print Screen - Insert - Delete - Applications Key + 执行键 + 打印屏幕 + 插入 + 删除 + 应用键 睡眠 - Num Lock - Scroll Lock + 数字锁定 + 滚动锁定 浏览器 后退 浏览器 前进 浏览器 刷新 @@ -1349,14 +1349,14 @@ 静音 音量加 音量减 - Next Track - Previous Track - Stop Media - Play/Pause Media - Start Mail Key - Select Media Key - Application 1 - Application 2 + 下一曲目 + 上一曲目 + 停止媒体 + 播放/暂停 媒体 + 启动邮件键 + 选择媒体键 + 应用 1 + 应用 2 Attn CrSel ExSel @@ -1380,49 +1380,49 @@ TB/s PB/s - Include &PIM when caching pre-boot authentication password - Include PIM when caching a password - Make disconnected network drives available for mounting + 当缓存预引导身份验证密码时,包含 &PIM + 在缓存密码时,包含 PIM + 使断开的网络驱动器可用于加载 键入的密码过长:在UTF-8下已超过64字节。 键入的密码中包含无法转换为UTF-8编码的Unicode字符。 - Error: Failed to load a system library. + 错误: 加载系统库失败。 输入的加密卷的大小不兼容所选择的exFAT文件系统。 - Randomness Collected From Mouse Movements - Volume ID: - Volume ID - Use Volume ID to mount favorite - The Volume ID value is invalid - No Volume with the specified ID was found on the system - Copy Value to Clipboard... - Do not request PIM in the pre-boot authentication screen (PIM value is stored unencrypted on disk) - WARNING: Please keep in mind that if you enable this option, the PIM value will be stored unencrypted on the disk.\n\nAre you sure you want to enable this option? - Personal Iterations Multiplier (PIM) maximum value is 2147468. - Skip Rescue Disk verification - Don't show wait message dialog when performing operations - Do not request Hash algorithm in the pre-boot authentication screen - The GOST block cipher, defined in the standard GOST 28147-89 under name Magma, is a Soviet and Russian government standard symmetric key block cipher.\n\nDeveloped in the 1970s, the standard had been marked "Top Secret" and then downgraded to "Secret" in 1990. It was a Soviet alternative to the United States standard algorithm, DES. - Kuznyechik is a block cipher first published in 2015 and defined in the National Standard of the Russian Federation GOST R 34.12-2015 and also in RFC 7801. 256-bit key, 128-bit block. Mode of operation is XTS. - Jointly developed by Mitsubishi Electric and NTT of Japan. First published on 2000. 256-bit key, 128-bit block. Mode of operation is XTS. It has been approved for use by the ISO/IEC, the European Union's NESSIE project and the Japanese CRYPTREC project. - Time - Iterations - Pre-Boot - Before you can encrypt the partition, you must create a VeraCrypt Rescue Disk (VRD), which serves the following purposes:\n\n- If the VeraCrypt Boot Loader, master key, or other critical data gets damaged, the VRD allows you to restore it (note, however, that you will still have to enter the correct password then).\n\n- If Windows gets damaged and cannot start, the VRD allows you to permanently decrypt the partition before Windows starts.\n\n- The VRD will contain a backup of the present EFI boot loader and will allow you to restore it if necessary.\n\nThe VeraCrypt Rescue Disk ZIP image will be created in the location specified below. - The Rescue Disk ZIP image has been created and stored in this file:\n%s\n\nNow you need to extract it to a USB stick that is formatted as FAT/FAT32.\n\n%lsAfter you create the Rescue Disk, click Next to verify that it has been correctly created. - The Rescue Disk ZIP image has been created and stored in this file:\n%s\n\nNow you should either extract the image to a USB stick that is formatted as FAT/FAT32 or move it to a safe location for later use.\n\n%lsClick Next to continue. - IMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\n - Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. - Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. - The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry - The volume file size specified in the command line is incompatible with selected ReFS filesystem. - Edit Boot Loader Configuration - Display EFI Platform Information - Boot Loader Configuration File - EFI Platform Information - WARNING: Inexperienced users should never attempt to manually edit boot loader configurations.\n\nContinue? - WARNING: Failed to validate the XML format of the Boot Loader configuration. Please check your modifications. - Advanced Options - It is strongly recommended that you create a new VeraCrypt Rescue Disk (which will contain the new version of the VeraCrypt Boot Loader) by selecting 'System' > 'Create Rescue Disk'.\nDo you want to do it now? + 从鼠标移动中收集的随机性 + 卷 ID: + 卷 ID + 使用卷 ID 加载到收藏夹 + 卷 ID 值无效 + 在系统上未找到具有指定 ID 的卷 + 将值复制到剪贴板… + 不要在预引导身份验证屏幕中请求 PIM (PIM 值在磁盘上未加密存储) + 警告: 请记住,如果启用此选项,PIM 值将在磁盘上不加密地存储。n\n 您确定要启用此选项吗? + 个人迭代乘数 (PIM) 最大值为 2147468。 + 跳过修复盘验证 + 执行操作时不显示等待消息对话框 + 在预引导身份验证屏幕中不请求哈希算法 + GOST 块密码,定义在标准 GOST 28147-89 名称 Magma 之下,是苏联和俄罗斯政府标准的对称密钥块密码。\n\n开发于二十世纪七十年代,该标准被标记为 "绝密",然后在 1990 年降级为 "秘密"。这是苏联对美国标准算法 DES 的替代。 + Kuznyechik 是一个分组密码首次发表于 2015年, 并在俄罗斯联邦 GOST R 34.12-2015 和 RFC 7801 的国家标准中定义。256位密钥,128 位块。操作方式 XTS。 + 由日本三菱电气和 NTT 共同开发。首先发表在2000。256位密钥,128 位块。操作方式 XTS。它已被批准供 ISO/IEC,欧盟的 NESSIE 项目和日本 CRYPTREC 项目使用。 + 时间 + 迭代 + 预启动 + 在对分区进行加密之前,必须创建一个 VeraCrypt 的修复盘 (VRD),该磁盘具有以下用途:\n\n- 如果 VeraCrypt 启动加载程序、主密钥或其他关键数据被破坏, 则 VRD 允许您还原它 (注意, 但是, 您将仍然必须输入正确的密码)。\n\n- 如果 windows 损坏且无法启动,VRD 允许您在 windows 启动之前永久解密该分区。\n\n- VRD 将包含当前 EFI 引导加载程序的备份, 并允许您恢复如果有必要。\n\nVeraCrypt 救援磁盘 ZIP 映像将在下面指定的位置创建。 + 修复盘 ZIP 映像已创建并存储在文件:\n%s\n\n现在您需要将其解压到一个格式化为 FAT/FAT32 的 U盘。\n\n%ls您创建修复盘后,单击 "下一步" 以验证它是否已正确创建。 + 修复盘 ZIP 映像已创建并存储在文件:\n%s\n\n现在您应该将镜像提取到格式化为 FAT/FAT32 的 U盘,或将其移动到安全位置以备以后使用。\n\n%ls 单击 "下一步" 继续。 + 重要:请注意,必须将 zip 文件直接提取到 U盘的根目录中。例如,如果 U盘的驱动器号是 E:, 那么解压 zip 文件,应该在 U盘上创建一个文件夹 E:\\EFI。 + 无法验证是否已正确提取了修复盘。\n\n如果您已经提取了修复盘,请弹出并重新插入 U盘;然后单击 "下一步" 重试。如果这没有帮助,请尝试另一个 U盘和/或其他 ZIP 软件。\n\n如果您尚未提取修复盘,请执行此操作,然后单击 "下一步"。\n\n如果您试图验证在启动此向导之前创建的 VeraCrypt 修复盘;请注意,无法使用此修复盘,因为它是为不同的主密钥创建的。您需要提取新生成的修复盘 ZIP 映像。 + 无法验证是否已正确提取了修复盘。\n\n您已将修复盘映像提取到 U盘上,请将其弹出并重新插入;然后再试一次。如果这没有帮助,请尝试其他 ZIP 软件和/或 媒体。\n\n如果您试图验证不同的主密钥、密码、salt 等创建的 VeraCrypt 修复盘, 请注意此修复盘将始终无法通过此验证。要创建与当前配置完全兼容的新的修复盘, 请选择 "系统" > "创建修复盘"。 + 恢复盘镜像文件已经创建并存储在文件:\n%s\n\n现在您需要提取恢复盘镜像到格式化为 FAT 和 FAT32 的 U盘。\n\n重要:注意 zip 文件必须直接提取到 U盘的根目录。例如,如果 U盘的盘符是 E: ,解压缩 ZIP 文件应该在 U盘创建一个文件夹 E:\\EFI。\n\n创建恢复盘后,选择 “系统” > “验证恢复盘” 以确认它已正确创建。 + 使用安全桌面输入密码 + 命令行中指定的卷文件大小与选定的 ReFS 文件系统不兼容。 + 编辑引导加载程序配置 + 显示 EFI 平台信息 + 启动加载程序配置文件 + EFI 平台信息 + 警告: 经验不足的用户不应尝试手动编辑引导加载程序配置。\n\n继续吗? + 警告: 未能验证启动加载程序配置的 XML 格式。请检查您的修改。 + 高级选项 + 强烈建议您创建一个新的 VeraCrypt 修复盘 (该磁盘将包含新版本的 VeraCrypt 引导加载程序),方法是选择 '系统' > '创建修复盘'。\n您现在要创建吗? -- cgit v1.2.3