<?xml version="1.0" encoding="utf-8"?>
<VeraCrypt>
  <localization prog-version="1.0d">
    <!-- Languages -->
    <language langid="zh-cn" name="简体中文" en-name="Chinese (Simplified)" version="1.0.0" translators="Barney Li" />
    <!-- Fonts -->
    <font lang="zh-cn" class="normal" size="11" face="Tahoma" />
    <font lang="zh-cn" class="bold" size="14" face="Tahoma" />
    <font lang="zh-cn" class="fixed" size="14" face="MingLiU" />
    <font lang="zh-cn" class="title" size="21" face="Tahoma" />
    <!-- Controls -->
    <control lang="zh-cn" key="IDCANCEL">取消</control>
    <control lang="zh-cn" key="IDC_ALL_USERS">为所有用户安装(&amp;F)</control>
    <control lang="zh-cn" key="IDC_BROWSE">浏览(&amp;W)...</control>
    <control lang="zh-cn" key="IDC_DESKTOP_ICON">在桌面添加 VeraCrypt 图标(&amp;D)</control>
    <control lang="zh-cn" key="IDC_DONATE">现在捐助...</control>
    <control lang="zh-cn" key="IDC_FILE_TYPE">关联 .tc 文件到 VeraCrypt(&amp;E) </control>
    <control lang="zh-cn" key="IDC_OPEN_CONTAINING_FOLDER">完成后打开目标位置(&amp;O)</control>
    <control lang="zh-cn" key="IDC_PROG_GROUP">创建 VeraCrypt 开始菜单项目(&amp;S)</control>
    <control lang="zh-cn" key="IDC_SYSTEM_RESTORE">创建系统还原点(&amp;R)</control>
    <control lang="zh-cn" key="IDC_UNINSTALL">卸载(&amp;U)</control>
    <control lang="zh-cn" key="IDC_WIZARD_MODE_EXTRACT_ONLY">释放(&amp;E)</control>
    <control lang="zh-cn" key="IDC_WIZARD_MODE_INSTALL">安装(&amp;I)</control>
    <control lang="zh-cn" key="IDD_INSTL_DLG">VeraCrypt 安装向导</control>
    <control lang="zh-cn" key="IDD_UNINSTALL">卸载 VeraCrypt</control>
    <control lang="zh-cn" key="IDHELP">帮助(&amp;H)</control>
    <control lang="zh-cn" key="IDT_EXTRACT_DESTINATION">请选择或者输入您希望释放到的位置:</control>
    <control lang="zh-cn" key="IDT_INSTALL_DESTINATION">请选择或输入您希望 VeraCrypt 程序文件释放到的位置。如果指定文件夹不存在，文件夹将会被自动创建。</control>
    <control lang="zh-cn" key="IDT_UNINSTALL_DIR">点击〖卸载〗按钮从系统中卸载 VeraCrypt。</control>
    <control lang="zh-cn" key="IDC_ABORT_BUTTON">放弃</control>
    <control lang="zh-cn" key="IDC_BENCHMARK">测试(&amp;B)</control>
    <control lang="zh-cn" key="IDC_CIPHER_TEST">测试(&amp;T)</control>
    <control lang="zh-cn" key="IDC_DEVICE_TRANSFORM_MODE_FORMAT">创建加密卷并格式化</control>
    <control lang="zh-cn" key="IDC_DEVICE_TRANSFORM_MODE_INPLACE">就地加密分区</control>
    <control lang="zh-cn" key="IDC_DISPLAY_KEYS">显示生成的密钥（及其部分）</control>
    <control lang="zh-cn" key="IDC_DISPLAY_POOL_CONTENTS">显示缓冲内容</control>
    <control lang="zh-cn" key="IDC_DOWNLOAD_CD_BURN_SOFTWARE">下载 CD/DVD 刻录软件（联网）</control>
    <control lang="zh-cn" key="IDC_FILE_CONTAINER">创建文件型加密卷</control>
    <control lang="zh-cn" key="IDC_GB">GB(&amp;G)</control>
    <control lang="zh-cn" key="IDC_HIDDEN_SYSENC_INFO_LINK">更多信息（联网）</control>
    <control lang="zh-cn" key="IDC_HIDDEN_VOL">隐藏的 VeraCrypt 加密卷(&amp;D) </control>
    <control lang="zh-cn" key="IDC_HIDDEN_VOL_HELP">关于隐藏加密卷的更多信息（联网）</control>
    <control lang="zh-cn" key="IDC_HIDVOL_WIZ_MODE_DIRECT">直接模式</control>
    <control lang="zh-cn" key="IDC_HIDVOL_WIZ_MODE_FULL">常规模式</control>
    <control lang="zh-cn" key="IDC_KB">KB(&amp;K)</control>
    <control lang="zh-cn" key="IDC_KEYFILES_ENABLE">使用密钥文件(&amp;S)</control>
    <control lang="zh-cn" key="IDC_KEY_FILES">密钥文件(&amp;K)..</control>
    <control lang="zh-cn" key="IDC_LINK_HASH_INFO">混杂算法的更多信息（联网）</control>
    <control lang="zh-cn" key="IDC_LINK_MORE_INFO_ABOUT_CIPHER">更多信息（联网）</control>
    <control lang="zh-cn" key="IDC_MB">MB(&amp;M)</control>
    <control lang="zh-cn" key="IDC_MORE_INFO_ON_CONTAINERS">更多信息（联网）</control>
    <control lang="zh-cn" key="IDC_MORE_INFO_ON_SYS_ENCRYPTION">关于系统盘加密的更多信息（联网）</control>
    <control lang="zh-cn" key="IDC_MORE_INFO_SYS_ENCRYPTION">更多信息（联网）</control>
    <control lang="zh-cn" key="IDC_MULTI_BOOT">多重启动</control>
    <control lang="zh-cn" key="IDC_NONSYS_DEVICE">加密非系统分区/设备</control>
    <control lang="zh-cn" key="IDC_NO_HISTORY">从不保留历史记录(&amp;R)</control>
    <control lang="zh-cn" key="IDC_OPEN_OUTER_VOLUME">打开外层加密卷</control>
    <control lang="zh-cn" key="IDC_PAUSE">暂停(&amp;P)</control>
    <control lan
/* zlib.h -- interface of the 'zlib' general purpose compression library
  version 1.2.11, January 15th, 2017

  Copyright (C) 1995-2017 Jean-loup Gailly and Mark Adler

  This software is provided 'as-is', without any express or implied
  warranty.  In no event will the authors be held liable for any damages
  arising from the use of this software.

  Permission is granted to anyone to use this software for any purpose,
  including commercial applications, and to alter it and redistribute it
  freely, subject to the following restrictions:

  1. The origin of this software must not be misrepresented; you must not
     claim that you wrote the original software. If you use this software
     in a product, an acknowledgment in the product documentation would be
     appreciated but is not required.
  2. Altered source versions must be plainly marked as such, and must not be
     misrepresented as being the original software.
  3. This notice may not be removed or altered from any source distribution.

  Jean-loup Gailly        Mark Adler
  jloup@gzip.org          madler@alumni.caltech.edu


  The data format used by the zlib library is described by RFCs (Request for
  Comments) 1950 to 1952 in the files http://tools.ietf.org/html/rfc1950
  (zlib format), rfc1951 (deflate format) and rfc1952 (gzip format).
*/

#ifndef ZLIB_H
#define ZLIB_H

#include "zconf.h"

