<?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-Hant" original="../ExtensionResources.resx">
    <body>
      <trans-unit id="ActivationArgumentsInvalidArgumentCount">
        <source>The Microsoft Testing Platform activation-argument payload has an invalid argument count.</source>
        <target state="new">The Microsoft Testing Platform activation-argument payload has an invalid argument count.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsInvalidArgumentLength">
        <source>The Microsoft Testing Platform activation-argument payload has an invalid argument length.</source>
        <target state="new">The Microsoft Testing Platform activation-argument payload has an invalid argument length.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsInvalidFileKey">
        <source>The Microsoft Testing Platform activation arguments contain an invalid file payload key.</source>
        <target state="new">The Microsoft Testing Platform activation arguments contain an invalid file payload key.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsInvalidFileReference">
        <source>The Microsoft Testing Platform activation arguments contain an invalid file payload reference.</source>
        <target state="new">The Microsoft Testing Platform activation arguments contain an invalid file payload reference.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsInvalidInlinePayload">
        <source>The Microsoft Testing Platform activation arguments contain an invalid inline payload.</source>
        <target state="new">The Microsoft Testing Platform activation arguments contain an invalid inline payload.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsMissingPayload">
        <source>The launch activation does not contain Microsoft Testing Platform arguments.</source>
        <target state="new">The launch activation does not contain Microsoft Testing Platform arguments.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsPayloadAuthenticationFailed">
        <source>The Microsoft Testing Platform activation-argument payload failed authentication.</source>
        <target state="new">The Microsoft Testing Platform activation-argument payload failed authentication.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsPayloadReadFailed">
        <source>The Microsoft Testing Platform activation-argument payload could not be read.</source>
        <target state="new">The Microsoft Testing Platform activation-argument payload could not be read.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsPayloadTooLarge">
        <source>The Microsoft Testing Platform activation-argument payload is too large.</source>
        <target state="new">The Microsoft Testing Platform activation-argument payload is too large.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsPayloadTruncated">
        <source>The Microsoft Testing Platform activation-argument payload is truncated.</source>
        <target state="new">The Microsoft Testing Platform activation-argument payload is truncated.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="ActivationArgumentsTrailingData">
        <source>The Microsoft Testing Platform activation-argument payload contains trailing data.</source>
        <target state="new">The Microsoft Testing Platform activation-argument payload contains trailing data.</target>
        <note>Do not localize the technology name {Locked="Microsoft Testing Platform"}.</note>
      </trans-unit>
      <trans-unit id="AmbiguousAppxManifestApplication">
        <source>The packaged app manifest declares multiple applications and none uniquely matches the executable '{0}'. Candidate Application User Model IDs: {1}.</source>
        <target state="translated">封裝的應用程式資訊清單會宣告多個應用程式，且沒有一個能唯一地符合可執行檔 '{0}'。候選應用程式使用者模型識別碼: {1}。</target>
        <note />
      </trans-unit>
      <trans-unit id="AppxManifestApplicationExecutableMismatch">
        <source>The packaged app manifest declares no application for the executable '{0}', so it describes a different application and activating it would target the wrong Application User Model ID. Declared application executables: {1}.</source>
        <target state="translated">封裝的應用程式資訊清單未針對可執行檔 '{0}' 宣告應用程式，因此它描述的是不同的應用程式，而啟用它會將目標指向錯誤的Application User Model ID碼。已宣告的應用程式可執行檔: {1}。</target>
        <note>Do not localize the technology name {Locked="Application User Model ID"}. {0} is an executable path. {1} is a comma-separated list of executable paths.</note>
      </trans-unit>
      <trans-unit id="InvalidAppxManifestMissingIdentity">
        <source>The packaged app manifest does not declare a valid &lt;Identity Name="..." Publisher="..." /&gt; element.</source>
        <target state="translated">封裝的應用程式清單未宣告有效的 &lt;Identity Name="..." Publisher="..." /&gt; 元素。</target>
        <note />
      </trans-unit>
      <trans-unit id="PackagedAppExtensionDescription">
        <source>Registers a packaged MSIX test host and activates it by Application User Model ID (Windows build), delivering Microsoft Testing Platform arguments through argv for packagedClassicApp/win32App hosts (including classic AppContainer hosts) or launch activation for windowsApp/UWP hosts. When opted in through TESTINGPLATFORM_PACKAGEDAPP_LAUNCHER=always, it also deploys a non-packaged (loose-layout) Windows test host to an isolated directory and launches it from there. Enabled only for a packaged layout by default, so an unpackaged app is left on the default launch path. End-to-end AppContainer execution additionally requires controller-pipe authorization. See https://github.com/microsoft/testfx/issues/10486.</source>
        <target state="needs-review-translation">註冊已封裝、完整信任的 MSIX 桌面測試主機，並透過Application User Model ID碼 (Windows 組建)啟用該主機，此外，當透過 TESTINGPLATFORM_PACKAGEDAPP_LAUNCHER=always 選擇啟用時，會將非封裝 (鬆散配置) 的 Windows 測試主機部署至隔離目錄，並從該目錄啟動。預設只會針對封裝配置啟用，因此未封裝的應用程式會保留在預設啟動路徑上。不支援真正的 UWP/AppContainer 主機。請參閱 https://github.com/microsoft/testfx/issues/9933。</target>
        <note>Do not localize the environment variable name or its value {Locked="TESTINGPLATFORM_PACKAGEDAPP_LAUNCHER"}{Locked="always"}, nor the technology names {Locked="Microsoft Testing Platform"}{Locked="MSIX"}{Locked="Application User Model ID"}{Locked="Windows"}{Locked="packagedClassicApp"}{Locked="win32App"}{Locked="windowsApp"}{Locked="UWP"}{Locked="AppContainer"}.</note>
      </trans-unit>
      <trans-unit id="PackagedAppExtensionDisplayName">
        <source>Packaged app test host launcher</source>
        <target state="translated">封裝應用程式測試主機啟動器</target>
        <note />
      </trans-unit>
      <trans-unit id="PackagedAppLaunchNotSupported">
        <source>Cannot launch the packaged Windows app '{0}' (found '{1}'). Registering and activating a packaged (MSIX) app requires the Windows build of this extension, which ships for net8.0-windows10.0.19041.0 and later. Target 'net8.0-windows10.0.19041.0' (or a later net*-windows Target Framework Moniker at platform version 10.0.19041.0 or higher) so NuGet selects that asset. The current build only launches non-packaged (loose-layout) test hosts. See https://github.com/microsoft/testfx/issues/9933.</source>
        <target state="translated">無法啟動已封裝的 Windows 應用程式 '{0}' (找到 '{1}')。若要註冊並啟用已封裝的 (MSIX) 應用程式，需要使用此延伸模組的 Windows 組建，此組建隨 net8.0-windows10.0.19041.0 及更新版本提供。目標為 'net8.0-windows10.0.19041.0' (或平台版本 10.0.19041.0 以上的較新 net*-windows 目標 Framework Moniker)，讓 NuGet 選取該資產。目前的組建只會啟動未封裝 (鬆散配置) 的測試主機。請參閱 https://github.com/microsoft/testfx/issues/9933。</target>
        <note />
      </trans-unit>
      <trans-unit id="PackagedAppNoApplicationToActivate">
        <source>Cannot activate the packaged Windows app '{0}' (found '{1}'): its manifest declares no &lt;Application&gt;, so there is no Application User Model ID to activate.</source>
        <target state="translated">無法啟動已封裝的 Windows 應用程式 '{0}' (找到 '{1}'): 其資訊清單未宣告任何 &lt;Application&gt;，因此沒有可啟用的應用程式使用者模型識別碼。</target>
        <note />
      </trans-unit>
      <trans-unit id="PackagedAppRegistrationFailed">
        <source>Failed to register the packaged Windows app layout '{0}'. Registering an unsigned build-output layout requires Developer Mode (or sideloading) to be enabled. Error: {1}</source>
        <target state="translated">無法註冊已封裝的 Windows 應用程式配置 '{0}'。註冊未簽署的建置輸出配置需要啟用 [開發人員模式] (或側載)。錯誤: {1}</target>
        <note />
      </trans-unit>
    </body>
  </file>
</xliff>