src/MSBuild/Resources/xlf/Strings.zh-Hans.xlf

﻿<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2-transitional.xsd">
  <file datatype="xml" source-language="en" target-language="zh-Hans" original="../Strings.resx">
    <body>
      <trans-unit id="AmbiguousProjectError">
        <source>MSBUILD : error MSB1011: Specify which project or solution file to use because this folder contains more than one project or solution file.</source>
        <target state="translated">MSBUILD : error MSB1011: 此文件夹中包含多个项目或解决方案文件，请指定要使用的项目或解决方案文件。</target>
        <note>{StrBegin="MSBUILD : error MSB1011: "}UE: If no project or solution file is explicitly specified on the MSBuild.exe command-line, then the engine searches for a
      project or solution file in the current directory by looking for *.*PROJ and *.SLN. If more than one file is found that matches this wildcard, we
      fire this error.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
      </trans-unit>
      <trans-unit id="ConfigurationFailurePrefixNoErrorCode">
        <source>MSBUILD : Configuration error {0}: {1}</source>
        <target state="translated">MSBUILD : 配置 error {0}: {1}</target>
        <note>{SubString="Configuration"}UE: This prefixes any error from reading the toolset definitions in msbuild.exe.config or the registry.
      There's no error code because one was included in the error message.
      LOCALIZATION: The word "Configuration" should be localized, the words "MSBuild" and "error" should NOT be localized.
    </note>
      </trans-unit>
      <trans-unit id="CannotAutoDisableAutoResponseFile">
        <source>MSBUILD : error MSB1027: The -noAutoResponse switch cannot be specified in the MSBuild.rsp auto-response file, nor in any response file that is referenced by the auto-response file.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1027: 不能在 MSBuild.rsp 自动响应文件中或由该自动响应文件引用的任何响应文件中指定 /noautoresponse 开关。</target>
        <note>{StrBegin="MSBUILD : error MSB1027: "}LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:", "-noAutoResponse" and "MSBuild.rsp" should not be localized.</note>
      </trans-unit>
      <trans-unit id="CopyrightMessage">
        <source>Microsoft (R) Build Engine version {0} for {1}
Copyright (C) Microsoft Corporation. All rights reserved.
</source>
        <target state="translated">用于 {1} 的 Microsoft (R) 生成引擎版本 {0}
版权所有(C) Microsoft Corporation。保留所有权利。
</target>
        <note>LOCALIZATION: {0} contains the DLL version number. {1} contains the name of a runtime, like ".NET Framework", ".NET Core", or "Mono"</note>
      </trans-unit>
      <trans-unit id="DuplicateProjectSwitchError">
        <source>MSBUILD : error MSB1008: Only one project can be specified.</source>
        <target state="translated">MSBUILD : error MSB1008: 只能指定一个项目。</target>
        <note>{StrBegin="MSBUILD : error MSB1008: "}UE: This happens if the user does something like "msbuild.exe myapp.proj myapp2.proj". This is not allowed.
    MSBuild.exe will only build a single project. The help topic may link to an article about how to author an MSBuild project
    that itself launches MSBuild on a number of other projects.
    LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
      </trans-unit>
      <trans-unit id="FatalError">
        <source>MSBUILD : error MSB1025: An internal failure occurred while running MSBuild.</source>
        <target state="translated">MSBUILD : error MSB1025: 运行 MSBuild 时发生内部错误。</target>
        <note>{StrBegin="MSBUILD : error MSB1025: "}UE: This message is shown when the application has to terminate either because of a bug in the code, or because some
      FX/CLR method threw an unexpected exception.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" and "MSBuild" should not be localized.</note>
      </trans-unit>
      <trans-unit id="HelpMessage_1_Syntax">
        <source>Syntax:              MSBuild.exe [options] [project file | directory]
</source>
        <target state="needs-review-translation">语法:              MSBuild.exe [选项] [项目文件 | 目录]
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_2_Description">
        <source>Description:         Builds the specified targets in the project file. If
                     a project file is not specified, MSBuild searches the
                     current working directory for a file that has a file
                     extension that ends in "proj" and uses that file.  If
                     a directory is specified, MSBuild searches that
                     directory for a project file.
</source>
        <target state="needs-review-translation">描述:         在项目文件中生成指定的目标。如果
                    未指定项目文件，MSBuild 将搜索
                    当前工作目录来查找文件
                    扩展名以“proj”结尾的文件并使用该文件。如果
                     如果指定了目录，MSBuild 将搜索此
                     目录来查找项目文件。
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_34_InteractiveSwitch">
        <source>  -interactive[:True|False]
                     Indicates that actions in the build are allowed to
                     interact with the user.  Do not use this argument
                     in an automated scenario where interactivity is
                     not expected.
                     Specifying -interactive is the same as specifying
                     -interactive:true.  Use the parameter to override a
                     value that comes from a response file.
    </source>
        <target state="new">  -interactive[:True|False]
                     Indicates that actions in the build are allowed to
                     interact with the user.  Do not use this argument
                     in an automated scenario where interactivity is
                     not expected.
                     Specifying -interactive is the same as specifying
                     -interactive:true.  Use the parameter to override a
                     value that comes from a response file.
    </target>
        <note>
      LOCALIZATION: "-interactive" should not be localized.
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_35_IsolateProjectsSwitch">
        <source>  -isolateProjects[:True|False]
                     Causes MSBuild to build each project in isolation.

                     This is a more restrictive mode of MSBuild as it requires
                     that the project graph be statically discoverable at
                     evaluation time, but can improve scheduling and reduce
                     memory overhead when building a large set of projects.
    </source>
        <target state="new">  -isolateProjects[:True|False]
                     Causes MSBuild to build each project in isolation.

                     This is a more restrictive mode of MSBuild as it requires
                     that the project graph be statically discoverable at
                     evaluation time, but can improve scheduling and reduce
                     memory overhead when building a large set of projects.
    </target>
        <note>
      LOCALIZATION: "MSBuild" should not be localized.
      LOCALIZATION: "-isolateProjects" should not be localized.
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.</note>
      </trans-unit>
      <trans-unit id="HelpMessage_3_SwitchesHeader">
        <source>Switches:            Note that you can specify switches using both
                     "-switch" and "/switch".
</source>
        <target state="needs-review-translation">开关:
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_4_HelpSwitch">
        <source>  -help              Display this usage message. (Short form: -? or -h)
</source>
        <target state="needs-review-translation">  /help       显示此用法消息。(缩写: /? 或 /h)
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_5_NoLogoSwitch">
        <source>  -noLogo            Do not display the startup banner and copyright message.
</source>
        <target state="needs-review-translation">  /nologo      不显示启动版权标志和版权消息。
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_6_VersionSwitch">
        <source>  -version           Display version information only. (Short form: -ver)
</source>
        <target state="needs-review-translation">  /version      仅显示版本信息。(缩写: /ver)
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_7_ResponseFile">
        <source>  @&lt;file&gt;            Insert command-line settings from a text file. To specify
                     multiple response files, specify each response file
                     separately.

                     Any response files named "msbuild.rsp" are automatically
                     consumed from the following locations:
                     (1) the directory of msbuild.exe
                     (2) the directory of the first project or solution built
</source>
        <target state="needs-review-translation">  @&lt;file&gt;            从文本文件插入命令行设置。若要指定
                    多个响应文件，请分别指定每个响应
                    文件。

                    自动从以下位置使用任何名为 "msbuild.rsp" 的
                    响应文件:
                    (1) msbuild.exe 的目录
                    (2) 生成的第一个项目或解决方案的目录
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_8_NoAutoResponseSwitch">
        <source>  -noAutoResponse    Do not auto-include any MSBuild.rsp files. (Short form:
                     -noAutoRsp)
</source>
        <target state="needs-review-translation">  /noautoresponse  不自动包括任何 MSBuild.rsp 文件。(缩写:
                    /noautorsp)
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_9_TargetSwitch">
        <source>  -target:&lt;targets&gt;  Build these targets in this project. Use a semicolon or a
                     comma to separate multiple targets, or specify each
                     target separately. (Short form: -t)
                     Example:
                       -target:Resources;Compile