#ifdef __cplusplus
extern "C" {
#endif

#define ZLIB_VERSION "1.2.11"
#define ZLIB_VERNUM 0x12b0
#define ZLIB_VER_MAJOR 1
#define ZLIB_VER_MINOR 2
#define ZLIB_VER_REVISION 11
#define ZLIB_VER_SUBREVISION 0

/*
    The 'zlib' compression library provides in-memory compression and
  decompression functions, including integrity checks of the uncompressed data.
  This version of the library supports only one compression method (deflation)
  but other algorithms will be added later and will have the same stream
  interface.

    Compression can be done in a single step if the buffers are large enough,
  or can be done by repeated calls of the compression function.  In the latter
  case, the application must provide more input and/or consume the output
  (providing more output space) before each call.

    The compressed data format used by default by the in-memory functions is
  the zlib format, which is a zlib wrapper documented in RFC 1950, wrapped
  around a deflate stream, which is itself documented in RFC 1951.

    The library also supports reading and writing files in gzip (.gz) format
  with an interface similar to that of stdio using the functions that start
  with "gz".  The gzip format is different from the zlib format.  gzip is a
  gzip wrapper, documented in RFC 1952, wrapped around a deflate stream.

    This library can optionally read and write gzip and raw deflate streams in
  memory as well.

    The zlib format was designed to be compact and fast for use in memory
  and on communications channels.  The gzip format was designed for single-
  file compression on file systems, has a larger header than zlib to maintain
  directory information, and uses a different, slower check method than zlib.

    The library does not install any signal handler.  The decoder checks
  the consistency of the compressed data, so the library should never crash
  even in the case of corrupted input.
*/

typedef voidpf (*alloc_func) OF((voidpf opaque, uInt items, uInt size));
typedef void   (*free_func)  OF((voidpf opaque, voidpf address));

struct internal_state;

typedef struct z_stream_s {
    z_const Bytef *next_in;     /* next input byte */
    uInt     avail_in;  /* number of bytes available at next_in */
    uLong    total_in;  /* total number of input bytes read so far */

    Bytef    *next_out; /* next output byte will go here */
    uInt     avail_out; /* remaining free space at next_out */
    uLong    total_out; /* total number of bytes output so far */

    z_const char *msg;  /* last error message, NULL if no error */
    struct internal_state FAR *state; /* not visible by applications */

    alloc_func zalloc;  /* used to allocate the internal state */
    free_func  zfree;   /* used to free the internal state */
    voidpf     opaque;  /* private data object passed to zalloc and zfree */

    int     data_type;  /* best guess about the data type: binary or text
                           for deflate, or the decoding state for inflate */
    uLong   adler;      /* Adler-32 or CRC-32 value of the uncompressed data */
    uLong   reserved;   /* reserved for future use */
} z_stream;

typedef z_stream FAR *z_streamp;

/*
     gzip header information passed to and from zlib routines.  See RFC 1952
  for more details on the meanings of these fields.
*/
typedef struct gz_header_s {
    int     text;       /* true if compressed data believed to be text */
    uLong   time;       /* modification time */
    int     xflags;     /* extra flags (not used when writing a gzip file) */
    int     os;         /* operating system */
    Bytef   *extra;     /* pointer to extra field or Z_NULL if none */
    uInt    extra_len;  /* extra field length (valid if extra != Z_NULL) */
    uInt    extra_max;  /* space at extra (only when reading header) */
    Bytef   *name;      /* pointer to zero-terminated file name or Z_NULL */
    uInt    name_max;   /* space at name (only when reading header) */
    Bytef   *comment;   /* pointer to zero-terminated comment or Z_NULL */
    uInt    comm_max;   /* space at comment (only when reading header) */
    int     hcrc;       /* true if there was or will be a header crc */
    int     done;       /* true when done reading gzip header (not used
                           when writing a gzip file) */
} gz_header;

typedef gz_header FAR *gz_headerp;

/*
     The application must update next_in and avail_in when avail_in has dropped
   to zero.  It must update next_out and avail_out when avail_out has dropped
   to zero.  The application must initialize zalloc, zfree and opaque before
   calling the init function.  All other fields are set by the compression
   library and must not be updated by the application.

     The opaque value provided by the application will be passed as the first
   parameter for calls of zalloc and zfree.  This can be useful for custom
   memory management.  The compression library attaches no meaning to the
   opaque value.

     zalloc must return Z_NULL if there is not enough memory for the object.
   If zlib is used in a multi-threaded application, zalloc and zfree must be
   thread safe.  In that case, zlib is thread-safe.  When zalloc and zfree are
   Z_NULL on entry to the initialization function, they are set to internal
   routines that use the standard library functions malloc() and free().

     On 16-bit systems, the functions zalloc and zfree must be able to allocate
   exactly 65536 bytes, but will not be required to allocate more than this if
   the symbol MAXSEG_64K is defined (see zconf.h).  WARNING: On MSDOS, pointers
   returned by zalloc for objects of exactly 65536 bytes *must* have their
   offset normalized to zero.  The default allocation function provided by this
   library ensures this (see zutil.c).  To reduce memory requirements and avoid
   any allocation of 64K objects, at the expense of compression ratio, compile
   the library with -DMAX_WBITS=14 (see zconf.h).

     The fields total_in and total_out can be used for statistics or progress
   reports.  After compression, total_in holds the total size of the
   uncompressed data and may be saved for use by the decompressor (particularly
   if the decompressor wants to decompress everything in a single step).
*/

                        /* constants */

#define Z_NO_FLUSH      0
#define Z_PARTIAL_FLUSH 1
#define Z_SYNC_FLUSH    2
#define Z_FULL_FLUSH    3
#define Z_FINISH        4
#define Z_BLOCK         5
#define Z_TREES         6
/* Allowed flush values; see deflate() and inflate() below for details */

#define Z_OK            0
#define Z_STREAM_END    1
#define Z_NEED_DICT     2
#define Z_ERRNO        (-1)
#define Z_STREAM_ERROR (-2)
#define Z_DATA_ERROR   (-3)
#define Z_MEM_ERROR    (-4)
#define Z_BUF_ERROR    (-5)
#define Z_VERSION_ERROR (-6)
/* Return codes for the compression/decompression functions. Negative values
 * are errors, positive values are used for special but normal events.
 */

#define Z_NO_COMPRESSION         0
#define Z_BEST_SPEED             1
#define Z_BEST_COMPRESSION       9
#define Z_DEFAULT_COMPRESSION  (-1)
/* compression levels */

#define Z_FILTERED            1
#define Z_HUFFMAN_ONLY        2
#define Z_RLE                 3
#define Z_FIXED               4
#define Z_DEFAULT_STRATEGY    0
/* compression strategy; see deflateInit2() below for details */

#define Z_BINARY   0
#define Z_TEXT     1
#define Z_ASCII    Z_TEXT   /* for compatibility with 1.2.2 and earlier */
#define Z_UNKNOWN  2
/* Possible values of the data_type field for deflate() */

#define Z_DEFLATED   8
/* The deflate compression method (the only one supported in this version) */

#define Z_NULL  0  /* for initializing zalloc, zfree, opaque */

#define zlib_version zlibVersion()
/* for compatibility with versions < 1.0.2 */


                        /* basic functions */

ZEXTERN const char * ZEXPORT zlibVersion OF((void));
/* The application can compare zlibVersion and ZLIB_VERSION for consistency.
   If the first character differs, the library code actually used is not
   compatible with the zlib.h header file used by the application.  This check
   is automatically made by deflateInit and inflateInit.
 */

/*
ZEXTERN int ZEXPORT deflateInit OF((z_streamp strm, int level));

     Initializes the internal stream state for compression.  The fields
   zalloc, zfree and opaque must be initialized before by the caller.  If
   zalloc and zfree are set to Z_NULL, deflateInit updates them to use default
   allocation functions.

     The compression level must be Z_DEFAULT_COMPRESSION, or between 0 and 9:
   1 gives best speed, 9 gives best compression, 0 gives no compression at all
   (the input data is simply copied a block at a time).  Z_DEFAULT_COMPRESSION
   requests a default compromise between speed and compression (currently
   equivalent to level 6).

     deflateInit returns Z_OK if success, Z_MEM_ERROR if there was not enough
   memory, Z_STREAM_ERROR if level is not a valid compression level, or
   Z_VERSION_ERROR if the zlib library version (zlib_version) is incompatible
   with the version assumed by the caller (ZLIB_VERSION).  msg is set to null
   if there is no error message.  deflateInit does not perform any compression:
   this will be done by deflate().
*/


ZEXTERN int ZEXPORT deflate OF((z_streamp strm, int flush));
/*
    deflate compresses as much data as possible, and stops when the input
  buffer becomes empty or the output buffer becomes full.  It may introduce
  some output latency (reading input without producing any output) except when
  forced to flush.

    The detailed semantics are as follows.  deflate performs one or both of the
  following actions:

  - Compress more input starting at next_in and update next_in and avail_in
    accordingly.  If not all input can be processed (because there is not
    enough room in the output buffer), next_in and avail_in are updated and
    processing will resume at this point for the next call of deflate().

  - Generate more output starting at next_out and update next_out and avail_out
    accordingly.  This action is forced if the parameter flush is non zero.
    Forcing flush frequently degrades the compression ratio, so this parameter
    should be set only when necessary.  Some output may be provided even if
    flush is zero.

    Before the call of deflate(), the application should ensure that at least
  one of the actions is possible, by providing more input and/or consuming more
  output, and updating avail_in or avail_out accordingly; avail_out should
  never be zero before the call.  The application can consume the compressed
  output when it wants, for example when the output buffer is full (avail_out
  == 0), or after each call of deflate().  If deflate returns Z_OK and with
  zero avail_out, it must be called again after making room in the output
  buffer because there might be more output pending. See deflatePending(),
  which can be used if desired to determine whether or not there is more ouput
  in that case.

    Normally the parameter flush is set to Z_NO_FLUSH, which allows deflate to
  decide how much data to accumulate before producing output, in order to
  maximize compression.

    If the parameter flush is set to Z_SYNC_FLUSH, all pending output is
  flushed to the output buffer and the output is aligned on a byte boundary, so
  that the decompressor can get all input data available so far.  (In
  particular avail_in is zero after the call if enough output space has been
  provided before the call.) Flushing may degrade compression for some
  compression algorithms and so it should be used only when necessary.  This
  completes the current deflate block and follows it with an empty stored block
  that is three bits plus filler bits to the next byte, followed by four bytes
  (00 00 ff ff).

    If flush is set to Z_PARTIAL_FLUSH, all pending output is flushed to the
  output buffer, but the output is not aligned to a byte boundary.  All of the
  input data so far will be available to the decompressor, as for Z_SYNC_FLUSH.
  This completes the current deflate block and follows it with an empty fixed
  codes block that is 10 bits long.  This assures that enough bytes are output
  in order for the decompressor to finish the block before the empty fixed
  codes block.

    If flush is set to Z_BLOCK, a deflate block is completed and emitted, as
  for Z_SYNC_FLUSH, but the output is not aligned on a byte boundary, and up to
  seven bits of the current block are held to be written as the next byte after
  the next deflate block is completed.  In this case, the decompressor may not
  be provided enough bits at this point in order to complete decompression of
  the data provided so far to the compressor.  It may need to wait for the next
  block to be emitted.  This is for advanced applications that need to control
  the emission of deflate blocks.

    If flush is set to Z_FULL_FLUSH, all output is flushed as with
  Z_SYNC_FLUSH, and the compression state is reset so that decompression can
  restart from this point if previous compressed data has been damaged or if
  random access is desired.  Using Z_FULL_FLUSH too often can seriously degrade
  compression.

    If deflate returns with avail_out == 0, this function must be called again
  with the same value of the flush parameter and more output space (updated
  avail_out), until the flush is complete (deflate returns with non-zero
  avail_out).  In the case of a Z_FULL_FLUSH or Z_SYNC_FLUSH, make sure that
  avail_out is greater than six to avoid repeated flush markers due to
  avail_out == 0 on return.

    If the parameter flush is set to Z_FINISH, pending input is processed,
  pending output is flushed and deflate returns with Z_STREAM_END if there was
  enough output space.  If deflate returns with Z_OK or Z_BUF_ERROR, this
  function must be called again with Z_FINISH and more output space (updated
  avail_out) but no more input data, until it returns with Z_STREAM_END or an
  error.  After deflate has returned Z_STREAM_END, the only possible operations
  on the stream are deflateReset or deflateEnd.

    Z_FINISH can be used in the first deflate call after deflateInit if all the
  compression is to be done in a single step.  In order to complete in one
  call, avail_out must be at least the value returned by deflateBound (see
  below).  Then deflate is guaranteed to return Z_STREAM_END.  If not enough
  output space is provided, deflate will not return Z_STREAM_END, and it must
  be called again as described above.

    deflate() sets strm->adler to the Adler-32 checksum of all input read
  so far (that is, total_in bytes).  If a gzip stream is being generated, then
  strm->adler will be the CRC-32 checksum of the input read so far.  (See
  deflateInit2 below.)

    deflate() may update strm->data_type if it can make a good guess about
  the input data type (Z_BINARY or Z_TEXT).  If in doubt, the data is
  considered binary.  This field is only for information purposes and does not
  affect the compression algorithm in any manner.

    deflate() returns Z_OK if some progress has been made (more input
  processed or more output produced), Z_STREAM_END if all input has been
  consumed and all output has been produced (only when flush is set to
  Z_FINISH), Z_STREAM_ERROR if the stream state was inconsistent (for example
  if next_in or next_out was Z_NULL or the state was inadvertently written over
  by the application), or Z_BUF_ERROR if no progress is possible (for example
  avail_in or avail_out was zero).  Note that Z_BUF_ERROR is not fatal, and
  deflate() can be called again with more input and more output space to
  continue compressing.
*/


ZEXTERN int ZEXPORT deflateEnd OF((z_streamp strm));
/*
     All dynamically allocated data structures for this stream are freed.
   This function discards any unprocessed input and does not flush any pending
   output.

     deflateEnd returns Z_OK if success, Z_STREAM_ERROR if the
   stream state was inconsistent, Z_DATA_ERROR if the stream was freed
   prematurely (some input or output was discarded).  In the error case, msg
   may be set but then points to a static string (which must not be
   deallocated).
*/


/*
ZEXTERN int ZEXPORT inflateInit OF((z_streamp strm));

     Initializes the internal stream state for decompression.  The fields
   next_in, avail_in, zalloc, zfree and opaque must be initialized before by
   the caller.  In the current version of inflate, the provided input is not
   read or consumed.  The allocation of a sliding window will be deferred to
   the first call of inflate (if the decompression does not complete on the
   first call).  If zalloc and zfree are set to Z_NULL, inflateInit updates
   them to use default allocation functions.

     inflateInit returns Z_OK if success, Z_MEM_ERROR if there was not enough
   memory, Z_VERSION_ERROR if the zlib library version is incompatible with the
   version assumed by the caller, or Z_STREAM_ERROR if the parameters are
   invalid, such as a null pointer to the structure.  msg is set to null if
   there is no error message.  inflateInit does not perform any decompression.
   Actual decompression will be done by inflate().  So next_in, and avail_in,
   next_out, and avail_out are unused and unchanged.  The current
   implementation of inflateInit() does not process any header information --
   that is deferred until inflate() is called.
*/


ZEXTERN int ZEXPORT inflate OF((z_streamp strm, int flush));
/*
    inflate decompresses as much data as possible, and stops when the input
  buffer becomes empty or the output buffer becomes full.  It may introduce
  some output latency (reading input without producing any output) except when
  forced to flush.

  The detailed semantics are as follows.  inflate performs one or both of the
  following actions:

  - Decompress more input starting at next_in and update next_in and avail_in
    accordingly.  If not all input can be processed (because there is not
    enough room in the output buffer), then next_in and avail_in are updated
    accordingly, and processing will resume at this point for the next call of
    inflate().

  - Generate more output starting at next_out and update next_out and avail_out
    accordingly.  inflate() provides as much output as possible, until there is
    no more input data or no more space in the output buffer (see below about
    the flush parameter).

    Before the call of inflate(), the application should ensure that at least
  one of the actions is possible, by providing more input and/or consuming more
  output, and updating the next_* and avail_* values accordingly.  If the
  caller of inflate() does not provide both available input and available
  output space, it is possible that there will be no progress made.  The
  application can consume the uncompressed output when it wants, for example
  when the output buffer is full (avail_out == 0), or after each call of
  inflate().  If inflate returns Z_OK and with zero avail_out, it must be
  called again after making room in the output buffer because there might be
  more output pending.

    The flush parameter of inflate() can be Z_NO_FLUSH, Z_SYNC_FLUSH, Z_FINISH,
  Z_BLOCK, or Z_TREES.  Z_SYNC_FLUSH requests that inflate() flush as much
  output as possible to the output buffer.  Z_BLOCK requests that inflate()
  stop if and when it gets to the next deflate block boundary.  When decoding
  the zlib or gzip format, this will cause inflate() to return immediately
  after the header and before the first block.  When doing a raw inflate,
  inflate() will go ahead and process the first block, and will return when it
  gets to the end of that block, or when it runs out of data.

    The Z_BLOCK option assists in appending to or combining deflate streams.
  To assist in this, on return inflate() always sets strm->data_type to the
  number of unused bits in the last byte taken from strm->next_in, plus 64 if
  inflate() is currently decoding the last block in the deflate stream, plus
  128 if inflate() returned immediately after decoding an end-of-block code or
  decoding the complete header up to just before the first byte of the deflate
  stream.  The end-of-block will not be indicated until all of the uncompressed
  data from that block has been written to strm->next_out.  The number of
  unused bits may in general be greater than seven, except when bit 7 of
  data_type is set, in which case the number of unused bits will be less than
  eight.  data_type is set as noted here every time inflate() returns for all
  flush options, and so can be used to determine the amount of currently
  consumed input in bits.

    The Z_TREES option behaves as Z_BLOCK does, but it also returns when the
  end of each deflate block header is reached, before any actual data in that
  block is decoded.  This allows the caller to determine the length of the
  deflate block header for later use in random access within a deflate block.
  256 is added to the value of strm->data_type when inflate() returns
  immediately after reaching the end of the deflate block header.

    inflate() should normally be called until it returns Z_STREAM_END or an
  error.  However if all decompression is to be performed in a single step (a
  single call of inflate), the parameter flush should be set to Z_FINISH.  In
  this case all pending input is processed and all pending output is flushed;
  avail_out must be large enough to hold all of the uncompressed data for the
  operation to complete.  (The size of the uncompressed data may have been
  saved by the compressor for this purpose.)  The use of Z_FINISH is not
  required to perform an inflation in one step.  However it may be used to
  inform inflate that a faster approach can be used for the single inflate()
  call.  Z_FINISH also informs inflate to not maintain a sliding window if the
  stream completes, which reduces inflate's memory footprint.  If the stream
  does not complete, either because not all of the stream is provided or not
  enough output space is provided, then a sliding window will be allocated and
  inflate() can be called again to continue the operation as if Z_NO_FLUSH had
  been used.

     In this implementation, inflate() always flushes as much output as
  possible to the output buffer, and always uses the faster approach on the
  first call.  So the effects of the flush parameter in this implementation are
  on the return value of inflate() as noted below, when inflate() returns early
  when Z_BLOCK or Z_TREES is used, and when inflate() avoids the allocation of
  memory for a sliding window when Z_FINISH is used.

     If a preset dictionary is needed after this call (see inflateSetDictionary
  below), inflate sets strm->adler to the Adler-32 checksum of the dictionary
  chosen by the compressor and returns Z_NEED_DICT; otherwise it sets
  strm->adler to the Adler-32 checksum of all output produced so far (that is,
  total_out bytes) and returns Z_OK, Z_STREAM_END or an error code as described
  below.  At the end of the stream, inflate() checks that its computed Adler-32
  checksum is equal to that saved by the compressor and returns Z_STREAM_END
  only if the checksum is correct.

    inflate() can decompress and check either zlib-wrapped or gzip-wrapped
  deflate data.  The header type is detected automatically, if requested when
  initializing with inflateInit2().  Any information contained in the gzip
  header is not retained unless inflateGetHeader() is used.  When processing
  gzip-wrapped deflate data, strm->adler32 is set to the CRC-32 of the output
  produced so far.  The CRC-32 is checked against the gzip trailer, as is the
  uncompressed length, modulo 2^32.

    inflate() returns Z_OK if some progress has been made (more input processed
  or more output produced), Z_STREAM_END if the end of the compressed data has
  been reached and all uncompressed output has been produced, Z_NEED_DICT if a
  preset dictionary is needed at this point, Z_DATA_ERROR if the input data was
  corrupted (input stream not conforming to the zlib format or incorrect check
  value, in which case strm->msg points to a string with a more specific
  error), Z_STREAM_ERROR if the stream structure was inconsistent (for example
  next_in or next_out was Z_NULL, or the state was inadvertently written over
  by the application), Z_MEM_ERROR if there was not enough memory, Z_BUF_ERROR
  if no progress was possible or if there was not enough room in the output
  buffer when Z_FINISH is used.  Note that Z_BUF_ERROR is not fatal, and
  inflate() can be called again with more input and more output space to
  continue decompressing.  If Z_DATA_ERROR is returned, the application may
  then call inflateSync() to look for a good compression block if a partial
  recovery of the data is to be attempted.
*/


ZEXTERN int ZEXPORT inflateEnd OF((z_streamp strm));
/*
     All dynamically allocated data structures for this stream are freed.
   This function discards any unprocessed input and does not flush any pending
   output.

     inflateEnd returns Z_OK if success, or Z_STREAM_ERROR if the stream state
   was inconsistent.
*/


                        /* Advanced functions */

/*
    The following functions are needed only in some special applications.
*/

/*
ZEXTERN int ZEXPORT deflateInit2 OF((z_streamp strm,
                                     int  level,
                                     int  method,
                                     int  windowBits,
                                     int  memLevel,
                                     int  strategy));

     This is another version of deflateInit with more compression options.  The
   fields next_in, zalloc, zfree and opaque must be initialized before by the
   caller.

     The method parameter is the compression method.  It must be Z_DEFLATED in
   this version of the library.

     The windowBits parameter is the base two logarithm of the window size
   (the size of the history buffer).  It should be in the range 8..15 for this
   version of the library.  Larger values of this parameter result in better
   compression at the expense of memory usage.  The default value is 15 if
   deflateInit is used instead.

     For the current implementation of deflate(), a windowBits value of 8 (a
   window size of 256 bytes) is not supported.  As a result, a request for 8
   will result in 9 (a 512-byte window).  In that case, providing 8 to
   inflateInit2() will result in an error when the zlib header with 9 is
   checked against the initialization of inflate().  The remedy is to not use 8
   with deflateInit2() with this initialization, or at least in that case use 9
   with inflateInit2().

     windowBits can also be -8..-15 for raw deflate.  In this case, -windowBits
   determines the window size.  deflate() will then generate raw deflate data
   with no zlib header or trailer, and will not compute a check value.

     windowBits can also be greater than 15 for optional gzip encoding.  Add
   16 to windowBits to write a simple gzip header and trailer around the
   compressed data instead of a zlib wrapper.  The gzip header will have no
   file name, no extra data, no comment, no modification time (set to zero), no
   header crc, and the operating system will be set to the appropriate value,
   if the operating system was determined at compile time.  If a gzip stream is
   being written, strm->adler is a CRC-32 instead of an Adler-32.

     For raw deflate or gzip encoding, a request for a 256-byte window is
   rejected as invalid, since only the zlib header provides a means of
   transmitting the window size to the decompressor.

     The memLevel parameter specifies how much memory should be allocated
   for the internal compression state.  memLevel=1 uses minimum memory but is
   slow and reduces compression ratio; memLevel=9 uses maximum memory for
   optimal speed.  The default value is 8.  See zconf.h for total memory usage
   as a function of windowBits and memLevel.

     The strategy parameter is used to tune the compression algorithm.  Use the
   value Z_DEFAULT_STRATEGY for normal data, Z_FILTERED for data produced by a
   filter (or predictor), Z_HUFFMAN_ONLY to force Huffman encoding only (no
   string match), or Z_RLE to limit match distances to one (run-length
   encoding).  Filtered data consists mostly of small values with a somewhat
   random distribution.  In this case, the compression algorithm is tuned to
   compress them better.  The effect of Z_FILTERED is to force more Huffman
   coding and less string matching; it is somewhat intermediate between
   Z_DEFAULT_STRATEGY and Z_HUFFMAN_ONLY.  Z_RLE is designed to be almost as
   fast as Z_HUFFMAN_ONLY, but give better compression for PNG image data.  The
   strategy parameter only affects the compression ratio but not the
   correctness of the compressed output even if it is not set appropriately.
   Z_FIXED prevents the use of dynamic Huffman codes, allowing for a simpler
   decoder for special applications.

     deflateInit2 returns Z_OK if success, Z_MEM_ERROR if there was not enough
   memory, Z_STREAM_ERROR if any parameter is invalid (such as an invalid
   method), or Z_VERSION_ERROR if the zlib library version (zlib_version) is
   incompatible with the version assumed by the caller (ZLIB_VERSION).  msg is
   set to null if there is no error message.  deflateInit2 does not perform any
   compression: this will be done by deflate().
*/

ZEXTERN int ZEXPORT deflateSetDictionary OF((z_streamp strm,
                                             const Bytef *dictionary,
                                             uInt  dictLength));
/*
     Initializes the compression dictionary from the given byte sequence
   without producing any compressed output.  When using the zlib format, this
   function must be called immediately after deflateInit, deflateInit2 or
   deflateReset, and before any call of deflate.  When doing raw deflate, this
   function must be called either before any call of deflate, or immediately
   after the completion of a deflate block, i.e. after all input has been
   consumed and all output has been delivered when using any of the flush
   options Z_BLOCK, Z_PARTIAL_FLUSH, Z_SYNC_FLUSH, or Z_FULL_FLUSH.  The
   compressor and decompressor must use exactly the same dictionary (see
   inflateSetDictionary).

     The dictionary should consist of strings (byte sequences) that are likely
   to be encountered later in the data to be compressed, with the most commonly
   used strings preferably put towards the end of the dictionary.  Using a
   dictionary is most useful when the data to be compressed is short and can be
   predicted with good accuracy; the data can then be compressed better than
   with the default empty dictionary.

     Depending on the size of the compression data structures selected by
   deflateInit or deflateInit2, a part of the dictionary may in effect be
   discarded, for example if the dictionary is larger than the window size
   provided in deflateInit or deflateInit2.  Thus the strings most likely to be
   useful should be put at the end of the dictionary, not at the front.  In
   addition, the current implementation of deflate will use at most the window
   size minus 262 bytes of the provided dictionary.

     Upon return of this function, strm->adler is set to the Adler-32 value
   of the dictionary; the decompressor may later use this value to determine
   which dictionary has been used by the compressor.  (The Adler-32 value
   applies to the whole dictionary even if only a subset of the dictionary is
   actually used by the compressor.) If a raw deflate was requested, then the
   Adler-32 value is not computed and strm->adler is not set.

     deflateSetDictionary returns Z_OK if success, or Z_STREAM_ERROR if a
   parameter is invalid (e.g.  dictionary being Z_NULL) or the stream state is
   inconsistent (for example if deflate has already been called for this stream
   or if not at a block boundary for raw deflate).  deflateSetDictionary does
   not perform any compression: this will be done by deflate().
*/

ZEXTERN int ZEXPORT deflateGetDictionary OF((z_streamp strm,
                                             Bytef *dictionary,
                                             uInt  *dictLength));
/*
     Returns the sliding dictionary being maintained by deflate.  dictLength is
   set to the number of bytes in the dictionary, and that many bytes are copied
   to dictionary.  dictionary must have enough space, where 32768 bytes is
   always enough.  If deflateGetDictionary() is called with dictionary equal to
   Z_NULL, then only the dictionary length is returned, and nothing is copied.
   Similary, if dictLength is Z_NULL, then it is not set.

     deflateGetDictionary() may return a length less than the window size, even
   when more than the window size in input has been provided. It may return up
   to 258 bytes less in that case, due to how zlib's implementation of deflate
   manages the sliding window and lookahead for matches, where matches can be
   up to 258 bytes long. If the application needs the last window-size bytes of
   input, then that would need to be saved by the application outside of zlib.

     deflateGetDictionary returns Z_OK on success, or Z_STREAM_ERROR if the
   stream state is inconsistent.
*/

ZEXTERN int ZEXPORT deflateCopy OF((z_streamp dest,
                                    z_streamp source));
/*
     Sets the destination stream as a complete copy of the source stream.

     This function can be useful when several compression strategies will be
   tried, for example when there are several ways of pre-processing the input
   data with a filter.  The streams that will be discarded should then be freed
   by calling deflateEnd.  Note that deflateCopy duplicates the internal
   compression state which can be quite large, so this strategy is slow and can
   consume lots of memory.

     deflateCopy returns Z_OK if success, Z_MEM_ERROR if there was not
   enough memory, Z_STREAM_ERROR if the source stream state was inconsistent
   (such as zalloc being Z_NULL).  msg is left unchanged in both source and
   destination.
*/

ZEXTERN int ZEXPORT deflateReset OF((z_streamp strm));
/*
     This function is equivalent to deflateEnd followed by deflateInit, but
   does not free and reallocate the internal compression state.  The stream
   will leave the compression level and any other attributes that may have been
   set unchanged.

     deflateReset returns Z_OK if success, or Z_STREAM_ERROR if the source
   stream state was inconsistent (such as zalloc or state being Z_NULL).
*/

ZEXTERN int ZEXPORT deflateParams OF((z_streamp strm,
                                      int level,
                                      int strategy));
/*
     Dynamically update the compression level and compression strategy.  The
   interpretation of level and strategy is as in deflateInit2().  This can be
   used to switch between compression and straight copy of the input data, or
   to switch to a different kind of input data requiring a different strategy.
   If the compression approach (which is a function of the level) or the
   strategy is changed, and if any input has been consumed in a previous
   deflate() call, then the input available so far is compressed with the old
   level and strategy using deflate(strm, Z_BLOCK).  There are three approaches
   for the compression levels 0, 1..3, and 4..9 respectively.  The new level
   and strategy will take effect at the next call of deflate().

     If a deflate(strm, Z_BLOCK) is performed by deflateParams(), and it does
   not have enough output space to complete, then the parameter change will not
   take effect.  In this case, deflateParams() can be called again with the
   same parameters and more output space to try again.

     In order to assure a change in the parameters on the first try, the
   deflate stream should be flushed using deflate() with Z_BLOCK or other flush
   request until strm.avail_out is not zero, before calling deflateParams().
   Then no more input data should be provided before the deflateParams() call.
   If this is done, the old level and strategy will be applied to the data
   compressed before deflateParams(), and the new level and strategy will be
   applied to the the data compressed after deflateParams().

     deflateParams returns Z_OK on success, Z_STREAM_ERROR if the source stream
   state was inconsistent or if a parameter was invalid, or Z_BUF_ERROR if
   there was not enough output space to complete the compression of the
   available input data before a change in the strategy or approach.  Note that
   in the case of a Z_BUF_ERROR, the parameters are not changed.  A return
   value of Z_BUF_ERROR is not fatal, in which case deflateParams() can be
   retried with more output space.
*/

ZEXTERN int ZEXPORT deflateTune OF((z_streamp strm,
                                    int good_length,
                                    int max_lazy,
                                    int nice_length,
                                    int max_chain));
/*
     Fine tune deflate's internal compression parameters.  This should only be
   used by someone who understands the algorithm used by zlib's deflate for
   searching for the best matching string, and even then only by the most
   fanatic optimizer trying to squeeze out the last compressed bit for their
   specific input data.  Read the deflate.c source code for the meaning of the
   max_lazy, good_length, nice_length, and max_chain parameters.

     deflateTune() can be called after deflateInit() or deflateInit2(), and
   returns Z_OK on success, or Z_STREAM_ERROR for an invalid deflate stream.
 */

ZEXTERN uLong ZEXPORT deflateBound OF((z_streamp strm,
                                       uLong sourceLen));
/*
     deflateBound() returns an upper bound on the compressed size after
   deflation of sourceLen bytes.  It must be called after deflateInit() or
   deflateInit2(), and after deflateSetHeader(), if used.  This would be used
   to allocate an output buffer for deflation in a single pass, and so would be
   called before deflate().  If that first deflate() call is provided the
   sourceLen input bytes, an output buffer allocated to the size returned by
   deflateBound(), and the flush value Z_FINISH, then deflate() is guaranteed
   to return Z_STREAM_END.  Note that it is possible for the compressed size to
   be larger than the value returned by deflateBound() if flush options other
   than Z_FINISH or Z_NO_FLUSH are used.
*/

ZEXTERN int ZEXPORT deflatePending OF((z_streamp strm,
                                       unsigned *pending,
                                       int *bits));
/*
     deflatePending() returns the number of bytes and bits of output that have
   been generated, but not yet provided in the available output.  The bytes not
   provided would be due to the available output space having being consumed.
   The number of bits of output not provided are between 0 and 7, where they
   await more bits to join them in order to fill out a full byte.  If pending
   or bits are Z_NULL, then those values are not set.

     deflatePending returns Z_OK if success, or Z_STREAM_ERROR if the source
   stream state was inconsistent.
 */

ZEXTERN int ZEXPORT deflatePrime OF((z_streamp strm,
                                     int bits,
                                     int value));
/*
     deflatePrime() inserts bits in the deflate output stream.  The intent
   is that this function is used to start off the deflate output with the bits
   leftover from a previous deflate stream when appending to it.  As such, this
   function can only be used for raw deflate, and must be used before the first
   deflate() call after a deflateInit2() or deflateReset().  bits must be less
   than or equal to 16, and that many of the least significant bits of value
   will be inserted in the output.

     deflatePrime returns Z_OK if success, Z_BUF_ERROR if there was not enough
   room in the internal buffer to insert the bits, or Z_STREAM_ERROR if the
   source stream state was inconsistent.
*/

ZEXTERN int ZEXPORT deflateSetHeader OF((z_streamp strm,
                                         gz_headerp head));
/*
     deflateSetHeader() provides gzip header information for when a gzip
   stream is requested by deflateInit2().  deflateSetHeader() may be called
   after deflateInit2() or deflateReset() and before the first call of
   deflate().  The text, time, os, extra field, name, and comment information
   in the provided gz_header structure are written to the gzip header (xflag is
   ignored -- the extra flags are set according to the compression level).  The
   caller must assure that, if not Z_NULL, name and comment are terminated with
   a zero byte, and that if extra is not Z_NULL, that extra_len bytes are
   available there.  If hcrc is true, a gzip header crc is included.  Note that
   the current versions of the command-line version of gzip (up through version
   1.3.x) do not support header crc's, and will report that it is a "multi-part
   gzip file" and give up.

     If deflateSetHeader is not used, the default gzip header has text false,
   the time set to zero, and os set to 255, with no extra, name, or comment
   fields.  The gzip header is returned to the default state by deflateReset().

     deflateSetHeader returns Z_OK if success, or Z_STREAM_ERROR if the source
   stream state was inconsistent.
*/

/*
ZEXTERN int ZEXPORT inflateInit2 OF((z_streamp strm,
                                     int  windowBits));

     This is another version of inflateInit with an extra parameter.  The
   fields next_in, avail_in, zalloc, zfree and opaque must be initialized
   before by the caller.

     The windowBits parameter is the base two logarithm of the maximum window
   size (the size of the history buffer).  It should be in the range 8..15 for
   this version of the library.  The default value is 15 if inflateInit is used
   instead.  windowBits must be greater than or equal to the windowBits value
   provided to deflateInit2() while compressing, or it must be equal to 15 if
   deflateInit2() was not used.  If a compressed stream with a larger window
   size is given as input, inflate() will return with the error code
   Z_DATA_ERROR instead of trying to allocate a larger window.

     windowBits can also be zero to request that inflate use the window size in
   the zlib header of the compressed stream.

     windowBits can also be -8..-15 for raw inflate.  In this case, -windowBits
   determines the window size.  inflate() will then process raw deflate data,
   not looking for a zlib or gzip header, not generating a check value, and not
   looking for any check values for comparison at the end of the stream.  This
   is for use with other formats that use the deflate compressed data format
   such as zip.  Those formats provide their own check values.  If a custom
   format is developed using the raw deflate format for compressed data, it is
   recommended that a check value such as an Adler-32 or a CRC-32 be applied to
   the uncompressed data as is done in the zlib, gzip, and zip formats.  For
   most applications, the zlib format should be used as is.  Note that comments
   above on the use in deflateInit2() applies to the magnitude of windowBits.

     windowBits can also be greater than 15 for optional gzip decoding.  Add
   32 to windowBits to enable zlib and gzip decoding with automatic header
   detection, or add 16 to decode only the gzip format (the zlib format will
   return a Z_DATA_ERROR).  If a gzip stream is being decoded, strm->adler is a
   CRC-32 instead of an Adler-32.  Unlike the gunzip utility and gzread() (see
   below), inflate() will not automatically decode concatenated gzip streams.
   inflate() will return Z_STREAM_END at the end of the gzip stream.  The state
   would need to be reset to continue decoding a subsequent gzip stream.

     inflateInit2 returns Z_OK if success, Z_MEM_ERROR if there was not enough
   memory, Z_VERSION_ERROR if the zlib library version is incompatible with the
   version assumed by the caller, or Z_STREAM_ERROR if the parameters are
   invalid, such as a null pointer to the structure.  msg is set to null if
   there is no error message.  inflateInit2 does not perform any decompression
   apart from possibly reading the zlib header if present: actual decompression
   will be done by inflate().  (So next_in and avail_in may be modified, but
   next_out and avail_out are unused and unchanged.) The current implementation
   of inflateInit2() does not process any header information -- that is
   deferred until inflate() is called.
*/

ZEXTERN int ZEXPORT inflateSetDictionary OF((z_streamp strm,
                                             const Bytef *dictionary,
                                             uInt  dictLength));
/*
     Initializes the decompression dictionary from the given uncompressed byte
   sequence.  This function must be called immediately after a call of inflate,
   if that call returned Z_NEED_DICT.  The dictionary chosen by the compressor
   can be determined from the Adler-32 value returned by that call of inflate.
   The compressor and decompressor must use exactly the same dictionary (see
   deflateSetDictionary).  For raw inflate, this function can be called at any
   time to set the dictionary.  If the provided dictionary is smaller than the
   window and there is already data in the window, then the provided dictionary
   will amend what's there.  The application must insure that the dictionary
   that was used for compression is provided.

     inflateSetDictionary returns Z_OK if success, Z_STREAM_ERROR if a
   parameter is invalid (e.g.  dictionary being Z_NULL) or the stream state is
   inconsistent, Z_DATA_ERROR if the given dictionary doesn't match the
   expected one (incorrect Adler-32 value).  inflateSetDictionary does not
   perform any decompression: this will be done by subsequent calls of
   inflate().
*/

ZEXTERN int ZEXPORT inflateGetDictionary OF((z_streamp strm,
                                             Bytef *dictionary,
                                             uInt  *dictLength));
/*
     Returns the sliding dictionary being maintained by inflate.  dictLength is
   set to the number of bytes in the dictionary, and that many bytes are copied
   to dictionary.  dictionary must have enough space, where 32768 bytes is
   always enough.  If inflateGetDictionary() is called with dictionary equal to
   Z_NULL, then only the dictionary length is returned, and nothing is copied.
   Similary, if dictLength is Z_NULL, then it is not set.

     inflateGetDictionary returns Z_OK on success, or Z_STREAM_ERROR if the
   stream state is inconsistent.
*/

ZEXTERN int ZEXPORT inflateSync OF((z_streamp strm));
/*
     Skips invalid compressed data until a possible full flush point (see above
   for the description of deflate with Z_FULL_FLUSH) can be found, or until all
   available input is skipped.  No output is provided.

     inflateSync searches for a 00 00 FF FF pattern in the compressed data.
   All full flush points have this pattern, but not all occurrences of this
   pattern are full flush points.

     inflateSync returns Z_OK if a possible full flush point has been found,
   Z_BUF_ERROR if no more input was provided, Z_DATA_ERROR if no flush point
   has been found, or Z_STREAM_ERROR if the stream structure was inconsistent.
   In the success case, the application may save the current current value of
   total_in which indicates where valid compressed data was found.  In the
   error case, the application may repeatedly call inflateSync, providing more
   input each time, until success or end of the input data.
*/

ZEXTERN int ZEXPORT inflateCopy OF((z_streamp dest,
                                    z_streamp source));
/*
     Sets the destination stream as a complete copy of the source stream.

     This function can be useful when randomly accessing a large stream.  The
   first pass through the stream can periodically record the inflate state,
   allowing restarting inflate at those points when randomly accessing the
   stream.

     inflateCopy returns Z_OK if success, Z_MEM_ERROR if there was not
   enough memory, Z_STREAM_ERROR if the source stream state was inconsistent
   (such as zalloc being Z_NULL).  msg is left unchanged in both source and
   destination.
*/

ZEXTERN int ZEXPORT inflateReset OF((z_streamp strm));
/*
     This function is equivalent to inflateEnd followed by inflateInit,
   but does not free and reallocate the internal decompression state.  The
   stream will keep attributes that may have been set by inflateInit2.

     inflateReset returns Z_OK if success, or Z_STREAM_ERROR if the source
   stream state was inconsistent (such as zalloc or state being Z_NULL).
*/

ZEXTERN int ZEXPORT inflateReset2 OF((z_streamp strm,
                                      int windowBits));
/*
     This function is the same as inflateReset, but it also permits changing
   the wrap and window size requests.  The windowBits parameter is interpreted
   the same as it is for inflateInit2.  If the window size is changed, then the
   memory allocated for the window is freed, and the window will be reallocated
   by inflate() if needed.

     inflateReset2 returns Z_OK if success, or Z_STREAM_ERROR if the source
   stream state was inconsistent (such as zalloc or state being Z_NULL), or if
   the windowBits parameter is invalid.
*/

ZEXTERN int ZEXPORT inflatePrime OF((z_streamp strm,
                                     int bits,
                                     int value));
/*
     This function inserts bits in the inflate input stream.  The intent is
   that this function is used to start inflating at a bit position in the
   middle of a byte.  The provided bits will be used before any bytes are used
   from next_in.  This function should only be used with raw inflate, and
   should be used before the first inflate() call after inflateInit2() or
   inflateReset().  bits must be less than or equal to 16, and that many of the
   least significant bits of value will be inserted in the input.

     If bits is negative, then the input stream bit buffer is emptied.  Then
   inflatePrime() can be called again to put bits in the buffer.  This is used
   to clear out bits leftover after feeding inflate a block description prior
   to feeding inflate codes.

     inflatePrime returns Z_OK if success, or Z_STREAM_ERROR if the source
   stream state was inconsistent.
*/

ZEXTERN long ZEXPORT inflateMark OF((z_streamp strm));
/*
     This function returns two values, one in the lower 16 bits of the return
   value, and the other in the remaining upper bits, obtained by shifting the
   return value down 16 bits.  If the upper value is -1 and the lower value is
   zero, then inflate() is currently decoding information outside of a block.
   If the upper value is -1 and the lower value is non-zero, then inflate is in
   the middle of a stored block, with the lower value equaling the number of
   bytes from the input remaining to copy.  If the upper value is not -1, then
   it is the number of bits back from the current bit position in the input of
   the code (literal or length/distance pair) currently being processed.  In
   that case the lower value is the number of bytes already emitted for that
   code.

     A code is being processed if inflate is waiting for more input to complete
   decoding of the code, or if it has completed decoding but is waiting for
   more output space to write the literal or match data.

     inflateMark() is used to mark locations in the input data for random
   access, which may be at bit positions, and to note those cases where the
   output of a code may span boundaries of random access blocks.  The current
   location in the input stream can be determined from avail_in and data_type
   as noted in the description for the Z_BLOCK flush parameter for inflate.

     inflateMark returns the value noted above, or -65536 if the provided
   source stream state was inconsistent.
*/

ZEXTERN int ZEXPORT inflateGetHeader OF((z_streamp strm,
                                         gz_headerp head));
/*
     inflateGetHeader() requests that gzip header information be stored in the
   provided gz_header structure.  inflateGetHeader() may be called after
   inflateInit2() or inflateReset(), and before the first call of inflate().
   As inflate() processes the gzip stream, head->done is zero until the header
   is completed, at which time head->done is set to one.  If a zlib stream is
   being decoded, then head->done is set to -1 to indicate that there will be
   no gzip header information forthcoming.  Note that Z_BLOCK or Z_TREES can be
   used to force inflate() to return immediately after header processing is
   complete and before any actual data is decompressed.

     The text, time, xflags, and os fields are filled in with the gzip header
   contents.  hcrc is set to true if there is a header CRC.  (The header CRC
   was valid if done is set to one.) If extra is not Z_NULL, then extra_max
   contains the maximum number of bytes to write to extra.  Once done is true,
   extra_len contains the actual extra field length, and extra contains the
   extra field, or that field truncated if extra_max is less than extra_len.
   If name is not Z_NULL, then up to name_max characters are written there,
   terminated with a zero unless the length is greater than name_max.  If
   comment is not Z_NULL, then up to comm_max characters are written there,
   terminated with a zero unless the length is greater than comm_max.  When any
   of extra, name, or comment are not Z_NULL and the respective field is not
   present in the header, then that field is set to Z_NULL to signal its
   absence.  This allows the use of deflateSetHeader() with the returned
   structure to duplicate the header.  However if those fields are set to
   allocated memory, then the application will need to save those pointers
   elsewhere so that they can be eventually freed.

     If inflateGetHeader is not used, then the header information is simply
   discarded.  The header is always checked for validity, including the header
   CRC if present.  inflateReset() will reset the process to discard the header
   information.  The application would need to call inflateGetHeader() again to
   retrieve the header from the next gzip stream.

     inflateGetHeader returns Z_OK if success, or Z_STREAM_ERROR if the source
   stream state was inconsistent.
*/

/*
ZEXTERN int ZEXPORT inflateBackInit OF((z_streamp strm, int windowBits,
                                        unsigned char FAR *window));

     Initialize the internal stream state for decompression using inflateBack()
   calls.  The fields zalloc, zfree and opaque in strm must be initialized
   before the call.  If zalloc and zfree are Z_NULL, then the default library-
   derived memory allocation routines are used.  windowBits is the base two
   logarithm of the window size, in the range 8..15.  window is a caller
   supplied buffer of that size.  Except for special applications where it is
   assured that deflate was used with small window sizes, windowBits must be 15
   and a 32K byte window must be supplied to be able to decompress general
   deflate streams.

     See inflateBack() for the usage of these routines.

     inflateBackInit will return Z_OK on success, Z_STREAM_ERROR if any of
   the parameters are invalid, Z_MEM_ERROR if the internal state could not be
   allocated, or Z_VERSION_ERROR if the version of the library does not match
   the version of the header file.
*/

typedef unsigned (*in_func) OF((void FAR *,
                                z_const unsigned char FAR * FAR *));
typedef int (*out_func) OF((void FAR *, unsigned char FAR *, unsigned));

ZEXTERN int ZEXPORT inflateBack OF((z_streamp strm,
                                    in_func in, void FAR *in_desc,
                                    out_func out, void FAR *out_desc));
/*
     inflateBack() does a raw inflate with a single call using a call-back
   interface for input and output.  This is potentially more efficient than
   inflate() for file i/o applications, in that it avoids copying between the
   output and the sliding window by simply making the window itself the output
   buffer.  inflate() can be faster on modern CPUs when used with large
   buffers.  inflateBack() trusts the application to not change the output
   buffer passed by the output function, at least until inflateBack() returns.

     inflateBackInit() must be called first to allocate the internal state
   and to initialize the state with the user-provided window buffer.
   inflateBack() may then be used multiple times to inflate a complete, raw
   deflate stream with each call.  inflateBackEnd() is then called to free the
   allocated state.

     A raw deflate stream is one with no zlib or gzip header or trailer.
   This routine would normally be used in a utility that reads zip or gzip
   files and writes out uncompressed files.  The utility would decode the
   header and process the trailer on its own, hence this routine expects only
   the raw deflate stream to decompress.  This is different from the default
   behavior of inflate(), which expects a zlib header and trailer around the
   deflate stream.

     inflateBack() uses two subroutines supplied by the caller that are then
   called by inflateBack() for input and output.  inflateBack() calls those
   routines until it reads a complete deflate stream and writes out all of the
   uncompressed data, or until it encounters an error.  The function's
   parameters and return types are defined above in the in_func and out_func
   typedefs.  inflateBack() will call in(in_desc, &buf) which should return the
   number of bytes of provided input, and a pointer to that input in buf.  If
   there is no input available, in() must return zero -- buf is ignored in that
   case -- and inflateBack() will return a buffer error.  inflateBack() will
   call out(out_desc, buf, len) to write the uncompressed data buf[0..len-1].
   out() should return zero on success, or non-zero on failure.  If out()
   returns non-zero, inflateBack() will return with an error.  Neither in() nor
   out() are permitted to change the contents of the window provided to
   inflateBackInit(), which is also the buffer that out() uses to write from.
   The length written by out() will be at most the window size.  Any non-zero
   amount of input may be provided by in().

     For convenience, inflateBack() can be provided input on the first call by
   setting strm->next_in and strm->avail_in.  If that input is exhausted, then
   in() will be called.  Therefore strm->next_in must be initialized before
   calling inflateBack().  If strm->next_in is Z_NULL, then in() will be called
   immediately for input.  If strm->next_in is not Z_NULL, then strm->avail_in
   must also be initialized, and then if strm->avail_in is not zero, input will
   initially be taken from strm->next_in[0 ..  strm->avail_in - 1].

     The in_desc and out_desc parameters of inflateBack() is passed as the
   first parameter of in() and out() respectively when they are called.  These
   descriptors can be optionally used to pass any information that the caller-
   supplied in() and out() functions need to do their job.

     On return, inflateBack() will set strm->next_in and strm->avail_in to
   pass back any unused input that was provided by the last in() call.  The
   return values of inflateBack() can be Z_STREAM_END on success, Z_BUF_ERROR
   if in() or out() returned an error, Z_DATA_ERROR if there was a format error
   in the deflate stream (in which case strm->msg is set to indicate the nature
   of the error), or Z_STREAM_ERROR if the stream was not properly initialized.
   In the case of Z_BUF_ERROR, an input or output error can be distinguished
   using strm->next_in which will be Z_NULL only if in() returned an error.  If
   strm->next_in is not Z_NULL, then the Z_BUF_ERROR was due to out() returning
   non-zero.  (in() will always be called before out(), so strm->next_in is
   assured to be defined if out() returns non-zero.)  Note that inflateBack()
   cannot return Z_OK.
*/

ZEXTERN int ZEXPORT inflateBackEnd OF((z_streamp strm));
/*
     All memory allocated by inflateBackInit() is freed.

     inflateBackEnd() returns Z_OK on success, or Z_STREAM_ERROR if the stream
   state was inconsistent.
*/

ZEXTERN uLong ZEXPORT zlibCompileFlags OF((void));
/* Return flags indicating compile-time options.

    Type sizes, two bits each, 00 = 16 bits, 01 = 32, 10 = 64, 11 = other:
     1.0: size of uInt
     3.2: size of uLong
     5.4: size of voidpf (pointer)
     7.6: size of z_off_t

    Compiler, assembler, and debug options:
     8: ZLIB_DEBUG
     9: ASMV or ASMINF -- use ASM code
     10: ZLIB_WINAPI -- exported functions use the WINAPI calling convention
     11: 0 (reserved)

    One-time table building (smaller code, but not thread-safe if true):
     12: BUILDFIXED -- build static block decoding tables when needed
     13: DYNAMIC_CRC_TABLE -- build CRC calculation tables when needed
     14,15: 0 (reserved)

    Library content (indicates missing functionality):
     16: NO_GZCOMPRESS -- gz* functions cannot compress (to avoid linking
                          deflate code when not needed)
     17: NO_GZIP -- deflate can't write gzip streams, and inflate can't detect
                    and decode gzip streams (to avoid linking crc code)
     18-19: 0 (reserved)

    Operation variations (changes in library functionality):
     20: PKZIP_BUG_WORKAROUND -- slightly more permissive inflate
     21: FASTEST -- deflate algorithm with only one, lowest compression level
     22,23: 0 (reserved)

    The sprintf variant used by gzprintf (zero is best):
     24: 0 = vs*, 1 = s* -- 1 means limited to 20 arguments after the format
     25: 0 = *nprintf, 1 = *printf -- 1 means gzprintf() not secure!
     26: 0 = returns value, 1 = void -- 1 means inferred string length returned

    Remainder:
     27-31: 0 (reserved)
 */

#ifndef Z_SOLO

                        /* utility functions */

/*
     The following utility functions are implemented on top of the basic
   stream-oriented functions.  To simplify the interface, some default options
   are assumed (compression level and memory usage, standard memory allocation
   functions).  The source code of these utility functions can be modified if
   you need special options.
*/

ZEXTERN int ZEXPORT compress OF((Bytef *dest,   uLongf *destLen,
                                 const Bytef *source, uLong sourceLen));
/*
     Compresses the source buffer into the destination buffer.  sourceLen is
   the byte length of the source buffer.  Upon entry, destLen is the total size
   of the destination buffer, which must be at least the value returned by
   compressBound(sourceLen).  Upon exit, destLen is the actual size of the
   compressed data.  compress() is equivalent to compress2() with a level
   parameter of Z_DEFAULT_COMPRESSION.

     compress returns Z_OK if success, Z_MEM_ERROR if there was not
   enough memory, Z_BUF_ERROR if there was not enough room in the output
   buffer.
*/

ZEXTERN int ZEXPORT compress2 OF((Bytef *dest,   uLongf *destLen,
                                  const Bytef *source, uLong sourceLen,
                                  int level));
/*
     Compresses the source buffer into the destination buffer.  The level
   parameter has the same meaning as in deflateInit.  sourceLen is the byte
   length of the source buffer.  Upon entry, destLen is the total size of the
   destination buffer, which must be at least the value returned by
   compressBound(sourceLen).  Upon exit, destLen is the actual size of the
   compressed data.

     compress2 returns Z_OK if success, Z_MEM_ERROR if there was not enough
   memory, Z_BUF_ERROR if there was not enough room in the output buffer,
   Z_STREAM_ERROR if the level parameter is invalid.
*/

ZEXTERN uLong ZEXPORT compressBound OF((uLong sourceLen));
/*
     compressBound() returns an upper bound on the compressed size after
   compress() or compress2() on sourceLen bytes.  It would be used before a
   compress() or compress2() call to allocate the destination buffer.
*/

ZEXTERN int ZEXPORT uncompress OF((Bytef *dest,   uLongf *destLen,
                                   const Bytef *source, uLong sourceLen));
/*
     Decompresses the source buffer into the destination buffer.  sourceLen is
   the byte length of the source buffer.  Upon entry, destLen is the total size
   of the destination buffer, which must be large enough to hold the entire
   uncompressed data.  (The size of the uncompressed data must have been saved
   previously by the compressor and transmitted to the decompressor by some
   mechanism outside the scope of this compression library.) Upon exit, destLen
   is the actual size of the uncompressed data.

     uncompress returns Z_OK if success, Z_MEM_ERROR if there was not
   enough memory, Z_BUF_ERROR if there was not enough room in the output
   buffer, or Z_DATA_ERROR if the input data was corrupted or incomplete.  In
   the case where there is not enough room, uncompress() will fill the output
   buffer with the uncompressed data up to that point.
*/

ZEXTERN int ZEXPORT uncompress2 OF((Bytef *dest,   uLongf *destLen,
                                    const Bytef *source, uLong *sourceLen));
/*
     Same as uncompress, except that sourceLen is a pointer, where the
   length of the source is *sourceLen.  On return, *sourceLen is the number of
   source bytes consumed.
*/

                        /* gzip file access functions */

/*
     This library supports reading and writing files in gzip (.gz) format with
   an interface similar to that of stdio, using the functions that start with
   "gz".  The gzip format is different from the zlib format.  gzip is a gzip
   wrapper, documented in RFC 1952, wrapped around a deflate stream.
*/

typedef struct gzFile_s *gzFile;    /* semi-opaque gzip file descriptor */

/*
ZEXTERN gzFile ZEXPORT gzopen OF((const char *path, const char *mode));

     Opens a gzip (.gz) file for reading or writing.  The mode parameter is as
   in fopen ("rb" or "wb") but can also include a compression level ("wb9") or
   a strategy: 'f' for filtered data as in "wb6f", 'h' for Huffman-only
   compression as in "wb1h", 'R' for run-length encoding as in "wb1R", or 'F'
   for fixed code compression as in "wb9F".  (See the description of
   deflateInit2 for more information about the strategy parameter.)  'T' will
   request transparent writing or appending with no compression and not using
   the gzip format.

     "a" can be used instead of "w" to request that the gzip stream that will
   be written be appended to the file.  "+" will result in an error, since
   reading and writing to the same gzip file is not supported.  The addition of
   "x" when writing will create the file exclusively, which fails if the file
   already exists.  On systems that support it, the addition of "e" when
   reading or writing will set the flag to close the file on an execve() call.

     These functions, as well as gzip, will read and decode a sequence of gzip
   streams in a file.  The append function of gzopen() can be used to create
   such a file.  (Also see gzflush() for another way to do this.)  When
   appending, gzopen does not test whether the file begins with a gzip stream,
   nor does it look for the end of the gzip streams to begin appending.  gzopen
   will simply append a gzip stream to the existing file.

     gzopen can be used to read a file which is not in gzip format; in this
   case gzread will directly read from the file without decompression.  When
   reading, this will be detected automatically by looking for the magic two-
   byte gzip header.

     gzopen returns NULL if the file could not be opened, if there was
   insufficient memory to allocate the gzFile state, or if an invalid mode was
   specified (an 'r', 'w', or 'a' was not provided, or '+' was provided).
   errno can be checked to determine if the reason gzopen failed was that the
   file could not be opened.
*/

ZEXTERN gzFile ZEXPORT gzdopen OF((int fd, const char *mode));
/*
     gzdopen associates a gzFile with the file descriptor fd.  File descriptors
   are obtained from calls like open, dup, creat, pipe or fileno (if the file
   has been previously opened with fopen).  The mode parameter is as in gzopen.

     The next call of gzclose on the returned gzFile will also close the file
   descriptor fd, just like fclose(fdopen(fd, mode)) closes the file descriptor
   fd.  If you want to keep fd open, use fd = dup(fd_keep); gz = gzdopen(fd,
   mode);.  The duplicated descriptor should be saved to avoid a leak, since
   gzdopen does not close fd if it fails.  If you are using fileno() to get the
   file descriptor from a FILE *, then you will have to use dup() to avoid
   double-close()ing the file descriptor.  Both gzclose() and fclose() will
   close the associated file descriptor, so they need to have different file
   descriptors.

     gzdopen returns NULL if there was insufficient memory to allocate the
   gzFile state, if an invalid mode was specified (an 'r', 'w', or 'a' was not
   provided, or '+' was provided), or if fd is -1.  The file descriptor is not
   used until the next gz* read, write, seek, or close operation, so gzdopen
   will not detect if fd is invalid (unless fd is -1).
*/

ZEXTERN int ZEXPORT gzbuffer OF((gzFile file, unsigned size));
/*
     Set the internal buffer size used by this library's functions.  The
   default buffer size is 8192 bytes.  This function must be called after
   gzopen() or gzdopen(), and before any other calls that read or write the
   file.  The buffer memory allocation is always deferred to the first read or
   write.  Three times that size in buffer space is allocated.  A larger buffer
   size of, for example, 64K or 128K bytes will noticeably increase the speed
   of decompression (reading).

     The new buffer size also affects the maximum length for gzprintf().

     gzbuffer() returns 0 on success, or -1 on failure, such as being called
   too late.
*/

ZEXTERN int ZEXPORT gzsetparams OF((gzFile file, int level, int strategy));
/*
     Dynamically update the compression level or strategy.  See the description
   of deflateInit2 for the meaning of these parameters.  Previously provided
   data is flushed before the parameter change.

     gzsetparams returns Z_OK if success, Z_STREAM_ERROR if the file was not
   opened for writing, Z_ERRNO if there is an error writing the flushed data,
   or Z_MEM_ERROR if there is a memory allocation error.
*/

ZEXTERN int ZEXPORT gzread OF((gzFile file, voidp buf, unsigned len));
/*
     Reads the given number of uncompressed bytes from the compressed file.  If
   the input file is not in gzip format, gzread copies the given number of
   bytes into the buffer directly from the file.

     After reaching the end of a gzip stream in the input, gzread will continue
   to read, looking for another gzip stream.  Any number of gzip streams may be
   concatenated in the input file, and will all be decompressed by gzread().
   If something other than a gzip stream is encountered after a gzip stream,
   that remaining trailing garbage is ignored (and no error is returned).

     gzread can be used to read a gzip file that is being concurrently written.
   Upon reaching the end of the input, gzread will return with the available
   data.  If the error code returned by gzerror is Z_OK or Z_BUF_ERROR, then
   gzclearerr can be used to clear the end of file indicator in order to permit
   gzread to be tried again.  Z_OK indicates that a gzip stream was completed
   on the last gzread.  Z_BUF_ERROR indicates that the input file ended in the
   middle of a gzip stream.  Note that gzread does not return -1 in the event
   of an incomplete gzip stream.  This error is deferred until gzclose(), which
   will return Z_BUF_ERROR if the last gzread ended in the middle of a gzip
   stream.  Alternatively, gzerror can be used before gzclose to detect this
   case.

     gzread returns the number of uncompressed bytes actually read, less than
   len for end of file, or -1 for error.  If len is too large to fit in an int,
   then nothing is read, -1 is returned, and the error state is set to
   Z_STREAM_ERROR.
*/

ZEXTERN z_size_t ZEXPORT gzfread OF((voidp buf, z_size_t size, z_size_t nitems,
                                     gzFile file));
/*
     Read up to nitems items of size size from file to buf, otherwise operating
   as gzread() does.  This duplicates the interface of stdio's fread(), with
   size_t request and return types.  If the library defines size_t, then
   z_size_t is identical to size_t.  If not, then z_size_t is an unsigned
   integer type that can contain a pointer.

     gzfread() returns the number of full items read of size size, or zero if
   the end of the file was reached and a full item could not be read, or if
   there was an error.  gzerror() must be consulted if zero is returned in
   order to determine if there was an error.  If the multiplication of size and
   nitems overflows, i.e. the product does not fit in a z_size_t, then nothing
   is read, zero is returned, and the error state is set to Z_STREAM_ERROR.

     In the event that the end of file is reached and only a partial item is
   available at the end, i.e. the remaining uncompressed data length is not a
   multiple of size, then the final partial item is nevetheless read into buf
   and the end-of-file flag is set.  The length of the partial item read is not
   provided, but could be inferred from the result of gztell().  This behavior
   is the same as the behavior of fread() implementations in common libraries,
   but it prevents the direct use of gzfread() to read a concurrently written
   file, reseting and retrying on end-of-file, when size is not 1.
*/

ZEXTERN int ZEXPORT gzwrite OF((gzFile file,
                                voidpc buf, unsigned len));
/*
     Writes the given number of uncompressed bytes into the compressed file.
   gzwrite returns the number of uncompressed bytes written or 0 in case of
   error.
*/

ZEXTERN z_size_t ZEXPORT gzfwrite OF((voidpc buf, z_size_t size,
                                      z_size_t nitems, gzFile file));
/*
     gzfwrite() writes nitems items of size size from buf to file, duplicating
   the interface of stdio's fwrite(), with size_t request and return types.  If
   the library defines size_t, then z_size_t is identical to size_t.  If not,
   then z_size_t is an unsigned integer type that can contain a pointer.

     gzfwrite() returns the number of full items written of size size, or zero
   if there was an error.  If the multiplication of size and nitems overflows,
   i.e. the product does not fit in a z_size_t, then nothing is written, zero
   is returned, and the error state is set to Z_STREAM_ERROR.
*/

ZEXTERN int ZEXPORTVA gzprintf Z_ARG((gzFile file, const char *format, ...));
/*
     Converts, formats, and writes the arguments to the compressed file under
   control of the format string, as in fprintf.  gzprintf returns the number of
   uncompressed bytes actually written, or a negative zlib error code in case
   of error.  The number of uncompressed bytes written is limited to 8191, or
   one less than the buffer size given to gzbuffer().  The caller should assure
   that this limit is not exceeded.  If it is exceeded, then gzprintf() will
   return an error (0) with nothing written.  In this case, there may also be a
   buffer overflow with unpredictable consequences, which is possible only if
   zlib was compiled with the insecure functions sprintf() or vsprintf()
   because the secure snprintf() or vsnprintf() functions were not available.
   This can be determined using zlibCompileFlags().
*/

ZEXTERN int ZEXPORT gzputs OF((gzFile file, const char *s));
/*
     Writes the given null-terminated string to the compressed file, excluding
   the terminating null character.

     gzputs returns the number of characters written, or -1 in case of error.
*/

ZEXTERN char * ZEXPORT gzgets OF((gzFile file, char *buf, int len));
/*
     Reads bytes from the compressed file until len-1 characters are read, or a
   newline character is read and transferred to buf, or an end-of-file
   condition is encountered.  If any characters are read or if len == 1, the
   string is terminated with a null character.  If no characters are read due
   to an end-of-file or len < 1, then the buffer is left untouched.

     gzgets returns buf which is a null-terminated string, or it returns NULL
   for end-of-file or in case of error.  If there was an error, the contents at
   buf are indeterminate.
*/

ZEXTERN int ZEXPORT gzputc OF((gzFile file, int c));
/*
     Writes c, converted to an unsigned char, into the compressed file.  gzputc
   returns the value that was written, or -1 in case of error.
*/

ZEXTERN int ZEXPORT gzgetc OF((gzFile file));
/*
     Reads one byte from the compressed file.  gzgetc returns this byte or -1
   in case of end of file or error.  This is implemented as a macro for speed.
   As such, it does not do all of the checking the other functions do.  I.e.
   it does not check to see if file is NULL, nor whether the structure file
   points to has been clobbered or not.
*/

ZEXTERN int ZEXPORT gzungetc OF((int c, gzFile file));
/*
     Push one character back onto the stream to be read as the first character
   on the next read.  At least one character of push-back is allowed.
   gzungetc() returns the character pushed, or -1 on failure.  gzungetc() will
   fail if c is -1, and may fail if a character has been pushed but not read
   yet.  If gzungetc is used immediately after gzopen or gzdopen, at least the
   output buffer size of pushed characters is allowed.  (See gzbuffer above.)
   The pushed character will be discarded if the stream is repositioned with
   gzseek() or gzrewind().
*/

ZEXTERN int ZEXPORT gzflush OF((gzFile file, int flush));
/*
     Flushes all pending output into the compressed file.  The parameter flush
   is as in the deflate() function.  The return value is the zlib error number
   (see function gzerror below).  gzflush is only permitted when writing.

     If the flush parameter is Z_FINISH, the remaining data is written and the
   gzip stream is completed in the output.  If gzwrite() is called again, a new
   gzip stream will be started in the output.  gzread() is able to read such
   concatenated gzip streams.

     gzflush should be called only when strictly necessary because it will
   degrade compression if called too often.
*/

/*
ZEXTERN z_off_t ZEXPORT gzseek OF((gzFile file,
                                   z_off_t offset, int whence));

     Sets the starting position for the next gzread or gzwrite on the given
   compressed file.  The offset represents a number of bytes in the
   uncompressed data stream.  The whence parameter is defined as in lseek(2);
   the value SEEK_END is not supported.

     If the file is opened for reading, this function is emulated but can be
   extremely slow.  If the file is opened for writing, only forward seeks are
   supported; gzseek then compresses a sequence of zeroes up to the new
   starting position.

     gzseek returns the resulting offset location as measured in bytes from
   the beginning of the uncompressed stream, or -1 in case of error, in
   particular if the file is opened for writing and the new starting position
   would be before the current position.
*/

ZEXTERN int ZEXPORT    gzrewind OF((gzFile file));
/*
     Rewinds the given file. This function is supported only for reading.

     gzrewind(file) is equivalent to (int)gzseek(file, 0L, SEEK_SET)
*/

/*
ZEXTERN z_off_t ZEXPORT    gztell OF((gzFile file));

     Returns the starting position for the next gzread or gzwrite on the given
   compressed file.  This position represents a number of bytes in the
   uncompressed data stream, and is zero when starting, even if appending or
   reading a gzip stream from the middle of a file using gzdopen().

     gztell(file) is equivalent to gzseek(file, 0L, SEEK_CUR)
*/

/*
ZEXTERN z_off_t ZEXPORT gzoffset OF((gzFile file));

     Returns the current offset in the file being read or written.  This offset
   includes the count of bytes that precede the gzip stream, for example when
   appending or when using gzdopen() for reading.  When reading, the offset
   does not include as yet unused buffered input.  This information can be used
   for a progress indicator.  On error, gzoffset() returns -1.
*/

ZEXTERN int ZEXPORT gzeof OF((gzFile file));
/*
     Returns true (1) if the end-of-file indicator has been set while reading,
   false (0) otherwise.  Note that the end-of-file indicator is set only if the
   read tried to go past the end of the input, but came up short.  Therefore,
   just like feof(), gzeof() may return false even if there is no more data to
   read, in the event that the last read request was for the exact number of
   bytes remaining in the input file.  This will happen if the input file size
   is an exact multiple of the buffer size.

     If gzeof() returns true, then the read functions will return no more data,
   unless the end-of-file indicator is reset by gzclearerr() and the input file
   has grown since the previous end of file was detected.
*/

ZEXTERN int ZEXPORT gzdirect OF((gzFile file));
/*
     Returns true (1) if file is being copied directly while reading, or false
   (0) if file is a gzip stream being decompressed.

     If the input file is empty, gzdirect() will return true, since the input
   does not contain a gzip stream.

     If gzdirect() is used immediately after gzopen() or gzdopen() it will
   cause buffers to be allocated to allow reading the file to determine if it
   is a gzip file.  Therefore if gzbuffer() is used, it should be called before
   gzdirect().

     When writing, gzdirect() returns true (1) if transparent writing was
   requested ("wT" for the gzopen() mode), or false (0) otherwise.  (Note:
   gzdirect() is not needed when writing.  Transparent writing must be
   explicitly requested, so the application already knows the answer.  When
   linking statically, using gzdirect() will include all of the zlib code for
   gzip file reading and decompression, which may not be desired.)
*/

ZEXTERN int ZEXPORT    gzclose OF((gzFile file));
/*
     Flushes all pending output if necessary, closes the compressed file and
   deallocates the (de)compression state.  Note that once file is closed, you
   cannot call gzerror with file, since its structures have been deallocated.
   gzclose must not be called more than once on the same file, just as free
   must not be called more than once on the same allocation.

     gzclose will return Z_STREAM_ERROR if file is not valid, Z_ERRNO on a
   file operation error, Z_MEM_ERROR if out of memory, Z_BUF_ERROR if the
   last read ended in the middle of a gzip stream, or Z_OK on success.
*/

ZEXTERN int ZEXPORT gzclose_r OF((gzFile file));
ZEXTERN int ZEXPORT gzclose_w OF((gzFile file));
/*
     Same as gzclose(), but gzclose_r() is only for use when reading, and
   gzclose_w() is only for use when writing or appending.  The advantage to
   using these instead of gzclose() is that they avoid linking in zlib
   compression or decompression code that is not used when only reading or only
   writing respectively.  If gzclose() is used, then both compression and
   decompression code will be included the application when linking to a static
   zlib library.
*/

ZEXTERN const char * ZEXPORT gzerror OF((gzFile file, int *errnum));
/*
     Returns the error message for the last error which occurred on the given
   compressed file.  errnum is set to zlib error number.  If an error occurred
   in the file system and not in the compression library, errnum is set to
   Z_ERRNO and the application may consult errno to get the exact error code.

     The application must not modify the returned string.  Future calls to
   this function may invalidate the previously returned string.  If file is
   closed, then the string previously returned by gzerror will no longer be
   available.

     gzerror() should be used to distinguish errors from end-of-file for those
   functions above that do not distinguish those cases in their return values.
*/

ZEXTERN void ZEXPORT gzclearerr OF((gzFile file));
/*
     Clears the error and end-of-file flags for file.  This is analogous to the
   clearerr() function in stdio.  This is useful for continuing to read a gzip
   file that is being written concurrently.
*/

#endif /* !Z_SOLO */

                        /* checksum functions */

/*
     These functions are not related to compression but are exported
   anyway because they might be useful in applications using the compression
   library.
*/

ZEXTERN uLong ZEXPORT adler32 OF((uLong adler, const Bytef *buf, uInt len));
/*
     Update a running Adler-32 checksum with the bytes buf[0..len-1] and
   return the updated checksum.  If buf is Z_NULL, this function returns the
   required initial value for the checksum.

     An Adler-32 checksum is almost as reliable as a CRC-32 but can be computed
   much faster.

   Usage example:

     uLong adler = adler32(0L, Z_NULL, 0);

     while (read_buffer(buffer, length) != EOF) {
       adler = adler32(adler, buffer, length);
     }
     if (adler != original_adler) error();
*/

ZEXTERN uLong ZEXPORT adler32_z OF((uLong adler, const Bytef *buf,
                                    z_size_t len));
/*
     Same as adler32(), but with a size_t length.
*/

/*
ZEXTERN uLong ZEXPORT adler32_combine OF((uLong adler1, uLong adler2,
                                          z_off_t len2));

     Combine two Adler-32 checksums into one.  For two sequences of bytes, seq1
   and seq2 with lengths len1 and len2, Adler-32 checksums were calculated for
   each, adler1 and adler2.  adler32_combine() returns the Adler-32 checksum of
   seq1 and seq2 concatenated, requiring only adler1, adler2, and len2.  Note
   that the z_off_t type (like off_t) is a signed integer.  If len2 is
   negative, the result has no meaning or utility.
*/

ZEXTERN uLong ZEXPORT crc32   OF((uLong crc, const Bytef *buf, uInt len));
/*
     Update a running CRC-32 with the bytes buf[0..len-1] and return the
   updated CRC-32.  If buf is Z_NULL, this function returns the required
   initial value for the crc.  Pre- and post-conditioning (one's complement) is
   performed within this function so it shouldn't be done by the application.

   Usage example:

     uLong crc = crc32(0L, Z_NULL, 0);

     while (read_buffer(buffer, length) != EOF) {
       crc = crc32(crc, buffer, length);
     }
     if (crc != original_crc) error();
*/

ZEXTERN uLong ZEXPORT crc32_z OF((uLong adler, const Bytef *buf,
                                  z_size_t len));
/*
     Same as crc32(), but with a size_t length.
*/

/*
ZEXTERN uLong ZEXPORT crc32_combine OF((uLong crc1, uLong crc2, z_off_t len2));

     Combine two CRC-32 check values into one.  For two sequences of bytes,
   seq1 and seq2 with lengths len1 and len2, CRC-32 check values were
   calculated for each, crc1 and crc2.  crc32_combine() returns the CRC-32
   check value of seq1 and seq2 concatenated, requiring only crc1, crc2, and
   len2.
*/


                        /* various hacks, don't look :) */

/* deflateInit and inflateInit are macros to allow checking the zlib version
 * and the compiler's view of z_stream:
 */
ZEXTERN int ZEXPORT deflateInit_ OF((z_streamp strm, int level,
                                     const char *version, int stream_size));
ZEXTERN int ZEXPORT inflateInit_ OF((z_streamp strm,
                                     const char *version, int stream_size));
ZEXTERN int ZEXPORT deflateInit2_ OF((z_streamp strm, int  level, int  method,
                                      int windowBits, int memLevel,
                                      int strategy, const char *version,
                                      int stream_size));
ZEXTERN int ZEXPORT inflateInit2_ OF((z_streamp strm, int  windowBits,
                                      const char *version, int stream_size));
ZEXTERN int ZEXPORT inflateBackInit_ OF((z_streamp strm, int windowBits,
                                         unsigned char FAR *window,
                                         const char *version,
                                         int stream_size));
#ifdef Z_PREFIX_SET
#  define z_deflateInit(strm, level) \
          deflateInit_((strm), (level), ZLIB_VERSION, (int)sizeof(z_stream))
#  define z_inflateInit(strm) \
          inflateInit_((strm), ZLIB_VERSION, (int)sizeof(z_stream))
#  define z_deflateInit2(strm, level, method, windowBits, memLevel, strategy) \
          deflateInit2_((strm),(level),(method),(windowBits),(memLevel),\
                        (strategy), ZLIB_VERSION, (int)sizeof(z_stream))
#  define z_inflateInit2(strm, windowBits) \
          inflateInit2_((strm), (windowBits), ZLIB_VERSION, \
                        (int)sizeof(z_stream))
#  define z_inflateBackInit(strm, windowBits, window) \
          inflateBackInit_((strm), (windowBits), (window), \
                           ZLIB_VERSION, (int)sizeof(z_stream))
#else
#  define deflateInit(strm, level) \
          deflateInit_((strm), (level), ZLIB_VERSION, (int)sizeof(z_stream))
#  define inflateInit(strm) \
          inflateInit_((strm), ZLIB_VERSION, (int)sizeof(z_stream))
#  define deflateInit2(strm, level, method, windowBits, memLevel, strategy) \
          deflateInit2_((strm),(level),(method),(windowBits),(memLevel),\
                        (strategy), ZLIB_VERSION, (int)sizeof(z_stream))
#  define inflateInit2(strm, windowBits) \
          inflateInit2_((strm), (windowBits), ZLIB_VERSION, \
                        (int)sizeof(z_stream))
#  define inflateBackInit(strm, windowBits, window) \
          inflateBackInit_((strm), (windowBits), (window), \
                           ZLIB_VERSION, (int)sizeof(z_stream))
#endif

#ifndef Z_SOLO

/* gzgetc() macro and its supporting function and exposed data structure.  Note
 * that the real internal state is much larger than the exposed structure.
 * This abbreviated structure exposes just enough for the gzgetc() macro.  The
 * user should not mess with these exposed elements, since their names or
 * behavior could change in the future, perhaps even capriciously.  They can
 * only be used by the gzgetc() macro.  You have been warned.
 */
struct gzFile_s {
    unsigned have;
    unsigned char *next;
    z_off64_t pos;
};
ZEXTERN int ZEXPORT gzgetc_ OF((gzFile file));  /* backward compatibility */
#ifdef Z_PREFIX_SET
#  undef z_gzgetc
#  define z_gzgetc(g) \
          ((g)->have ? ((g)->have--, (g)->pos++, *((g)->next)++) : (gzgetc)(g))
#else
#  define gzgetc(g) \
          ((g)->have ? ((g)->have--, (g)->pos++, *((g)->next)++) : (gzgetc)(g))
#endif

/* provide 64-bit offset functions if _LARGEFILE64_SOURCE defined, and/or
 * change the regular functions to 64 bits if _FILE_OFFSET_BITS is 64 (if
 * both are true, the application gets the *64 functions, and the regular
 * functions are changed to 64 bits) -- in case these are set on systems
 * without large file support, _LFS64_LARGEFILE must also be true
 */
#ifdef Z_LARGE64
   ZEXTERN gzFile ZEXPORT gzopen64 OF((const char *, const char *));
   ZEXTERN z_off64_t ZEXPORT gzseek64 OF((gzFile, z_off64_t, int));
   ZEXTERN z_off64_t ZEXPORT gztell64 OF((gzFile));
   ZEXTERN z_off64_t ZEXPORT gzoffset64 OF((gzFile));
   ZEXTERN uLong ZEXPORT adler32_combine64 OF((uLong, uLong, z_off64_t));
   ZEXTERN uLong ZEXPORT crc32_combine64 OF((uLong, uLong, z_off64_t));
#endif

#if !defined(ZLIB_INTERNAL) && defined(Z_WANT64)
#  ifdef Z_PREFIX_SET
#    define z_gzopen z_gzopen64
#    define z_gzseek z_gzseek64
#    define z_gztell z_gztell64
#    define z_gzoffset z_gzoffset64
#    define z_adler32_combine z_adler32_combine64
#    define z_crc32_combine z_crc32_combine64
#  else
#    define gzopen gzopen64
#    define gzseek gzseek64
#    define gztell gztell64
#    define gzoffset gzoffset64
#    define adler32_combine adler32_combine64
#    define crc32_combine crc32_combine64
#  endif
#  ifndef Z_LARGE64
     ZEXTERN gzFile ZEXPORT gzopen64 OF((const char *, const char *));
     ZEXTERN z_off_t ZEXPORT gzseek64 OF((gzFile, z_off_t, int));
     ZEXTERN z_off_t ZEXPORT gztell64 OF((gzFile));
     ZEXTERN z_off_t ZEXPORT gzoffset64 OF((gzFile));
     ZEXTERN uLong ZEXPORT adler32_combine64 OF((uLong, uLong, z_off_t));
     ZEXTERN uLong ZEXPORT crc32_combine64 OF((uLong, uLong, z_off_t));
#  endif
#else
   ZEXTERN gzFile ZEXPORT gzopen OF((const char *, const char *));
   ZEXTERN z_off_t ZEXPORT gzseek OF((gzFile, z_off_t, int));
   ZEXTERN z_off_t ZEXPORT gztell OF((gzFile));
   ZEXTERN z_off_t ZEXPORT gzoffset OF((gzFile));
   ZEXTERN uLong ZEXPORT adler32_combine OF((uLong, uLong, z_off_t));
   ZEXTERN uLong ZEXPORT crc32_combine OF((uLong, uLong, z_off_t));
#endif

#else /* Z_SOLO */

   ZEXTERN uLong ZEXPORT adler32_combine OF((uLong, uLong, z_off_t));
   ZEXTERN uLong ZEXPORT crc32_combine OF((uLong, uLong, z_off_t));

#endif /* !Z_SOLO */

/* undocumented functions */
ZEXTERN const char   * ZEXPORT zError           OF((int));
ZEXTERN int            ZEXPORT inflateSyncPoint OF((z_streamp));
ZEXTERN const z_crc_t FAR * ZEXPORT get_crc_table    OF((void));
ZEXTERN int            ZEXPORT inflateUndermine OF((z_streamp, int));
ZEXTERN int            ZEXPORT inflateValidate OF((z_streamp, int));
ZEXTERN unsigned long  ZEXPORT inflateCodesUsed OF ((z_streamp));
ZEXTERN int            ZEXPORT inflateResetKeep OF((z_streamp));
ZEXTERN int            ZEXPORT deflateResetKeep OF((z_streamp));
#if (defined(_WIN32) || defined(__CYGWIN__)) && !defined(Z_SOLO)
ZEXTERN gzFile         ZEXPORT gzopen_w OF((const wchar_t *path,
                                            const char *mode));
#endif
#if defined(STDC) || defined(Z_HAVE_STDARG_H)
#  ifndef Z_SOLO
ZEXTERN int            ZEXPORTVA gzvprintf Z_ARG((gzFile file,
                                                  const char *format,
                                                  va_list va));
#  endif
#endif

#ifdef __cplusplus
}
#endif

#endif /* ZLIB_H */

"ni">&amp;I)</string>
    <string lang="zh-cn" key="EXTRACT">释放(&amp;X)</string>
    <string lang="zh-cn" key="NODRIVER">不能连接到 VeraCrypt 设备驱动。如果设备驱动不能运行则 VeraCrypt 也无法正常工作。\n\n请注意，由于 Windows 系统问题，在能够正常加载设备驱动前可能需要注销或者重启计算机。</string>
    <string lang="zh-cn" key="NOFONT">加载/准备字体时出错。</string>
    <string lang="zh-cn" key="NOT_FOUND">驱动器盘符未发现或没有指定驱动器盘符。</string>
    <string lang="zh-cn" key="DRIVE_LETTER_UNAVAILABLE">驱动器盘符不可用。</string>
    <string lang="zh-cn" key="NO_FILE_SELECTED">未选定文件！</string>
    <string lang="zh-cn" key="NO_FREE_DRIVES">无可用驱动器盘符。</string>
    <string lang="zh-cn" key="NO_FREE_DRIVE_FOR_OUTER_VOL">外层加密卷无可用盘符！ 加密卷创建不能进行。</string>
    <string lang="zh-cn" key="NO_OS_VER">无法检测操作系统版本号，或您正在使用不被支持的操作系统。</string>
    <string lang="zh-cn" key="NO_PATH_SELECTED">未选定路径！</string>
    <string lang="zh-cn" key="NO_SPACE_FOR_HIDDEN_VOL">创建隐藏加密卷的自由空间不足！ 加密卷创建不能继续。</string>
    <string lang="zh-cn" key="HIDDEN_VOLUME_TOO_SMALL_FOR_OS_CLONE">错误：您复制到外层加密卷的文件占用的空间过多。因此，没有足够的空间创建隐藏加密卷。\n\n注意，隐藏加密卷的容量至少要大于系统分区（当前运行的系统所在的分区）的容量。原因是隐形操作系统需要把系统分区的内容完全复制到隐藏加密卷来创建。\n\n\n创建隐形操作系统的过程无法再继续。</string>
    <string lang="zh-cn" key="OPENFILES_DRIVER">此驱动无法卸载这个加密卷。位于此加密卷上某些文件可能仍被打开。</string>
    <string lang="zh-cn" key="OPENFILES_LOCK">无法锁定此加密卷。此加密卷上仍有些文件被打开。因而也无法卸载。</string>
    <string lang="zh-cn" key="VOL_LOCK_FAILED_OFFER_FORCED_DISMOUNT">VeraCrypt 不能锁定该加密卷，这是因为此加密卷正在被操作系统或者其它程序占用（例如加密卷中有文件被打开）。\n\n您确认要强制卸载加密卷吗？</string>
    <string lang="zh-cn" key="OPEN_VOL_TITLE">请选择一个 VeraCrypt 加密卷</string>
    <string lang="zh-cn" key="OPEN_TITLE">指定路径和文件名</string>
    <string lang="zh-cn" key="SELECT_PKCS11_MODULE">选择 PKCS #11 运行库</string>
    <string lang="zh-cn" key="OUTOFMEMORY">内存不足</string>
    <string lang="zh-cn" key="FORMAT_DEVICE_FOR_ADVANCED_ONLY">重要：我们强烈建议非熟练用户在选定的分区/设备里面建立文件类型的加密卷，而不是尝试加密整个分区/驱动器。\n\n例如，当您创建一个 VeraCrypt 文件类型加密卷时（相对于加密整个分区/驱动器），则不存在毁坏大量的文件的风险。请注意，一个 VeraCrypt 文件类型加密卷（尽管其包含虚拟的加密磁盘）事实上就象任意一个普通的文件一样。如若获取更多信息，请参考VeraCrypt User Guide中的 Beginner's Tutorial 章节。\n\n您确认要加密整个设备/分区吗？</string>
    <string lang="zh-cn" key="OVERWRITEPROMPT">警告：加密卷 '%hs' 已存在！\n\n重要：VeraCrypt 并不会加密这个文件，而是会删除这个文件。 您确定要删除这个文件并用一个新的 VeraCrypt 加密卷来替换它吗？</string>
    <string lang="zh-cn" key="OVERWRITEPROMPT_DEVICE">务必小心：当前存储在选择的 %s '%hs'%s 上的所有数据将会丢失（它们并不会被加密）！\n\n您一定要继续格式化吗？</string>
    <string lang="zh-cn" key="NONSYS_INPLACE_ENC_CONFIRM">警告：您在加密卷完全加密前不能加载此加密卷或者访问存储于该卷上的任何文件。\n\n您确认要开始加密选择的 %s '%hs'%s 吗？</string>
    <string lang="zh-cn" key="NONSYS_INPLACE_ENC_CONFIRM_BACKUP">警告：请注意如果在就地加密现有数据时突然断电，或者在 VeraCrypt 就地加密现有数据时由于软硬件故障而导致电脑死机，可能会损坏或丢失一些数据。因此，在您开始加密前，请确认您已经备份了要加密的数据。\n\n您确认已经有这样的备份了吗？</string>
    <string lang="zh-cn" key="OVERWRITEPROMPT_DEVICE_HIDDEN_OS_PARTITION">警告：任何存在于分区 '%hs'%s（即位于系统分区后面的第一个分区）的文件将会因被擦除而丢失。（这些文件并不会被加密）！\n\n您确认要继续格式化吗？</string>
    <string lang="zh-cn" key="OVERWRITEPROMPT_DEVICE_SECOND_WARNING_LOTS_OF_DATA">警告：选定的分区包含大量的数据！！！任何存储于此分区上的文件将会被擦除（他们并不会被加密）！</string>
    <string lang="zh-cn" key="ERASE_FILES_BY_CREATING_VOLUME">通过在分区内创建 VeraCrypt 加密卷擦除该分区上的任何文件</string>
    <string lang="zh-cn" key="PASSWORD">密码</string>
    <string lang="zh-cn" key="IDD_PCDM_CHANGE_PKCS5_PRF">设置首密钥衍生算法</string>
    <string lang="zh-cn" key="IDD_PCDM_ADD_REMOVE_VOL_KEYFILES">添加/移除 密钥文件..</string>
    <string lang="zh-cn" key="IDD_PCDM_REMOVE_ALL_KEYFILES_FROM_VOL">从加密卷中移除所有密钥文件</string>
    <string lang="zh-cn" key="PASSWORD_CHANGED">密码 和/或 密钥文件已成功修改。\n\n重要：请确认您已经阅读了用户指南的'Security Requirements and Precautions'章节中的'Changing Passwords and Keyfiles'部分。</string>
    <string lang="zh-cn" key="SYS_PASSWORD_CHANGED_ASK_RESCUE_DISK">重要：如果您不销毁 VeraCrypt 应急盘，您的系统分区/驱动器仍然可以通过使用旧密码解密（通过启动 VeraCrypt 应急盘和输入旧密码）。您应当创建一个新的 VeraCrypt 应急盘，之后并销毁原来的应急盘。\n\n您希望创建一个新的 VeraCrypt 应急盘吗？</string>
    <string lang="zh-cn" key="SYS_HKD_ALGO_CHANGED_ASK_RESCUE_DISK">请注意，VeraCrypt 应急盘仍然使用着早期的加密算法。如果您觉的先前的加密算法不安全，您应当创建一个新的 VeraCrypt 应急盘，之后并销毁原来的应急盘。\n\n您希望创建一个新的 VeraCrypt 应急盘吗？</string>
    <string lang="zh-cn" key="KEYFILES_NOTE">任何类型的文件（例如：.mp3、.jpg、.zip、.avi）都可以作为 VeraCrypt 的密钥文件。VeraCrypt 并不会修改密钥文件的内容。 您可以选择一个以上的密钥文件（与次序无关）。如果您添加了一个文件夹，里面的所有非隐藏文件都将作为密钥文件。点击〖添加口令牌〗来选择存储于安全口令牌或智能卡中的密钥文件（或者导入密钥文件到安全口令牌或智能卡）。</string>
    <string lang="zh-cn" key="KEYFILE_CHANGED">密钥文件已成功添加/移除。</string>
    <string lang="zh-cn" key="KEYFILE_EXPORTED">密钥文件已导出.</string>
    <string lang="zh-cn" key="PKCS5_PRF_CHANGED">首密钥衍生算法已成功设置。</string>
    <string lang="zh-cn" key="NONSYS_INPLACE_ENC_RESUME_PASSWORD_PAGE_HELP">请为您想要继续就地加密的非系统分区输入密码 和/或 密钥文件。\n\n\n注解：在您点击〖下一步〗之后，VeraCrypt 将尝试查找所有加密过程被中断的非系统分区（这些中断加密的分区的 VeraCrypt 头信息可以使用提供的密码 和/或 密钥文件解密）。如果发现了多个此类的分区，您需要在下个步骤里面选择他们其中的一个。</string>
    <string lang="zh-cn" key="NONSYS_INPLACE_ENC_RESUME_VOL_SELECT_HELP">请选择下面列表中的一个加密卷。此列表包含所有加密被中断的非系统加密卷，它们的头信息可以使用提供的密码 和/或 密钥文件解密。</string>
    <string lang="zh-cn" key="PASSWORD_HELP">选择一个安全的密码非常重要。您应该避免选取能够在字典中查到的简单词汇（或是2、3、4 这类字符组合）作为密码，也不应包含任何名字或生日，同时也不应该容易被猜到。安全的密码应当包含随机的大小写字母、数字、以及类似 @ ^ = $ * + 这样的特殊字符。我们推荐使用大于 20 个字符的密码（越长越好）。最大的密码长度为 64 个字符。</string>
    <string lang="zh-cn" key="PASSWORD_HIDDENVOL_HELP">请为隐藏加密卷选择一个密码。 </string>
    <string lang="zh-cn" key="PASSWORD_HIDDEN_OS_HELP">请为隐形操作系统设置一个密码（即隐藏加密卷的密码）。</string>
    <string lang="zh-cn" key="PASSWORD_HIDDEN_OS_NOTE">重要：您在本步骤中为隐形操作系统设置的密码必须绝对不同于其它的两个密码（也就是要不同于外层加密卷的密码和迷惑操作系统的密码）。</string>
    <string lang="zh-cn" key="PASSWORD_HIDDENVOL_HOST_DIRECT_HELP">请输入外层加密卷的密码（您将在该加密卷中创建隐藏加密卷）。\n\n在单击〖下一步〗后，VeraCrypt 会尝试加载此加密卷。一旦加密卷被加载，将进行簇状图扫描来确定连续的自由空间大小（如果有的话），此空间的尾部与加密卷尾部一致。该区域将提供给隐藏加密卷并因此会限制它的最大可能大小。簇状图扫描是必要的，这可以确保外层加密卷的数据不会被隐藏加密卷覆盖。</string>
    <string lang="zh-cn" key="PASSWORD_HIDDENVOL_HOST_HELP">\n请选择外层加密卷的密码。在您被攻击者强迫说出启动验证密码的情况下，这个密码可以告诉攻击者。\n\n重要：您为外层加密卷选择的密码必须不同于隐藏加密卷的密码。\n\n说明：密码的最大长度为 64 个字符。</string>
    <string lang="zh-cn" key="PASSWORD_SYSENC_OUTERVOL_HELP">请选择外层加密卷的密码。在您被攻击者强迫说出系统分区后面的第一个分区（外层加密卷和包含隐形操作系统的隐藏加密卷均位于这个分区）密码的情况下，这个密码可以告诉这些攻击者。而隐藏加密卷和隐形操作系统仍然是安全的。需要注意的是，外层加密卷的密码并不是迷惑操作系统的密码。\n\n重要：您为迷惑操作系统选择的密码必须不同于隐藏加密卷的密码（也就是隐形操作系统的密码）。</string>
    <string lang="zh-cn" key="PASSWORD_HIDVOL_HOST_TITLE">外层加密卷密码</string>
    <string lang="zh-cn" key="PASSWORD_HIDVOL_TITLE">隐藏加密卷密码</string>
    <string lang="zh-cn" key="PASSWORD_HIDDEN_OS_TITLE">隐形操作系统的密码</string>
    <string lang="zh-cn" key="PASSWORD_LENGTH_WARNING">警告：简短密码容易被暴力破解技术破解！\n\n我们建议选择一个超过 20 个字符的密码。\n\n您确定要使用简短密码吗？</string>
    <string lang="zh-cn" key="PASSWORD_TITLE">加密卷密码</string>
    <string lang="zh-cn" key="PASSWORD_WRONG">密码不正确或不是 VeraCrypt 加密卷。</string>
    <string lang="zh-cn" key="PASSWORD_OR_KEYFILE_WRONG">密钥 和/或 密码不正确或不是 VeraCrypt 加密卷。</string>
    <string lang="zh-cn" key="PASSWORD_OR_MODE_WRONG">错误的加载模式/密码或不是 VeraCrypt 加密卷。</string>
    <string lang="zh-cn" key="PASSWORD_OR_KEYFILE_OR_MODE_WRONG">错误的加载模式，无效的密钥文件 和/或 密码，或者不是 VeraCrypt 加密卷。</string>
    <string lang="zh-cn" key="PASSWORD_WRONG_AUTOMOUNT">密码不正确或不是 VeraCrypt 加密卷。</string>
    <string lang="zh-cn" key="PASSWORD_OR_KEYFILE_WRONG_AUTOMOUNT">密钥 和/或 密码不正确或不是 VeraCrypt 加密卷</string>
    <string lang="zh-cn" key="PASSWORD_WRONG_CAPSLOCK_ON">\n\n警告：Caps Lock 已经开启。 这可能导致您密码输入错误。</string>
    <string lang="zh-cn" key="HIDDEN_FILES_PRESENT_IN_KEYFILE_PATH">\n\n警告：在密钥文件搜索路径中存在隐藏文件。此类隐藏文件无法被用作密钥文件。如果您需要将它们当作密钥文件使用，请去除它们的“隐藏”属性（使用鼠标右键点击文件，选择〖属性〗，去除勾选“隐藏”标志再点击〖确定〗按钮）。注意：隐藏文件仅在启用相关选项后才可见（我的电脑 -&gt; 工具 -&gt; 文件夹选项 -&gt; 查看）。</string>
    <string lang="zh-cn" key="HIDDEN_VOL_PROT_PASSWORD_US_KEYB_LAYOUT">如果您试图保护包含隐形系统的隐藏加密卷，请确认输入隐藏加密卷密码时您正在使用标准的美国键盘布局。这是因为这些密码实在启动验证环境中输入的，而此时非美国键盘布局将无法使用。</string>
    <string lang="zh-cn" key="FOUND_NO_PARTITION_W_DEFERRED_INPLACE_ENC">VeraCrypt 未发现加密过程被中断的，同时头信息可以使用提供的密码 和/或 密钥文件解密的非系统分区。\n\n请确认密码 和/或 密钥文件是正确的，并且确认此 分区/卷 并未被操作系统或其它程序（也包含杀毒软件）占用。</string>
    <string lang="zh-cn" key="SYSENC_MOUNT_WITHOUT_PBA_NOTE">\n\n注意：如果您试图加载不带有启动验证的加密系统驱动器中的分区，或者是加载没有运行的加密系统分区，您可以通过选择〖系统〗 -&gt;〖以非启动验证方式加载〗。</string>
    <string lang="zh-cn" key="MOUNT_WITHOUT_PBA_VOL_ON_ACTIVE_SYSENC_DRIVE">在此模式下，您不能加载此驱动器上的分区（该驱动器的部分内容处于当前活动加密系统的关键范围）。\n\n要想以此模式加载此分区，您需要先启动到安装在不同驱动器上的操作系统（与该系统是否加密无关），或者是先启动一个未加密的操作系统。</string>
    <string lang="zh-cn" key="PREV">&lt; 后退(&amp;B)</string>
    <string lang="zh-cn" key="RAWDEVICES">不能列表安装在系统上的 raw 设备！</string>
    <string lang="zh-cn" key="READONLYPROMPT">加密卷 '%hs' 存在，并且是只读的。您确定要替换它吗？</string>
    <string lang="zh-cn" key="SELECT_DEST_DIR">选择目标目录</string>
    <string lang="zh-cn" key="SELECT_KEYFILE">选择密钥文件</string>
    <string lang="zh-cn" key="SELECT_KEYFILE_PATH">选择密钥文件的搜索路径。警告：注意，记忆的只是路径，而不会记忆文件名！</string>
    <string lang="zh-cn" key="SERPENT_HELP">Serpent 为与 AES 竞争算法中的一种。设计者为 Ross Anderson、Eli Biham、和 Lars Knudsen。发表于 1998 年。256 位密钥，128 位数据块，操作模式为 XTS。</string>
    <string lang="zh-cn" key="SIZE_HELP">请指定要创建的加密卷的大小。\n\n如果您打算创建一个动态的（稀疏文件）容器，该参数对应于该容器的最大尺寸。\n\n注意：最小的 FAT 加密卷大小为 292 KB。最小的 NTFS 加密卷大小为 3792 KB。</string>
    <string lang="zh-cn" key="SIZE_HELP_HIDDEN_HOST_VOL">请指定要创建的外层加密卷的大小（随后将在其内创建隐藏加密卷）。包含隐藏卷的外层加密卷最小可能大小为 340 KB。</string>
    <string lang="zh-cn" key="SIZE_HELP_HIDDEN_VOL">请指定要创建的隐藏加密卷的大小。隐藏加密卷的最小可能大小为 40 KB（格式化为NTFS时为 3664 KB）。最小可能的 NTFS 加密卷大小为 2829 KB。您可以指定加密卷的最大容量如上面所示。</string>
    <string lang="zh-cn" key="SIZE_HIDVOL_HOST_TITLE">外层加密卷大小</string>
    <string lang="zh-cn" key="SIZE_HIDVOL_TITLE">隐藏加密卷大小</string>
    <string lang="zh-cn" key="SIZE_PARTITION_HELP">请在确认选定的 分区/设备 的容量正确无误后单击〖下一步〗。</string>
    <string lang="zh-cn" key="SIZE_PARTITION_HIDDEN_SYSENC_HELP">外层加密卷和隐藏加密卷（包含隐形操作系统）将存在于上面分区。\n\n请确认上面显示的分区大小和数值是正确的，如果正确，请点击〖下一步〗。</string>
    <string lang="zh-cn" key="SIZE_PARTITION_HIDDEN_VOL_HELP">\n\n注意：如若在其内创建隐藏加密卷，则外层加密卷最小可能大小为 340 KB。</string>
    <string lang="zh-cn" key="SIZE_TITLE">加密卷大小</string>
    <string lang="zh-cn" key="SPARSE_FILE">动态加密卷</string>
    <string lang="zh-cn" key="TESTS_FAILED">警告：自检失败！</string>
    <string lang="zh-cn" key="TESTS_PASSED">全部算法自检通过</string>
    <string lang="zh-cn" key="TEST_INCORRECT_TEST_DATA_UNIT_SIZE">您提供的数据单元数值太长或太短。</string>
    <string lang="zh-cn" key="TEST_INCORRECT_SECONDARY_KEY_SIZE">您提供的次密钥太长或太短。</string>
    <string lang="zh-cn" key="TEST_CIPHERTEXT_SIZE">您提供的测试加密文本太长或太短。</string>
    <string lang="zh-cn" key="TEST_KEY_SIZE">您提供的测试密钥太长或太短。</string>
    <string lang="zh-cn" key="TEST_PLAINTEXT_SIZE">您提供的测试明码文本太长或太短。</string>
    <string lang="zh-cn" key="TWO_LAYER_CASCADE_HELP">在 XTS 模式的层叠操作中需要两个密码。每个块首先使用 %hs（%d 位密钥），之后使用 %hs（%d 位密钥）加密。每个密码使用其各自的密钥。所有的密钥均各自独立。</string>
    <string lang="zh-cn" key="THREE_LAYER_CASCADE_HELP">在 XTS 模式的层叠操作中需要 3 个密码。每个块首先以 %hs（%d 位密钥）加密，然后以 %hs（%d 位密钥）加密，最后以 %hs（%d 位密钥）加密。每个密码均使用各自的密钥。所有的密钥均彼此独立。</string>
    <string lang="zh-cn" key="AUTORUN_MAY_NOT_ALWAYS_WORK">需要注意的是，依赖于操作系统配置，这些自动运行和自动加载功能可能仅当便携磁盘文件创建在非可擦写 CD/DVD 类介质时才能使用。同样也要注意这并不是 VeraCrypt 程序设计缺陷（而是 Windows 系统的限制）。</string>
    <string lang="zh-cn" key="TRAVELER_DISK_CREATED">VeraCrypt 便携磁盘已成功创建。\n\n注意：您必须具有系统管理员身份才能以便携模式运行 VeraCrypt。同时也要注意尽管以便携模式运行 VeraCrypt，也可能能够从注册表中被检测到曾经运行过 VeraCrypt。</string>
    <string lang="zh-cn" key="TC_TRAVELER_DISK">VeraCrypt 便携磁盘</string>
    <string lang="zh-cn" key="TWOFISH_HELP">设计者：Bruce Schneie、John Kelsey、Doug Whiting、David Wagner、Chris Hall、Niels Ferguson。发表于 1998 年。256 位密钥，128 位块，操作模式为 XTS。Twofish 为 AES 竞争算法中的一种。</string>
    <string lang="zh-cn" key="MORE_INFO_ABOUT">关于 %hs 的更多信息（联网）</string>
    <string lang="zh-cn" key="UNKNOWN">未知</string>
    <string lang="zh-cn" key="ERR_UNKNOWN">发生未预期的或未知错误（%d）。</string>
    <string lang="zh-cn" key="UNMOUNTALL_LOCK_FAILED">一些加密卷包含的文件或文件夹 正被应用程序或系统使用。\n\n强行卸载吗？</string>
    <string lang="zh-cn" key="UNMOUNT_BUTTON">卸载(&amp;D)</string>
    <string lang="zh-cn" key="UNMOUNT_FAILED">卸载失败！</string>
    <string lang="zh-cn" key="UNMOUNT_LOCK_FAILED">加密卷包含的文件或文件夹 被应用程序或系统使用。\n\n强行卸载吗？</string>
    <string lang="zh-cn" key="NO_VOLUME_MOUNTED_TO_DRIVE">没有加密卷被加载到您所指定的盘符。</string>
    <string lang="zh-cn" key="VOL_ALREADY_MOUNTED">您试图要加载的加密卷早已加载。</string>
    <string lang="zh-cn" key="VOL_MOUNT_FAILED">试图加载加密卷时出错。</string>
    <string lang="zh-cn" key="VOL_SEEKING">在加密卷里寻址时出错。</string>
    <string lang="zh-cn" key="VOL_SIZE_WRONG">错误：错误的加密卷大小.</string>
    <string lang="zh-cn" key="WARN_QUICK_FORMAT">警告：您应当只能在下面的情况下使用快速格式化：\n\n1) 设备不包含敏感数据，且您不需要隐蔽性。\n2) 设备或分区已经被完全加密过。\n\n您确认要使用快速格式化吗？</string>
    <string lang="zh-cn" key="CONFIRM_SPARSE_FILE">动态的容器是一个预先分配的 NTFS 稀疏文件，它的物理大小（实际磁盘空间占用）在有新数据添加到里面的时候才会增加。\n\n警告: 稀疏文件基础的加密卷性能比常规加密卷的性能有较大降低。稀疏文件基础的加密卷的安全性也要弱些－因为它有可能泄漏哪些加密卷扇区未被使用的情况。另外，稀疏文件基础的加密卷无法实现隐蔽性（容纳一个隐藏加密卷）。同时需要注意到是如果数据被写入到稀疏文件基础的加密卷，而此时主机文件系统剩余空间不足，加密的文件系统可能会损坏。\n\n您确认要创建稀疏文件基础的加密卷吗？</string>
    <string lang="zh-cn" key="SPARSE_FILE_SIZE_NOTE">注意，Windows 系统和 VeraCrypt 报告的动态加密卷的大小会等于它的最大尺寸。要查看当前容器的物理大小（占用的实际磁盘空间），在 Windows 资源管理器窗口右键单击容器文件，之后选择“属性”并查看“占用空间”的数值。\n\n同时也要注意，如果您把动态加密卷移动到另外容器或驱动器，容器的物理大小会变为它的最大大小。 (为避免此类情况发生，您可以在目标位置创建一个新的动态加密卷，然后把文件从老的加密卷中复制过来)</string>
    <string lang="zh-cn" key="PASSWORD_CACHE_WIPED_SHORT">密码缓存已擦除</string>
    <string lang="zh-cn" key="PASSWORD_CACHE_WIPED">存储在 VeraCrypt 驱动缓存中的密码（和/或 已处理的密钥文件内容）已经被擦除。</string>
    <string lang="zh-cn" key="WRONG_VOL_TYPE">VeraCrypt 不能修改外层加密卷的密码。</string>
    <string lang="zh-cn" key="SELECT_FREE_DRIVE">请从列表中选择一个未被占用的驱动器盘符。</string>
    <string lang="zh-cn" key="SELECT_A_MOUNTED_VOLUME">请在驱动器列表中选择一个已加载的加密卷。</string>
    <string lang="zh-cn" key="AMBIGUOUS_VOL_SELECTION">当前选择了两个已加载的加密卷（一个位于盘符列表中，另外一个位于列表下面的文本输入框中）。\n\n请确认您要选择的加密卷：</string>
    <string lang="zh-cn" key="CANT_CREATE_AUTORUN">错误：不能创建 autorun.inf</string>
    <string lang="zh-cn" key="ERR_PROCESS_KEYFILE">处理密钥文件时出错！</string>
    <string lang="zh-cn" key="ERR_PROCESS_KEYFILE_PATH">处理密钥文件路径时出错！</string>
    <string lang="zh-cn" key="ERR_KEYFILE_PATH_EMPTY">密钥文件路径不包含文件。\n\n请注意，在密钥文件搜索路径中发现的该文件夹（以及其中包含的文件）已忽略。</string>
    <string lang="zh-cn" key="UNSUPPORTED_OS">VeraCrypt 不支持此操作系统。</string>
    <string lang="zh-cn" key="UNSUPPORTED_BETA_OS">错误：VeraCrypt 仅支持稳定的操作系统版本（不支持 beta 版和 RC 版）。</string>
    <string lang="zh-cn" key="ERR_MEM_ALLOC">错误：不能分配内存。</string>
    <string lang="zh-cn" key="ERR_PERF_COUNTER">错误：不能恢复性能计数器的值。</string>
    <string lang="zh-cn" key="ERR_VOL_FORMAT_BAD">错误：错误的加密卷格式。</string>
    <string lang="zh-cn" key="ERR_HIDDEN_NOT_NORMAL_VOLUME">错误：您提供了一个隐藏加密卷的密码（而不是常规加密卷的密码）。</string>
    <string lang="zh-cn" key="ERR_HIDDEN_VOL_HOST_ENCRYPTED_INPLACE">安全起见，隐藏加密卷不能在带有就地加密文件系统的 VeraCrypt 加密卷中创建（这是因为该加密卷上的自由空间没有填充随机数据）</string>
    <string lang="zh-cn" key="LEGAL_NOTICES_DLG_TITLE">VeraCrypt - 法律提示</string>
    <string lang="zh-cn" key="ALL_FILES">所有文件</string>
    <string lang="zh-cn" key="TC_VOLUMES">VeraCrypt 加密卷</string>
    <string lang="zh-cn" key="DLL_FILES">运行库模块</string>
    <string lang="zh-cn" key="FORMAT_NTFS_STOP">NTFS 格式化不能继续。</string>
    <string lang="zh-cn" key="CANT_MOUNT_VOLUME">不能加载加密卷。</string>
    <string lang="zh-cn" key="CANT_DISMOUNT_VOLUME">不能卸载加密卷。</string>
    <string lang="zh-cn" key="FORMAT_NTFS_FAILED">格式化成 NTFS 磁盘格式时失败。\n\n请选择不同的文件系统格式（如果可能的话）再尝试一次。此外，您可以保留该加密卷为未格式化加密卷（文件系统选择为“无”），退出向导，加载这个加密卷，然后再使用系统或第三方工具格式化这个已经加载的加密卷（该加载的加密卷仍然为加密状态）。</string>
    <string lang="zh-cn" key="FORMAT_NTFS_FAILED_ASK_FAT">Windows 格式化加密卷为 NTFS 时失败。\n\n您希望格式化为 FAT 文件系统吗？</string>
    <string lang="zh-cn" key="DEFAULT">默认</string>
    <string lang="zh-cn" key="PARTITION_LOWER_CASE">分区</string>
    <string lang="zh-cn" key="PARTITION_UPPER_CASE">分区</string>
    <string lang="zh-cn" key="DEVICE">设备</string>
    <string lang="zh-cn" key="DEVICE_LOWER_CASE">设备</string>
    <string lang="zh-cn" key="DEVICE_UPPER_CASE">设备</string>
    <string lang="zh-cn" key="VOLUME">加密卷</string>
    <string lang="zh-cn" key="VOLUME_LOWER_CASE">加密卷</string>
    <string lang="zh-cn" key="VOLUME_UPPER_CASE">加密卷</string>
    <string lang="zh-cn" key="LABEL">卷标</string>
    <string lang="zh-cn" key="CLUSTER_TOO_SMALL">相对加密卷大小而言，选择的簇大小太小。 将替代使用大一些的簇大小。</string>
    <string lang="zh-cn" key="CANT_GET_VOLSIZE">错误：不能获取加密卷大小信息！\n\n请确认选择的加密卷未被系统或 其它程序使用。</string>
    <string lang="zh-cn" key="HIDDEN_VOL_HOST_SPARSE">隐藏加密卷不能创建于动态（稀疏文件）的外层加密卷中。要达到足够的隐蔽性，隐藏加密卷应当在非动态加密卷中创建。</string>
    <string lang="zh-cn" key="HIDDEN_VOL_HOST_UNSUPPORTED_FILESYS">VeraCrypt 加密卷创建向导只能在 FAT 或 NTFS 加密卷内创建隐藏加密卷。</string>
    <string lang="zh-cn" key="HIDDEN_VOL_HOST_UNSUPPORTED_FILESYS_WIN2000">在 Windows 2000 系统里，VeraCrypt 加密卷创建向导只能在 FAT 加密卷里面创建隐藏加密卷。</string>
    <string lang="zh-cn" key="HIDDEN_VOL_HOST_NTFS">注意：FAT 文件系统比 NTFS 文件系统更适合作为外层加密卷（例如，如果外层加密卷被格式化为 FAT 格式，能够创建的隐藏加密卷的大小可能会更大一些）。</string>
    <string lang="zh-cn" key="HIDDEN_VOL_HOST_NTFS_ASK">注意：FAT 文件系统比 NTFS 文件系统更适合作为外层加密卷（例如，如果外层加密卷被格式化为 FAT 格式，能够创建的隐藏加密卷的大小可能会更大一些）（原因是 NTFS 文件系统总是在卷的中部存储内部数据，因此，隐藏加密卷只能创建在外层加密卷的后半部分）。\n\n您确认要继续格式化外层为 NTFS 格式吗？</string>
    <string lang="zh-cn" key="OFFER_FAT_FORMAT_ALTERNATIVE">您想要把加密卷格式化为 FAT 格式吗？</string>
    <string lang="zh-cn" key="FAT_NOT_AVAILABLE_FOR_SO_LARGE_VOLUME">注意：此加密卷无法以 FAT 文件系统格式化，因为其大小超过 FAT32 文件系统所支持的最大值（512 字节扇区最大 2TB，4096 字节扇区最大 16TB）。</string>
    <string lang="zh-cn" key="PARTITION_TOO_SMALL_FOR_HIDDEN_OS">错误：隐形操作系统的分区（也就是系统分区后面的第一个分区）必须至少比系统分区大 5%（系统分区就是当前运行的操作系统所在的分区）。</string>
    <string lang="zh-cn" key="PARTITION_TOO_SMALL_FOR_HIDDEN_OS_NTFS">错误：隐形操作系统的分区（也就是系统分区后面的第一个分区）必须至少比系统分区大 110%（2.1 倍）（系统分区就是当前运行的操作系统所在的分区）。原因是 NTFS 文件系统总是在卷的中部存储内部数据，因此，隐藏加密卷只能创建在外层加密卷的后半部分。</string>
    <string lang="zh-cn" key="OUTER_VOLUME_TOO_SMALL_FOR_HIDDEN_OS_NTFS">错误：如果外层加密卷被格式化为 NTFS，则它必须至少比系统分区大 110%（2.1 倍）。原因是 NTFS 文件系统总是在卷的中部存储内部数据，因此，隐藏加密卷只能创建在外层加密卷的后半部分。\n\n说明：外层加密卷需和隐形操作系统位于同一分区（即位于系统分区后面的第一个分区）。</string>
    <string lang="zh-cn" key="NO_PARTITION_FOLLOWS_BOOT_PARTITION">错误：在系统分区后面没有其它分区。\n\n注意，在您创建隐形操作系统之前，您需要在此系统驱动器上创建一个分区。该分区必须是系统分区后的第一个分区，并且必须至少比系统分区大 5%（系统分区就是当前运行的操作系统所在的分区）。然而，如果外层加密卷（不要与系统分区混淆）被格式化为 NTFS 格式，则该分区必须至少比系统分区大 110%（2.1 倍）（原因是 NTFS 文件系统总是在卷的中部存储内部数据，因此，包含系统克隆的隐藏加密卷只能创建在外层加密卷的后半部分）。</string>
    <string lang="zh-cn" key="TWO_SYSTEMS_IN_ONE_PARTITION_REMARK">注释：同时在单一分区的 VeraCrypt 外层和隐藏加密卷里面创建两个系统并不可行（因此也不被支持）。因为使用外层操作系统会经常要求写入数据到隐形操作系统所在区域（如果使用隐藏加密卷保护机制，也会因此而带来系统崩溃，即蓝屏错误）。</string>
    <string lang="zh-cn" key="FOR_MORE_INFO_ON_PARTITIONS">关于创建和管理分区的更多信息，请参考您的操作系统所提供的文档，或者联系您的计算机提供商以获取技术支持。</string>
    <string lang="zh-cn" key="SYSTEM_PARTITION_NOT_ACTIVE">错误：当前运行的操作系统并未安装到启动分区（第一个作用/激活的分区）。目前不支持此情况。</string>
    <string lang="zh-cn" key="CONFIRM_FAT_FOR_FILES_OVER_4GB">您已经表明了要在加密卷里面存放大于 4GB 的文件。然而，您选择了 FAT 文件系统，此系统无法存储大于 4 GB 的文件。\n\n您确认要格式化该卷为 FAT 格式吗？</string>
    <string lang="zh-cn" key="CANT_ACCESS_VOL">错误：不能访问加密卷！\n\n请确认选择的加密卷存在，并且该加密卷并未由系统或其它程序使用，同时该加密卷未被写保护，并且您具有对该加密卷的读写权限，并且确认该加密卷未被写保护。</string>
    <string lang="zh-cn" key="INPLACE_ENC_CANT_ACCESS_OR_GET_INFO_ON_VOL">错误：不能访问该加密卷 和/或 获取该加密卷的信息。\n\n请确认该加密卷存在，并且未被操作系统或其它程序占用，以及您具有对该加密卷的读写权限，同时还要保证该加密卷未被写保护。</string>
    <string lang="zh-cn" key="INPLACE_ENC_CANT_ACCESS_OR_GET_INFO_ON_VOL_ALT">错误：不能访问该加密卷 和/或 获取该加密卷的信息。请确认选择的加密卷存在，并且未被操作系统或其它程序占用，以及您具有对该加密卷的读写权限，同时还要保证该加密卷未被写保护。\n\n如果此问题仍然存在，遵循以下步骤可能有所帮助。</string>
    <string lang="zh-cn" key="INPLACE_ENC_GENERIC_ERR_ALT_STEPS">发生了一个错误，VeraCrypt 无法加密分区。请尝试修复任何前面报告的问题之后再次尝试。如果此问题依然存在，遵循以下步骤可能有所帮助。</string>
    <string lang="zh-cn" key="INPLACE_ENC_GENERIC_ERR_RESUME">发生了一个错误，VeraCrypt 无法继续加密分区的过程。\n\n请尝试修复任何前面报告的问题之后再次尝试加密过程。注意：该加密卷在完全加密前将无法加载。</string>
    <string lang="zh-cn" key="CANT_DISMOUNT_OUTER_VOL">错误：不能卸载外层加密卷！\n\n如果加密卷中的文件或文件夹被程序或被 系统使用，则该加密卷不能被锁定。\n\n请关闭任何可能使用加密卷上文件或目录 的程序，然后再点击〖重试〗。</string>
    <string lang="zh-cn" key="CANT_GET_OUTER_VOL_INFO">错误：不能获取外层加密卷的信息！ 加密卷创建不能继续。</string>
    <string lang="zh-cn" key="CANT_ACCESS_OUTER_VOL">错误：不能访问外层加密卷！ 加密卷创建不能继续。</string>
    <string lang="zh-cn" key="CANT_MOUNT_OUTER_VOL">错误：不能加载外层加密卷！ 加密卷创建不能继续。</string>
    <string lang="zh-cn" key="CANT_GET_CLUSTER_BITMAP">错误：不能获取加密卷簇状图！ 加密卷创建不能继续。</string>
    <string lang="zh-cn" key="ALPHABETICAL_CATEGORIZED">按字母顺序</string>
    <string lang="zh-cn" key="MEAN_SPEED">按平均速度（递减）</string>
    <string lang="zh-cn" key="ALGORITHM">算法</string>
    <string lang="zh-cn" key="ENCRYPTION">加密</string>
    <string lang="zh-cn" key="DECRYPTION">解密</string>
    <string lang="zh-cn" key="MEAN">平均</string>
    <string lang="zh-cn" key="DRIVE">盘符</string>
    <string lang="zh-cn" key="SIZE">大小</string>
    <string lang="zh-cn" key="ENCRYPTION_ALGORITHM">加密算法</string>
    <string lang="zh-cn" key="ENCRYPTION_ALGORITHM_LV">加密算法</string>
    <string lang="zh-cn" key="TYPE">类型</string>
    <string lang="zh-cn" key="VALUE">值</string>
    <string lang="zh-cn" key="PROPERTY">属性</string>
    <string lang="zh-cn" key="LOCATION">位置</string>
    <string lang="zh-cn" key="BYTES">字节</string>
    <string lang="zh-cn" key="HIDDEN">隐藏</string>
    <string lang="zh-cn" key="OUTER">外层</string>
    <string lang="zh-cn" key="NORMAL">常规</string>
    <string lang="zh-cn" key="SYSTEM_VOLUME_TYPE_ADJECTIVE">系统</string>
    <string lang="zh-cn" key="TYPE_HIDDEN_SYSTEM_ADJECTIVE">隐藏（系统）</string>
    <string lang="zh-cn" key="READ_ONLY">只读</string>
    <string lang="zh-cn" key="SYSTEM_DRIVE">系统驱动器</string>
    <string lang="zh-cn" key="SYSTEM_DRIVE_ENCRYPTING">系统驱动器（正在加密 - %.2f%% 已完成）</string>
    <string lang="zh-cn" key="SYSTEM_DRIVE_DECRYPTING">系统驱动器（正在解密 - %.2f%% 已完成）</string>
    <string lang="zh-cn" key="SYSTEM_DRIVE_PARTIALLY_ENCRYPTED">系统驱动器（%.2f%% 已加密）</string>
    <string lang="zh-cn" key="SYSTEM_PARTITION">系统分区</string>
    <string lang="zh-cn" key="HIDDEN_SYSTEM_PARTITION">隐形操作系统</string>
    <string lang="zh-cn" key="SYSTEM_PARTITION_ENCRYPTING">系统分区（正在加密 - %.2f%% 已完成）</string>
    <string lang="zh-cn" key="SYSTEM_PARTITION_DECRYPTING">系统分区（正在解密 - %.2f%% 已完成）</string>
    <string lang="zh-cn" key="SYSTEM_PARTITION_PARTIALLY_ENCRYPTED">系统分区（%.2f%% 已加密）</string>
    <string lang="zh-cn" key="HID_VOL_DAMAGE_PREVENTED">是（防止损坏！）</string>
    <string lang="zh-cn" key="NONE">无</string>
    <string lang="zh-cn" key="KEY_SIZE">主密钥大小</string>
    <string lang="zh-cn" key="SECONDARY_KEY_SIZE_XTS">次密钥大小（XTS 模式）</string>
    <string lang="zh-cn" key="SECONDARY_KEY_SIZE_LRW">调整密钥大小（LRW 模式）</string>
    <string lang="zh-cn" key="BITS">位</string>
    <string lang="zh-cn" key="BLOCK_SIZE">块大小</string>
    <string lang="zh-cn" key="PKCS5_PRF">PKCS-5 PRF</string>
    <string lang="zh-cn" key="PKCS5_ITERATIONS">PKCS-5 迭代次数</string>
    <string lang="zh-cn" key="VOLUME_CREATE_DATE">加密卷创建时间</string>
    <string lang="zh-cn" key="VOLUME_HEADER_DATE">头信息上次修改时间</string>
    <string lang="zh-cn" key="VOLUME_HEADER_DAYS">（%I64d 天前）</string>
    <string lang="zh-cn" key="VOLUME_FORMAT_VERSION">加密卷格式版本</string>
    <string lang="zh-cn" key="BACKUP_HEADER">内嵌的备份头信息</string>
    <string lang="zh-cn" key="VC_BOOT_LOADER_VERSION">VeraCrypt 启动管理器版本</string>
    <string lang="zh-cn" key="FIRST_AVAILABLE">首个可用的</string>
    <string lang="zh-cn" key="REMOVABLE_DISK">移动硬盘</string>
    <string lang="zh-cn" key="HARDDISK">硬盘</string>
    <string lang="zh-cn" key="UNCHANGED">不改变</string>
    <string lang="zh-cn" key="SETUP_MODE_TITLE">向导模式</string>
    <string lang="zh-cn" key="SETUP_MODE_INFO">请选择一种安装模式，如果不确认，请使用默认模式。</string>
    <string lang="zh-cn" key="SETUP_MODE_HELP_INSTALL">如果您想安装 VeraCrypt 到当前系统，请选择此选项。</string>
    <string lang="zh-cn" key="SETUP_MODE_HELP_UPGRADE">注意：即使在系统分区/设备已加密的情况下，或者您正在使用隐形系统的情况下，您也可以执行更新而无需解密.</string>
    <string lang="zh-cn" key="SETUP_MODE_HELP_EXTRACT">如果选择该选项，所有文件都会被从安装包中释放出来，但是不会向系统中安装任何文件。如果您计划加密 Windows 系统分区或系统驱动器，请不要选择此选项。选择此选项有时会比较有用，例如，您希望以便携模式运行 VeraCrypt。VeraCrypt 不一定要必须安装到系统中。在所有文件释放后，您可以直接运行释放后的 'VeraCrypt.exe' 文件（这时 VeraCrypt 会以便携模式运行）。您也可以把释放后的文件复制到其它计算机。</string>
    <string lang="zh-cn" key="SETUP_OPTIONS_TITLE">安装选项</string>
    <string lang="zh-cn" key="SETUP_OPTIONS_INFO">这里您可以设置控制安装过程的不同选项。</string>
    <string lang="zh-cn" key="SETUP_PROGRESS_TITLE">正在安装</string>
    <string lang="zh-cn" key="SETUP_PROGRESS_INFO">VeraCrypt 正在安装，请稍候。</string>
    <string lang="zh-cn" key="SETUP_FINISHED_TITLE_DON">VeraCrypt 已经成功安装</string>
    <string lang="zh-cn" key="SETUP_FINISHED_UPGRADE_TITLE_DON">VeraCrypt 已经成功更新</string>
    <string lang="zh-cn" key="SETUP_FINISHED_INFO_DON">请考虑给予捐助。您可在任何时间点击〖完成〗按钮关闭安装程序。 </string>
    <string lang="zh-cn" key="EXTRACTION_OPTIONS_TITLE">释放选项</string>
    <string lang="zh-cn" key="EXTRACTION_OPTIONS_INFO">您可以在这里设置控制释放过程的不同选项。</string>
    <string lang="zh-cn" key="EXTRACTION_PROGRESS_INFO">正在释放文件，请稍候。</string>
    <string lang="zh-cn" key="EXTRACTION_FINISHED_TITLE_DON">文件已经成功释放</string>
    <string lang="zh-cn" key="EXTRACTION_FINISHED_INFO">所有文件已经被成功释放到目标文件夹。</string>
    <string lang="zh-cn" key="AUTO_FOLDER_CREATION">如果指定文件夹，将会自动创建该文件夹。</string>
    <string lang="zh-cn" key="SETUP_UPGRADE_DESTINATION">VeraCrypt 程序文件将会更新到 VeraCrypt 的安装位置。如果您需要选择一个不同的位置，请先卸载当前安装的 VeraCrypt 。</string>
    <string lang="zh-cn" key="AFTER_UPGRADE_RELEASE_NOTES">您想联网查看当前版本的 VeraCrypt 的发行说明吗？</string>
    <string lang="zh-cn" key="AFTER_INSTALL_TUTORIAL">如果您以前从未没有使用过 VeraCrypt，我们推荐您先阅读“VeraCrypt User Guide”文档中的“Beginner's Tutorial”章节。您想要查看用户指南吗（联网）？</string>
    <string lang="zh-cn" key="SELECT_AN_ACTION">请从下面选项中选择要执行的操作：</string>
    <string lang="zh-cn" key="REPAIR_REINSTALL">修复/重新安装</string>
    <string lang="zh-cn" key="UPGRADE">更新</string>
    <string lang="zh-cn" key="UNINSTALL">卸载</string>
    <string lang="zh-cn" key="SETUP_ADMIN">要成功安装或卸载 VeraCrypt，您必须具有系统管理员权限。您确认要继续吗？</string>
    <string lang="zh-cn" key="TC_INSTALLER_IS_RUNNING">VeraCrypt 安装程序正在执行 VeraCrypt 的安装或更新。在您继续进行前，请等待其完成或者关闭它。如果您无法关闭它，请在继续之前重启计算机。</string>
    <string lang="zh-cn" key="INSTALL_FAILED">安装失败。</string>
    <string lang="zh-cn" key="UNINSTALL_FAILED">卸载失败。</string>
    <string lang="zh-cn" key="DIST_PACKAGE_CORRUPTED">该安装包已经损坏。请尝试重新下载安装包（优先建议从 VeraCrypt 官方网站 www.veracrypt.org 下载）。</string>
    <string lang="zh-cn" key="CANNOT_WRITE_FILE_X">不能写入文件 %hs</string>
    <string lang="zh-cn" key="EXTRACTING_VERB">正在释放</string>
    <string lang="zh-cn" key="CANNOT_READ_FROM_PACKAGE">不能从安装包中读取数据</string>
    <string lang="zh-cn" key="CANT_VERIFY_PACKAGE_INTEGRITY">不能验证安装包的完整性。</string>
    <string lang="zh-cn" key="EXTRACTION_FAILED">释放失败。</string>
    <string lang="zh-cn" key="ROLLBACK">安装已经回滚。</string>
    <string lang="zh-cn" key="INSTALL_OK">VeraCrypt 已成功安装。</string>
    <string lang="zh-cn" key="SETUP_UPDATE_OK">VeraCrypt 已经成功更新。</string>
    <string lang="zh-cn" key="UPGRADE_OK_REBOOT_REQUIRED">VeraCrypt 已经更新到新版本。在您开始使用新版本前，您必须重启计算机。\n\n您希望现在就重启计算机吗？</string>
    <string lang="zh-cn" key="SYS_ENC_UPGRADE_FAILED">警告：VeraCrypt 更新失败！\n\n重要：在您关机或重新启动系统前 ，我们强烈建议您使用系统还原（〖开始〗菜单 -&gt; 所有程序 -&gt;  附件 -&gt; 系统工具 -&gt; 系统还原），以恢复系统到名为“VeraCrypt 安装”的还原点。如果系统还原不可用，您应该在关机前尝试再从新安装原始版本的 VeraCrypt。</string>
    <string lang="zh-cn" key="UNINSTALL_OK">VeraCrypt 已成功卸载。\n\n单击〖完成〗按钮来移除 VeraCrypt 安装程序和文件夹 %hs。注意：如果该文件夹中含有非安装程序创建的文件，则该文件夹不会被移除。</string>
    <string lang="zh-cn" key="REMOVING_REG">正在移除 VeraCrypt 注册表项目。</string>
    <string lang="zh-cn" key="ADDING_REG">正在添加注册表项目</string>
    <string lang="zh-cn" key="REMOVING_APPDATA">正在删除程序相关数据</string>
    <string lang="zh-cn" key="INSTALLING">正在安装</string>
    <string lang="zh-cn" key="STOPPING">正在停止</string>
    <string lang="zh-cn" key="REMOVING">正在删除</string>
    <string lang="zh-cn" key="ADDING_ICON">添加图标</string>
    <string lang="zh-cn" key="CREATING_SYS_RESTORE">创建系统还原点</string>
    <string lang="zh-cn" key="FAILED_SYS_RESTORE">创建系统还原点失败！</string>
    <string lang="zh-cn" key="INSTALLER_UPDATING_BOOT_LOADER">正在更新启动管理器</string>
    <string lang="zh-cn" key="INSTALL_OF_FAILED">安装 '%hs' 失败。 %hs 您想要继续安装吗？</string>
    <string lang="zh-cn" key="UNINSTALL_OF_FAILED">卸载 '%hs' 失败。 %hs 您想要继续卸载吗？</string>
    <string lang="zh-cn" key="INSTALL_COMPLETED">安装完毕。</string>
    <string lang="zh-cn" key="CANT_CREATE_FOLDER">无法创建文件夹 '%hs' </string>
    <string lang="zh-cn" key="CLOSE_TC_FIRST">不能卸载 VeraCrypt 设备驱动。\n\n请首先关闭所有打开的 VeraCrypt 窗口。如果这样仍然不起作用，请重启计算机然后再试一次。</string>
    <string lang="zh-cn" key="DISMOUNT_ALL_FIRST">在安装或者卸载 VeraCrypt 之前必须先要卸载所有的 VeraCrypt 加密卷。</string>
    <string lang="zh-cn" key="UNINSTALL_OLD_VERSION_FIRST">当前系统已经安装了老版本的 VeraCrypt。在安装新版本前需要卸载旧版本的 VeraCrypt。\n\n在您关闭此对话框之后，将会加载旧版本的卸载程序。在卸载的过程中将不会执行任何加密分区的解密操作。在卸载旧版本的 VeraCrypt 之后，请再次运行新版 VeraCrypt 安装程序。</string>
    <string lang="zh-cn" key="REG_INSTALL_FAILED">安装注册表项目失败</string>
    <string lang="zh-cn" key="DRIVER_INSTALL_FAILED">安装设备驱动失败。请重启计算机后再尝试安装 VeraCrypt。</string>
    <string lang="zh-cn" key="STARTING_DRIVER">正在启动 VeraCrypt 设备驱动</string>
    <string lang="zh-cn" key="DRIVER_UINSTALL_FAILED">卸载设备驱动失败。请注意，由于 Windows 系统问题，在设置驱动能够继续卸载或重新安装前可能需要注销或者重启系统。</string>
    <string lang="zh-cn" key="INSTALLING_DRIVER">正在安装 VeraCrypt 设备驱动</string>
    <string lang="zh-cn" key="STOPPING_DRIVER">正在停止 VeraCrypt 设备驱动</string>
    <string lang="zh-cn" key="REMOVING_DRIVER">正在卸载 VeraCrypt 设备驱动</string>
    <string lang="zh-cn" key="COM_REG_FAILED">注册用户账户控制支持运行库失败。</string>
    <string lang="zh-cn" key="COM_DEREG_FAILED">取消用户账户支持运行库失败。</string>
    <string lang="zh-cn" key="TRAVELER_LIMITATIONS_NOTE">便携模式注意事项：\n\n操作系统要求驱动程序在启动前已注册，因此，VeraCrypt 的驱动程序不是完全便携的（但 VeraCrypt 程序本身是完全便携的，也就是说，它们无需安装也不用在操作系统中注册）。此外，也须注意VeraCrypt 需要提供透明的实时加密/解密的驱动。</string>
    <string lang="zh-cn" key="TRAVELER_UAC_NOTE">注意：如果您决定以便携方式运行 VeraCrypt（不同于安装后运行 VeraCrypt），系统会在您每次尝试运行 VeraCrypt 的时候询问您运行 VeraCrypt  的权限（UAC 提示）。\n\n原因是您以便携模式运行 VeraCrypt 时，VeraCrypt需要加载和运行 VeraCrypt 设备驱动。VeraCrypt 需要此设备驱提供透明实时加解密，并且不具有管理员权限的用户在 Windows 中将不能启动设备驱动。因此，系统将会要求您使用管理器特权运行 VeraCrypt 的权限（UAC 提示）。\n\n说明：如果您在系统中安装了 VeraCrypt，系统在每次启动 VeraCrypt 时将不会询问运行权限（无 UAC 提示）。\n\n您确认要释放这些文件吗？</string>
    <string lang="zh-cn" key="CONTAINER_ADMIN_WARNING">警告：这个加密卷创建向导的实例具有管理员权限。\n\n您新建的加密卷可能许可为加载时不允许向该加密卷写入数据。如果要避免这种情况发生，请关闭加密卷向导的实例并在非管理员权限下加载新的向导。\n\n您要关闭这个加密卷创建向导的实例吗？ a</string>
    <string lang="zh-cn" key="CANNOT_DISPLAY_LICENSE">错误：不能显示授权许可。</string>
    <string lang="zh-cn" key="OUTER_VOL_WRITE_PREVENTED">外层(!)</string>
    <string lang="zh-cn" key="DAYS">天</string>
    <string lang="zh-cn" key="HOURS">小时</string>
    <string lang="zh-cn" key="MINUTES">分钟</string>
    <string lang="zh-cn" key="SECONDS">秒</string>
    <string lang="zh-cn" key="OPEN">打开</string>
    <string lang="zh-cn" key="DISMOUNT">卸载</string>
    <string lang="zh-cn" key="SHOW_TC">显示 VeraCrypt</string>
    <string lang="zh-cn" key="HIDE_TC">隐藏 VeraCrypt</string>
    <string lang="zh-cn" key="TOTAL_DATA_READ">加载后读取的数据</string>
    <string lang="zh-cn" key="TOTAL_DATA_WRITTEN">加载后写入的数据</string>
    <string lang="zh-cn" key="ENCRYPTED_PORTION">加密部分</string>
    <string lang="zh-cn" key="ENCRYPTED_PORTION_FULLY_ENCRYPTED">100%（完全加密）</string>
    <string lang="zh-cn" key="ENCRYPTED_PORTION_NOT_ENCRYPTED">0%（未加密）</string>
    <string lang="zh-cn" key="PROCESSED_PORTION_X_PERCENT">%.3f%%</string>
    <string lang="zh-cn" key="PROCESSED_PORTION_100_PERCENT">100%</string>
    <string lang="zh-cn" key="PROGRESS_STATUS_WAITING">正在等待</string>
    <string lang="zh-cn" key="PROGRESS_STATUS_PREPARING">正在准备</string>
    <string lang="zh-cn" key="PROGRESS_STATUS_RESIZING">正在改变大小</string>
    <string lang="zh-cn" key="PROGRESS_STATUS_ENCRYPTING">正在加密</string>
    <string lang="zh-cn" key="PROGRESS_STATUS_DECRYPTING">正在解密</string>
    <string lang="zh-cn" key="PROGRESS_STATUS_FINALIZING">正在完成</string>
    <string lang="zh-cn" key="PROGRESS_STATUS_PAUSED">已暂停</string>
    <string lang="zh-cn" key="PROGRESS_STATUS_FINISHED">已完成</string>
    <string lang="zh-cn" key="PROGRESS_STATUS_ERROR">错误</string>
    <string lang="zh-cn" key="FAVORITE_DISCONNECTED_DEV">设备已断开</string>
    <string lang="zh-cn" key="SYS_FAVORITE_VOLUMES_SAVED">系统收藏加密卷已保存。\n\n要想在系统启动时加载系统收藏加密卷，请选择〖设置〗 -&gt; 〖系统收藏加密卷〗 -&gt; 〖在 Windows 启动时加载系统收藏加密卷〗。</string>
    <string lang="zh-cn" key="FAVORITE_ADD_DRIVE_DEV_WARNING">您添加到收藏的既不是加密分区也不是动态加密卷。因此，如果设备号发生改变，VeraCrypt 将不能载入此收藏加密卷。</string>
    <string lang="zh-cn" key="FAVORITE_ADD_PARTITION_TYPE_WARNING">您添加到收藏的加密卷不是 Windows 能够识别的分区。\n\n因此，如果设备号发生改变，VeraCrypt 将不能载入此收藏加密卷。请设置分区的类型为 Windows 系统所能够识别的类型(使用Windows 'diskpart' 工具的 SETID 命令)。之后再添加此分区到收藏。</string>
    <string lang="zh-cn" key="FAVORITE_ARRIVAL_MOUNT_BACKGROUND_TASK_ERR">VeraCrypt 后台任务已禁用，或被设置为在没有加密卷加载时退出（或者 VeraCrypt 正在以便携模式运行）。当含有这些加密卷的设备连接到电脑的时候，后台服务被禁用可能会阻止收藏加密卷自动加载。\n\n说明：要启用 VeraCrypt 后台任务，选择〖设置〗 -&gt; 〖参数选择〗之后勾选“VeraCrypt 后台任务”部份的“启用”复选框。</string>
    <string lang="zh-cn" key="FAVORITE_ARRIVAL_MOUNT_NETWORK_PATH_ERR">当含有这些加密卷的设备连接到电脑的时候，存储于共享网络上的远程文件系统的加密容器不能被自动加载。</string>
    <string lang="zh-cn" key="FAVORITE_ARRIVAL_MOUNT_DEVICE_PATH_ERR">下面显示的设备既不是分区也不是动态加密卷。因此，当设备连接到电脑的时候，存储于这些设备中的加密卷将不能自动加载。</string>
    <string lang="zh-cn" key="FAVORITE_ARRIVAL_MOUNT_PARTITION_TYPE_ERR">请设置下面显示的分区的类型为 Windows 系统所能够识别的类型(使用Windows 'diskpart' 工具的 SETID 命令)。之后从收藏中移除该分区并随后再次添加它。这可以使设备连接时，包含于其中的加密卷可以被 VeraCrypt 自动加载。</string>
    <string lang="zh-cn" key="FAVORITE_LABEL_DEVICE_PATH_ERR">下面显示的设备既不是分区也不是动态加密卷。因此，不会赋予它们磁盘盘符。</string>
    <string lang="zh-cn" key="FAVORITE_LABEL_PARTITION_TYPE_ERR">请设置下面显示的分区的类型为 Windows 系统所能够识别的类型(使用 Windows 'diskpart' 工具的 SETID 命令)。之后从收藏中移除该分区并随后再次添加它。这可以使 VeraCrypt 能够赋予盘符给这个分区。</string>
    <string lang="zh-cn" key="SYSTEM_FAVORITE_NETWORK_PATH_ERR">由于 Windows 系统的限制，在网络上共享的远程文件系统上的加密容器不能被加载为系统收藏加密卷（然而，它可以在用户登录时被加载为普通的收藏加密卷）。</string>
    <string lang="zh-cn" key="ENTER_PASSWORD_FOR">为 %hs 输入密码</string>
    <string lang="zh-cn" key="ENTER_PASSWORD_FOR_LABEL">为 '%s' 输入密码</string>
    <string lang="zh-cn" key="ENTER_NORMAL_VOL_PASSWORD">输入常规外层加密卷的密码</string>
    <string lang="zh-cn" key="ENTER_HIDDEN_VOL_PASSWORD">输入隐藏加密卷的密码</string>
    <string lang="zh-cn" key="ENTER_HEADER_BACKUP_PASSWORD">输入存储在备份文件中的加密卷头的密码</string>
    <string lang="zh-cn" key="KEYFILE_CREATED">密钥文件已成功创建。</string>
    <string lang="zh-cn" key="HEADER_DAMAGED_AUTO_USED_HEADER_BAK">警告：加密卷头信息已经损坏！VeraCrypt 将自动使用内嵌在加密卷中的头信息备份。\n\n您应当通过选择〖工具〗-&gt;〖恢复加密卷头信息〗来修复头信息。</string>
    <string lang="zh-cn" key="VOL_HEADER_BACKED_UP">加密卷头信息备份已经成功创建。\n\n重要：使用恢复功能恢复时也会恢复当前加密卷的密码。另外，如果创建加密卷的时候使用了密钥文件，恢复后也需要同样的密钥文件来打开加密卷。\n\n警告：该加密卷头信息备份只能用在这个提供备份的加密卷上。如果您把该头信息备份恢复到其它加密卷，您可能能够打开加密卷，但是您将不能解密存储于加密卷的任何数据（这是因为您已经改变了加密卷的主密钥）。</string>
    <string lang="zh-cn" key="VOL_HEADER_RESTORED">加密卷头信息备份已经成功恢复。\n\n重要：请注意旧密码也同样被恢复了。另外，备份时如果需要密钥文件来加载加密卷，恢复后也需要同样的密钥文件。</string>
    <string lang="zh-cn" key="EXTERNAL_VOL_HEADER_BAK_FIRST_INFO">安全起见，您需要输入正确的加密卷密码（和/或 提供正确的密钥文件）。\n\n注意：如果该加密卷中包含隐藏加密卷，您需要先输入正确的外层加密卷的密码（和/或 正确的密钥文件）。之后，如果选择老备份隐藏加密卷的头信息，您需要输入正确的隐藏加密卷密码（和/或 提供正确的密钥文件）。</string>
    <string lang="zh-cn" key="CONFIRM_VOL_HEADER_BAK">您确认要创建加密卷 %hs 的头信息的备份吗？\n\n在您点击〖是〗后，将会弹出备份的头信息文件的文件名提示对话框。\n\n注意：常规加密卷和隐藏加密卷头信息均将使用新的元素加密并存储到备份文件中。如果加密卷中没有隐藏加密卷，在备份文件中为隐藏加密卷保留的区域将会使用随机数据填充（以保持隐蔽性）。您需要输入创建头信息备份时的正确的密码（和/或 提供正确的密钥文件）。密码或密钥文件会自动确定要恢复的加密卷头信息类型，即常规的或是隐藏的（VeraCrypt 通过尝试和错误来侦测类型），尽管有时在加密卷里面并没有隐藏加密卷（为保留隐蔽性）。当从备份文件中恢复一个加密卷的头信息时，可以选择恢复哪个头信息（例如，隐藏解密卷或是标准加密卷）</string>
    <string lang="zh-cn" key="CONFIRM_VOL_HEADER_RESTORE">您确认要恢复加密卷 %hs 的头信息吗？\n\n警告：恢复加密卷头信息也会恢复在创建备份时 有效的密码。另外，如果在备份时需要使用密钥文件加载加密卷，那么在头信息恢复后，仍然需要同样的密钥文件。\n\n在您点击〖是〗后，您将选择头信息备份文件。</string>
    <string lang="zh-cn" key="DOES_VOLUME_CONTAIN_HIDDEN">此加密卷包含隐藏加密卷吗？</string>
    <string lang="zh-cn" key="VOLUME_CONTAINS_HIDDEN">此加密卷包含隐藏加密卷</string>
    <string lang="zh-cn" key="VOLUME_DOES_NOT_CONTAIN_HIDDEN">此加密卷不包含隐藏加密卷</string>
    <string lang="zh-cn" key="HEADER_RESTORE_EXTERNAL_INTERNAL">请选择您想要使用的加密卷头信息备份类型：</string>
    <string lang="zh-cn" key="HEADER_RESTORE_INTERNAL">从加密卷内嵌的备份中恢复加密卷头信息</string>
    <string lang="zh-cn" key="HEADER_RESTORE_EXTERNAL">从外部备份文件中恢复加密卷头信息</string>
    <string lang="zh-cn" key="HEADER_BACKUP_SIZE_INCORRECT">加密卷头信息备份文件的尺寸不对。</string>
    <string lang="zh-cn" key="VOLUME_HAS_NO_BACKUP_HEADER">加密卷中没有内嵌的备份头信息（注意，仅在 VeraCrypt 6.0 和以后的版本才包含内嵌的头信息）。</string>
    <string lang="zh-cn" key="BACKUP_HEADER_NOT_FOR_SYS_DEVICE">您正在尝试备份系统分区/设备的头信息，该功能不被允许。对于系统分区/设备头信息的备份/恢复 只能通过使用 VeraCrypt 应急盘来进行。\n\n您希望创建 VeraCrypt 应急盘吗？</string>
    <string lang="zh-cn" key="RESTORE_HEADER_NOT_FOR_SYS_DEVICE">您正在尝试恢复系统分区/设备的头信息，但是您选择的是系统分区/设备。该功能不被允许。 对于系统分区/设备头信息的备份/恢复 只能通过使用 VeraCrypt 应急盘来进行。\n\n您希望创建 VeraCrypt 应急盘吗？</string>
    <string lang="zh-cn" key="RESCUE_DISK_NON_WIZARD_CREATION_SELECT_PATH">在点击〖确定〗按钮后，您将会设置新的 VeraCrypt 应急盘  ISO 镜像文件的名称和存放位置。</string>
    <string lang="zh-cn" key="RESCUE_DISK_NON_WIZARD_CREATION_BURN">应急盘  ISO 镜像文件已经创建并存储为文件： %hs\n\n现在您需要把应急盘刻录到 CD 或 DVD。\n\n重要：文件必须以 ISO 镜像文件方式刻录到 CD/DVD（不要刻录为单个的数据文件）。要获取更多的关于如何刻录 ISO 文件的信息，请参考您的 CD/DVD 刻录软件的说明书。\n\n请您在刻录应急盘之后，选择〖系统〗 -&gt; 〖验证应急盘〗来验证应急盘是否已经成功刻录。</string>
    <string lang="zh-cn" key="RESCUE_DISK_NON_WIZARD_CREATION_WIN_ISOBURN">应急盘  ISO 镜像文件已经创建并存储为文件： %hs\n\n现在您需要把应急盘刻录到 CD 或 DVD。\n\n您想要启动 Windows 自带的磁盘镜像刻录功能吗？\n\n注意，请您在刻录应急盘之后，选择〖系统〗 -&gt; 〖验证应急盘〗来验证应急盘是否已经成功刻录。</string>
    <string lang="zh-cn" key="RESCUE_DISK_NON_WIZARD_CHECK_INSERT">请插入 VeraCrypt 应急盘到 CD/DVD 光驱并点〖确定〗按钮开始验证。</string>
    <string lang="zh-cn" key="RESCUE_DISK_NON_WIZARD_CHECK_PASSED">VeraCrypt 应急盘已经被成功验证。</string>
    <string lang="zh-cn" key="RESCUE_DISK_NON_WIZARD_CHECK_FAILED">应急盘验证失败。\n\n如果您已经刻录了应急盘，请弹出后重新插入应急盘到 CD/DVD，之后再试一次。如果仍然无效，请尝试使用其它 CD/DVD 刻录软件或刻录盘。\n\n如果您尝试验证一个为不同的主密钥、密码、元素等创建的 VeraCrypt 应急盘，请注意这样的应急盘会无法通过验证。要创建一个新的和当前配置完全兼容的应急盘，请选择〖系统〗 -&gt; 〖创建应急盘〗。</string>
    <string lang="zh-cn" key="ERROR_CREATING_RESCUE_DISK">创建 VeraCrypt 应急盘时失败。</string>
    <string lang="zh-cn" key="CANNOT_CREATE_RESCUE_DISK_ON_HIDDEN_OS">VeraCrypt 应急盘在隐形操作系统运行时无法创建。\n\n要创建 VeraCrypt 应急盘，请启动到迷惑操作系统之后选择〖系统〗 -&gt; 〖创建应急盘〗。</string>
    <string lang="zh-cn" key="RESCUE_DISK_CHECK_FAILED">不能确定应急盘是否刻录成功。\n\n如果您已经刻录了应急盘，请弹出后重新插入应急盘到 CD/DVD，之后再尝试验证一次。如果仍然无效，请尝试使用其它 %s 。\n\n如果您还没有创建应急盘，请首先创建一个，然后再点〖下一步〗按钮。\n\n如果您尝试验证一个运行加密盘创建向导以前创建的应急盘，则这样的应急盘是无法用于当前系统的，这是因为它是使用了不同的主密钥创建的。您需要刻录和创建一个新的应急盘。</string>
    <string lang="zh-cn" key="RESCUE_DISK_CHECK_FAILED_SENTENCE_APPENDIX"> 和/或 其它 CD/DVD 刻录软件</string>
    <string lang="zh-cn" key="SYSTEM_FAVORITES_DLG_TITLE">VeraCrypt - 系统收藏加密卷</string>
    <string lang="zh-cn" key="SYS_FAVORITES_HELP_LINK">什么是系统收藏加密卷？（联网）</string>
    <string lang="zh-cn" key="SYS_FAVORITES_REQUIRE_PBA">系统分区/驱动器看起来没有加密。\n\n系统收藏加密卷只能使用启动验证中的密码加载。因此，要启用系统收藏加密卷功能，您需要先加密系统分区/驱动器。</string>
    <string lang="zh-cn" key="DISMOUNT_FIRST">在操作前请卸载加密卷。</string>
    <string lang="zh-cn" key="CANNOT_SET_TIMER">错误：不能设置计时器。</string>
    <string lang="zh-cn" key="IDPM_CHECK_FILESYS">检查文件系统</string>
    <string lang="zh-cn" key="IDPM_REPAIR_FILESYS">修复文件系统</string>
    <string lang="zh-cn" key="IDPM_ADD_TO_FAVORITES">添加到收藏...</string>
    <string lang="zh-cn" key="IDPM_ADD_TO_SYSTEM_FAVORITES">添加为系统收藏加密卷...</string>
    <string lang="zh-cn" key="IDPM_PROPERTIES">属性(&amp;R)...</string>
    <string lang="zh-cn" key="HIDDEN_VOL_PROTECTION">隐藏加密卷被保护</string>
    <string lang="zh-cn" key="NOT_APPLICABLE_OR_NOT_AVAILABLE">N/A</string>
    <string lang="zh-cn" key="UISTR_YES">是</string>
    <string lang="zh-cn" key="UISTR_NO">否</string>
    <string lang="zh-cn" key="UISTR_DISABLED">禁用</string>
    <string lang="zh-cn" key="DIGIT_ONE">1 个</string>
    <string lang="zh-cn" key="TWO_OR_MORE">2 个或多个</string>
    <string lang="zh-cn" key="MODE_OF_OPERATION">操作模式</string>
    <string lang="zh-cn" key="LABEL_ITEM">卷标：   </string>
    <string lang="zh-cn" key="SIZE_ITEM">大小：   </string>
    <string lang="zh-cn" key="PATH_ITEM">路径：   </string>
    <string lang="zh-cn" key="DRIVE_LETTER_ITEM">驱动器盘符:   </string>
    <string lang="zh-cn" key="UNSUPPORTED_CHARS_IN_PWD">错误：密码必须仅包含 ASCII 字符。\n\n密码中的非-ASCII 字符可能会导致在 操作系统配置改变时加密卷不能加载。\n\n允许使用下面字符：\n\n  ! " # $ % &amp; ' ( ) * + , - . / 0 1 2 3 4  5 6 7 8 9 : ; &lt; = &gt; ? @ A B C D E F  G H I J K L M N O P Q R S T U V W X  Y Z [ \\ ] ^ _ ` a b c d e f g h i j k l m  n o p q r s t u v w k y z { | } ~</string>
    <string lang="zh-cn" key="UNSUPPORTED_CHARS_IN_PWD_RECOM">警告：密码中包含非-ASCII 字符。可能会导致在操作系统配置改变时加密卷不能加载。\n\n您应当使用 ASCII 字符替换密码中的非 ASCII 字符。 如要这样做，点击〖加密卷〗 -&gt; 〖修改加密卷密码〗\n\n下面字符为 ASCII 字符：\n\n  ! " # $ % &amp; ' ( ) * + , - . / 0 1 2 3 4  5 6 7 8 9 : ; &lt; = &gt; ? @ A B C D E F  G H I J K L M N O P Q R S T U V W X  Y Z [ \\ ] ^ _ ` a b c d e f g h i j k l m  n o p q r s t u v w k y z { | } ~</string>
    <string lang="zh-cn" key="EXE_FILE_EXTENSION_CONFIRM">警告：我们强烈建议您避免使用可执行文件名（例如 .exe，.sys，或 .dll）以及其它可能有问题的类似扩展名作为加密卷的名称。使用这些扩展名通常会导致 Windows 或反病毒软件干预加密卷，这很可能会严重影响加密卷的性能，也可能会导致其它严重的问题。\n\n我们强烈建议您移除此扩展名或更换其扩展名（例如，改变为 .iso，.img，.dat）。\n\n您确认继续使用可能有潜在问题的扩展名吗？</string>
    <string lang="zh-cn" key="EXE_FILE_EXTENSION_MOUNT_WARNING">警告：该加密卷带有可执行文件的扩展名（例如 .exe，.sys，或 .dll）或其它可能有问题的类似扩展名作为加密卷的名称。 这很可能导致 Windows 或反病毒软件干预加密卷，会严重影响加密卷的性能，也可能会导致其它严重的问题。\n\n我们强烈建议您在卸载加密卷后移除此扩展名或更换为其它扩展名（例如，改变为 .iso，.img，.dat）。</string>
    <string lang="zh-cn" key="HOMEPAGE">主页（联网）</string>
    <string lang="zh-cn" key="LARGE_IDE_WARNING_XP">警告：看起来您还没有安装任何 Windows 操作系统的补丁包。您不应当向未 安装 SP1 或以后补丁包的 Windows XP 系统中的大于128 GB 的 IDE 硬盘写 入数据！如果这样做，磁盘上的数据（不论是否为 VeraCrypt 加密卷）可能 会损坏。注意：这是 Windows 操作系统的限制，而不是 VeraCrypt 错误。</string>
    <string lang="zh-cn" key="LARGE_IDE_WARNING_2K">警告：看起来您的 Windows 2000 系统还未安装 SP3 或以后补丁包。 您不应当向这个系统中大于 128 GB 的 IDE 硬盘写入数据！如果这样 做了，磁盘上的数据（不论是否为 VeraCrypt 加密卷）可能会损坏。 注意：这是 Windows 操作系统的限制，而不是 VeraCrypt 的错误。\n\n注意：您也需在注册表里面启用 48-位 LBA 支持；更多信息，请参考 http：//support.microsoft.com/kb/305098/EN-US</string>
    <string lang="zh-cn" key="LARGE_IDE_WARNING_2K_REGISTRY">警告：您的系统不支持 48-位 LBA ATAPI。因此，您将不能写入到超过 128GB 容量的 IDE 磁盘！如果您仍然坚持这样做，磁盘上的数据（不论其是否为 VeraCrypt 加密卷）将会损坏。请注意，这是 Windows 系统的限制，不是 VeraCrypt 软件的限制。\n\n要启用 48-位 LBA 支持，请在注册表的HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\atapi\\Parameters下添加一个 'EnableBigLba' 键值并设置其值为 1。\n\n更多信息请参考 http://support.microsoft.com/kb/305098</string>
    <string lang="zh-cn" key="VOLUME_TOO_LARGE_FOR_FAT32">错误：大于 4 GB 的文件不能存储于 FAT32 文件系统。因此，存储于 FAT32 文件系统上的文件类型的加密卷（或外层加密卷）不能大于 4 GB。\n\n如果您需要大容量的加密卷，请在 NTFS 文件系统（或者，如果您使用 Windows Vista SP1 或以后版本的系统，在扩展的 exFAT 文件系统）中创建，除此之外，您也可以使用创建加密分区来代替创建文件型加密盘。</string>
    <string lang="zh-cn" key="VOLUME_TOO_LARGE_FOR_WINXP">警告：Windows XP 不支持大于 2048GB 的文件（将会被报告为“无足够存储空间”）。因此，在 Windows XP 中您不能创建大于 2048GB 的文件类型加密盘。\n\n请注意，在 Windows XP 中仍然是可以加密整个设备或者创建大于 2048GB 的分区类型 VeraCrypt 加密卷的。</string>
    <string lang="zh-cn" key="FREE_SPACE_FOR_WRITING_TO_OUTER_VOLUME">警告：如果您想以后向外层加密卷中添加更多的数据或文件，您应当考虑为隐藏加密卷选择一个小一点的尺寸。\n\n您确认要以指定的尺寸继续吗？</string>
    <string lang="zh-cn" key="NO_VOLUME_SELECTED">未选择加密卷。\n\n点击〖选择设备...〗或〖选择文件...〗来选择 VeraCrypt 加密卷。</string>
    <string lang="zh-cn" key="NO_SYSENC_PARTITION_SELECTED">没有选择分区。\n\n点击〖选择设备〗来选择一个通常需要启动验证的已卸载的分区（例如，一个位于另外加密系统驱动器上的另外一个没有运行的系统的分区，或者是另外一个操作系统的加密系统分区）。\n\n注意：选择的分区将被以常规 VeraCrypt 加密卷的方式加载而无需启动验证。这在执行备份和修复等操作时比较有用。</string>
    <string lang="zh-cn" key="CONFIRM_SAVE_DEFAULT_KEYFILES">警告：如果默认的密钥文件被设定和启用后，则不能加载不使用该密钥文件的加密卷。因此，如果默认的密钥文件被设定和启用后，在打开非密钥文件加密的加密卷时，请记住取消对〖使用密钥文件〗选项的选择（在密码输入框的下面）。\n\n您确认保存选定的密钥文件/路径作为默认值吗？</string>
    <string lang="zh-cn" key="HK_AUTOMOUNT_DEVICES">自动加载设备</string>
    <string lang="zh-cn" key="HK_DISMOUNT_ALL">全部卸载</string>
    <string lang="zh-cn" key="HK_WIPE_CACHE">擦除缓存</string>
    <string lang="zh-cn" key="HK_DISMOUNT_ALL_AND_WIPE">卸载全部  &amp;  擦除缓存</string>
    <string lang="zh-cn" key="HK_FORCE_DISMOUNT_ALL_AND_WIPE">强制全部卸载并擦除缓存</string>
    <string lang="zh-cn" key="HK_FORCE_DISMOUNT_ALL_AND_WIPE_AND_EXIT">强制全部卸载擦除缓存并退出程序</string>
    <string lang="zh-cn" key="HK_MOUNT_FAVORITE_VOLUMES">加载收藏加密卷</string>
    <string lang="zh-cn" key="HK_SHOW_HIDE_MAIN_WINDOW">显示/隐藏 VeraCrypt 主窗口</string>
    <string lang="zh-cn" key="PRESS_A_KEY_TO_ASSIGN">（单击这里并按下某个键盘按键）</string>
    <string lang="zh-cn" key="ACTION">操作</string>
    <string lang="zh-cn" key="SHORTCUT">热键</string>
    <string lang="zh-cn" key="CANNOT_USE_RESERVED_KEY">错误：该热键为系统保留热键，请选择一个其它热键。</string>
    <string lang="zh-cn" key="SHORTCUT_ALREADY_IN_USE">错误：热键被占用。</string>
    <string lang="zh-cn" key="HOTKEY_REGISTRATION_ERROR">警告：一个或多个 VeraCrypt 作用于系统范围的热键不能使用！\n\n请确认 VeraCrypt 的这些热键没有被其它程序或操作系统占用。</string>
    <string lang="zh-cn" key="PAGING_FILE_CREATION_PREVENTED">已阻止创建虚拟内存页面文件。\n\n请注意，由于 Windows 自身的问题，页面文件不能位于非系统类 VeraCrypt 加密卷（包括系统收藏加密卷）。VeraCrypt 仅支持在加密的系统分区/设备上创建页面文件。</string>
    <string lang="zh-cn" key="SYS_ENC_HIBERNATION_PREVENTED">VeraCrypt 加密休眠文件时发生了错误或者非兼容问题。因此系统的休眠已经被阻止。\n\n注意：当计算机处于休眠模式（或进入节电模式），系统内存的信息会被写入位于驱动器上的休眠文件。VeraCrypt 不能阻止在内存中打开的加密密钥和敏感文件的内容以未加密的形式存放于休眠文件。</string>
    <string lang="zh-cn" key="HIDDEN_OS_HIBERNATION_PREVENTED">休眠功能已经被阻止。\n\nVeraCrypt 不支持使用额外启动分区的隐形系统中的休眠功能。请注意启动分区是由迷惑系统和隐形系统共用的。因此，要防止数据泄露和休眠可能会带来的问题，VeraCrypt 不得不阻止隐形系统向共用的启动分区写入数据，以及阻止隐形系统休眠。</string>
    <string lang="zh-cn" key="VOLUME_MOUNTED_AS_DRIVE_LETTER_X_DISMOUNTED">加载为 %c: 的 VeraCrypt 加密卷已卸载。</string>
    <string lang="zh-cn" key="MOUNTED_VOLUMES_DISMOUNTED">VeraCrypt 加密卷已卸载。</string>
    <string lang="zh-cn" key="VOLUMES_DISMOUNTED_CACHE_WIPED">VeraCrypt 加密卷已经卸载，密码缓存已擦除。</string>
    <string lang="zh-cn" key="SUCCESSFULLY_DISMOUNTED">已成功卸载</string>
    <string lang="zh-cn" key="CONFIRM_BACKGROUND_TASK_DISABLED">警告：如果 VeraCrypt 后台任务被禁用，下面的功能将会失效：\n\n1）系统热键\n2）自动卸载加密卷（例如注销时，意外的主设备移除，超时，等等）\n3）自动加载收藏加密卷\n4）提示（例如：对隐藏加密卷的损坏被阻止时）\n5）通知栏图标\n\n注意：您可以随时在通过右键单击 VeraCrypt 的通知栏图标并选择〖退出〗来停止后台任务。\n\n您确认要停止 VeraCrypt 的后台任务吗？</string>
    <string lang="zh-cn" key="CONFIRM_NO_FORCED_AUTODISMOUNT">警告：如果此选项被禁用，包含打开的文件/目录 的加密卷将不能自动卸载。\n\n您确认要禁用这个选项吗？</string>
    <string lang="zh-cn" key="WARN_PREF_AUTO_DISMOUNT">警告：包含打开的文件/目录的加密卷将不能自动卸载。\n\n要防止这种情况，在对话框窗口中启用下面选项： 〖强行自动卸载，不论加密卷是否包含打开的文件或目录〗</string>
    <string lang="zh-cn" key="WARN_PREF_AUTO_DISMOUNT_ON_POWER">警告：当笔记本电力不足时，Windows 可能会在计算机进入待机模式时，系统会向正在运行中的程序发送相应的信息。因此，这种情况下 VeraCrypt 可能会无法自动卸载加密卷。</string>
    <string lang="zh-cn" key="NONSYS_INPLACE_ENC_RESUME_PROMPT">您已经安排了加密 分区/设备 的计划。该计划尚未完成。\n\n您希望现在继续这个加密过程吗？</string>
    <string lang="zh-cn" key="SYSTEM_ENCRYPTION_RESUME_PROMPT">您已经计划了加密或解密系统分区/驱动器的操作。但该操作尚未完成。\n\n您希望开始（或继续）该操作吗？</string>
    <string lang="zh-cn" key="ASK_NONSYS_INPLACE_ENC_NOTIFICATION_REMOVAL">您想要软件提示您是否要继续当前计划的加密非系统分区/卷的加密过程吗？</string>
    <string lang="zh-cn" key="KEEP_PROMPTING_ME">是，一直提示我</string>
    <string lang="zh-cn" key="DO_NOT_PROMPT_ME">否，不要再提示我</string>
    <string lang="zh-cn" key="NONSYS_INPLACE_ENC_NOTIFICATION_REMOVAL_NOTE">重要：请一定记住，任何时候，您都可以通过从 VeraCrypt 窗口的主菜单中选择〖加密卷〗 -&gt; 〖继续被中断的过程〗，来继续任何非系统服务/卷的加密过程。</string>
    <string lang="zh-cn" key="SYSTEM_ENCRYPTION_SCHEDULED_BUT_PBA_FAILED">您已经设置了加密解密系统分区或驱动器的计划任务。然而，启动验证已失败（或被绕过）。\n\n注意：如果您在启动验证环境中解密了系统分区/驱动器，您可能需要从 VeraCrypt 窗口的〖系统〗 菜单 -&gt; 〖永久解密系统分区/驱动器〗完成最后的设置步骤。</string>
    <string lang="zh-cn" key="CONFIRM_EXIT">警告：如果 VeraCrypt 现在退出，以下功能将被禁用：\n\n1）系统热键\n2）自动卸载加密卷（例如注销时，意外的主设备移除，超时，等等）\n3）自动加载收藏加密卷 \n4）提示（例如，当阻止损害隐藏加密卷时）\n\n注意：如果您不希望 VeraCrypt 在关闭程序窗口后以后台方式运行，请在程序参数选择里面禁用后台任务选项。（并且，如有必要，在程序参数里面禁用 VeraCrypt 的自动运行）。\n\n您确定要退出 VeraCrypt 吗？</string>
    <string lang="zh-cn" key="CONFIRM_EXIT_UNIVERSAL">退出吗？</string>
    <string lang="zh-cn" key="CHOOSE_ENCRYPT_OR_DECRYPT">VeraCrypt 没有足够信息确定是否要加密还是解密。</string>
    <string lang="zh-cn" key="CHOOSE_ENCRYPT_OR_DECRYPT_FINALIZE_DECRYPT_NOTE">VeraCrypt 无足够的信息来确定加解密状态。\n\n注意：如果您在启动验证环境解密系统分区/驱动器，您可能需要点击 Decrypt（解密）来最后完成解密过程。</string>
    <string lang="zh-cn" key="NONSYS_INPLACE_ENC_DEFER_CONFIRM">您想要中断和推迟对分区/驱动器的加密吗？\n\n注意：要记住这个加密卷在完全加密前是不能被加载的。您可以继续加密过程，加密则会在中断的地方继续。要达到这点，例如，可以从 VeraCrypt 主窗口的菜单中选择〖加密卷〗 -&gt; 〖继续被中断的过程〗。</string>
    <string lang="zh-cn" key="SYSTEM_ENCRYPTION_DEFER_CONFIRM">您想要中断和推迟对系统分区/驱动器的加密吗？\n\n注意：您以后也可以从中断位置恢复加密进程。操作如下：在 VeraCrypt 界面中选择〖系统〗 -&gt; 〖继续被中断的过程〗。如果您想永久中止或回滚加密进程，请选择〖系统〗 -&gt; 〖永久解密系统分区/驱动器〗。</string>
    <string lang="zh-cn" key="SYSTEM_DECRYPTION_DEFER_CONFIRM">您想要中断和推迟对系统分区/驱动器的加密吗？\n\n注意：您以后也可以从中断位置恢复加密进程。操作如下：在 VeraCrypt 界面中选择〖系统〗 -&gt; 〖继续被中断的过程〗。如果您想回滚解密进程（和开始加密），选择〖系统〗 -&gt; 〖加密系统分区/驱动器〗。</string>
    <string lang="zh-cn" key="FAILED_TO_INTERRUPT_SYSTEM_ENCRYPTION">错误：中断加密/解密系统分区或驱动器的操作失败。</string>
    <string lang="zh-cn" key="FAILED_TO_INTERRUPT_WIPING">错误：中断擦除过程时失败。</string>
    <string lang="zh-cn" key="FAILED_TO_RESUME_SYSTEM_ENCRYPTION">错误：继续加密/解密系统分区或驱动器的操作失败。</string>
    <string lang="zh-cn" key="FAILED_TO_START_WIPING">错误：启动擦除过程时失败。</string>
    <string lang="zh-cn" key="INCONSISTENCY_RESOLVED">发现不一致性。\n\n\n（如果您使用此链接报告这个错误，请在报告中包含下面信息： %hs）</string>
    <string lang="zh-cn" key="UNEXPECTED_STATE">错误：未知状态。\n\n\n（如果您报告与之相关的 BUG，请在错误报告里面包含下面的技术信息： %hs）</string>
    <string lang="zh-cn" key="NOTHING_TO_RESUME">没有可以继续的进程/任务。</string>
    <string lang="zh-cn" key="HIDVOL_PROT_BKG_TASK_WARNING">警告： VeraCrypt 后台任务已禁用。在您退出 VeraCrypt 后，如果设置了阻止损坏隐藏加密卷，您也将无法得到提示。\n\n注意：您可以随时在通过右键单击 VeraCrypt 通知栏图标并 选择〖退出〗来停止后台任务。\n\n\n您要启用 VeraCrypt 后台任务吗？</string>
    <string lang="zh-cn" key="LANG_PACK_VERSION">语言包版本： %s</string>
    <string lang="zh-cn" key="CHECKING_FS">正在检测加载为 %hs 的 VeraCrypt 加密卷的文件系统...</string>
    <string lang="zh-cn" key="REPAIRING_FS">正在试图修复加载为 %hs 的 VeraCrypt 加密卷的文件系统...</string>
    <string lang="zh-cn" key="WARN_CBC_MODE">警告：该加密卷以 CBC 模式加密。由于安全原因，CBC 模式自从 VeraCrypt 4.1 以后已不再推荐。\n\n我们强烈建议您把原来的数据移动到使用此版本 VeraCrypt 创建的加密卷里面。在执行此操作后，您应当安全的擦除或销毁早期的加密盘。要获取更多信息，请参考软件文档中的版本历史或者 VeraCrypt 4.1 或以后版本的发布说明。</string>
    <string lang="zh-cn" key="WARN_64_BIT_BLOCK_CIPHER">警告：该加密卷使用了已废弃的加密算法。\n\n所有 64-位块加密算法（Blowfish，CAST-128，和 Triple DES）已经逐渐不再被使用了。该加密卷在以后版本的 VeraCrypt 可能会被打开。然而以后则不会针对这些废弃算法采取一些改善措施。我们推荐您创建一个使用 128-位块加密算法的 Truecrypt 加密卷（如：AES，Serpent，Twofish，等等）并把使用旧算法的加密卷里面的文件移动到新的加密卷里面去。</string>
    <string lang="zh-cn" key="SYS_AUTOMOUNT_DISABLED">您的系统未被配置为自动加载新加密卷。 因此也不可能加载设备类的加密卷。自动卸载 可以在执行下列命令后重启系统来启用。\n\n\nmountvol.exe /E</string>
    <string lang="zh-cn" key="SYS_ASSIGN_DRIVE_LETTER">请在继续前为该设备/分区分配一个盘符（〖控制面板〗 -&gt; 〖系统和维护〗 -&gt; 〖管理工具〗 - 〖创建和格式化分区〗）。\n\n这些是操作系统所要求的。</string>
    <string lang="zh-cn" key="MOUNT_TC_VOLUME">加载 VeraCrypt 加密卷</string>
    <string lang="zh-cn" key="DISMOUNT_ALL_TC_VOLUMES">卸载所有 VeraCrypt 加密卷</string>
    <string lang="zh-cn" key="UAC_INIT_ERROR">VeraCrypt 获取系统管理员权限失败。</string>
    <string lang="zh-cn" key="ERR_ACCESS_DENIED">访问被操作系统拒绝。\n\n可能原因：操作系统要求您对某些文件夹、文件、和设备具有读写权限（或管理员权限），以便您能够从其中读写数据。通常情况下，非系统管理员仅允许在他自己的文档文件夹中创建、读取和修改文件。</string>
    <string lang="zh-cn" key="SECTOR_SIZE_UNSUPPORTED">错误：该驱动器使用了不被支持的扇区尺寸。\n\n如果设备的扇区大于 4096 字节，目前不可能在其上创建 分区/设备 类的加密卷。然而，您可以在此类驱动器上创建文件类型的加密卷。</string>
    <string lang="zh-cn" key="SYSENC_UNSUPPORTED_SECTOR_SIZE_BIOS">目前情况下，如果安装系统的磁盘扇区尺寸不是 512 字节，则无法在此基础上创建加密系统。</string>
    <string lang="zh-cn" key="NO_SPACE_FOR_BOOT_LOADER">VeraCrypt 启动管理器要求系统驱动器最前端至少有 32 KB 的未分配空间（VeraCrypt 启动管理器需要安装到该区域）。很不幸，您的驱动器无法满足这个条件。\n\n请不要把这个问题报告为 VeraCrypt 的程序缺陷。要解决这个问题，您需要对硬盘重新分区并保留硬盘的前 32 KB 为空闲状态（大多数情况下，需要您删除和重建第一个分区）。我们推荐您使用微软的分区管理来完成这个操作，例如，当您安装 Windows 时的分区管理程序。</string>
    <string lang="zh-cn" key="FEATURE_UNSUPPORTED_ON_CURRENT_OS">此功能不支持当前您正在使用的操作系统版本。</string>
    <string lang="zh-cn" key="SYS_ENCRYPTION_UNSUPPORTED_ON_CURRENT_OS">VeraCrypt 不支持在您当前使用的操作系统版本内加密系统分区/驱动器。</string>
    <string lang="zh-cn" key="SYS_ENCRYPTION_UNSUPPORTED_ON_VISTA_SP0">在您加密 Windows Vista 的系统分区/设备 前，您需要为 Vista 安装 Service Pack 1 或更高版本的补丁。\n\n提示：Vista Service Pack 1解决了启动系统时的自由基础内存缺陷。</string>
    <string lang="zh-cn" key="SYS_ENCRYPTION_UPGRADE_UNSUPPORTED_ON_VISTA_SP0">VeraCrypt 不再支持对未安装 SP 补丁的 Windows Vista 系统的系统分区/设备的加密。在升级 VeraCrypt 之前，请安装 Vista 的 Service Pack 1 或更高补丁版本。</string>
    <string lang="zh-cn" key="FEATURE_REQUIRES_INSTALLATION">错误：此功能要求 VeraCrypt 必须安装于当前系统（您正在以便携模式运行 VeraCrypt）。\n\n请安装 VeraCrypt 之后再试一次。</string>
    <string lang="zh-cn" key="WINDOWS_NOT_ON_BOOT_DRIVE_ERROR">警告：Windows 看起来并未安装在它所启动的驱动器上。此功能目前尚不支持。\n\n尽在您确认 Windows 的确安装在它所启动的驱动器上时，您才应当继续。\n\n您确认要继续吗？</string>
    <string lang="zh-cn" key="GPT_BOOT_DRIVE_UNSUPPORTED">您的系统驱动器具有 GUID 分区表（GPT）。当前只支持具有 MBR 的分区表。</string>
    <string lang="zh-cn" key="TC_BOOT_LOADER_ALREADY_INSTALLED">警告：VeraCrypt 启动管理器已经安装到了您的系统驱动器上了！\n\n这可能在您的计算机上已经加密了另外一个系统。\n\n警告：继续加密当前运行的系统可能会导致其它系统无法启动或导致数据无法访问。\n\n您确定要继续吗？</string>
    <string lang="zh-cn" key="SYS_LOADER_RESTORE_FAILED">恢复原来的系统启动管理器时失败。\n\n请使用您的 VeraCrypt 应急盘（'Repair Options' &gt; 'Restore original system loader'）或者 Windows 安装盘来清除 VeraCrypt 启动管理器。</string>
    <string lang="zh-cn" key="SYS_LOADER_UNAVAILABLE_FOR_RESCUE_DISK">原来的系统引导器没有保存到应急盘上（可能原因：备份文件丢失）。</string>
    <string lang="zh-cn" key="ERROR_MBR_PROTECTED">写入 MBR 扇区时失败。\n\n您的 BIOS 可能设置为保护了 MBR 扇区或一些还原软件也会保护 MBR。请确认没有安装保护 MBR 的还原软件和检查您的 BIOS 设置（启动计算机后按 F2，Delete，或 Esc）中的 MBR/反病毒保护。</string>
    <string lang="zh-cn" key="BOOT_LOADER_VERSION_INCORRECT_PREFERENCES">所要求版本的 VeraCrypt 启动管理器当前没有安装。这可能导致某些设置无法保存。</string>
    <string lang="zh-cn" key="CUSTOM_BOOT_LOADER_MESSAGE_HELP">提示：在某些环境，您可能希望避免外人（攻击者）在您启动计算机时看到您使用 VeraCrypt 加密了系统。上面的选项允许您自定义 VeraCrypt 启动管理器屏幕比避免此类事情发生。如果您启用了第一个选项，在启动验证屏幕不会显示任何文本（即时输入错误密码也不会提示）。在输入密码的时候计算机看起来就像被冻结的一样。此外，也可以显示自定义的信息来误导攻击者。例如，例如“Missing operating system”之类的英文信息（这个信息在 Windows 启动管理器未发现启动分区的时候显示）。然而，必须要提醒的是，如果攻击者分析硬盘的内容，他仍然可以发现硬盘上存在 VeraCrypt 启动管理器。</string>
    <string lang="zh-cn" key="CUSTOM_BOOT_LOADER_MESSAGE_PROMPT">警告：请记住，如果您启用此选项，VeraCrypt 启动管理器不会显示任何文本（即便是输错密码也不会显示任何文本）。计算机在够输入密码的时候计算机看起来就像被冻结（没有响应）一样（光标不会移动并且在按下按键的时候也不会显示掩码）。\n\n您确认要启用此选项吗？ </string>
    <string lang="zh-cn" key="SYS_PARTITION_OR_DRIVE_APPEARS_FULLY_ENCRYPTED">您的系统分区/驱动器看起来已经完全加密了。</string>
    <string lang="zh-cn" key="SYSENC_UNSUPPORTED_FOR_DYNAMIC_DISK">VeraCrypt 不支持加密已经转换为动态磁盘的系统驱动器。</string>
    <string lang="zh-cn" key="WDE_UNSUPPORTED_FOR_EXTENDED_PARTITIONS">该系统驱动器包含扩展（逻辑）分区。\n\n 您只能在 Windows Vista 或以后版本中加密包含扩展（逻辑）分区的整个系统驱动器。而在 Windows XP 系统中，您只可以加密仅含有一个主分区的整个系统驱动器。\n\n请注意：您仍然可以加密系统分区，来取代加密整个驱动器（并且，有别于加密整个驱动器，您可以在驱动器上的任何非系统分区创建分区类型的 VeraCrypt 加密卷）。</string>
    <string lang="zh-cn" key="WDE_EXTENDED_PARTITIONS_WARNING">警告： 由于您运行的系统为 Windows XP/2003，在您开始加密驱动器之后，您一定不要在其上面再创建建扩展（逻辑）分区（您只可以创建主分区）。当您开始加密以后，任何的扩展分区均将无法再继续访问。\n\n说明：如果您无法接受这个条件，您可以返回和选择只加密系统所在分区而不是选择加密系统所在硬盘驱动器（另外，您可以在驱动器上的任何非系统分区创建分区类型的加密卷）。\n\n作为替代方案，如果您无法接受这个条件，您也可以考虑升级到 Windows Vista 或以后版本（您只可以在 Windows Vista 或以后版本中加密包含扩展/逻辑分区的整个驱动器）。</string>
    <string lang="zh-cn" key="SYSDRIVE_NON_STANDARD_PARTITIONS">您的系统驱动器包含非标准分区。\n\n如果您正使用笔记本电脑，您的系统驱动器可能包含特别的恢复分区。当整个系统驱动器被加密后（包括任何恢复分区），如果计算机使用设计不当的BIOS系统可能无法启动。在系统盘解密前，也将无法使用任何恢复分区。因此，我们建议您只加密系统分区。</string>
    <string lang="zh-cn" key="ASK_ENCRYPT_PARTITION_INSTEAD_OF_DRIVE">您确认要加密系统所在分区，而不是加密整个硬盘吗？\n\n说明：除了加密系统所在分区之外，您可以在该硬盘驱动器上的非系统分区创建分区类型的 VeraCrypt 加密卷。</string>
    <string lang="zh-cn" key="WHOLE_SYC_DEVICE_RECOM">由于您的系统驱动器仅包含一个占据了整个驱动器的分区，更适合（更安全）加密整个包含松散空间（通常位于这样分区的周围）的驱动器。\n\n您希望加密整个系统驱动器吗？</string>
    <string lang="zh-cn" key="TEMP_NOT_ON_SYS_PARTITION">您的系统已配置为在非系统分区存储临时文件。\n\n临时文件应该只位于系统分区（出于安全考虑）。</string>
    <string lang="zh-cn" key="USER_PROFILE_NOT_ON_SYS_PARTITION">您的用户配置文件并非设置在系统分区。\n\n用户配置文件应该只存储于系统分区（出于安全考虑）。</string>
    <string lang="zh-cn" key="PAGING_FILE_NOT_ON_SYS_PARTITION">非系统分区存在页面文件。\n\n页面文件应该只存储于系统分区（出于安全考虑）</string>
    <string lang="zh-cn" key="RESTRICT_PAGING_FILES_TO_SYS_PARTITION">您想要设置 Windows 仅在 Windows 分区生成页面文件吗？\n\n请注意，如果您点击〖是〗，计算机将会重新启动。之后请启动 VeraCrypt 和尝试再次创建隐形系统。</string>
    <string lang="zh-cn" key="LEAKS_OUTSIDE_SYSPART_UNIVERSAL_EXPLANATION"> 否则，隐形系统的隐蔽性将会受到严重影响。\n\n说明：如果攻击者分析这些文件的内容（存在于非系统分区中），他可能会发现您在隐形系统创建模式里面使用了此向导（这可能暗示计算机上存在隐形系统）。还需说明的是，存储于系统分区的此类文件，在隐形系统创建过程中将会被安全擦除。</string>
    <string lang="zh-cn" key="DECOY_OS_REINSTALL_WARNING">警告：在隐形系统创建过程中，您将会被要求全新安装当前运行的操作系统（以便安全创建迷惑系统）。\n\n说明：当前运行的操作系统和该系统分区的全部内容将会被复制到隐藏加密卷（以便创建隐形系统）。\n\n\n您确认您将使用 Windows 安装介质安装此系统吗（或使用服务分区）？</string>
    <string lang="zh-cn" key="DECOY_OS_REQUIREMENTS">安全起见，如果当前运行的操作系统需要激活，则必须在继续进行克隆前激活。注意到隐形操作系统将通过复制当前操作系统的内容到隐藏加密卷来得以创建（因此如果当前操作系统未激活，则隐形操作系统也处于未激活状态）。更多信息，请参考《VeraCrypt User's Guide》的 "Security Precautions Pertaining to Hidden Volumes" 章节。\n\n重要：在继续进行前，确认您已经阅读了《VeraCrypt User's Guide》的 "Security Precautions Pertaining to Hidden Volumes" 章节。\n\n\n当前运行的操作系统满足上面的条件吗？</string>
    <string lang="zh-cn" key="CONFIRM_HIDDEN_OS_EXTRA_BOOT_PARTITION">您的系统使用了一个额外的启动分区。VeraCrypt 不支持使用额外启动分区的隐形系统的休眠（迷惑系统完全可以休眠）。\n\n请注意，启动分区应当被迷惑系统和隐形系统所共同使用。因此，为了防止数据泄露和由于休眠所导致的问题，VeraCrypt 只能阻止隐形系统写入数据到共用的启动分区和阻止隐形系统使用休眠。\n\n\n您确认要继续吗？如果选择〖否〗，则会显示移除额外启动分区的提示信息。</string>
    <string lang="zh-cn" key="EXTRA_BOOT_PARTITION_REMOVAL_INSTRUCTIONS">\n在安装 Windows 之前可以移除额外的启动分区。想要如此，请遵循以下步骤（译者注：这些步骤没有在XP安装光盘看到，请读者自悟吧，抱歉）：\n\n1）启动您的 Windows 安装光盘。\n\n2）在 Windows 安装屏幕，选择 '现在安装' -&gt; '自定义（高级）'.\n\n3）点击 '驱动器 选项'。\n\n4）选择主系统分区并选择删除这个分区，之后再确认删除（安装盘删除分区的时候会多次确认）。\n\n5）选择 '系统保留' 分区，选择 '扩展'，并增加它的大小直到可以安装系统为止。\n\n6）选择 '应用' 和确认。\n\n7）安装 Windows 到 '系统保留' 分区。\n\n\n如果攻击者询问您移除额外启动分区的原因，您可以回答是因为您不希望数据泄露到未加密的启动分区。\n\n注意：您可以通过点击下面的“打印”按钮打印这些文本。如果您打印了这些文本，强烈建议您在移除额外启动分区后销毁这些纸张（否则，如果这些纸张被发现，可能暗示着存在隐形系统）。</string>
    <string lang="zh-cn" key="GAP_BETWEEN_SYS_AND_HIDDEN_OS_PARTITION">警告：在系统分区和其后的第一个分区之间存在未分配空间。在您创建隐形操作系统之后，您必须不能在此未分配空间上创建任何新的分区，否则，隐形操作系统将无法启动（直到删除了这个新创建的分区）。</string>
    <string lang="zh-cn" key="ALGO_NOT_SUPPORTED_FOR_SYS_ENCRYPTION">此算法当前不支持系统加密。</string>
    <string lang="zh-cn" key="KEYFILES_NOT_SUPPORTED_FOR_SYS_ENCRYPTION">密钥文件当前不支持用在系统加密中。</string>
    <string lang="zh-cn" key="CANNOT_RESTORE_KEYBOARD_LAYOUT">警告：VeraCrypt 不能存储原始键盘布局。这可能导致您无法正确输入密码。</string>
    <string lang="zh-cn" key="CANT_CHANGE_KEYB_LAYOUT_FOR_SYS_ENCRYPTION">错误：不能设置 VeraCrypt 键盘布局为标准的美国键盘布局。\n\n说明：在 Windows 启动前的启动验证里需要输入密码，此时非美国标准键盘布局不可用。因此，密码必须使用标准的美国键盘布局输入。</string>
    <string lang="zh-cn" key="ALT_KEY_CHARS_NOT_FOR_SYS_ENCRYPTION">由于 VeraCrypt 临时改变键盘布局为标准的美国键盘，目前在按下 ALT 按键的情况下无法通过键盘输入字符。然而您可以按下 Shift 键的时候输入大多数此类字符。</string>
    <string lang="zh-cn" key="KEYB_LAYOUT_CHANGE_PREVENTED">VeraCrypt 会阻止对键盘布局的修改。</string>
    <string lang="zh-cn" key="KEYB_LAYOUT_SYS_ENC_EXPLANATION">说明：在 Windows 启动前的启动验证里需要输入密码，此时非美国标准键盘布局不可用。因此，密码必须使用标准的美国键盘布局输入。然而，这不需要您必须使用真实的美国键盘。VeraCrypt 在您没有美国键盘的情况下也能够自动的保证您能够安全的输入密码（现在和启动验证环境）。</string>
    <string lang="zh-cn" key="RESCUE_DISK_INFO">在您加密系统分区/驱动器前，您必须创建一个 VeraCrypt 应急盘，用途如下：\n\n- 如果 VeraCrypt 启动管理器、主密钥、或其它关键数据损坏了，可以使用应急盘修复它们（当然您必须输入正确的密码）。\n\n- 如果 Windows 系统损坏了并且无法启动，您可以在 Windows 启动前使用应急盘永久解密这个分区/驱动器。\n\n- 应急盘包含第一个柱面当前内容的备份（通常包含系统引导器或者启动管理器），在必要的时候您可以恢复它们。\n\nVeraCrypt 应急盘 ISO 映像文件将会在下面指定位置创建。</string>
    <string lang="zh-cn" key="RESCUE_DISK_WIN_ISOBURN_PRELAUNCH_NOTE">在您点击确定后，微软的 Windows 磁盘映像刻录器将会被启动。请使用它刻录 VeraCrypt 应急盘映像文件到 CD 或 DVD 中。\n\n在操作完这些之后，请返回到 VeraCrypt 加密卷创建向导并遵循向导的指令。</string>
    <string lang="zh-cn" key="RESCUE_DISK_BURN_INFO">应急盘  ISO 镜像文件已经创建并存储为文件： %hs\n\n现在您需要把应急盘刻录到 CD 或 DVD。\n\n在刻录应急盘后，点击〖下一步〗按钮验证应急盘已经成功刻录。\n\n%ls在刻录完应急盘之后，请点击〖下一步〗按钮验证应急盘是否被成功刻录。</string>
    <string lang="zh-cn" key="RESCUE_DISK_BURN_INFO_NO_CHECK">应急盘映像文件已经被创建并且存储为文件： %hs\n\n现在您应当刻录该应急盘到 CD/DVD 中去或者移动该 ISO 文件到一个安全的位置以备以后使用。\n\n%ls点击〖下一步〗继续。</string>
    <string lang="zh-cn" key="RESCUE_DISK_BURN_INFO_NONWIN_ISO_BURNER">重要：请注意，映像文件必须以 ISO 磁盘映像文件的方式刻录到 CD/DVD 中去（不能刻录为单个的数据文件）。要获取更多的关于如何刻录 ISO 文件的信息，请参考您的 CD/DVD 刻录软件的说明书。如果您还没有刻录 ISO 镜像文件的光盘刻录软件，请点下面链接下载这样的免费刻录软件。\n\n</string>
    <string lang="zh-cn" key="LAUNCH_WIN_ISOBURN">启动微软 Windows 磁盘映像刻录器</string>
    <string lang="zh-cn" key="RESCUE_DISK_BURN_NO_CHECK_WARN">警告：如果您已经创建了 VeraCrypt 应急盘，它将不能再用于系统分区/驱动器，这是因为您每次加密系统分区/驱动器时都会使用不同的主密钥，尽管您使用的是同样的密码，您也必须创建一个新的 VeraCrypt 应急盘。</string>
    <string lang="zh-cn" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">错误：不能保存系统加密设置。</string>
    <string lang="zh-cn" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">不能初始化系统加密预测试。</string>
    <string lang="zh-cn" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">不能初始化创建隐形操作系统的过程。</string>
    <string lang="zh-cn" key="WIPE_MODE_TITLE">擦除模式</string>
    <string lang="zh-cn" key="INPLACE_ENC_WIPE_MODE_INFO">在某些存储介质上，当数据被其他数据覆盖后，也仍有可能通过磁力显微技术恢复出来被覆盖的数据。这也包括一些被加密方式覆盖的数据（这在 VeraCrypt 加密那些原来没有加密的系统分区或系统驱动器时可能会发生）。根据一些研究机构和政府机构发布的文献，通过使用伪随机或非随机数据覆盖一定次数可以阻止数据恢复或使数据恢复变的异常困难。因此，如果您确认攻击者可能会使用类似磁力显微技术恢复您的加密数据，您可以选择下拉列表中几种擦除算法中的一种（已经存在的数据不会丢失）。需要说明的是在分区/驱动器加密后不需要再执行擦除操作。当分区/驱动器被完全加密后，不会再有非加密数据向其写入。写入加密卷中的任何数据都是在内存中实时加密，然后这些已加密数据才会被写入到磁盘。</string>
    <string lang="zh-cn" key="WIPE_MODE_INFO">在某些存储介质上，当数据被其他数据覆盖后，也仍有可能通过磁力显微技术恢复出来被覆盖的数据。根据一些研究机构和政府机构发布的文献，通过使用伪随机或非随机数据覆盖一定次数可以阻止数据恢复或使数据恢复变的异常困难。因此，如果您确认攻击者可能会使用类似磁力显微技术恢复您的加密数据，您可以选择下拉列表中几种擦除算法中的一种（已经存在的数据不会丢失）。\n\n说明：擦除次数越多，花费的时间越长。</string>
    <string lang="zh-cn" key="DEVICE_WIPE_PAGE_TITLE">正在擦除</string>
    <string lang="zh-cn" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\n说明：您可以中断擦除的过程，关闭您的计算机，重新启动隐形系统并在此后继续这个过程（该向导将会被自动运行）。然而，如果您中断此过程，整个擦除将会从头开始执行。</string>
    <string lang="zh-cn" key="DEVICE_WIPE_PAGE_INFO">\n\n说明：如果您中断了擦除的过程并想在以后继续擦除，整个的过程将不得不从头开始。</string>
    <string lang="zh-cn" key="CONFIRM_WIPE_ABORT">您确认要放弃擦除过程吗？</string>
    <string lang="zh-cn" key="CONFIRM_WIPE_START">警告：所选 分区/设备 的全部内容将会被擦除并因此而丢失。</string>
    <string lang="zh-cn" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">原始操作系统所在的分区将会被擦除。\n\n说明：该分区的全部内容已经复制到了隐形系统分区。</string>
    <string lang="zh-cn" key="WIPE_MODE_WARN">警告：请注意如果使用 3-次擦除模式，加密驱动器/分区需要时间将会增加为原来的4倍。同样，如果选择35-次擦除模式，所消耗的时间会为原来的36倍（如果分区容量很大，很可能花费几周的时间）。\n\n然而，请注意在分区/驱动器完全加密后【无须】再对其执行擦除操作。在分区/驱动器被完全加密后，将不会再有非加密的数据向该分区/驱动器写入。所有写入的数据首先都会在内存中即时加密，之后才会向分区/驱动器写入加密的数据（因此并不会影响性能）。\n\n您确认要使用这种擦除模式吗？</string>
    <string lang="zh-cn" key="WIPE_MODE_NONE">无（最快）</string>
    <string lang="zh-cn" key="WIPE_MODE_1_RAND">1-次擦除（随机数据）</string>
    <string lang="zh-cn" key="WIPE_MODE_3_DOD_5220">3-次擦除（US DoD 5220.22-M）</string>
    <string lang="zh-cn" key="WIPE_MODE_7_DOD_5220">7-次擦除（US DoD 5220.22-M）</string>
    <string lang="zh-cn" key="WIPE_MODE_35_GUTMANN">35-次擦除（"Gutmann"）</string>
    <string lang="zh-cn" key="WIPE_MODE_256">256-次擦除</string>
    <string lang="zh-cn" key="SYS_MULTI_BOOT_MODE_TITLE">操作系统数目</string>
    <string lang="zh-cn" key="MULTI_BOOT_FOR_ADVANCED_ONLY">警告：入门用户请勿尝试加密多重启动方式的 Windows 。\n\n希望继续吗？</string>
    <string lang="zh-cn" key="HIDDEN_OS_MULTI_BOOT">当创建或使用隐形操作系统时，只有满足如下条件时，VeraCrypt 才支持多重启动配置：\n\n- 当前运行操作系统必须安装在启动驱动器，并且该驱动器中不能包含其它操作系统。\n\n- 安装在其它驱动器的操作系统不能使用任何位于当前运行操作系统所在驱动器中的启动管理器。\n\n确认满足以上条件吗？</string>
    <string lang="zh-cn" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">在创建或使用隐形操作系统时，VeraCrypt 不支持此多重启动配置。</string>
    <string lang="zh-cn" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">引导驱动器</string>
    <string lang="zh-cn" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">当前运行的操作系统安装到了引导驱动器上了吗？\n\n说明：有时 Windows 可能并未安装到 Windows 启动管理器（活动分区）分区上。如果属于这种情况，请选择〖否〗。</string>
    <string lang="zh-cn" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt 当前不支持加密安装到非活动分区上的系统。</string>
    <string lang="zh-cn" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">系统驱动器数目</string>
    <string lang="zh-cn" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">有多少个驱动器含有操作系统？\n\n说明：例如，您在主驱动器上安装了任意系统（例如. Windows，Mac OS X，Linux，等等），在第二个驱动器上安装了其它的操作系统，这时就选择“2 个或多个”。</string>
    <string lang="zh-cn" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt 目前不支持对包含多个操作系统的整个硬盘驱动器的加密。\n\n可能的解决方法：\n\n- 您可以后退并选择只加密单系统分区加密其中的一个系统（与选择加密整个系统驱动器相反）。\n\n- 或者，您也可以把要加密的驱动器中的其它系统迁移到其它的驱动器，而只在其中保留一个系统。</string>
    <string lang="zh-cn" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">单驱动器中包含多个系统</string>
    <string lang="zh-cn" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">在当前运行的系统所安装的驱动器中，是否包含其它任何操作系统？\n\n说明：例如当前运行的操作系统安装在驱动器 #0，该驱动器包含几个分区，其中一个分区安装了 Windows 系统，而另一个分区安装了其它任何操作系统（例如. Windows，Mac OS X，Linux，等等.），请选择〖是〗。</string>
    <string lang="zh-cn" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">非 Windows 启动管理器</string>
    <string lang="zh-cn" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">是否安装了一个非 Windows 启动管理器（或启动管理器）到 MBR 中了吗?\n\n说明：例如，可启动的驱动器的第一个柱面包含 GRUB、LILO、XOSL，或其它非 Windows 启动管理器（或启动管理器），则选择“是”。</string>
    <string lang="zh-cn" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">多重启动</string>
    <string lang="zh-cn" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt 目前不支持在 MBR 中安装的非 Windows 多重启动管理器。\n\n可能的解决办法：\n\n- 如果您使用了一个启动管理器来启动 Windows 或 Linux，把启动管理器（典型的，例如 GRUB）从 MBR 中迁移到分区上。之后再次启动向导和加密系统分区/设备。说明：VeraCrypt 启动管理器将会成为主启动管理器，并且会允许您把原来的启动管理器（例如 GRUB）作为第二启动管理器（通过在 VeraCrypt 启动管理器屏幕按下 ESC 按键），因此您仍然可以启动 Linux。</string>
    <string lang="zh-cn" key="WINDOWS_BOOT_LOADER_HINTS">如果当前运行的系统安装在活动分区上，随后，在您加密了该分区后，尽管您想要启动其它未加密的系统，您仍然要输入正确的密码（因为它们都会共享同一个加密的 Windows 启动管理器）。\n\n相反的，如果当前运行的系统并没有安装到 Windows 的启动分区（或者如果其它系统并未使用 Windows 启动管理器），随后，在您加密了该分区后，您在启动其它未加密的系统时不需要输入正确的密码 -- 您只需按 ESC 按键来启动未加密的系统（如果存在多个未加密的系统，您也同样需要在 VeraCrypt 的启动管理器中选择要启动的系统）。\n\n说明：通常情况下，最早安装的那个系统一般都会安装到启动分区。</string>
    <string lang="zh-cn" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">加密主机保护区域（Host Protected Area）</string>
    <string lang="zh-cn" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">在很多硬盘的尾部，存在一个相对于操作系统隐藏的区域（这些区域通常被称作主机保护区域）。然而，某些程序可以从这些区域中读写数据。\n\n警告：某些计算机供应商可能使用这些区域存储用于 RAID、系统恢复、系统设置、诊断的工具和数据，或用于其它目地。如果此类工具和数据必须在启动前访问，那么这些隐藏区域不应当被加密（在上面选择〖否〗）。\n\n您希望 VeraCrypt 检测和解密系统驱动器尾部这些隐藏区域吗？</string>
    <string lang="zh-cn" key="SYSENC_TYPE_PAGE_TITLE">系统加密类型</string>
    <string lang="zh-cn" key="SYSENC_NORMAL_TYPE_HELP">如果您只想加密系统分区或整个系统驱动器，请选择此项。</string>
    <string lang="zh-cn" key="SYSENC_HIDDEN_TYPE_HELP">可能存在某些人强迫您解密操作系统的情况。在很多情况下您可能无法拒绝泄漏密码（例如，被勒索）。如果选择此选项，您将会创建一个没有任何手段可以识别的隐形操作系统（当然这得需要您遵循一定的步骤创建）。因此，您一定不要解密或者泄漏隐形操作系统的密码（译者注：这是因为隐形操作系统的存在只有您才知道，您不说的情况下没有任何手段可以检测到），如若获取更多信息，请单击下面链接。</string>
    <string lang="zh-cn" key="HIDDEN_OS_PREINFO">可能存在某些人强迫您解密操作系统的情况。在很多情况下您可能无法拒绝泄漏密码（例如，被勒索）。\n\n使用本向导，您将能够创建一个没有任何手段可以识别的隐形操作系统（当然这得需要您遵循一定的步骤创建）。因此，您一定不要解密隐形系统或者泄漏隐形操作系统的密码（译者注：这是因为隐形操作系统的存在只有您才知道，您不说的情况下没有任何手段可以检测到）。</string>
    <string lang="zh-cn" key="SYSENC_HIDDEN_OS_REQ_CHECK_PAGE_TITLE">隐形操作系统</string>
    <string lang="zh-cn" key="SYSENC_HIDDEN_OS_REQ_CHECK_PAGE_HELP">在后面步骤中，您将在系统分区之后的分区中创建两个 VeraCrypt 加密卷（外层的和隐藏的）。隐藏加密卷将包含隐形操作系统。VeraCrypt 将通过复制系统分区（即当前系统所在分区）的内容到隐藏加密卷来创建隐形操作系统。对于外层加密卷而言，您可以复制一些您实际上并不想隐藏的貌似敏感的文件。它们将用来对付那些强迫您说出隐藏系统分区密码的人。您可以把含隐形操作系统的外层加密卷的密码告诉它们（此时仍然无法发现是否存在隐形操作系统）。\n\n最后，在当前当前运行的系统的分区，您将会安装一个新的系统并加密以后作为迷惑系统来使用。这个迷惑系统不要含有任何敏感文件并且用来对付那些强迫您说出启动验证密码的人。总而言之，一共有三个密码，两个密码用于对付那些攻击者（分别对应迷惑操作系统和外层加密卷。如果您使用第三个密码，则将会启动隐形操作系统。</string>
    <string lang="zh-cn" key="SYSENC_DRIVE_ANALYSIS_TITLE">正在检测隐藏扇区</string>
    <string lang="zh-cn" key="SYSENC_DRIVE_ANALYSIS_INFO">当 VeraCrypt 正在检测系统驱动器尾部可能存在的隐藏扇区时，请稍候。注意该操作可能花费较长时间才能完成。\n\n注意：在极少数情况下，某些计算机环境中，系统可能在检测过程中失去响应。如果发生此情况，重启计算机，运行 VeraCrypt，重复前面步骤并跳过此检测过程。此问题并不是 VeraCrypt 程序错误。</string>
    <string lang="zh-cn" key="SYS_ENCRYPTION_SPAN_TITLE">要加密的区域</string>
    <string lang="zh-cn" key="SYS_ENCRYPTION_SPAN_WHOLE_SYS_DRIVE_HELP">如果您想加密操作系统安装和启动的分区，请选择此项。除了 VeraCrypt 启动管理器存放的第一个柱面之外，包括所有分区的整个硬盘驱动器将会被加密。任何要访问该驱动器上系统或文件的人都需要每次在系统启动前输入正确的密码。如果 Windows 并未安装到第二块或外部驱动器上并且没有从这些驱动器上启动，此选项不能用于加密第二块或外部驱动器。</string>
    <string lang="zh-cn" key="COLLECTING_RANDOM_DATA_TITLE">正在搜集随机数据</string>
    <string lang="zh-cn" key="KEYS_GEN_TITLE">密钥已生成</string>
    <string lang="zh-cn" key="CD_BURNER_NOT_PRESENT">VeraCrypt 未在系统上发现刻录机。VeraCrypt 需要 CD/DVD 刻录机来刻录一张可启动的 VeraCrypt 应急盘，应急盘包含密钥、VeraCrypt 启动管理器、原始启动管理器等信息的备份。\n\n我们强烈建议您刻录一张 VeraCrypt 应急盘。.</string>
    <string lang="zh-cn" key="CD_BURNER_NOT_PRESENT_WILL_STORE_ISO">我没有 CD/DVD 刻录机，但是我想在可移动驱动器上存放应急盘 ISO 映像文件（例如，USB 闪存）。</string>
    <string lang="zh-cn" key="CD_BURNER_NOT_PRESENT_WILL_CONNECT_LATER">我将会在以后添加 CD/DVD 刻录机到电脑上。现在终止创建过程。</string>
    <string lang="zh-cn" key="CD_BURNER_NOT_PRESENT_CONNECTED_NOW">现在 CD/DVD 刻录机已经连接到电脑上了。继续并且刻录应急盘。</string>
    <string lang="zh-cn" key="CD_BURNER_NOT_PRESENT_WILL_STORE_ISO_INFO">请遵循下面步骤：\n\n1）现在连接可移动驱动器到电脑上，例如 USB 闪存。\n\n2）复制 VeraCrypt 应急盘映像文件（%s）到可移动驱动器上。\n\n考虑到您以后有使用 VeraCrypt 应急盘的可能，建议您把这个可移动驱动器连接到其它有刻录机的电脑上，使用这个映像文件刻录一张应急盘。重要：请注意，VeraCrypt 应急盘映像文件必须以映像文件方式刻录，不能刻录为数据光盘。</string>
    <string lang="zh-cn" key="RESCUE_DISK_RECORDING_TITLE">正在刻录应急盘</string>
    <string lang="zh-cn" key="RESCUE_DISK_CREATED_TITLE">应急盘已创建</string>
    <string lang="zh-cn" key="SYS_ENCRYPTION_PRETEST_TITLE">系统加密预测试</string>
    <string lang="zh-cn" key="RESCUE_DISK_DISK_VERIFIED_TITLE">应急盘已验证</string>
    <string lang="zh-cn" key="RESCUE_DISK_VERIFIED_INFO">\nVeraCrypt 应急盘已成功验证。请从光驱中取出应急盘并把它存放到安全的地方。\n\n点击〖下一步〗继续。</string>
    <string lang="zh-cn" key="REMOVE_RESCUE_DISK_FROM_DRIVE">警告：在下面步骤中，VeraCrypt 应急盘必须不能放在光驱中。否则就不可能正确完成此步骤。\n\n请从光驱中取出应急盘并把他放在一个安全的地方，之后点〖确定〗按钮。</string>
    <string lang="zh-cn" key="PREBOOT_NOT_LOCALIZED">警告：由于启动验证环境（即在 Windows 系统启动前）的技术局限，VeraCrypt 在启动验证环境显示的文本不能汉化。VeraCrypt 启动管理器的界面完全为英文模式。\n\n确认继续吗？</string>
    <string lang="zh-cn" key="SYS_ENCRYPTION_PRETEST_INFO">在加密系统分区或启动前，VeraCrypt 需要验证每个环节都正确无误。\n\n在点击〖测试〗按钮以后，所有的组件（例如，启动验证组件，即 VeraCrypt 启动管理器）将会被安装并且您的计算机将会重启。之后您需要在 Windows 启动前的 VeraCrypt 启动管理器界面输入您的密码。在 Windows 启动后，程序将会自动通知您测试的结果。\n\n以下设备将会被修改: 驱动器 #%d\n\n\n如果您点击〖取消〗，将不会安装任何内容并且预测试将不会被执行。</string>
    <string lang="zh-cn" key="SYS_ENCRYPTION_PRETEST_INFO2_PORTION_1">重要提示 -- 请仔细阅读或打印（点击〖打印〗）：\n\n注意：在您成功重启计算机和启动 Windows 前，您的文件并没有被加密。因此，如果出现任何失败，您的数据不会丢失。然而，如果过程中发生某些错误，您可能在启动 Windows 时会遇到麻烦。因此，请阅读（如果可能，请打印）下面的操作指南，以了解在重启计算机后不能启动 Windows 时如何操作。\n\n</string>
    <string lang="zh-cn" key="SYS_ENCRYPTION_PRETEST_INFO2_PORTION_2">不能启动 Windows 时如何操作 ------------------------------------------------\n\n注意：这些指令仅在您还没有开始加密时有效。\n\n- 如果在输入正确的密码后 Windows 未能启动（或者您持续的输入正确的密码但 VeraCrypt 始终提示密码错误），请不要惊慌。重启计算机（或关机后再开机），在 TrueCrpyt 启动管理器屏幕，按下键盘的 ESC 按键（并且如果您有多个系统，就选择启动哪个系统）。之后 Windows 应当会启动（此时尚未加密系统）并且 VeraCrypt 会自动询问您是否要卸载启动验证组件。如果由于系统分区/驱动器已经加密而导致前面步骤无效（没有正确的密码，没有人可以启动加密系统或者访问该驱动器上的加密数据，即使他遵循前面步骤）。\n\n</string>
    <string lang="zh-cn" key="SYS_ENCRYPTION_PRETEST_INFO2_PORTION_3">- 如果前面步骤无效或者 VeraCrypt 启动管理器屏幕并没有出现（在 Windows 启动前），请在光驱中插入 VeraCrypt 应急盘并重启计算机。如果 VeraCrypt 启动管理器屏幕没有出现 或者如果您在启动管理器屏幕的 'Keyboard Controls'  部份没有看到 'Repair Options' 项目，很可能您的 BIOS 设置了硬盘优先于光驱启动。如果是这种情况，重启计算机，当您一看到 BIOS 启动屏幕的时候按下 F2 或 DEL 按键，直到 BISO 设置界面出现。如果 BIOS 设置界面没有出现，再次重启计算机，在您按下重启键的时候就按住 F2 或 DEL 按键。当 BIOS 设置界面出现时，配置您的 BIOS 优先从光驱启动（相关信息可以参考您的主板说明书或者资讯您的计算机供应商寻求技术协助）。之后重启计算机。VeraCrypt 启动管理器应该就会从应急盘中启动了。在VeraCrypt 启动管理器屏幕，按下键盘的 F8 按键选择修复选项（Repair Options）。在修复选项 'Repair Options' 菜单，选择 'Restore VeraCrypt Boot Loader'（恢复启动管理器）。之后从光驱中取出应急盘并重启计算机。之后 Windows 应当会启动（此时尚未加密系统）。\n\n</string>
    <string lang="zh-cn" key="SYS_ENCRYPTION_PRETEST_INFO2_PORTION_4">注意，如果由于系统分区/驱动器已经加密而导致前面步骤无效（没有正确的密码，没有人可以启动加密系统或者访问该驱动器上的加密数据，即使他遵循前面步骤）。\n\n\n即使您丢失了您的 VeraCrypt 应急盘并且被攻击者发现了，他们没有正确的密码也无法解密已经加密了的系统分区或驱动器。</string>
    <string lang="zh-cn" key="SYS_ENCRYPTION_PRETEST_RESULT_TITLE">预测试已经完成</string>
    <string lang="zh-cn" key="SYS_ENCRYPTION_PRETEST_RESULT_INFO">预测试已经成功完成。\n\n警告：请注意，加密时如果遇到突然断电、或者加密时由于软硬件故障而导致的电脑死机，可能会损坏或丢失一些数据。因此，在您开始加密前，请确认您已经备份了要加密的数据。如果您还没有备份，请现在就备份这些数据（您可以点击〖推迟〗，备份文件，之后在以后的任何时候再运行 VeraCrypt，并选择〖系统〗-&gt;〖继续被中断的进程〗来启动加密）。\n\n当一切准备就绪时，点击〖加密〗开始执行加密过程。</string>
    <string lang="zh-cn" key="SYSENC_ENCRYPTION_PAGE_INFO">您可以在任何时候点击〖暂停〗或者〖推迟〗以中断加解密进程、退出向导、重启或关闭计算机，并在以后继续中断的进程，继续时将会从中断位置开始。为防止系统或程序读写系统盘盘造成性能变差，VeraCrypt 会自动等待数据读写完毕后（参考上面的状态）自动继续加解密。</string>
    <string lang="zh-cn" key="NONSYS_INPLACE_ENC_ENCRYPTION_PAGE_INFO">\n\n您可以在加密过程的任何时候点击〖暂停〗或者〖推迟〗，来中断加密的过程，退出向导，重启计算机，并在此后继续该过程，继续的时候将会从上次中断之处开始。注意：此加密卷在完全加密之前无法被加载。</string>
    <string lang="zh-cn" key="SYSENC_HIDDEN_OS_INITIAL_INFO_TITLE">隐形系统已启动</string>
    <string lang="zh-cn" key="SYSENC_HIDDEN_OS_WIPE_INFO_TITLE">原始系统</string>
    <string lang="zh-cn" key="SYSENC_HIDDEN_OS_WIPE_INFO">Windows 会在系统分区创建（通常情况下，您并不知道或者同意）不同的日志文件、临时文件等等。同时也会在系统分区存储内存中的内容到休眠文件或虚拟内存页面文件。因此，如果攻击者分析原始系统（即隐形系统所克隆的系统来源）所在分区的文件，他可能会发现，例如，您使用过 VeraCrypt 向导的隐形系统创建模式（因此可能暗示计算机中存在隐形系统。\n\n要预防此类问题，在后面步骤中，VeraCrypt 将会安全擦除原始系统所在分区的所有内容。在此之后，为了达到隐蔽性，您需要在此分区上安装新的操作系统并使用 VeraCrypt 加密它（即成为所谓的迷惑系统）。因此您将会创建完成这个迷惑系统并且整个隐形系统的创建过程也会相应的完成。</string>
    <string lang="zh-cn" key="OS_WIPING_NOT_FINISHED_ASK">隐形系统已经成功创建。然而，在您使用隐形系统（以及达到隐蔽性）之前，您需要安全擦除当前运行的系统所在分区的全部内容（使用 VeraCrypt）。在您这样做之前，您需要重启计算机，并在之后的VeraCrypt 启动管理器屏幕（在 Windows 启动前出现），输入隐形系统的密码。之后，在隐形系统启动后，VeraCrypt 向导将会自动加载。\n\n说明：如果您现在选择终止隐形系统的创建过程，您将【无法再】继续该过程并且隐形系统将【不能再】被访问（这是因为 VeraCrypt 启动管理器将会被移除）。</string>
    <string lang="zh-cn" key="HIDDEN_OS_CREATION_NOT_FINISHED_ASK">您已经设置了创建隐形系统的计划任务。该计划尚未完成。要完成该计划，您需要重启计算机，并在 VeraCrypt 启动管理器屏幕（在 Windows 启动前出现），输入隐形系统的密码。\n\n注意：如果您现在选择终止隐形系统的创建过程，您将【无法】再继续该过程。</string>
    <string lang="zh-cn" key="HIDDEN_OS_CREATION_NOT_FINISHED_CHOICE_RETRY">重启计算机并继续</string>
    <string lang="zh-cn" key="HIDDEN_OS_CREATION_NOT_FINISHED_CHOICE_TERMINATE">永久终止隐形系统的创建过程</string>
    <string lang="zh-cn" key="HIDDEN_OS_CREATION_NOT_FINISHED_CHOICE_ASK_LATER">什么也不做并在以后询问</string>
    <string lang="zh-cn" key="RESCUE_DISK_HELP_PORTION_1">\n如果可能，请打印此段文本（单击下面的〖打印〗按钮）。\n\n\nVeraCrypt 应急盘使用时机和使用方法（加密后）-----------------------------------------------------------------------------------\n\n</string>
    <string lang="zh-cn" key="RESCUE_DISK_HELP_PORTION_2">I. 如何启动 VeraCrypt 应急盘\n\n要使用 VeraCrypt 应急盘，把应急盘插入光驱并重启计算机。如果 VeraCrypt 应急盘屏幕并没有出现（或者如果您在启动管理器屏幕的 'Keyboard Controls〗 部份没有看到 'Repair Options' 项目），很可能您的 BIOS 设置了硬盘优先于光驱启动。如果是这种情况，重启计算机，当您一看到 BIOS 启动屏幕的时候按下 F2 或 DEL 按键，直到 BISO 设置界面出现。如果 BIOS 设置界面没有出现，再次重启计算机，在您按下重启键的时候就按住 F2 或 DEL 按键。当 BIOS 设置界面出现时，配置您的 BIOS 优先从光驱启动（相关信息可以参考您的主板说明书或者资讯您的计算机供应商寻求技术协助）。之后重启计算机。VeraCrypt 启动管理器应该就会从应急盘中启动了。提示：在VeraCrypt 启动管理器屏幕，您可以按下键盘的 F8 按键选择修复选项（Repair Options）。\n\n\n</string>
    <string lang="zh-cn" key="RESCUE_DISK_HELP_PORTION_3">II. VeraCrypt 应急盘使用时机和使用方法（加密后）\n\n</string>
    <string lang="zh-cn" key="RESCUE_DISK_HELP_PORTION_4">1）如果在您启动计算机前没有出现 VeraCrypt 启动管理器屏幕（或者 Windows 没有能够启动），那么 VeraCrypt 启动管理器可能已经损坏。VeraCrypt 应急盘允许您恢复启动管理器并重新获取对加密系统和数据的访问（当然您仍然需要输入正确的密码）。在应急盘屏幕选择修复选项 'Repair Options' &gt; 'Restore VeraCrypt Boot Loader'（恢复启动管理器）。之后按下 'Y' 按键确认操作，从光驱中取出应急盘并重启计算机。\n\n</string>
    <string lang="zh-cn" key="RESCUE_DISK_HELP_PORTION_5">2）如果您持续输入正确密码而 VeraCrypt 仍然提示密码错误（password is incorrect），很可能是主密钥或其它关键数据已经毁坏。VeraCrypt 应急盘允许您恢复这些数据因此就可以重新访问这些加密的系统和数据了（当然您仍然需要输入正确的密码）。在应急盘屏幕，选择修复选项 'Repair Options' &gt; 'Restore key data'（恢复密钥数据）。之后输入您的密码，按下键盘的 'Y' 确认操作，从光驱中取出应急盘并重启计算机。\n\n</string>
    <string lang="zh-cn" key="RESCUE_DISK_HELP_PORTION_6">3）如果 VeraCrypt 启动管理器被恶意程序损坏了或感染了，您可以通过运行应急盘来避免运行恶意程序。在光驱中插入应急盘之后在应急盘屏幕输入您的密码。\n\n</string>
    <string lang="zh-cn" key="RESCUE_DISK_HELP_PORTION_7">4）如果 Windows 已经损坏并且不能启动，VeraCrypt 应急盘也可以允许您在启动 Windows 前永久解密分区/驱动器，在应急盘屏幕，选择修复选项 'Repair Options' &gt; 'Permanently decrypt system partition/drive'（永久解密系统分区/驱动器）。之后输入正确的密码直到解密完成。接下来，您就可以启动 Windows 的安装光盘来修复 Windows 了。\n\n</string>
    <string lang="zh-cn" key="RESCUE_DISK_HELP_PORTION_8">提示：另外一种方式，如果 Windows 已经损坏不能启动，您需要修复它（或者访问其上的文件），您可以通过以下步骤避免解密系统分区/驱动器：如果您在计算机上安装了多个操作系统，启动其中的某个不需要启动验证的系统。如果您的计算机没有安装多个操作系统，您可以启动一个 WinPE 或者 BartPE CD/DVD 系统，或者是把硬盘驱动器连接到其它计算机上作为从盘并启动其它计算机上的系统。在启动到此类系统环境之后，运行 VeraCrypt，点击〖选择设备〗，选择该受影响的系统分区，点击〖确定〗，选择〖系统〗-&gt;〖以非启动验证方式加载〗，输入您的启动验证密码并点击〖确定〗按钮。该分区将会以常规 VeraCrypt 加密分区的方式加载（数据也会象常规加密卷数据一样在内存中即时加解密）。\n\n\n</string>
    <string lang="zh-cn" key="RESCUE_DISK_HELP_PORTION_9">注意：即使您丢失了您的 VeraCrypt 应急盘并且被攻击者发现了，他们没有正确的密码也无法解密已经加密了的系统分区或驱动器。</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_1">\n\n重要 -- 如有可能请打印出来（点击〖打印〗）。\n\n\n注意：这些文本在您每次启动隐形系统时会自动显示，直到您开始创建迷惑系统。\n\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_2">如何成功和安全的创建迷惑系统 ----------------------------------------------------------------------------\n\n为了达到隐蔽性的目地，您现在应当创建迷惑系统。要达到这个目地，请遵循如下步骤：\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_3">1）安全考虑，关闭您的计算机并保持关机状态几分钟（时间越长越好）。这是出于清除内存中敏感数据的需要。之后打开计算机但不要启动隐形系统。\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_4">2）在已擦除内容的原系统分区上安装 Windows（也就是之前隐形系统克隆的系统源分区）。\n\n重要：在您开始安装迷惑操作系统时，隐形系统将无法启动（这是因为 VeraCrypt 启动管理器将会被 Windows 系统安装程序所清除）。这种情况是很正常的，遇到了请不必惊慌。一旦您开始加密迷惑系统，您就能够启动隐形系统了（这是因为 VeraCrypt 之后会自动在系统启动器上安装 VeraCrypt 启动管理器）。\n\n重要：迷惑系统分区的大小必须等于隐藏加密卷的大小（此条件已达到）。并且，您必须不能在迷惑系统分区和隐形系统所在分区之间创建任何分区。\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_5">3）启动迷惑系统（即您在前面的第 2) 步中安装的并把 VeraCrypt 安装到其中的那个系统）。\n\n必须牢记迷惑系统中从来都不要包含任何敏感数据。\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_6">4）在迷惑系统中，运行 VeraCrypt 并选择〖系统〗-&gt;〖加密系统分区/驱动器〗。将会出现 VeraCrypt 加密卷创建向导。\n\n VeraCrypt 加密卷创建向导中执行以下步骤。\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_7">5）在 VeraCrypt 加密卷创建向导中，不要选择“隐藏” 选项。保持“常规”选项为选中状态并点击〖下一步〗。\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_8">6）选择选项“加密 Windows 系统分区”并点击〖下一步〗。\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_9">7）如果计算机中只安装了一个隐形系统和迷惑系统，请选择“单系统”（如果在这两个系统之外还有其它系统，请选择“多系统”）。之后点击〖下一步〗。\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_10">8）重要：在本步中，对于迷惑系统，您必须选择与加密隐形系统相同的加密算法和哈希算法！否则将无法访问隐形系统。换句话说，迷惑系统和隐形系统的加密算法必须系统。说明：原因是迷惑系统和隐形系统共用一个单启动管理器，这个管理器只支持用户选择的某个单一算法（对于每种算法，都会对应一个特定的 VeraCrypt 启动管理器版本）。\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_11">9）在这个步骤中，为迷惑系统选择一个密码。当您被要求或者强迫提供启动验证密码时您可以泄漏这个迷惑系统的密码（另外一个可以泄漏的密码是外层加密卷密码）。而第三个密码（也就是启动验证里面用于启动隐形系统的密码）仍然是保密的。\n\n重要：迷惑系统的密码必须完全不同于隐藏加密卷的密码（隐藏加密卷的密码也就是隐形操作系统的密码）。\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_12">10）遵循向导的其余指令以加密迷惑操作系统。\n\n\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_13">在迷惑操作系统创建之后 ------------------------------------------------\n\n在您加密了迷惑操作系统之后，这个隐形系统的创建就完成了，这时您可以使用三个密码：\n\n1）启动验证中用于启动隐形系统的密码。\n\n2）启动验证中用于启动迷惑操作系统的密码。\n\n3）用于外层加密卷的密码。\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_14">如果您想启动隐形操作系统，只需要在 VeraCrypt 启动管理器屏幕（该屏幕出现于您开机或者重启系统的时候）输入隐形操作系统的密码。\n\n如果您想启动迷惑操作系统，只需要在 VeraCrypt 启动管理器屏幕输入迷惑操作系统的密码即可。\n\n迷惑操作系统的密码可以泄漏给强迫您说出密码的人，而此时隐藏加密卷（以及隐形操作系统）的存在仍然是保密的。\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_15">第三个密码（外层加密卷的密码），可以泄漏给强迫您说出系统分区之后那个分区密码的人（这个分区包含外层加密卷和隐藏加密卷，隐藏加密卷中即为隐形系统）。而此时隐藏加密卷（以及隐形操作系统）的存在仍然是保密的。\n\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_16">如果您把迷惑系统的密码泄漏给强迫您说出密码的人，如果他询问为什么（迷惑）系统分区的自由空间包含随机数据，您可以回答，例如："这个分区以前包含 VeraCrypt 加密的系统但是我忘记了密码（或者说这个系统已经损坏和无法启动了），因此我不得不安装了 Windows 和重新加密了这个分区"。\n\n\n</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_17">如果您遵循了前面的指令并且遵循了《VeraCrypt User Guide》中的 "Security Precautions Pertaining to Hidden Volumes" 章节所提到的防护措施，则外人无法证明隐藏加密卷和隐形系统的存在，哪怕是外层加密卷已加载或迷惑操作系统已解密/启动。\n\n如果您打印了此文本，在您创建迷惑操作系统之后并理解了文本中所述内容之后，强烈建议您销毁这个文本（否则，如果该文本纸张被发现，可能会暗示计算机上有存在隐形系统的可能）。</string>
    <string lang="zh-cn" key="DECOY_OS_INSTRUCTIONS_PORTION_18">警告：如果您没有保护隐藏加密卷（保护的做法参考 VeraCrypt 用户指南的"Protection of Hidden Volumes Against Damage"章节），请不要向外层加密卷写入数据。否则您可能会覆盖或损坏隐藏隐藏加密卷！请不要想外层加密卷写入数据（注意，迷惑操作系统并未安装在外层加密卷）。否则，您可能会覆盖和损坏隐藏加密卷（以及在其内的隐形系统）！</string>
    <string lang="zh-cn" key="HIDDEN_OS_CREATION_PREINFO_TITLE">正在克隆操作系统</string>
    <string lang="zh-cn" key="HIDDEN_OS_CREATION_PREINFO_HELP">在下一步中，VeraCrypt 将会通过复制当前运行系统的内容到隐藏加密卷来创建隐形系统（被复制的数据将会使用与迷惑系统不同的密钥实时加密））。\n\n请注意该过程将会在启动验证环境中执行（在 Windows 启动前），并可能花费较长的时间；可能需要花费几个小时或者几天（依据系统分区容量和计算机性能而定，例如PM1.6GHz加密时大概的速度是0.5GB/分钟左右）。\n\n您可以中断该过程，关机，启动操作系统并在此之后继续该过程。然而，如果您中断该过程，整个复制系统的过程将会不得不从头开始（因为系统分区的内容在克隆期间必须不能被改变）。</string>
    <string lang="zh-cn" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">您想要取消整个隐形操作系统的创建过程吗？\n\n注意：如果现在取消，您将无法继续该进程。</string>
    <string lang="zh-cn" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">您要取消系统加密预测试吗？</string>
    <string lang="zh-cn" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt 系统加密预测试失败。您希望再试一次吗？\n\n如果选择〖否〗，则启动验证组件将会被卸载。\n\n说明：如果 VeraCrypt 启动管理器在 Windows 启动前不要求您输入密码，这很可能是您的操作系统并没有从该系统所安装的驱动器引导的。目前并不支持这种方式。\n\n- 如果您使用了AES 之外的加密算法并且预测试失败了（并且您也输入了密码），这可能由有设计缺陷的驱动导致的。选择〖否〗，尝试再次加密系统分区/设备，但是要使用 AES 加密算法（该算法所需内存最低）。\n\n- 更多可能导致该错误的原因，请参考: http://www.veracrypt.org/docs/?s=troubleshooting</string>
    <string lang="zh-cn" key="SYS_DRIVE_NOT_ENCRYPTED">该系统分区/驱动器看起来没有被加密（或者是没有被完全加密）。</string>
    <string lang="zh-cn" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">您的系统分区/驱动器已加密（部分或完全加密）。\n\n请在继续进行前解密该系统分区/驱动器。操作步骤：在 VeraCrypt 主窗口的菜单中，选择〖系统〗-&gt;〖永久解密系统分区/驱动器〗。</string>
    <string lang="zh-cn" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">当系统分区/驱动器已部份或完全加密时，您不能降级 VeraCrypt 的版本（但是可以更新到新版本或者从新安装同一版本）。</string>
    <string lang="zh-cn" key="SYS_ENCRYPTION_OR_DECRYPTION_IN_PROGRESS">您的系统分区/驱动器正在被加密/解密，或正在被修改。请在继续操作前中断这个加密/解密/修改进程（或者等待直到其完成）。</string>
    <string lang="zh-cn" key="SYSTEM_ENCRYPTION_IN_PROGRESS_ELSEWHERE">已经有 VeraCrypt 加密卷创建向导的实例在运行，并且正在执行对系统分区/驱动器的加密或解密操作。在您继续前，请等候其完成或者关闭该实例。如果您无法关闭这个实例，请在继续操作前重启计算机。</string>
    <string lang="zh-cn" key="SYSTEM_ENCRYPTION_NOT_COMPLETED">加密或解密系统分区/驱动器的进程尚未完成。在进程完成前请稍候。</string>
    <string lang="zh-cn" key="ERR_ENCRYPTION_NOT_COMPLETED">错误：加密分区/驱动器的过程已经未完成，该过程必须首先完成。</string>
    <string lang="zh-cn" key="ERR_NONSYS_INPLACE_ENC_INCOMPLETE">错误：加密 分区/卷 的过程尚未完成。您必须首先完成此过程。\n\n说明：要继续该过程，在 TrueCrype 主界面的菜单中，选择〖加密卷〗-&gt;〖继续被中断的过程〗。</string>
    <string lang="zh-cn" key="ERR_SYS_HIDVOL_HEAD_REENC_MODE_WRONG">密码正确，VeraCrypt 已经成功解密加密卷头信息并检测到了该加密卷存在一个隐形的操作系统。然而，您不能以此种方式修改隐形系统卷的头信息。\n\n要修改隐形系统卷的密码，请启动隐形操作系统，之后在 VeraCrypt 主界面选择〖系统〗-&gt;〖修改密码〗。\n\n要设置首密钥的生成算法，启动隐形操作系统并在程序窗口选择〖系统〗-&gt;〖设置首密钥生成算法〗。</string>
    <string lang="zh-cn" key="CANNOT_DECRYPT_HIDDEN_OS">VeraCrypt 不支持就地（在隐形系统内）解密隐形操作系统分区。\n\n说明：如果您要解密迷惑操作系统，可以启动到迷惑操作系统，在 VeraCrypt 程序中选择〖系统〗-&gt;〖永久解密系统分区/驱动器〗。</string>
    <string lang="zh-cn" key="ERR_PARAMETER_INCORRECT">错误：错误/无效的参数。</string>
    <string lang="zh-cn" key="DEVICE_SELECTED_IN_NON_DEVICE_MODE">您已经选择了一个分区或者设备，但是在向导模式您只能选择文件型加密卷。\n\n您希望改变向导模式吗？</string>
    <string lang="zh-cn" key="CONFIRM_CHANGE_WIZARD_MODE_TO_FILE_CONTAINER">您想取代创建为 VeraCrypt 文件型加密卷吗？</string>
    <string lang="zh-cn" key="CONFIRM_SYSTEM_ENCRYPTION_MODE">您已经选择了系统分区/驱动器（或启动分区），但是您选择的向导模式只适用于非系统驱动器。\n\n您希望设置启动验证（意味着每次启动 Windows 前，都需要您输入密码）和加密系统分区或驱动器吗？</string>
    <string lang="zh-cn" key="CONFIRM_DECRYPT_SYS_DEVICE">您确认要永久解密系统分区/驱动器吗？</string>
    <string lang="zh-cn" key="CONFIRM_DECRYPT_SYS_DEVICE_CAUTION">警告：如果您永久解密系统分区或驱动器，数据将会恢复为未加密状态。\n\n您确认要永久解密系统分区或驱动器吗？</string>
    <string lang="zh-cn" key="CONFIRM_CASCADE_FOR_SYS_ENCRYPTION">警告：如果您使用一种级联算法加密操作系统，您可能会遇到以下问题：\n\n1）VeraCrypt 启动管理器体积偏大，因此驱动器的第一个柱面可能无法容纳 VeraCrypt 启动管理器的备份。因此，当其损坏的时候（这个可能会经常发生，例如，在某些程序的有设计缺陷的反隐私操作情况下），您将需要使用 VeraCrypt 应急盘启动和修复 VeraCrypt 启动管理器。\n\n2）在一些计算机上，导致休眠时间过长。\n\n这些潜在的问题可以通过选择一种非级联算法（例如 AES）来预防。\n\n您真的要坚持继续使用级联算法吗？</string>
    <string lang="zh-cn" key="NOTE_CASCADE_FOR_SYS_ENCRYPTION">如果您遇到任何前面描述的问题，请解密该分区/驱动器（如果已加密）并使用一种非级联算法加密（例如 AES）。</string>
    <string lang="zh-cn" key="UPDATE_TC_IN_DECOY_OS_FIRST">警告：安全考虑，在更新隐形系统中的 VeraCrypt 之前，您应当先更新迷惑系统中的 VeraCrypt。\n\n可以这样实现：启动到迷惑系统，运行 VeraCrypt 安装程序。之后启动到隐形系统和运行 VeraCrypt 安装程序。\n\n注意：迷惑系统和隐形系统共用一个启动管理器。如果你仅在隐形系统升级 VeraCrypt，迷惑系统的 VeraCrypt 驱动版本则与 VeraCrypt 启动管理器的版本不同，亦可能暗示在电脑上存在隐形系统。\n\n\n您确认要继续吗？</string>
    <string lang="zh-cn" key="UPDATE_TC_IN_HIDDEN_OS_TOO">VeraCrypt 启动管理器的版本与系统中安装的 VeraCrypt 驱动和程序版本不一致。\n\n您应当运行 VeraCrypt 安装程序（版本号与 VeraCrypt 启动管理器相同）来更新操作系统中的 VeraCrypt。</string>
    <string lang="zh-cn" key="BOOT_LOADER_VERSION_DIFFERENT_FROM_DRIVER_VERSION">启动该系统的 VeraCrypt 启动管理器版本号不同于安装在系统上的 VeraCrypt 设备驱动或 VeraCrypt 应用程序的版本号。请注意，早期版本可能存在一些新版已经修复的 BUG。\n\n如果您并未从应急盘启动，您应当重新安装 VeraCrypt 或者更新到最新的稳定版本（启动管理器也会随之更新）。\n\n如果您从应急盘启动，您应当更新应急盘（〖系统〗-&gt;〖创建应急盘〗）。</string>
    <string lang="zh-cn" key="BOOT_LOADER_UPGRADE_OK">VeraCrypt 启动管理器已经成功更新。\n\n强烈建议您重启计算机后选择〖系统〗-&gt;〖创建应急盘〗来创建一个新的 VeraCrypt 应急盘（将会包含新版的 VeraCrypt 启动管理器）。</string>
    <string lang="zh-cn" key="BOOT_LOADER_UPGRADE_OK_HIDDEN_OS">VeraCrypt 启动管理器已经更新。\n\n强烈建议您启动迷惑操作系统并通过选择菜单〖系统〗 -&gt;〖创建应急盘〗创建一个新的 VeraCrypt应急盘（将会包含新版本的 VeraCrypt 启动管理器）。</string>
    <string lang="zh-cn" key="BOOT_LOADER_UPGRADE_FAILED">更新 VeraCrypt 启动管理器时失败。</string>
    <string lang="zh-cn" key="SYS_DRIVE_SIZE_PROBE_TIMEOUT">VeraCrypt 检测系统驱动器真实大小失败，因此，操作系统所报告的大小（将会比实际小）将会被使用。另外需要指明的是，这并不是 VeraCrypt 的程序问题（BUG）。</string>
    <string lang="zh-cn" key="HIDDEN_SECTOR_DETECTION_FAILED_PREVIOUSLY">警告：看起来 VeraCrypt 曾经检测过此系统驱动器上的隐藏扇区。如果您在上次检测过程中遇到任何问题，您可以通过跳过隐藏扇区检测来避免这个问题。注意，如果跳过检测，VeraCrypt 将会使用操作系统报告的容量（要小于真实驱动器的容量）。\n\n此问题并不是 VeraCrypt 的程序 Bug。</string>
    <string lang="zh-cn" key="SKIP_HIDDEN_SECTOR_DETECTION">跳过隐藏扇区的检测（使用操作系统报告的容量）</string>
    <string lang="zh-cn" key="RETRY_HIDDEN_SECTOR_DETECTION">尝试再次检测隐藏扇区</string>
    <string lang="zh-cn" key="ENABLE_BAD_SECTOR_ZEROING">错误：磁盘上一个或多个扇区的内容无法读取（可能由于物理因素影响）。\n\n这些扇区能够重新读取之前，就地加密的过程将无法继续。VeraCrypt 能够尝试向其中写入 0 来使这些扇区可读（之后这些 0 填充的区块将会被加密）。然而，请注意存储于这些不可读扇区的数据将会丢失。如果您想要避免数据丢失，您可以使用适当的第三方软件恢复这些损坏数据的某些部分。\n\n注意：在有物理损坏扇区的情况下（不同于简单的数据损坏和校验错误），当有数据试图向这些损坏扇区写入数据时，大多数存储设备都会在内部为这些要写入的数据重新分配扇区（因此当前损坏扇区上的现有数据可能在启动器上仍然保持未加密状态）。\n\n您希望 VeraCrypt 为这些不可读扇区填充 0 吗？</string>
    <string lang="zh-cn" key="DISCARD_UNREADABLE_ENCRYPTED_SECTORS">错误：磁盘上一个或多个扇区的内容无法读取（可能由于物理因素影响）。\n\n为了能够继续加密，VeraCrypt 不得不放弃这些不可读扇区（扇区内容会被伪随机数据填充）。请注意，在继续进行之前，您可以尝试使用适当的第三方软件恢复任何损坏数据的一部分。\n\n您希望 VeraCrypt 废弃不可读扇区中的数据吗？</string>
    <string lang="zh-cn" key="ZEROED_BAD_SECTOR_COUNT">说明：VeraCrypt 已经把 %I64d 的不可读扇区（%s）的当前内容全部替换为加密的全部为 0 的纯文本块。</string>
    <string lang="zh-cn" key="ENTER_TOKEN_PASSWORD">输入口令牌 '%s' 的密码/PIN:</string>
    <string lang="zh-cn" key="PKCS11_LIB_LOCATION_HELP">为允许 VeraCrypt 访问安全口令牌或智能卡，您首先需要为口令牌或智能卡安装一种 PKCS #11 运行库，这些运行库可能已经随设备提供，或者可以从供应商网站或其它第三方网站上下载。\n\n在您安装了运行库后，您可以通过单击〖选择运行库〗手动选择，或者通过单击〖自动检测运行库〗来让 VeraCrypt 发现和选择（仅会搜索 Windows 系统目录，比较耗费时间）。</string>
    <string lang="zh-cn" key="SELECT_PKCS11_MODULE_HELP">说明：对于安装到您计算机上的 PKCS #11 运行库以及安全口令牌或智能卡的文件名和位置，请参考口令牌、智能卡的文档，或者参考第三方软件。\n\n单击〖确定〗按钮选择路径和文件名。</string>
    <string lang="zh-cn" key="NO_PKCS11_MODULE_SPECIFIED">为允许 VeraCrypt 访问安全口令牌或智能卡，您需要为口令牌或智能卡选择一种 PKCS #11 运行库。要做到这点，请选择〖设置〗-&gt;〖安全口令牌〗。</string>
    <string lang="zh-cn" key="PKCS11_MODULE_INIT_FAILED">初始化 PKCS #11 安全口令牌运行库失败。\n\n请确认指定路径和文件名对应有效的 PKCS #11 运行库。要指定 PKCS #11 运行库路径和文件名，选择〖设置〗 -&gt;〖安全口令牌〗。</string>
    <string lang="zh-cn" key="PKCS11_MODULE_AUTO_DETECTION_FAILED">在 Windows 系统目录未发现 PKCS #11 运行库。\n\n请确认您的安全口令牌或智能卡已经安装了 PKCS #11 运行库（这些运行库可能已经随设备提供，或者可以从供应商网站或其它第三方网站上下载）。如果是被安装到 Windows 系统目录之外的地方，请点击〖选择运行库〗来定位运行库位置（例如：口令牌/智能卡 的安装文件夹。</string>
    <string lang="zh-cn" key="NO_TOKENS_FOUND">未发现安全口令牌。\n\n请确认您的安全口令牌已经连接到您的计算机上并且已经安装好了正确的设备驱动程序。</string>
    <string lang="zh-cn" key="TOKEN_KEYFILE_NOT_FOUND">安全口令牌密钥文件未发现。</string>
    <string lang="zh-cn" key="TOKEN_KEYFILE_ALREADY_EXISTS">已经存在同名的安全口令牌密钥文件。</string>
    <string lang="zh-cn" key="CONFIRM_SEL_FILES_DELETE">您想要删除指定文件吗？</string>
    <string lang="zh-cn" key="INVALID_TOKEN_KEYFILE_PATH">安全口令牌密钥文件路径无效。</string>
    <string lang="zh-cn" key="SECURITY_TOKEN_ERROR">安全口令牌错误</string>
    <string lang="zh-cn" key="CKR_PIN_INCORRECT">安全口令牌密码不正确。</string>
    <string lang="zh-cn" key="CKR_DEVICE_MEMORY">安全口令牌无足够的 内存/空间 执行请求的操作。\n\n如果您试图导入一个密钥文件，您应当选择一个小一些的文件或者使用由 VeraCrypt 生成的密钥文件（选择〖工具〗-&gt;〖密钥文件生成器〗）。</string>
    <string lang="zh-cn" key="ALL_TOKEN_SESSIONS_CLOSED">所有打开的口令牌会话均已关闭。</string>
    <string lang="zh-cn" key="SELECT_TOKEN_KEYFILES">选择安全口令牌密钥文件</string>
    <string lang="zh-cn" key="TOKEN_SLOT_ID">插槽</string>
    <string lang="zh-cn" key="TOKEN_NAME">口令牌名称</string>
    <string lang="zh-cn" key="TOKEN_DATA_OBJECT_LABEL">文件名</string>
    <string lang="zh-cn" key="BOOT_PASSWORD_CACHE_KEYBOARD_WARNING">重要：请注意，启动验证的密码总是以美国键盘布局输入的。因此，对于使用非美国键盘布局输入密码的加密卷，是不可能使用缓存密码加载的（注意这不是 VeraCrypt 的程序缺陷）。要允许这样的加密卷使用启动验证密码加载，请遵循以下步骤：\n\n1）点击〖选择文件〗或〖选择设备〗并选择加密卷。 2）选择〖加密卷〗-&gt;〖修改加密卷密码〗。 3）输入当前加密卷的密码。 4）修改键盘布局为 English (US)，通过点击 Windows 通知栏上的语言栏和选择“英语(美国)”。 5）在 VeraCrypt 新密码位置，输入启动验证密码。 6）在确认密码位置重复输入密码，之后点〖确定〗。警告：如果您采用这些步骤，请牢记，加密卷密码总是只能以美国键盘布局输入（这样才能在启动验证环境中自动匹配）。</string>
    <string lang="zh-cn" key="SYS_FAVORITES_KEYBOARD_WARNING">系统收藏加密卷将会以启动验证密码加载。如果任何系统收藏加密卷使用了不同的密码，它将不会被加载。</string>
    <string lang="zh-cn" key="SYS_FAVORITES_ADMIN_ONLY_INFO">请注意，如果您希望系统收藏加密卷不会受到常规 VeraCrypt 加密卷操作的影响（例如〖全部卸载〗），您应当启用选项〖在 VeraCrypt 中，只允许系统管理员查看和卸载系统收藏加密卷〗。另外，如果 VeraCrypt 以非管理员身份运行（在 Windows Vista 和以后版本的系统中默认为非管理员身份），系统收藏加密卷将不会出现在 VeraCrypt 程序窗口的驱动盘符列表中。</string>
    <string lang="zh-cn" key="SYS_FAVORITES_ADMIN_ONLY_WARNING">重要：请必须记住，此选项已经启用并且 VeraCrypt 不具有系统管理员权限，已加载的系统收藏加密卷不会显示在 VeraCrypt 程序窗口并且它们也不能被卸载。因此，如果您需要卸载系统收藏加密卷，请右键单击 VeraCrypt 图标（在开始菜单中），并选择“运行方式”和选择管理员帐户运行。“全部卸载”、“自动卸载”热键等功能也存在上面所说的限制。</string>
    <string lang="zh-cn" key="SETTING_REQUIRES_REBOOT">请注意，此设置在系统重启后才会生效。</string>
    <string lang="zh-cn" key="COMMAND_LINE_ERROR">解析命令行时出错。</string>
    <string lang="zh-cn" key="RESCUE_DISK">应急盘</string>
    <string lang="zh-cn" key="SELECT_FILE_AND_MOUNT">选择和加载文件(&amp;F)...</string>
    <string lang="zh-cn" key="SELECT_DEVICE_AND_MOUNT">选择和加载设备(&amp;D)...</string>
    <string lang="zh-cn" key="DISABLE_NONADMIN_SYS_FAVORITES_ACCESS">在 VeraCrypt 中，只允许系统管理员查看和卸载系统收藏加密卷</string>
    <string lang="zh-cn" key="MOUNT_SYSTEM_FAVORITES_ON_BOOT">在 Windows 启动时加载系统收藏加密卷（在启动过程的初始阶段）</string>
    <string lang="zh-cn" key="MOUNTED_VOLUME_DIRTY">警告：加载为 '%s' 的加密卷上的文件系统并未彻底卸载因此而存在错误。继续使用损坏的文件系统可能会导致数据丢失或者损坏。\n\n注意：在您物理移除或卸载包含已加载的 VeraCrypt 加密卷的设备（例如U盘或移动硬盘）之前，您应当先在 VeraCrypt 中卸载加密卷。\n\n\n您希望 Windows  系统尝试检测和修复可能的文件系统错误吗？</string>
    <string lang="zh-cn" key="SYS_FAVORITE_VOLUME_DIRTY">警告：一个或者多个系统收藏加密卷并没有完全卸载，因此可能包含文件系统错误。请查看系统事件日志获取更多信息。\n\n使用损坏的文件系统可以导致数据丢失或者数据损坏。您应当检查受影响的收藏加密卷的磁盘错误（在 VeraCrypt 中右键单击每个打开的收藏加密卷，之后选择〖修复文件系统〗）。</string>
    <string lang="zh-cn" key="FILESYS_REPAIR_CONFIRM_BACKUP">警告：使用微软的 'chkdsk' 工具修复受损的文件系统时可能会导致受损区域的数据丢失。因此，建议您首先备份存储在 VeraCrypt 加密卷中的文件到另外完好的加密卷。\n\n您确认现在就修复文件系统吗？</string>
    <string lang="zh-cn" key="MOUNTED_CONTAINER_FORCED_READ_ONLY">由于写入权限被拒绝，加密卷 '%s' 不得不以只读模式加载。\n\n请确认文件类型加密卷的安全许可允许您对其执行写入操作（右键单击此容器并选择 属性 -&gt; 安全）。\n\n注意，由于 Windows 的原因，您可能在设置成合适的安全属性后还会看到这个警告，这并非是 VeraCrypt 的程序故障。一个可能的解决方法是移动您的加密卷文件，例如移动到文档文件夹。\n\n如果您确实要保持加密卷的只读模式，请设置加密卷的属性为只读（右键单击加密盘文件并选择属性 -&gt; 只读），这样就可以禁止显示警告了。</string>
    <string lang="zh-cn" key="MOUNTED_DEVICE_FORCED_READ_ONLY">由于写入权限被拒绝，加密卷 '%s' 不得不以只读模式加载。\n\n请确认没有其它程序（例如，防病毒程序）正在访问加密卷所在的分区/设备。</string>
    <string lang="zh-cn" key="MOUNTED_DEVICE_FORCED_READ_ONLY_WRITE_PROTECTION">加密卷 '%s' 加载为只读模式，这是因为操作系统报告主设备为写保护状态。\n\n请注意，在一些第三方的芯片驱动中，已有错误报告指出可能会造成可写入介质错误的被系统报告为写保护。这个问题并不是由 VeraCrypt 造成。这可以通过更新或卸载当前系统中的任何第三方芯片组驱动（非微软认证）。</string>
    <string lang="zh-cn" key="LIMIT_ENC_THREAD_POOL_NOTE">请注意，超线程技术为每个物理核心提供了多个逻辑核心。当启用了超线程，上面选中的数字表示逻辑处理器数（核心数）。</string>
    <string lang="zh-cn" key="NUMBER_OF_THREADS">%d 线程</string>
    <string lang="zh-cn" key="DISABLED_HW_AES_AFFECTS_PERFORMANCE">请注意，硬件加速 AES 已禁用，这将会影响测试结果（使性能变差）。\n\n要启用硬件加速，请选择〖设置〗-&gt;〖性能〗并禁用相应选项。</string>
    <string lang="zh-cn" key="LIMITED_THREAD_COUNT_AFFECTS_PERFORMANCE">请注意，线程的数目当前受限，这将会影响测试结果（使性能变差）。\n\n要利用处理器的潜能，请选择〖设置〗-&gt;〖性能〗并禁用相应选项。</string>
    <string lang="zh-cn" key="ASK_REMOVE_DEVICE_WRITE_PROTECTION">您想要 VeraCrypt 尝试禁用此分区/设备 的写保护吗？</string>
    <string lang="zh-cn" key="CONFIRM_SETTING_DEGRADES_PERFORMANCE">警告：此设置可能会降低性能。\n\n您确认要使用该设置吗？</string>
    <string lang="zh-cn" key="HOST_DEVICE_REMOVAL_DISMOUNT_WARN_TITLE">警告：VeraCrypt 加密卷已自动卸载</string>
    <string lang="zh-cn" key="HOST_DEVICE_REMOVAL_DISMOUNT_WARN">在您物理卸载或关闭连接到已加载的加密卷前，您应当总是先在 VeraCrypt 中卸载它。\n\n意外发生的卸载通常是由于线缆、驱动器（附件）等导致的。</string>
    <string lang="zh-cn" key="TEST">测试</string>
    <string lang="zh-cn" key="KEYFILE">密钥文件</string>
    <string lang="zh-cn" key="VKEY_08">Backspace</string>
    <string lang="zh-cn" key="VKEY_09">Tab</string>
    <string lang="zh-cn" key="VKEY_0C">Clear</string>
    <string lang="zh-cn" key="VKEY_0D">Enter</string>
    <string lang="zh-cn" key="VKEY_13">Pause</string>
    <string lang="zh-cn" key="VKEY_14">Caps Lock</string>
    <string lang="zh-cn" key="VKEY_20">空格键</string>
    <string lang="zh-cn" key="VKEY_21">Page Up</string>
    <string lang="zh-cn" key="VKEY_22">Page Down</string>
    <string lang="zh-cn" key="VKEY_23">End</string>
    <string lang="zh-cn" key="VKEY_24">Home</string>
    <string lang="zh-cn" key="VKEY_25">左箭头</string>
    <string lang="zh-cn" key="VKEY_26">上箭头</string>
    <string lang="zh-cn" key="VKEY_27">右箭头</string>
    <string lang="zh-cn" key="VKEY_28">下箭头</string>
    <string lang="zh-cn" key="VKEY_29">选择键</string>
    <string lang="zh-cn" key="VKEY_2A">打印键</string>
    <string lang="zh-cn" key="VKEY_2B">Execute Key</string>
    <string lang="zh-cn" key="VKEY_2C">Print Screen</string>
    <string lang="zh-cn" key="VKEY_2D">Insert</string>
    <string lang="zh-cn" key="VKEY_2E">Delete</string>
    <string lang="zh-cn" key="VKEY_5D">Applications Key</string>
    <string lang="zh-cn" key="VKEY_5F">睡眠</string>
    <string lang="zh-cn" key="VKEY_90">Num Lock</string>
    <string lang="zh-cn" key="VKEY_91">Scroll Lock</string>
    <string lang="zh-cn" key="VKEY_A6">浏览器 后退</string>
    <string lang="zh-cn" key="VKEY_A7">浏览器 前进</string>
    <string lang="zh-cn" key="VKEY_A8">浏览器 刷新</string>
    <string lang="zh-cn" key="VKEY_A9">浏览器 停止</string>
    <string lang="zh-cn" key="VKEY_AA">浏览器 搜索</string>
    <string lang="zh-cn" key="VKEY_AB">浏览器 收藏</string>
    <string lang="zh-cn" key="VKEY_AC">浏览器 主页</string>
    <string lang="zh-cn" key="VKEY_AD">静音</string>
    <string lang="zh-cn" key="VKEY_AE">音量加</string>
    <string lang="zh-cn" key="VKEY_AF">音量减</string>
    <string lang="zh-cn" key="VKEY_B0">Next Track</string>
    <string lang="zh-cn" key="VKEY_B1">Previous Track</string>
    <string lang="zh-cn" key="VKEY_B2">Stop Media</string>
    <string lang="zh-cn" key="VKEY_B3">Play/Pause Media</string>
    <string lang="zh-cn" key="VKEY_B4">Start Mail Key</string>
    <string lang="zh-cn" key="VKEY_B5">Select Media Key</string>
    <string lang="zh-cn" key="VKEY_B6">Application 1</string>
    <string lang="zh-cn" key="VKEY_B7">Application 2</string>
    <string lang="zh-cn" key="VKEY_F6">Attn</string>
    <string lang="zh-cn" key="VKEY_F7">CrSel</string>
    <string lang="zh-cn" key="VKEY_F8">ExSel</string>
    <string lang="zh-cn" key="VKEY_FA">播放</string>
    <string lang="zh-cn" key="VKEY_FB">缩放</string>
    <string lang="zh-cn" key="VK_NUMPAD">数字键盘</string>
    <string lang="zh-cn" key="VK_SHIFT">Shift</string>
    <string lang="zh-cn" key="VK_CONTROL">Control</string>
    <string lang="zh-cn" key="VK_ALT">Alt</string>
    <string lang="zh-cn" key="VK_WIN">Win</string>
    <string lang="zh-cn" key="BYTE">B</string>
    <string lang="zh-cn" key="KB">KB</string>
    <string lang="zh-cn" key="MB">MB</string>
    <string lang="zh-cn" key="GB">GB</string>
    <string lang="zh-cn" key="TB">TB</string>
    <string lang="zh-cn" key="PB">PB</string>
    <string lang="zh-cn" key="B_PER_SEC">B/s</string>
    <string lang="zh-cn" key="KB_PER_SEC">KB/s</string>
    <string lang="zh-cn" key="MB_PER_SEC">MB/s</string>
    <string lang="zh-cn" key="GB_PER_SEC">GB/s</string>
    <string lang="zh-cn" key="TB_PER_SEC">TB/s</string>
    <string lang="zh-cn" key="PB_PER_SEC">PB/s</string>
    <string lang="zh-cn" key="TRIPLE_DOT_GLYPH_ELLIPSIS">…</string>
  </localization>
  <!-- XML Schema -->
  <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xs:element name="VeraCrypt">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="localization">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="language">
                  <xs:complexType>
                    <xs:attribute name="langid" type="xs:string" use="required" />
                    <xs:attribute name="name" type="xs:string" use="required" />
                    <xs:attribute name="en-name" type="xs:string" use="required" />
                    <xs:attribute name="version" type="xs:string" use="required" />
                    <xs:attribute name="translators" type="xs:string" use="required" />
                  </xs:complexType>
                </xs:element>
                <xs:element minOccurs="4" maxOccurs="4" name="font">
                  <xs:complexType>
                    <xs:attribute name="lang" type="xs:string" use="required" />
                    <xs:attribute name="class" type="xs:string" use="required" />
                    <xs:attribute name="size" type="xs:unsignedByte" use="required" />
                    <xs:attribute name="face" type="xs:string" use="required" />
                  </xs:complexType>
                </xs:element>
                <xs:element maxOccurs="unbounded" name="control">
                  <xs:complexType>
                    <xs:simpleContent>
                      <xs:extension base="xs:string">
                        <xs:attribute name="lang" type="xs:string" use="required" />
                        <xs:attribute name="key" type="xs:string" use="required" />
                      </xs:extension>
                    </xs:simpleContent>
                  </xs:complexType>
                </xs:element>
                <xs:element maxOccurs="unbounded" name="string">
                  <xs:complexType>
                    <xs:simpleContent>
                      <xs:extension base="xs:string">
                        <xs:attribute name="lang" type="xs:string" use="required" />
                        <xs:attribute name="key" type="xs:string" use="required" />
                      </xs:extension>
                    </xs:simpleContent>
                  </xs:complexType>
                </xs:element>
              </xs:sequence>
              <xs:attribute name="prog-version" type="xs:string" use="required" />
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:schema>
</VeraCrypt>