</source>
        <target state="needs-review-translation">  /target:&lt;targets&gt; 在此项目中生成这些目标。使用分号或
                    逗号分隔多个目标，或者分别指定
                    每个目标。(缩写: /t)
                    示例:
                      /target:Resources;Compile
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_10_PropertySwitch">
        <source>  -property:&lt;n&gt;=&lt;v&gt;  Set or override these project-level properties. &lt;n&gt; is
                     the property name, and &lt;v&gt; is the property value. Use a
                     semicolon or a comma to separate multiple properties, or
                     specify each property separately. (Short form: -p)
                     Example:
                       -property:WarningLevel=2;OutDir=bin\Debug\
</source>
        <target state="needs-review-translation">  /property:= 设置或重写这些项目级属性。&lt;n&gt; 是
                    属性名，&lt;v&gt; 为属性值。请使用
                    分号或逗号分隔多个属性，或者
                    分别指定每个属性。(缩写: /p)
                    示例:
                      /property:WarningLevel=2;OutDir=bin\Debug\
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_11_LoggerSwitch">
        <source>  -logger:&lt;logger&gt;   Use this logger to log events from MSBuild. To specify
                     multiple loggers, specify each logger separately.
                     The &lt;logger&gt; syntax is:
                       [&lt;logger class&gt;,]&lt;logger assembly&gt;[;&lt;logger parameters&gt;]
                     The &lt;logger class&gt; syntax is:
                       [&lt;partial or full namespace&gt;.]&lt;logger class name&gt;
                     The &lt;logger assembly&gt; syntax is:
                       {&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
                     The &lt;logger parameters&gt; are optional, and are passed
                     to the logger exactly as you typed them. (Short form: -l)
                     Examples:
                       -logger:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
                       -logger:XMLLogger,C:\Loggers\MyLogger.dll;OutputAsHTML
</source>
        <target state="needs-review-translation">  /logger:&lt;logger&gt; 使用此记录器来记录 MSBuild 中的事件。若要指定
                    多个记录器，请分别指定每个记录器。
                    &lt;logger&gt; 语法为:
                      [&lt;logger class&gt;,]&lt;logger assembly&gt;[;&lt;logger parameters&gt;]
                    &lt;logger class&gt; 语法为:
                      [&lt;partial or full namespace&gt;.]&lt;logger class name&gt;
                    &lt;logger assembly&gt; 语法为:
                      {&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
                    &lt;logger parameters&gt; 是可选的，并按键入的
                    形式原样传递给记录器。(缩写: /l)
                    示例:
                      /logger:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
                      /logger:XMLLogger,C:\Loggers\MyLogger.dll;OutputAsHTML
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_12_VerbositySwitch">
        <source>  -verbosity:&lt;level&gt; Display this amount of information in the event log.
                     The available verbosity levels are: q[uiet], m[inimal],
                     n[ormal], d[etailed], and diag[nostic]. (Short form: -v)
                     Example:
                       -verbosity:quiet
</source>
        <target state="needs-review-translation">  /verbosity:&lt;level&gt; 在事件日志中显示此级别的信息量。
                    可用的详细级别有: q[uiet]、m[inimal]、
                    n[ormal]、d[etailed] 和 diag[nostic]。(缩写: /v)
                    示例:
                      /verbosity:quiet
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_13_ConsoleLoggerParametersSwitch">
        <source>  -consoleLoggerParameters:&lt;parameters&gt;
                     Parameters to console logger. (Short form: -clp)
                     The available parameters are:
                        PerformanceSummary--Show time spent in tasks, targets
                            and projects.
                        Summary--Show error and warning summary at the end.
                        NoSummary--Don't show error and warning summary at the
                            end.
                        ErrorsOnly--Show only errors.
                        WarningsOnly--Show only warnings.
                        NoItemAndPropertyList--Don't show list of items and
                            properties at the start of each project build.
                        ShowCommandLine--Show TaskCommandLineEvent messages
                        ShowTimestamp--Display the Timestamp as a prefix to any
                            message.
                        ShowEventId--Show eventId for started events, finished
                            events, and messages
                        ForceNoAlign--Does not align the text to the size of
                            the console buffer
                        DisableConsoleColor--Use the default console colors
                            for all logging messages.
                        DisableMPLogging-- Disable the multiprocessor
                            logging style of output when running in
                            non-multiprocessor mode.
                        EnableMPLogging--Enable the multiprocessor logging
                            style even when running in non-multiprocessor
                            mode. This logging style is on by default.
                        ForceConsoleColor--Use ANSI console colors even if
                            console does not support it
                        Verbosity--overrides the -verbosity setting for this
                            logger.
                     Example:
                        -consoleLoggerParameters:PerformanceSummary;NoSummary;
                                                 Verbosity=minimal
</source>
        <target state="needs-review-translation">  /consoleloggerparameters:&lt;parameters&gt;
                     控制台记录器的参数。(缩写: /clp)
                     可用的参数有:
                        PerformanceSummary -- 显示在任务、目标和项目上
                            花费的时间。
                        Summary -- 结束时显示错误和警告的摘要。
                        NoSummary -- 结束时不显示错误和警告
                            的摘要。
                        ErrorsOnly -- 仅显示错误。
                        WarningsOnly -- 仅显示警告。
                        NoItemAndPropertyList -- 在开始生成每个项目时不显示
                            项和属性的列表。
                        ShowCommandLine -- 显示 TaskCommandLineEvent 消息
                        ShowTimestamp -- 将时间戳作为所有消息的前缀
                            显示。
                        ShowEventId -- 显示已开始事件、已完成事件和消息
                            的事件 ID
                        ForceNoAlign -- 不将文本与控制台缓冲区的大小
                            匹配
                        DisableConsoleColor -- 将默认控制台颜色
                            用于所有记录消息。
                        DisableMPLogging -- 在非多处理器
                            模式下运行时，禁用输出的多处理器
                            日志记录样式。
                        EnableMPLogging -- 即使在非多处理器
                            模式下运行，也启用多处理器
                            日志记录样式。默认情况下启用此日志记录样式。
                        ForceConsoleColor -- 使用 ANSI 控制台颜色，即使
                            控制台不支持它
                        Verbosity -- 重写此记录器的 /verbosity
                            设置。
                     示例:
                        /consoleloggerparameters:PerformanceSummary;NoSummary;
                                                 Verbosity=minimal
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_14_NoConsoleLoggerSwitch">
        <source>  -noConsoleLogger   Disable the default console logger and do not log events
                     to the console. (Short form: -noConLog)
</source>
        <target state="needs-review-translation">  /noconsolelogger  禁用默认控制台记录器，并且不将事件
                    记录到控制台。(缩写: /noconlog)
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_15_ValidateSwitch">
        <source>  -validate          Validate the project against the default schema. (Short
                     form: -val)

  -validate:&lt;schema&gt; Validate the project against the specified schema. (Short
                     form: -val)
                     Example:
                       -validate:MyExtendedBuildSchema.xsd
</source>
        <target state="needs-review-translation">  /validate          依据默认架构验证项目。(缩写:
                    /val)

 /validate:&lt;schema&gt; 依据指定的架构验证项目。(缩写:
                    /val)
                    示例:
                      /validate:MyExtendedBuildSchema.xsd
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_17_MaximumCPUSwitch">
        <source>  -maxCpuCount[:n]   Specifies the maximum number of concurrent processes to
                     build with. If the switch is not used, the default
                     value used is 1. If the switch is used without a value
                     MSBuild will use up to the number of processors on the
                     computer. (Short form: -m[:n])
      </source>
        <target state="needs-review-translation">  /maxcpucount[:n]   指定用于生成的最大
                    并发进程数。如果未使用开关，则使用的默认值
                    为 1。如果使用开关时不带值，
                    MSBuild 将最多使用计算机上的
                    处理器数。(缩写: /m[:n])
      </target>
        <note>
          LOCALIZATION: "maxCpuCount" should not be localized.
          LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
      </note>
      </trans-unit>
      <trans-unit id="HelpMessage_16_Examples">
        <source>Examples:

        MSBuild MyApp.sln -t:Rebuild -p:Configuration=Release
        MSBuild MyApp.csproj -t:Clean
                             -p:Configuration=Debug;TargetFrameworkVersion=v3.5
    </source>
        <target state="needs-review-translation">示例:

       MSBuild MyApp.sln /t:Rebuild /p:Configuration=Release
       MSBuild MyApp.csproj /t:Clean
                            /p:Configuration=Debug;TargetFrameworkVersion=v3.5
    </target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpPrompt">
        <source>For switch syntax, type "MSBuild -help"</source>
        <target state="needs-review-translation">若要显示开关的语法，请键入“MSBuild /help”</target>
        <note>UE: this message is shown when the user makes a syntax error on the command-line for a switch.
    LOCALIZATION: "MSBuild -help" should not be localized.</note>
      </trans-unit>
      <trans-unit id="HelpMessage_18_DistributedLoggerSwitch">
        <source>  -distributedLogger:&lt;central logger&gt;*&lt;forwarding logger&gt;
                     Use this logger to log events from MSBuild, attaching a
                     different logger instance to each node. To specify
                     multiple loggers, specify each logger separately.
                     (Short form -dl)
                     The &lt;logger&gt; syntax is:
                       [&lt;logger class&gt;,]&lt;logger assembly&gt;[;&lt;logger parameters&gt;]
                     The &lt;logger class&gt; syntax is:
                       [&lt;partial or full namespace&gt;.]&lt;logger class name&gt;
                     The &lt;logger assembly&gt; syntax is:
                       {&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
                     The &lt;logger parameters&gt; are optional, and are passed
                     to the logger exactly as you typed them. (Short form: -l)
                     Examples:
                       -dl:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
                       -dl:MyLogger,C:\My.dll*ForwardingLogger,C:\Logger.dll
</source>
        <target state="needs-review-translation">  /distributedlogger:&lt;central logger&gt;*&lt;forwarding logger&gt;
                    使用此记录器来记录 MSBuild 中的事件，向每个节点
                    附加不同的记录器实例。若要指定
                    多个记录器，请分别指定每个记录器。
                    (缩写 /dl)
                    &lt;logger&gt; 语法为:
                      [&lt;logger class&gt;,]&lt;logger assembly&gt;[;&lt;logger parameters&gt;]
                    &lt;logger class&gt; 语法为:
                      [&lt;partial or full namespace&gt;.]&lt;logger class name&gt;
                    &lt;logger assembly&gt; 语法为:
                      {&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
                    &lt;logger parameters&gt; 是可选的，并按键入的
                    形式原样传递给记录器。(缩写: /l)
                    示例:
                      /dl:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
                      /dl:MyLogger,C:\My.dll*ForwardingLogger,C:\Logger.dll
</target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_19_IgnoreProjectExtensionsSwitch">
        <source>  -ignoreProjectExtensions:&lt;extensions&gt;
                     List of extensions to ignore when determining which
                     project file to build. Use a semicolon or a comma
                     to separate multiple extensions.
                     (Short form: -ignore)
                     Example:
                       -ignoreProjectExtensions:.sln
    </source>
        <target state="needs-review-translation">  /ignoreprojectextensions:&lt;extensions&gt;
                    确定要生成的项目文件时要忽略的
                    扩展名的列表。使用分号或逗号来分隔
                    多个扩展名。
                    (缩写: /ignore)
                    示例:
                      /ignoreprojectextensions:.sln
    </target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_23_ToolsVersionSwitch">
        <source>  -toolsVersion:&lt;version&gt;
                     The version of the MSBuild Toolset (tasks, targets, etc.)
                     to use during build. This version will override the
                     versions specified by individual projects. (Short form:
                     -tv)
                     Example:
                       -toolsVersion:3.5
   </source>
        <target state="needs-review-translation">  /toolsversion:&lt;version&gt;
                    要在生成过程中使用的 MSBuild 工具集(任务、目标等)
                    的版本。此版本将重写
                    个别项目指定的版本。(缩写:
                    /tv)
                    示例:
                      /toolsversion:3.5
   </target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_20_FileLoggerSwitch">
        <source>  -fileLogger[n]     Logs the build output to a file. By default
                     the file is in the current directory and named
                     "msbuild[n].log". Events from all nodes are combined into
                     a single log. The location of the file and other
                     parameters for the fileLogger can be specified through
                     the addition of the "-fileLoggerParameters[n]" switch.
                     "n" if present can be a digit from 1-9, allowing up to
                     10 file loggers to be attached. (Short form: -fl[n])
    </source>
        <target state="needs-review-translation">  /fileLogger[n]     将生成输出记录到文件中。默认情况下，
                    该文件在当前目录中，名称为
                    "msbuild[n].log"。所有节点中的事件合并到
                    单个日志中。fileLogger 的文件和
                    其他参数的位置可以通过添加
                    "/fileLoggerParameters[n]" 开关来指定。
                    "n" (如果存在)可以为 1-9 的数字，允许最多附加
                    10 个文件记录器。(缩写: /fl[n])
    </target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_21_DistributedFileLoggerSwitch">
        <source>  -distributedFileLogger
                     Logs the build output to multiple log files, one log file
                     per MSBuild node. The initial location for these files is
                     the current directory. By default the files are called
                     "MSBuild&lt;nodeid&gt;.log". The location of the files and
                     other parameters for the fileLogger can be specified
                     with the addition of the "-fileLoggerParameters" switch.

                     If a log file name is set through the fileLoggerParameters
                     switch the distributed logger will use the fileName as a
                     template and append the node id to this fileName to
                     create a log file for each node.
    </source>
        <target state="needs-review-translation">  /distributedFileLogger
                    将生成输出记录到多个日志文件，每个 MSBuild 节点
                    一个日志文件。这些文件的初始位置为
                    当前目录。默认情况下，这些文件名为
                    "MSBuild&lt;nodeid&gt;.log"。可通过添加
                    "/fileLoggerParameters" 开关来指定
                    这些文件的位置和 fileLogger 的其他参数。

                    如果日志文件名是通过 fileLoggerParameters
                    开关设置的，分布式记录器将使用 fileName 作为
                    模板并将节点 ID 附加到此 fileName
                    以便为每个节点创建一个日志文件。
    </target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_22_FileLoggerParametersSwitch">
        <source>  -fileLoggerParameters[n]:&lt;parameters&gt;
                     Provides any extra parameters for file loggers.
                     The presence of this switch implies the
                     corresponding -fileLogger[n] switch.
                     "n" if present can be a digit from 1-9.
                     -fileLoggerParameters is also used by any distributed
                     file logger, see description of -distributedFileLogger.
                     (Short form: -flp[n])
                     The same parameters listed for the console logger are
                     available. Some additional available parameters are:
                        LogFile--path to the log file into which the
                            build log will be written.
                        Append--determines if the build log will be appended
                            to or overwrite the log file. Setting the
                            switch appends the build log to the log file;
                            Not setting the switch overwrites the
                            contents of an existing log file.
                            The default is not to append to the log file.
                        Encoding--specifies the encoding for the file,
                            for example, UTF-8, Unicode, or ASCII
                     Default verbosity is Detailed.
                     Examples:
                       -fileLoggerParameters:LogFile=MyLog.log;Append;
                                           Verbosity=diagnostic;Encoding=UTF-8

                       -flp:Summary;Verbosity=minimal;LogFile=msbuild.sum
                       -flp1:warningsonly;logfile=msbuild.wrn
                       -flp2:errorsonly;logfile=msbuild.err
    </source>
        <target state="needs-review-translation">  /fileloggerparameters[n]:&lt;parameters&gt;
                    为文件记录器提供任何额外的参数。
                    存在此开关意味着
                    存在对应的 /filelogger[n] 开关。
                    "n" (如果存在)可以为 1-9 的数字。
                    任何分布式文件记录器也可以使用 /fileloggerparameters，
                    具体可参阅 /distributedFileLogger 的说明。
                    (缩写: /flp[n])
                    为控制台记录器列出的相同参数
                    可用。某些其他可用参数有:
                       LogFile -- 生成日志将写入其中的
                           日志文件的路径。
                       Append -- 确定是将生成日志附加到日志文件，
                           还是覆盖日志文件。如果设置此
                           开关，则会将生成日志附加到日志文件；
                           如果不设置此开关，则会覆盖
                           现有日志文件的内容。
                           默认值为不附加到日志文件。
                       Encoding -- 指定文件的编码，
                           例如，UTF-8、Unicode 或 ASCII
                    默认的详细级别为 Detailed。
                    示例:
                      /fileLoggerParameters:LogFile=MyLog.log;Append;
                                          Verbosity=diagnostic;Encoding=UTF-8

                      /flp:Summary;Verbosity=minimal;LogFile=msbuild.sum
                      /flp1:warningsonly;logfile=msbuild.wrn
                      /flp2:errorsonly;logfile=msbuild.err
    </target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "MSBuild", "MSBuild.exe" and "MSBuild.rsp"
      2) the string "proj" that describes the extension we look for
      3) all switch names and their short forms e.g. -property, or -p
      4) all verbosity levels and their short forms e.g. quiet, or q
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_24_NodeReuse">
        <source>  -nodeReuse:&lt;parameters&gt;
                     Enables or Disables the reuse of MSBuild nodes.
                     The parameters are:
                     True --Nodes will remain after the build completes
                            and will be reused by subsequent builds (default)
                     False--Nodes will not remain after the build completes
                     (Short form: -nr)
                     Example:
                       -nr:true
    </source>
        <target state="needs-review-translation">  /nodeReuse:&lt;parameters&gt;
                    启用或禁止重复使用 MSBuild 节点。
                    参数包括:
                    True -- 生成完成后节点将保留，
                           并且将由后面的生成重复使用(默认)
                    False -- 生成完成后节点将不会保留
                    (缩写: /nr)
                    示例:
                      /nr:true
    </target>
        <note />
      </trans-unit>
      <trans-unit id="HelpMessage_25_PreprocessSwitch">
        <source>  -preprocess[:file]
                     Creates a single, aggregated project file by
                     inlining all the files that would be imported during a
                     build, with their boundaries marked. This can be
                     useful for figuring out what files are being imported
                     and from where, and what they will contribute to
                     the build. By default the output is written to
                     the console window. If the path to an output file
                     is provided that will be used instead.
                     (Short form: -pp)
                     Example:
                       -pp:out.txt
    </source>
        <target state="needs-review-translation">  /preprocess[:file]
                    通过嵌入将在生成过程中导入的
                    所有文件并标记其边界，
                    创建一个聚合的项目文件。这对于
                    了解导入什么文件、从何处导入以及
                    这些文件在生成中的构成
                    非常有用。默认情况下，输出将写入
                    控制台窗口。如果提供输出文件的路径，
                    则将改用该路径。
                    (缩写: /pp)
                    示例:
                      /pp:out.txt
    </target>
        <note />
      </trans-unit>
      <trans-unit id="HelpMessage_26_DetailedSummarySwitch">
        <source>  -detailedSummary
                     Shows detailed information at the end of the build
                     about the configurations built and how they were
                     scheduled to nodes.
                     (Short form: -ds)
    </source>
        <target state="needs-review-translation">  /detailedsummary
                    在生成的结尾显示有关
                    所生成的配置以及如何向节点安排
                    这些配置的详细信息。
                    (缩写: /ds)
    </target>
        <note />
      </trans-unit>
      <trans-unit id="InvalidConfigurationFile">
        <source>MSBUILD : Configuration error MSB1043: The application could not start. {0}</source>
        <target state="translated">MSBUILD : Configuration error MSB1043: 应用程序未能启动。{0}</target>
        <note>
      {StrBegin="MSBUILD : Configuration error MSB1043: "}
      UE: This error is shown when the msbuild.exe.config file had invalid content.
      LOCALIZATION: The prefix "MSBUILD : Configuration error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="InvalidInteractiveValue">
        <source>MSBUILD : error MSB1055: Interactive value is not valid. {0}</source>
        <target state="new">MSBUILD : error MSB1055: Interactive value is not valid. {0}</target>
        <note>
      {StrBegin="MSBUILD : error MSB1055: "}
      UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
      This error is shown when a user specifies a value for the interactive parameter that is not equivalent to Boolean.TrueString or Boolean.FalseString.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="InvalidIsolateProjectsValue">
        <source>MSBUILD : error MSB1056: Isolate projects value is not valid. {0}</source>
        <target state="new">MSBUILD : error MSB1056: Isolate projects value is not valid. {0}</target>
        <note>
      {StrBegin="MSBUILD : error MSB1056: "}
      UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
      This error is shown when a user specifies a value for the -isolateProjects parameter that is not equivalent to Boolean.TrueString or Boolean.FalseString.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="InvalidLoggerError">
        <source>MSBUILD : error MSB1019: Logger switch was not correctly formed.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1019: 记录器开关的格式不正确。</target>
        <note>{StrBegin="MSBUILD : error MSB1019: "}UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
      This error is shown when a user does any of the following:
      msbuild.exe -logger:;"logger parameters"                    (missing logger class and assembly)
      msbuild.exe -logger:loggerclass,                            (missing logger assembly)
      msbuild.exe -logger:loggerclass,;"logger parameters"        (missing logger assembly)
      The correct way to specify a logger is to give both the logger class and logger assembly, or just the logger assembly (logger
      parameters are optional).
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
      </trans-unit>
      <trans-unit id="InvalidMaxCPUCountValue">
        <source>MSBUILD : error MSB1030: Maximum CPU count is not valid. {0}</source>
        <target state="needs-review-translation">MSBUILD : error MSB1030: 最大 CPU 计数无效。{0}</target>
        <note>
      {StrBegin="MSBUILD : error MSB1030: "}
      UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
      This error is shown when a user specifies an invalid CPU value. For example, -m:foo instead of -m:2.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="InvalidMaxCPUCountValueOutsideRange">
        <source>MSBUILD : error MSB1032: Maximum CPU count is not valid. Value must be an integer greater than zero and no more than 1024.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1032: 最大 CPU 计数无效。值必须为大于 0 且小于 1024 的整数。</target>
        <note>{StrBegin="MSBUILD : error MSB1032: "}
      UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
      This error is shown when a user specifies a CPU value that is zero or less. For example, -m:0 instead of -m:2.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="InvalidNodeNumberValue">
        <source>MSBUILD : error MSB1033: Node number is not valid. {0}.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1033: 节点数无效。{0}。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1033: "}
      UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
      This error is shown when a user specifies a CPU value that is zero or less. For example, -nodeMode:foo instead of -nodeMode:2.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="InvalidNodeNumberValueIsNegative">
        <source>MSBUILD : error MSB1034: Node number is not valid. Value must be an integer greater than zero.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1034: 节点数无效。值必须为大于 0 的整数。</target>
        <note>{StrBegin="MSBUILD : error MSB1034: "}
        UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
        This error is shown when a user specifies a CPU value that is zero or less. For example, -nodeMode:0 instead of -nodeMode:2.
        LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
      </note>
      </trans-unit>
      <trans-unit id="InvalidPropertyError">
        <source>MSBUILD : error MSB1006: Property is not valid.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1006: 属性无效。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1006: "}UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
      This error is shown if the user does any of the following:
      msbuild.exe -property:foo              (missing property value)
      msbuild.exe -property:=4               (missing property name)
      The user must pass in an actual property name and value following the switch, as in "msbuild.exe -property:Configuration=Debug".
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="InvalidSchemaFile">
        <source>MSBUILD : MSB1046: The schema "{0}" is not valid. {1}</source>
        <target state="translated">MSBUILD : MSB1046: 架构“{0}”无效。{1}</target>
        <note>{StrBegin="MSBUILD : MSB1046: "}UE: This message is shown when the schema file provided for the validation of a project is itself not valid.
    LOCALIZATION: "{0}" is the schema file path. "{1}" is a message from an FX exception that describes why the schema file is bad.</note>
      </trans-unit>
      <trans-unit id="InvalidSwitchIndicator">
        <source>Switch: {0}</source>
        <target state="needs-review-translation">开关:{0}</target>
        <note>
      UE: This is attached to error messages caused by an invalid switch. This message indicates what the invalid arg was.
      For example, if an unknown switch is passed to MSBuild.exe, the error message will look like this:
      MSBUILD : error MSB1001: Unknown switch.
      Switch: -bogus
      LOCALIZATION: {0} contains the invalid switch text.
    </note>
      </trans-unit>
      <trans-unit id="InvalidToolsVersionError">
        <source>MSBUILD : error MSB1040: ToolsVersion is not valid. {0}</source>
        <target state="needs-review-translation">MSBUILD : error MSB1040: ToolsVersion 无效。{0}</target>
        <note>
      {StrBegin="MSBUILD : error MSB1040: "}
      UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
      This error is shown when a user specifies an unknown toolversion, eg -toolsVersion:99
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="InvalidVerbosityError">
        <source>MSBUILD : error MSB1018: Verbosity level is not valid.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1018: 详细级别无效。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1018: "}UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
      This error is shown when a user specifies an unknown verbosity level e.g. "msbuild -verbosity:foo". The only valid verbosities
      (and their short forms) are: q[uiet], m[inimal], n[ormal], d[etailed], diag[nostic].
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="LoggerFatalError">
        <source>MSBUILD : error MSB1028: The logger failed unexpectedly.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1028: 记录器意外失败。</target>
        <note>{StrBegin="MSBUILD : error MSB1028: "}
      UE: This error is shown when a logger specified with the -logger switch throws an exception while being
      initialized. This message is followed by the exception text including the stack trace.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
      </trans-unit>
      <trans-unit id="LoggerFailurePrefixNoErrorCode">
        <source>MSBUILD : Logger error {0}: {1}</source>
        <target state="translated">MSBUILD: 记录器 error {0}: {1}</target>
        <note>UE: This prefixes the error message emitted by a logger, when a logger fails in a controlled way using a LoggerException.
      For example, the logger is indicating that it could not create its output file.
      There's no error code because one was supplied by the logger.
      LOCALIZATION: The word "Logger" should be localized, the words "MSBuild" and "error" should NOT be localized.
      </note>
      </trans-unit>
      <trans-unit id="LoggerFailurePrefixWithErrorCode">
        <source>MSBUILD : Logger error MSB1029: {0}</source>
        <target state="translated">MSBUILD : 记录器 error MSB1029: {0}</target>
        <note>{SubString="Logger", "{0}"}{StrBegin="MSBUILD : "}
        UE: This prefixes the error message emitted by a logger, when a logger fails in a controlled way using a LoggerException.
        For example, the logger is indicating that it could not create its output file.
        This is like LoggerFailurePrefixNoErrorCode, but the logger didn't supply its own error code, so we have to provide one.
        LOCALIZATION: The word "Logger" should be localized, the words "MSBuild" and "error" should NOT be localized.
      </note>
      </trans-unit>
      <trans-unit id="MissingLoggerError">
        <source>MSBUILD : error MSB1007: Specify a logger.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1007: 请指定记录器。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1007: "}UE: This happens if the user does something like "msbuild.exe -logger". The user must pass in an actual logger class
      following the switch, as in "msbuild.exe -logger:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral".
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="MissingMaxCPUCountError">
        <source>MSBUILD : error MSB1031: Specify the maximum number of CPUs.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1031: 指定最大 CPU 数。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1031: "}UE: This happens if the user does something like "msbuild.exe -m". The user must pass in an actual number like -m:4.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="MissingProjectError">
        <source>MSBUILD : error MSB1003: Specify a project or solution file. The current working directory does not contain a project or solution file.</source>
        <target state="translated">MSBUILD : error MSB1003: 请指定项目或解决方案文件。当前工作目录中未包含项目或解决方案文件。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1003: "}UE: The user must either specify a project or solution file to build, or there must be a project file in the current directory
      with a file extension ending in "proj" (e.g., foo.csproj), or a solution file ending in "sln".
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="MissingPropertyError">
        <source>MSBUILD : error MSB1005: Specify a property and its value.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1005: 请指定属性及其属性值。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1005: "}UE: This happens if the user does something like "msbuild.exe -property". The user must pass in an actual property
      name and value following the switch, as in "msbuild.exe -property:Configuration=Debug".
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="MissingResponseFileError">
        <source>MSBUILD : error MSB1012: Specify a response file.</source>
        <target state="translated">MSBUILD : error MSB1012: 请指定响应文件。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1012: "}UE: This error would occur if the user did something like "msbuild.exe @ foo.proj". The at-sign must be followed by a
      response file.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="MissingTargetError">
        <source>MSBUILD : error MSB1004: Specify the name of the target.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1004: 请指定目标的名称。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1004: "}UE: This happens if the user does something like "msbuild.exe -target". The user must pass in an actual target name
      following the switch, as in "msbuild.exe -target:blah".
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="MissingToolsVersionError">
        <source>MSBUILD : error MSB1039: Specify the version of the toolset.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1039: 指定工具集的版本。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1039: "}
      UE: This happens if the user does something like "msbuild.exe -toolsVersion". The user must pass in an actual toolsversion
      name following the switch, as in "msbuild.exe -toolsVersion:3.5".
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="MissingVerbosityError">
        <source>MSBUILD : error MSB1016: Specify the verbosity level.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1016: 请指定详细级别。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1016: "}UE: This happens if the user does something like "msbuild.exe -verbosity". The user must pass in a verbosity level
      after the switch e.g. "msbuild.exe -verbosity:detailed".
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="MultipleSchemasError">
        <source>MSBUILD : error MSB1024: Only one schema can be specified for validation of the project.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1024: 只能指定一个项目验证架构。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1024: "}UE: The user did something like msbuild -validate:foo.xsd -validate:bar.xsd. We only allow one schema to be specified.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="PickedUpSwitchesFromAutoResponse">
        <source>Some command line switches were read from the auto-response file "{0}". To disable this file, use the "-noAutoResponse" switch.</source>
        <target state="needs-review-translation">将从自动响应文件“{0}”中读取某些命令行开关。若要禁用此文件，请使用“/noautoresponse”开关。</target>
        <note>
      UE: This message appears in high verbosity modes when we used some
      switches from the auto-response file msbuild.rsp: otherwise the user may be unaware
      where the switches are coming from.
    </note>
      </trans-unit>
      <trans-unit id="ProjectNotFoundError">
        <source>MSBUILD : error MSB1009: Project file does not exist.</source>
        <target state="translated">MSBUILD : error MSB1009: 项目文件不存在。</target>
        <note>{StrBegin="MSBUILD : error MSB1009: "}UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
      </trans-unit>
      <trans-unit id="PossiblyOmittedMaxCPUSwitch">
        <source>Building the projects in this solution one at a time. To enable parallel build, please add the "-m" switch.</source>
        <target state="needs-review-translation">在此解决方案中一次生成一个项目。若要启用并行生成，请添加“/m”开关。</target>
        <note />
      </trans-unit>
      <trans-unit id="ProjectSchemaErrorHalt">
        <source>MSBUILD : MSB1045: Stopping because of syntax errors in project file.</source>
        <target state="translated">MSBUILD : MSB1045: 由于项目文件中存在语法错误而正在停止。</target>
        <note>{StrBegin="MSBUILD : MSB1045: "}</note>
      </trans-unit>
      <trans-unit id="ReadResponseFileError">
        <source>MSBUILD : error MSB1023: Cannot read the response file. {0}</source>
        <target state="translated">MSBUILD : error MSB1023: 无法读取响应文件。{0}</target>
        <note>{StrBegin="MSBUILD : error MSB1023: "}UE: This error is shown when the response file cannot be read off disk.
    LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized. {0} contains a localized message explaining
    why the response file could not be read -- this message comes from the CLR/FX.</note>
      </trans-unit>
      <trans-unit id="RepeatedResponseFileError">
        <source>MSBUILD : error MSB1013: The response file was specified twice. A response file can be specified only once. Any files named "msbuild.rsp" in the directory of MSBuild.exe or in the directory of the first project or solution built (which if no project or solution is specified is the current working directory) were automatically used as response files.</source>
        <target state="translated">MSBUILD : error MSB1013: 该响应文件被指定了两次。每个响应文件只能指定一次。MSBuild.exe 的目录中或生成的第一个项目或解决方案目录(如果未指定任何项目或解决方案，则为当前工作目录)中任何名为“msbuild.rsp”的文件自动用作响应文件。</target>
        <note>{StrBegin="MSBUILD : error MSB1013: "}UE: Response files are just text files that contain a bunch of command-line switches to be passed to MSBuild.exe. The
    purpose is so you don't have to type the same switches over and over again ... you can just pass in the response file instead.
    Response files can include the @ switch in order to further include other response files. In order to prevent a circular
    reference here, we disallow the same response file from being included twice. This error message would be followed by the
    exact @ switch that resulted in the duplicate response file.
    LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
      </trans-unit>
      <trans-unit id="ResponseFileNotFoundError">
        <source>MSBUILD : error MSB1022: Response file does not exist.</source>
        <target state="translated">MSBUILD : error MSB1022: 响应文件不存在。</target>
        <note>{StrBegin="MSBUILD : error MSB1022: "}UE: This message would show if the user did something like "msbuild @bogus.rsp" where bogus.rsp doesn't exist. This
    message does not need in-line parameters because the exception takes care of displaying the invalid arg.
    LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
      </trans-unit>
      <trans-unit id="SchemaFileLocation">
        <source>Validating project using schema file "{0}".</source>
        <target state="translated">正在使用架构文件“{0}”验证项目。</target>
        <note>LOCALIZATION: "{0}" is the location of the schema file.</note>
      </trans-unit>
      <trans-unit id="SchemaValidationError">
        <source>MSBUILD : MSB1044: Project is not valid. {0}</source>
        <target state="needs-review-translation">MSBUILD : MSB1044: 项目无效。{0}</target>
        <note>{StrBegin="MSBUILD : MSB1044: "}UE: This error is shown when the user asks his project to be validated against a schema (-val switch for
    MSBuild.exe), and the project has errors. "{0}" contains a message explaining the problem.
    LOCALIZATION: "{0}" is a message from the System.XML schema validator and is already localized.</note>
      </trans-unit>
      <trans-unit id="SchemaNotFoundError">
        <source>MSBUILD : error MSB1026: Schema file does not exist.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1026: 架构文件不存在。</target>
        <note>{StrBegin="MSBUILD : error MSB1026: "}UE: This error is shown when the user specifies a schema file using the -validate:&lt;schema&gt; switch, and the file
    does not exist on disk. This message does not need in-line parameters because the exception takes care of displaying the
    invalid arg.
    LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
      </trans-unit>
      <trans-unit id="SchemaNotFoundErrorWithFile">
        <source>MSBUILD : error MSB1026: Schema file '{0}' does not exist.</source>
        <target state="translated">MSBUILD : error MSB1026: 架构文件“{0}”不存在。</target>
        <note>{StrBegin="MSBUILD : error MSB1026: "}UE: This error is printed if the default schema does not exist or in the extremely unlikely event
    that an explicit schema file was passed and existed when the command line parameters were checked but was deleted from disk before this check was made.
    LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
      </trans-unit>
      <trans-unit id="UnexpectedParametersError">
        <source>MSBUILD : error MSB1002: This switch does not take any parameters.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1002: 此开关不采用任何参数。</target>
        <note>{StrBegin="MSBUILD : error MSB1002: "}UE: For example, if somebody types "msbuild.exe -noLogo:1", they would get this error because the -noLogo switch
    should not be followed by any parameters ... it stands alone.
    LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
      </trans-unit>
      <trans-unit id="UnknownSwitchError">
        <source>MSBUILD : error MSB1001: Unknown switch.</source>
        <target state="translated">MSBUILD : error MSB1001: 未知开关。</target>
        <note>{StrBegin="MSBUILD : error MSB1001: "}UE: This occurs when the user passes in an unrecognized switch on the MSBuild.exe command-line.
    LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
      </trans-unit>
      <trans-unit id="UnsupportedOS">
        <source>MSBUILD : error MSB1015: MSBuild does not run on this version of the operating system. It is only supported on Windows 2000, Windows XP, and later versions.</source>
        <target state="translated">MSBUILD : error MSB1015: MSBuild 不能在此版本的操作系统上运行。它仅在 Windows 2000、Windows XP 及更高版本的操作系统上受支持。</target>
        <note>{StrBegin="MSBUILD : error MSB1015: "}LOCALIZATION: The error prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
      </trans-unit>
      <trans-unit id="Using35Engine">
        <source>Forcing load of Microsoft.Build.Engine because MSBUILDOLDOM=1...</source>
        <target state="translated">强制加载 Microsoft.Build.Engine，因为 MSBUILDOLDOM=1...</target>
        <note />
      </trans-unit>
      <trans-unit id="MissingIgnoreProjectExtensionsError">
        <source>MSBUILD : error MSB1035: Specify the project extensions to ignore.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1035: 指定要忽略的项目扩展名。</target>
        <note>{StrBegin="MSBUILD : error MSB1035: "}
      UE: This happens if the user does something like "msbuild.exe -ignoreProjectExtensions". The user must pass in one or more
      project extensions to ignore e.g. "msbuild.exe -ignoreProjectExtensions:.sln".
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="InvalidExtensionToIgnore">
        <source>MSBUILD : error MSB1036: There is an invalid extension in the -ignoreProjectExtensions list. Extensions must start with a period ".", have one or more characters after the period and not contain any invalid path characters or wildcards.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1036: /ignoreprojectextensions 列表中存在无效扩展名。扩展名必须以句点“.”开头，句点后有一个或多个字符，并且不包含任何无效的路径字符或通配符。</target>
        <note>{StrBegin="MSBUILD : error MSB1036: "}LOCALIZATION: The error prefix "MSBUILD : error MSBxxxx:" should not be localized.</note>
      </trans-unit>
      <trans-unit id="MissingConsoleLoggerParameterError">
        <source>MSBUILD : error MSB1037: Specify one or more parameters for the console logger if using the -consoleLoggerParameters switch</source>
        <target state="needs-review-translation">MSBUILD : error MSB1037: 为控制台记录器指定一个或多个参数(如果使用 /consoleLoggerParameters 开关)</target>
        <note>{StrBegin="MSBUILD : error MSB1037: "}
      UE: This happens if the user does something like "msbuild.exe -consoleLoggerParameters:". The user must pass in one or more parameters
      after the switch e.g. "msbuild.exe -consoleLoggerParameters:ErrorSummary".
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="MissingFileLoggerParameterError">
        <source>MSBUILD : error MSB1038: Specify one or more parameters for the file logger if using the -fileLoggerParameters switch</source>
        <target state="needs-review-translation">MSBUILD : error MSB1038: 为文件记录器指定一个或多个参数(如果使用 /fileLoggerParameters 开关)</target>
        <note>{StrBegin="MSBUILD : error MSB1038: "}
      UE: This happens if the user does something like "msbuild.exe -fileLoggerParameters:". The user must pass in one or more parameters
      after the switch e.g. "msbuild.exe -fileLoggerParameters:logfile=c:\temp\logfile".
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="MissingNodeReuseParameterError">
        <source>MSBUILD : error MSB1041: Specify one or more parameters for node reuse if using the -nodeReuse switch</source>
        <target state="needs-review-translation">MSBUILD : error MSB1041: 为节点重用指定一个或多个参数(如果使用 /nodereuse 开关)</target>
        <note>{StrBegin="MSBUILD : error MSB1041: "}
      UE: This happens if the user does something like "msbuild.exe -nodeReuse:" without a true or false
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
     </note>
      </trans-unit>
      <trans-unit id="InvalidNodeReuseValue">
        <source>MSBUILD : error MSB1042: Node reuse value is not valid. {0}.</source>
        <target state="translated">MSBUILD : error MSB1042: 节点重用值无效。{0}。</target>
        <note>{StrBegin="MSBUILD : error MSB1042: "}
     UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
     This error is shown when a user specifies a node reuse value that is not equivilant to Boolean.TrueString or Boolean.FalseString.
     LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
  </note>
      </trans-unit>
      <trans-unit id="AbortingBuild">
        <source>Attempting to cancel the build...</source>
        <target state="translated">正在尝试取消生成...</target>
        <note />
      </trans-unit>
      <trans-unit id="InvalidPreprocessPath">
        <source>MSBUILD : error MSB1047: File to preprocess to is not valid. {0}</source>
        <target state="translated">MSBUILD : error MSB1047: 要预处理的文件无效。{0}</target>
        <note>{StrBegin="MSBUILD : error MSB1047: "}</note>
      </trans-unit>
      <trans-unit id="LoggerCreationError">
        <source>MSBUILD : error MSB1021: Cannot create an instance of the logger. {0}</source>
        <target state="translated">MSBUILD : error MSB1021: 无法创建记录器的实例。{0}</target>
        <note>{StrBegin="MSBUILD : error MSB1021: "}
      UE: This error is shown when a logger cannot be loaded and instantiated from its assembly.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized. {0} contains a message explaining why the
      logger could not be created -- this message comes from the CLR/FX and is localized.</note>
      </trans-unit>
      <trans-unit id="LoggerNotFoundError">
        <source>MSBUILD : error MSB1020: The logger was not found. Check the following: 1.) The logger name specified is the same as the name of the logger class. 2.) The logger class is "public" and implements the Microsoft.Build.Framework.ILogger interface. 3.) The path to the logger assembly is correct, or the logger can be loaded using only the assembly name provided.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1020: 找不到记录器。请检查下列各项: 1.)指定的记录器名称与记录器类的名称相同。2.)记录器类为“public”并且实现 Microsoft.Build.Framework.ILogger 接口。3.)记录器程序集的路径正确无误，或者只使用所提供的程序集名称就可以加载记录器。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1020: "}UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
      This error is shown when a user specifies an logger that does not exist e.g. "msbuild -logger:FooLoggerClass,FooAssembly". The
      logger class must exist in the given assembly.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="ProjectUpgradeNeededToVcxProj">
        <source>MSBUILD : error MSB4192: The project file "{0}" is in the ".vcproj" or ".dsp" file format, which MSBuild cannot build directly. Please convert the project by opening it in the Visual Studio IDE or running the conversion tool, or, for ".vcproj", use MSBuild to build the solution file containing the project instead.</source>
        <target state="translated">MSBUILD : error MSB4192: 项目文件“{0}”为“.vcproj”或“.dsp”文件格式，而 MSBuild 无法直接生成这些文件格式。请通过在 Visual Studio IDE 中打开该项目或运行转换工具来转换该项目；对于“.vcproj”格式，还可以使用 MSBuild 来生成包含该项目的解决方案文件。</target>
        <note>{StrBegin="MSBUILD : error MSB4192: "} LOC: ".vcproj" and ".dsp" should not be localized</note>
      </trans-unit>
      <trans-unit id="NeedJustMyCode">
        <source>If MSBuild debugging does not work correctly, please verify that the "Just My Code" feature is enabled in Visual Studio, and that you have selected the managed debugger.</source>
        <target state="translated">如果 MSBuild 调试无法正常工作，请验证 Visual Studio 中是否已启用“仅我的代码”功能，以及您是否选择了托管调试器。</target>
        <note />
      </trans-unit>
      <trans-unit id="DebuggingSolutionFiles">
        <source>MSBUILD : error MSB1048: Solution files cannot be debugged directly. Run MSBuild first with an environment variable MSBUILDEMITSOLUTION=1 to create a corresponding ".sln.metaproj" file. Then debug that.</source>
        <target state="translated">MSBUILD : error MSB1048: 无法直接调试解决方案文件。首先使用环境变量 MSBUILDEMITSOLUTION=1 运行 MSBuild 以创建对应的“.sln.metaproj”文件。然后进行调试。</target>
        <note>{StrBegin="MSBUILD : error MSB1048: "} LOC: ".SLN" should not be localized</note>
      </trans-unit>
      <trans-unit id="BuildStarted">
        <source>Build started.</source>
        <target state="translated">已启动生成。</target>
        <note />
      </trans-unit>
      <trans-unit id="FileLocation">
        <source>{0} ({1},{2})</source>
        <target state="translated">{0} ({1},{2})</target>
        <note>A file location to be embedded in a string.</note>
      </trans-unit>
      <trans-unit id="AmbiguousProjectDirectoryError">
        <source>MSBUILD : error MSB1050: Specify which project or solution file to use because the folder "{0}" contains more than one project or solution file.</source>
        <target state="translated">MSBUILD : error MSB1050: “{0}”文件夹中包含多个项目或解决方案文件，请指定要使用的项目或解决方案文件。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1050: "}UE: If no project or solution file is explicitly specified on the MSBuild.exe command-line, then the engine searches for a
      project or solution file in the current directory by looking for *.*PROJ and *.SLN. If more than one file is found that matches this wildcard, we
      fire this error.
      LOCALIZATION: The prefix "MSB1050 : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_28_WarnAsErrorSwitch">
        <source>  -warnAsError[:code[;code2]]
                     List of warning codes to treats as errors.  Use a semicolon
                     or a comma to separate multiple warning codes. To treat all
                     warnings as errors use the switch with no values.
                     (Short form: -err[:c;[c2]])

                     Example:
                       -warnAsError:MSB4130

                     When a warning is treated as an error the target will
                     continue to execute as if it was a warning but the overall
                     build will fail.
    </source>
        <target state="needs-review-translation">  /warnaserror[:code[;code2]]
                     视为错误的警告代码列表。使用分号
                     或逗号分隔多个警告代码。将所有
                     警告视为错误，使用没有值的开关
                     (缩写: /err[:c;[c2]])

                     示例:
                       /warnaserror:MSB4130

                     当警告被视为错误时，目标将
                     当作警告继续执行，但是整个
                     生成将失败。
    </target>
        <note>
      LOCALIZATION: "-warnAsError" and "-err" should not be localized.
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_29_WarnAsMessageSwitch">
        <source>  -warnAsMessage[:code[;code2]]
                     List of warning codes to treats as low importance
                     messages.  Use a semicolon or a comma to separate
                     multiple warning codes.
                     (Short form: -noWarn[:c;[c2]])

                     Example:
                       -warnAsMessage:MSB3026
    </source>
        <target state="needs-review-translation">  /warnasmessage[:code[;code2]]
                     视为低重要性消息的警告代码列表。
                     使用分号或逗号分隔
                     多个警告代码。
                     (缩写: /nowarn[:c;[c2]])

                     示例:
                       /warnasmessage:MSB3026
    </target>
        <note>
      LOCALIZATION: "-warnAsMessage" and "-noWarn" should not be localized.
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="ParameterRequiredError">
        <source>MSBUILD : error MSB1049: The {0} parameter must be specified</source>
        <target state="translated">MSBUILD : error MSB1049: 必须指定 {0} 参数</target>
        <note>{StrBegin="MSBUILD : error MSB1049: "}</note>
      </trans-unit>
      <trans-unit id="MissingWarnAsMessageParameterError">
        <source>MSBUILD : error MSB1051: Specify one or more warning codes to treat as low importance messages when using the -warnAsMessage switch.</source>
        <target state="needs-review-translation">MSBUILD : error MSB1051: 在使用 /warnasmessage 开关时，指定一个或多个警告代码作为低重要性消息。</target>
        <note>
      {StrBegin="MSBUILD : error MSB1051: "}
      UE: This happens if the user does something like "msbuild.exe -warnAsMessage:" without any codes.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_30_BinaryLoggerSwitch">
        <source>  -binaryLogger[:[LogFile=]output.binlog[;ProjectImports={None,Embed,ZipFile}]]
                     Serializes all build events to a compressed binary file.
                     By default the file is in the current directory and named
                     "msbuild.binlog". The binary log is a detailed description
                     of the build process that can later be used to reconstruct
                     text logs and used by other analysis tools. A binary log
                     is usually 10-20x smaller than the most detailed text
                     diagnostic-level log, but it contains more information.
                     (Short form: -bl)

                     The binary logger by default collects the source text of
                     project files, including all imported projects and target
                     files encountered during the build. The optional
                     ProjectImports switch controls this behavior:

                      ProjectImports=None     - Don't collect the project
                                                imports.
                      ProjectImports=Embed    - Embed project imports in the
                                                log file.
                      ProjectImports=ZipFile  - Save project files to
                                                output.projectimports.zip
                                                where output is the same name
                                                as the binary log file name.

                     The default setting for ProjectImports is Embed.
                     Note: the logger does not collect non-MSBuild source files
                     such as .cs, .cpp etc.

                     A .binlog file can be "played back" by passing it to
                     msbuild.exe as an argument instead of a project/solution.
                     Other loggers will receive the information contained
                     in the log file as if the original build was happening.
                     You can read more about the binary log and its usages at:
                     https://github.com/Microsoft/msbuild/wiki/Binary-Log

                     Examples:
                       -bl
                       -bl:output.binlog
                       -bl:output.binlog;ProjectImports=None
                       -bl:output.binlog;ProjectImports=ZipFile
                       -bl:..\..\custom.binlog
                       -binaryLogger
    </source>
        <target state="needs-review-translation">  /binaryLogger[:[LogFile=]output.binlog[;ProjectImports={None,Embed,ZipFile}]]
                     将所有生成事件序列化为压缩的二进制文件。
                     默认情况下该文件位于当前目录并且名为 "msbuild.binlog"。
                     二进制日志是生成过程的详细描述，
                     以后可将其于重新构建文本日志
                     并由其他分析工具所使用。
                     二进制日志通常比大多数详细的文本诊断级日志小 10 到 20 倍，
                     但它可以包含更多信息。
                     (缩写: /bl)

                     默认情况下，二进制记录器收集项目文件的源文本，
                     包括生成期间所有导入的
                     项目和目标文件。可选的
                     ProjectImports 开关控制此行为:


                      ProjectImports=None     - 不收集项目
                                                导入项。
                      ProjectImports=Embed    - 在日志文件中
                                                嵌入项目导入项。
                      ProjectImports=ZipFile  - 将项目文件保存到
                                                output.projectimports.zip，
                                                其中输出的名称
                                                与二进制日志文件名称相同。

                     ProjectImports 的默认设置为 Embed。
                     注意: 记录器不会收集非 MSBuild 源文件，
                     例如 .cs、.cpp 等。

                     可将 .binlog 文件以参数（而不是项目/解决方案）的形式传递给
                     msbuild.exe 对其进行“播放”。
                     其他记录器将接收日志文件中的信息，
                     就像原始的生成正在发生一样。
                     你可以通过以下网址阅读有关二进制文件及其用法的详细信息:
                     https://github.com/Microsoft/msbuild/wiki/Binary-Log

                     示例:
                       /bl
                       /bl:output.binlog
                       /bl:output.binlog;ProjectImports=None
                       /bl:output.binlog;ProjectImports=ZipFile
                       /bl:..\..\custom.binlog
                       /binaryLogger
    </target>
        <note>
      LOCALIZATION: The following should not be localized:
      1) "msbuild"
      2) the string "binlog" that describes the file extension
      3) all switch names and their short forms e.g. -bl and -binaryLogger
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_31_RestoreSwitch">
        <source>  -restore[:True|False]
                     Runs a target named Restore prior to building
                     other targets and ensures the build for these
                     targets uses the latest restored build logic.
                     This is useful when your project tree requires
                     packages to be restored before it can be built.
                     Specifying -restore is the same as specifying
                     -restore:True. Use the parameter to override
                     a value that comes from a response file.
                     (Short form: -r)
    </source>
        <target state="needs-review-translation">  /restore[:True|False]
                     在生成其他目标前，运行名为 Restore 的目标。
                     当系统树需要先将包还原才能生成包时，
                     将会用到此操作。
                     指定 /restore 与指定
                     /restore:True 等同。请使用此参数
                     替代来自响应文件的值。
                     (缩写: /r)
    </target>
        <note>
      LOCALIZATION: "-restore" and "-r" should not be localized.
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="InvalidNodeReuseTrueValue">
        <source>MSBUILD : error MSB1042: Node reuse value is not valid. This version of MSBuild does not support node reuse. If specified, the node reuse switch value must be false.</source>
        <target state="translated">MSBUILD: 错误 MSB1042: 节点重复使用值无效。此版本的 MSBuild 不支持节点重复使用。若已指定，则节点重复使用开关值必须为 false。</target>
        <note>{StrBegin="MSBUILD : error MSB1042: "}
     UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
     This error is shown when a user specifies a node reuse value that is not equivalent to Boolean.TrueString or Boolean.FalseString.
     LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
  </note>
      </trans-unit>
      <trans-unit id="InvalidRestoreValue">
        <source>MSBUILD : error MSB1052: Restore value is not valid. {0}</source>
        <target state="translated">MSBUILD: 错误 MSB1052: 还原值无效。{0}</target>
        <note>{StrBegin="MSBUILD : error MSB1052: "}
      UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
      This error is shown when a user specifies a restore value that is not equivalent to Boolean.TrueString or Boolean.FalseString.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
    </note>
      </trans-unit>
      <trans-unit id="HelpMessage_32_ProfilerSwitch">
        <source>  -profileEvaluation:&lt;file&gt;
                     Profiles MSBuild evaluation and writes the result
                     to the specified file. If the extension of the specified
                     file is '.md', the result is generated in markdown
                     format. Otherwise, a tab separated file is produced.
    </source>
        <target state="needs-review-translation">  /profileevaluation:&lt;file&gt;
                     解析 MSBuild 评估并将结果写入
                     指定文件。如果指定文件的扩展名
                     为“.md”，则结果将以 markdown 格式
                     生成。否则，将生成制表符分隔文件。
    </target>
        <note />
      </trans-unit>
      <trans-unit id="HelpMessage_33_RestorePropertySwitch">
        <source>  -restoreProperty:&lt;n&gt;=&lt;v&gt;
                     Set or override these project-level properties only
                     during restore and do not use properties specified
                     with the -property argument. &lt;n&gt; is the property
                     name, and &lt;v&gt; is the property value. Use a
                     semicolon or a comma to separate multiple properties,
                     or specify each property separately.
                     (Short form: -rp)
                     Example:
                       -restoreProperty:IsRestore=true;MyProperty=value
    </source>
        <target state="needs-review-translation">  /restoreProperty:&lt;n&gt;=&lt;v&gt;
                     在还原期间仅设置或重写这些项目级
                     属性并且不使用通过
                     /property 参数指定的属性。&lt;n&gt; 是属性
                     名，&lt;v&gt; 是属性值。请使用
                     分号或逗号分隔多个属性，
                     或分别指定每个属性。
                     (缩写: /rp)
                     示例:
                       /restoreProperty:IsRestore=true;MyProperty=value
    </target>
        <note>
      LOCALIZATION: "-restoreProperty" and "-rp" should not be localized.
      LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
    </note>
      </trans-unit>
      <trans-unit id="InvalidProfilerValue">
        <source>MSBUILD : error MSB1053: Provided filename is not valid. {0}</source>
        <target state="translated">MSBUILD : 错误 MSB1053: 提供的文件名无效。{0}</target>
        <note />
      </trans-unit>
      <trans-unit id="MissingProfileParameterError">
        <source>MSBUILD :error MSB1054: A filename must be specified to generate the profiler result.</source>
        <target state="translated">MSBUILD :错误 MSB1054: 必须指定文件名才可生成探查器结果。</target>
        <note />
      </trans-unit>
    </body>
  </file>
</xliff>