dotnet
/
msbuild
зеркало из https://github.com/dotnet/msbuild.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность

Localized file check-in by OneLocBuild Task: Build definition ID 9434: Build ID 10462874 (#10893)

This commit is contained in:
dotnet bot 2024-10-29 11:44:53 +01:00 коммит произвёл GitHub
Родитель 4f7bb623e6
Коммит 0c2c2ce93d
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: B5690EEEBB952194
33 изменённых файлов: 735 добавлений и 709 удалений
Показать статистику Скачать Patch файл Скачать Diff файл Показать все файлы Свернуть все файлы

2
src/Build/Resources/xlf/Strings.cs.xlf сгенерированный
Просмотреть файл

@ -1767,7 +1767,7 @@ Chyby: {3}</target>
</trans-unit>
<trans-unit id="SolutionVenusProjectSkipped">
<source>Skipping because the "$(AspNetConfiguration)" configuration is not supported for this web project. You can use the AspNetConfiguration property to override the configuration used for building web projects, by adding /p:AspNetConfiguration=&lt;value&gt; to the command line. Currently web projects only support Debug and Release configurations.</source>
<target state="translated">Vynecháno, protože konfigurace "$(AspNetConfiguration)" není pro tento webový projekt podporována. Pomocí vlastnosti AspNetConfiguration můžete přepsat konfiguraci používanou k sestavování webových projektů, a to přidáním příkazu /p:AspNetConfiguration=&lt;hodnota&gt; do příkazového řádku. Webové projekty nyní podporují pouze konfigurace Debug a Release.</target>
<target state="translated">Vynecháno, protože konfigurace $(AspNetConfiguration) není pro tento webový projekt podporována. Pomocí vlastnosti AspNetConfiguration můžete přepsat konfiguraci používanou k sestavování webových projektů, a to přidáním příkazu /p:AspNetConfiguration=&lt;hodnota&gt; do příkazového řádku. Webové projekty nyní podporují pouze konfigurace Debug a Release.</target>
<note>
UE: This is not an error, so doesn't need an error code.
LOCALIZATION: Do NOT localize "AspNetConfiguration", "Debug", "Release".

10
src/Build/Resources/xlf/Strings.de.xlf сгенерированный
Просмотреть файл

@ -294,7 +294,7 @@
</trans-unit>
<trans-unit id="CustomCheckBaseTypeNotAssignable">
<source>Failed to load the custom check type: '{0}' from the assembly: '{1}'. Make sure it inherits the Microsoft.Build.Experimental.BuildCheck.Check base class. If it is not intended to be a custom check, than it should not be exposed. More info: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</source>
<target state="translated">Fehler beim Laden des benutzerdefinierten Prüftyps „{0}“ aus der Assembly: {1}. Stellen Sie sicher, dass sie die Basisklasse „Microsoft.Build.Experimental.BuildCheck.Check“ erbt. Wenn es sich nicht um eine benutzerdefinierte Überprüfung handelt, sollte sie nicht verfügbar gemacht werden. Weitere Informationen: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<target state="translated">Fehler beim Laden des benutzerdefinierten Prüftyps „{0}“ aus der Assembly: {1}. Stellen Sie sicher, dass es die Basisklasse „Microsoft.Build.Experimental.BuildCheck.Check“ erbt. Wenn es sich nicht um eine benutzerdefinierte Überprüfung handelt, sollte es nicht verfügbar gemacht werden. Weitere Informationen: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<note>The message is emitted when the custom check assembly can not be successfully registered.</note>
</trans-unit>
<trans-unit id="CustomCheckFailedAcquisition">
@ -309,7 +309,7 @@
</trans-unit>
<trans-unit id="CustomCheckRegistered">
<source>The custom check: '{0}' is registered for the build from the location: '{1}'.</source>
<target state="translated">Dies benutzerdefinierte Überprüfung „{0}“ ist für den Build von folgendem Speicherort aus registriert: „{1}”.</target>
<target state="translated">Dies benutzerdefinierte Überprüfung „{0}“ ist für den Build vom Folgenden aus registriert: „{1}”.</target>
<note />
</trans-unit>
<trans-unit id="CustomCheckSuccessfulAcquisition">
@ -380,7 +380,7 @@
</trans-unit>
<trans-unit id="IllegalCharactersInFileOrDirectory">
<source>There are illegal characters in '{0}' in the {1} item.</source>
<target state="translated">Unzulässige Zeichen in „{0}“ im Element {1}.</target>
<target state="translated">Unzulässige Zeichen in „{0}“ im {1}-Element.</target>
<note />
</trans-unit>
<trans-unit id="ImportedProjectFromVSDistribution">
@ -633,7 +633,7 @@
<source>The "{0}" resolver attempted to resolve the SDK "{1}".
Warnings: {2}
Errors: {3}</source>
<target state="translated">Der Konfliktlöser "{0}" hat versucht, das SDK "{1}" aufzulösen.
<target state="translated">Der Konfliktlöser „{0}“ hat versucht, das SDK „{1}“ aufzulösen.
Warnungen: {2}
Fehler: {3}</target>
<note>
@ -759,7 +759,7 @@ Fehler: {3}</target>
<trans-unit id="UnhandledMSBuildError">
<source>This is an unhandled exception in MSBuild -- PLEASE UPVOTE AN EXISTING ISSUE OR FILE A NEW ONE AT https://aka.ms/msbuild/unhandled
{0}</source>
<target state="translated">Dies ist ein Ausnahmefehler in MSBuild. STIMMEN SIE EINEM VORHANDENEN ISSUE ZU, ODER ERSTELLEN SIE EIN NEUES ISSUE UNTER https://aka.ms/msbuild/unhandled
<target state="translated">Dies ist eine nicht behandelte Ausnahme in MSBuild. RUFEN SIE EIN VORHANDENES PROBLEM AUF, ODER ERSTELLEN SIE EIN NEUES UNTER https://aka.ms/msbuild/unhandled
{0}</target>
<note />
</trans-unit>

6
src/Build/Resources/xlf/Strings.es.xlf сгенерированный
Просмотреть файл

@ -294,7 +294,7 @@
</trans-unit>
<trans-unit id="CustomCheckBaseTypeNotAssignable">
<source>Failed to load the custom check type: '{0}' from the assembly: '{1}'. Make sure it inherits the Microsoft.Build.Experimental.BuildCheck.Check base class. If it is not intended to be a custom check, than it should not be exposed. More info: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</source>
<target state="translated">No se pudo cargar el tipo de comprobación personalizada: "{0}" desde el ensamblado: "{1}". Asegúrese de que hereda la clase base Microsoft.Build.Experimental.BuildCheck.Check. Si no se pretende que sea una comprobación personalizada, no debe exponerse. Más información: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<target state="translated">No se pudo cargar el tipo de comprobación personalizado: "{0}" desde el ensamblado: "{1}". Asegúrese de que hereda la clase base Microsoft.Build.Experimental.BuildCheck.Check. Si no está pensado para ser una comprobación personalizada, no debe exponerse. Más información: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<note>The message is emitted when the custom check assembly can not be successfully registered.</note>
</trans-unit>
<trans-unit id="CustomCheckFailedAcquisition">
@ -380,7 +380,7 @@
</trans-unit>
<trans-unit id="IllegalCharactersInFileOrDirectory">
<source>There are illegal characters in '{0}' in the {1} item.</source>
<target state="translated">Hay caracteres no válidos en "{0}" en el elemento {1}.</target>
<target state="translated">Hay caracteres no válidos en '{0}' en el elemento {1}.</target>
<note />
</trans-unit>
<trans-unit id="ImportedProjectFromVSDistribution">
@ -633,7 +633,7 @@
<source>The "{0}" resolver attempted to resolve the SDK "{1}".
Warnings: {2}
Errors: {3}</source>
<target state="translated">El solucionador "{0}" intentó resolver el SDK "{1}".
<target state="translated">El resolvedor "{0}" intentó resolver el SDK "{1}".
Advertencias: {2}
Errores: {3}</target>
<note>

30
src/Build/Resources/xlf/Strings.fr.xlf сгенерированный
Просмотреть файл

@ -4,7 +4,7 @@
<body>
<trans-unit id="AbortingBuild">
<source>Attempting to cancel the build...</source>
<target state="translated">Tentative d'annulation de la build en cours...</target>
<target state="translated">Tentative d'annulation de la génération en cours...</target>
<note />
</trans-unit>
<trans-unit id="AmbiguousTaskParameterError">
@ -133,7 +133,7 @@
</trans-unit>
<trans-unit id="BuildCheckEnabled">
<source>The BuildCheck is enabled for this build.</source>
<target state="translated">Le BuildCheck est activé pour cette build.</target>
<target state="translated">BuildCheck est activé pour cette build.</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0101_MessageFmt">
@ -148,7 +148,7 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0102_MessageFmt">
<source>Tasks {0} and {1} from projects {2} and {3} write the same file: {4}.</source>
<target state="translated">Tâches {0} et {1} des projets {2} et {3} écrivent le même fichier : {4}.</target>
<target state="translated">Tâches {0} et {1} de projets {2} et {3} écrivez le même fichier : {4}.</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0102_Title">
@ -158,7 +158,7 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0103_MessageAddendum">
<source>'{0}' with value: '{1}'</source>
<target state="translated">« {0} » avec la valeur « {1} »</target>
<target state="translated">'{0}' avec valeur : '{1}'</target>
<note>Will be used as a parameter {0} in previous message.</note>
</trans-unit>
<trans-unit id="BuildCheck_BC0103_MessageFmt">
@ -168,12 +168,12 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0103_Title">
<source>No implicit property derived from an environment variable should be used during the build.</source>
<target state="translated">Aucune propriété implicite dérivée d'une variable d'environnement ne doit être utilisée pendant la build.</target>
<target state="translated">Aucune propriété implicite dérivée d'une variable d'environnement ne doit être utilisée pendant la construction.</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0201_MessageFmt">
<source>Property: '{0}' was accessed, but it was never initialized.</source>
<target state="translated">La propriété « {0} » a été consultée, mais elle n'a jamais été initialisée.</target>
<target state="translated">Propriété : « {0} » a été consultée, mais elle n'a jamais été initialisée.</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0201_Title">
@ -183,7 +183,7 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0202_MessageFmt">
<source>Property: '{0}' first declared/initialized at {1} used before it was initialized.</source>
<target state="translated">La propriété « {0} » a été déclarée/initialisée pour la première fois à l'utilisation de {1} avant d'être initialisée.</target>
<target state="translated">Propriété : '{0}' déclarée/initialisée pour la première fois à l'utilisation de {1} avant d'être initialisée.</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0202_Title">
@ -193,7 +193,7 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0203_MessageFmt">
<source>Property: '{0}' was declared/initialized, but it was never used.</source>
<target state="translated">La propriété « {0} » a été déclarée/initialisée, mais elle n'a jamais été utilisée.</target>
<target state="translated">Propriété : '{0}' a été déclarée/initialisée, mais elle n'a jamais été utilisée.</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0203_Title">
@ -284,7 +284,7 @@
</trans-unit>
<trans-unit id="CustomCheckAssemblyNotExist">
<source>Failed to find the specified custom check assembly: '{0}'. Please check if it exists.</source>
<target state="translated">Impossible de trouver l’assembly de vérification personnalisé spécifié : « {0} ». Veuillez vérifier s’il existe.</target>
<target state="translated">Impossible de trouver l’assembly de vérification personnalisé spécifié : «{0}». Veuillez vérifier s’il existe.</target>
<note>The message is emitted when the custom check assembly can not be found.</note>
</trans-unit>
<trans-unit id="CouldNotDifferentiateBetweenCompatibleMethods">
@ -294,27 +294,27 @@
</trans-unit>
<trans-unit id="CustomCheckBaseTypeNotAssignable">
<source>Failed to load the custom check type: '{0}' from the assembly: '{1}'. Make sure it inherits the Microsoft.Build.Experimental.BuildCheck.Check base class. If it is not intended to be a custom check, than it should not be exposed. More info: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</source>
<target state="translated">Échec du chargement du type de vérification personnalisé « {0} » à partir de l’assembly « {1} ». Assurez-vous qu’il hérite de la classe de base Microsoft.Build.Experimental.BuildCheck.Check. S’il ne s’agit pas d’une vérification personnalisée, elle ne doit pas être exposée. Plus d’informations : https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<target state="translated">Échec du chargement du type de vérification personnalisé «{0}» à partir de l’assembly : «{1}». Assurez-vous qu’il hérite de la classe de base Microsoft.Build.Experimental.BuildCheck.Check. S’il ne s’agit pas d’une vérification personnalisée, elle ne doit pas être exposée. Plus d’informations : https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<note>The message is emitted when the custom check assembly can not be successfully registered.</note>
</trans-unit>
<trans-unit id="CustomCheckFailedAcquisition">
<source>Failed to register the custom check: '{0}'.</source>
<target state="translated">Échec de l’inscription de la vérification personnalisée : « {0} ».</target>
<target state="translated">Échec de l’inscription de la vérification personnalisée : «{0}».</target>
<note>The message is emitted on failed loading of the custom check in process.</note>
</trans-unit>
<trans-unit id="CustomCheckFailedRuleLoading">
<source>Failed to instantiate the custom check rule with the following exception: '{0}'.</source>
<target state="translated">Échec de l’instanciation de la règle de vérification personnalisée avec l’exception suivante : « {0} ».</target>
<target state="translated">Échec de l’instanciation de la règle de vérification personnalisée avec l’exception suivante : «{0}».</target>
<note>The message is emitted on failed loading of the custom check rule in process.</note>
</trans-unit>
<trans-unit id="CustomCheckRegistered">
<source>The custom check: '{0}' is registered for the build from the location: '{1}'.</source>
<target state="translated">La vérification personnalisée « {0} » est inscrite pour la build à partir de l’emplacement : « {1} ».</target>
<target state="translated">La vérification personnalisée «{0}» est inscrite pour la build à partir de l’emplacement : «{1}».</target>
<note />
</trans-unit>
<trans-unit id="CustomCheckSuccessfulAcquisition">
<source>Custom check rule: '{0}' has been registered successfully.</source>
<target state="translated">Règle de vérification personnalisée : « {0} » a été correctement inscrite.</target>
<target state="translated">Règle de vérification personnalisée : «{0}» a été correctement inscrite.</target>
<note>The message is emitted on successful loading of the custom check rule in process.</note>
</trans-unit>
<trans-unit id="DefaultSDKResolverError">
@ -759,7 +759,7 @@ Erreurs : {3}</target>
<trans-unit id="UnhandledMSBuildError">
<source>This is an unhandled exception in MSBuild -- PLEASE UPVOTE AN EXISTING ISSUE OR FILE A NEW ONE AT https://aka.ms/msbuild/unhandled
{0}</source>
<target state="translated">Il s’agit d’une exception non prise en charge dans MSBuild –– VOTEZ POUR UN PROBLÈME EXISTANT OU CRÉEZ-EN UN SUR https://aka.ms/msbuild/unhandled
<target state="translated">Il s’agit d’une exception non gérée dans MSBuild –– VOTEZ POUR UN PROBLÈME EXISTANT OU ENTREZ UN NOUVEAU FICHIER À https://aka.ms/msbuild/unhandled.
{0}</target>
<note />
</trans-unit>

16
src/Build/Resources/xlf/Strings.it.xlf сгенерированный
Просмотреть файл

@ -148,7 +148,7 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0102_MessageFmt">
<source>Tasks {0} and {1} from projects {2} and {3} write the same file: {4}.</source>
<target state="translated">Le attività {0} e {1} dai progetti {2} e {3} scrivono lo stesso file: {4}.</target>
<target state="translated">Le attività {0} e {1} dai progetti {2} e {3} scrivere lo stesso file: {4}.</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0102_Title">
@ -284,7 +284,7 @@
</trans-unit>
<trans-unit id="CustomCheckAssemblyNotExist">
<source>Failed to find the specified custom check assembly: '{0}'. Please check if it exists.</source>
<target state="translated">Non è possibile trovare l'assembly del controllo personalizzato specificato: '{0}'. Verificare se esiste.</target>
<target state="translated">Impossibile trovare l'assembly di controllo personalizzato specificato: “{0}”. Verificare se esiste.</target>
<note>The message is emitted when the custom check assembly can not be found.</note>
</trans-unit>
<trans-unit id="CouldNotDifferentiateBetweenCompatibleMethods">
@ -294,27 +294,27 @@
</trans-unit>
<trans-unit id="CustomCheckBaseTypeNotAssignable">
<source>Failed to load the custom check type: '{0}' from the assembly: '{1}'. Make sure it inherits the Microsoft.Build.Experimental.BuildCheck.Check base class. If it is not intended to be a custom check, than it should not be exposed. More info: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</source>
<target state="translated">Non è possibile caricare il tipo di controllo personalizzato '{0}' dall'assembly '{1}'. Assicurarsi che erediti la classe di base Microsoft.Build.Experimental.BuildCheck.Check. Se non è destinato a essere un controllo personalizzato, non deve essere esposto. Altre informazioni: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<target state="translated">Non è stato possibile caricare il tipo di controllo personalizzato: “{0}” dall'assembly: “{1}”. Assicurarsi che erediti la classe di base Microsoft.Build.Experimental.BuildCheck.Check. Se non è destinato a essere un controllo personalizzato, non deve essere esposto. Per altre informazioni: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<note>The message is emitted when the custom check assembly can not be successfully registered.</note>
</trans-unit>
<trans-unit id="CustomCheckFailedAcquisition">
<source>Failed to register the custom check: '{0}'.</source>
<target state="translated">Non è possibile registrare il controllo personalizzato: '{0}'.</target>
<target state="translated">Impossibile registrare il controllo personalizzato: “{0}”.</target>
<note>The message is emitted on failed loading of the custom check in process.</note>
</trans-unit>
<trans-unit id="CustomCheckFailedRuleLoading">
<source>Failed to instantiate the custom check rule with the following exception: '{0}'.</source>
<target state="translated">Non è possibile creare un'istanza della regola del controllo personalizzato con l'eccezione seguente: '{0}'.</target>
<target state="translated">Non è stato possibile creare un'istanza della regola di controllo personalizzata con l'eccezione seguente: “{0}”.</target>
<note>The message is emitted on failed loading of the custom check rule in process.</note>
</trans-unit>
<trans-unit id="CustomCheckRegistered">
<source>The custom check: '{0}' is registered for the build from the location: '{1}'.</source>
<target state="translated">Il controllo personalizzato '{0}' è registrato per la compilazione dal percorso '{1}'.</target>
<target state="translated">Il controllo personalizzato “{0}” è registrato per la compilazione dal percorso “{1}”.</target>
<note />
</trans-unit>
<trans-unit id="CustomCheckSuccessfulAcquisition">
<source>Custom check rule: '{0}' has been registered successfully.</source>
<target state="translated">La regola del controllo personalizzato '{0}' è stata registrata correttamente.</target>
<target state="translated">La regola di controllo personalizzata “{0}” è stata registrata correttamente.</target>
<note>The message is emitted on successful loading of the custom check rule in process.</note>
</trans-unit>
<trans-unit id="DefaultSDKResolverError">
@ -633,7 +633,7 @@
<source>The "{0}" resolver attempted to resolve the SDK "{1}".
Warnings: {2}
Errors: {3}</source>
<target state="translated">Il resolver "{0}" ha tentato di risolvere l'SDK "{1}".
<target state="translated">Il resolver "{0}" ha provato a risolvere l'SDK "{1}".
Avvisi: {2}
Errori: {3}</target>
<note>

34
src/Build/Resources/xlf/Strings.ja.xlf сгенерированный
Просмотреть файл

@ -4,7 +4,7 @@
<body>
<trans-unit id="AbortingBuild">
<source>Attempting to cancel the build...</source>
<target state="translated">ビルドの取り消を試みています...</target>
<target state="translated">ビルドを取り消そうとしています...</target>
<note />
</trans-unit>
<trans-unit id="AmbiguousTaskParameterError">
@ -138,17 +138,17 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0101_MessageFmt">
<source>Projects {0} and {1} have conflicting output paths: {2}.</source>
<target state="translated">プロジェクト {0} と {1} で、出力パス: {2} が競合しています。</target>
<target state="translated">プロジェクト {0} と {1} の出力パスが競合しています: {2}。</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0101_Title">
<source>Two projects should not share their 'OutputPath' nor 'IntermediateOutputPath' locations.</source>
<target state="translated">2 つのプロジェクトで、'OutputPath' と 'IntermediateOutputPath' の場所の、どちらも共有することはできません。</target>
<target state="translated">2 つのプロジェクトで 'OutputPath' と 'IntermediateOutputPath' の場所を共有することはできません。</target>
<note>'OutputPath' and 'IntermediateOutputPath' not to be translated.</note>
</trans-unit>
<trans-unit id="BuildCheck_BC0102_MessageFmt">
<source>Tasks {0} and {1} from projects {2} and {3} write the same file: {4}.</source>
<target state="translated">プロジェクト {2} と {3} のタスク {0} と {1} が、同じファイル: {4} に書き込んでいます。</target>
<target state="translated">プロジェクト {2} と {3} のタスク {0} と {1} は、同じファイルを書き込みます: {4}。</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0102_Title">
@ -158,32 +158,32 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0103_MessageAddendum">
<source>'{0}' with value: '{1}'</source>
<target state="translated">値が '{1}' の '{0}'</target>
<target state="translated">'{0}' (値 '{1}')</target>
<note>Will be used as a parameter {0} in previous message.</note>
</trans-unit>
<trans-unit id="BuildCheck_BC0103_MessageFmt">
<source>Property is derived from environment variable: {0}. Properties should be passed explicitly using the /p option.</source>
<target state="translated">プロパティは環境変数: {0} から派生しています。プロパティは、/p オプションを使用して明示的に渡す必要があります。</target>
<target state="translated">プロパティは環境変数から派生しています: {0}。プロパティは、/p オプションを使用して明示的に渡す必要があります。</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0103_Title">
<source>No implicit property derived from an environment variable should be used during the build.</source>
<target state="translated">環境変数から派生した暗黙的なプロパティをビルド中に使用しないでください。</target>
<target state="translated">ビルド中に環境変数から派生した暗黙的なプロパティを使用しないでください。</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0201_MessageFmt">
<source>Property: '{0}' was accessed, but it was never initialized.</source>
<target state="translated">プロパティ: '{0}' は、初期化されないままアクセスされました。</target>
<target state="translated">プロパティ: '{0}' にアクセスしましたが、初期化されませんでした。</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0201_Title">
<source>A property that is accessed should be declared first.</source>
<target state="translated">アクセスされるプロパティを、最初に宣言する必要があります。</target>
<target state="translated">アクセスされるプロパティを、まず宣言する必要があります。</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0202_MessageFmt">
<source>Property: '{0}' first declared/initialized at {1} used before it was initialized.</source>
<target state="translated">{1} で最初に宣言/初期化されたプロパティ: '{0}' が初期化前に使用されました。</target>
<target state="translated">{1} で最初に宣言/初期化されたプロパティ: '{0}' は初期化前に使用されました。</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0202_Title">
@ -193,12 +193,12 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0203_MessageFmt">
<source>Property: '{0}' was declared/initialized, but it was never used.</source>
<target state="translated">プロパティ: '{0}' は宣言/初期化されましたが、使用されたことがありません。</target>
<target state="translated">プロパティ: '{0}' は宣言または初期化されましたが、使用されませんでした。</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0203_Title">
<source>A property that is not used should not be declared.</source>
<target state="translated">使用されないプロパティを宣言する必要はありません。</target>
<target state="translated">使用されていないプロパティは宣言しないでください。</target>
<note />
</trans-unit>
<trans-unit id="BuildFinishedQuestionFailure">
@ -284,7 +284,7 @@
</trans-unit>
<trans-unit id="CustomCheckAssemblyNotExist">
<source>Failed to find the specified custom check assembly: '{0}'. Please check if it exists.</source>
<target state="translated">指定されたカスタム チェック アセンブリ: '{0}' が見つかりませんでした。これが存在することを確認してください。</target>
<target state="translated">指定されたカスタム チェック アセンブリが見つかりませんでした: '{0}'。存在するかどうか確認してください。</target>
<note>The message is emitted when the custom check assembly can not be found.</note>
</trans-unit>
<trans-unit id="CouldNotDifferentiateBetweenCompatibleMethods">
@ -294,12 +294,12 @@
</trans-unit>
<trans-unit id="CustomCheckBaseTypeNotAssignable">
<source>Failed to load the custom check type: '{0}' from the assembly: '{1}'. Make sure it inherits the Microsoft.Build.Experimental.BuildCheck.Check base class. If it is not intended to be a custom check, than it should not be exposed. More info: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</source>
<target state="translated">アセンブリ: '{1}' から、カスタム チェックの種類: '{0}'を読み込めませんでした。Microsoft.Build.Experimental.BuildCheck.Check の基底クラスを継承していることを確認してください。カスタム チェックを意図していない場合は、公開しないでください。詳細情報: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<target state="translated">カスタム チェックの種類を読み込めませんでした: アセンブリ '{1}' の '{0}'。Microsoft.Build.Experimental.BuildCheck.Check 基底クラスを継承していることを確認してください。カスタム チェックを意図していない場合は、公開しないでください。詳細情報: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<note>The message is emitted when the custom check assembly can not be successfully registered.</note>
</trans-unit>
<trans-unit id="CustomCheckFailedAcquisition">
<source>Failed to register the custom check: '{0}'.</source>
<target state="translated">カスタム チェック: '{0}'を登録できませんでした。</target>
<target state="translated">カスタム チェックを登録できませんでした: '{0}'。</target>
<note>The message is emitted on failed loading of the custom check in process.</note>
</trans-unit>
<trans-unit id="CustomCheckFailedRuleLoading">
@ -309,7 +309,7 @@
</trans-unit>
<trans-unit id="CustomCheckRegistered">
<source>The custom check: '{0}' is registered for the build from the location: '{1}'.</source>
<target state="translated">カスタム チェック: '{0}' は、場所: '{1}' からビルドに登録されています。</target>
<target state="translated">カスタム チェック '{0}' は、場所 '{1}' からビルドに登録されています。</target>
<note />
</trans-unit>
<trans-unit id="CustomCheckSuccessfulAcquisition">
@ -380,7 +380,7 @@
</trans-unit>
<trans-unit id="IllegalCharactersInFileOrDirectory">
<source>There are illegal characters in '{0}' in the {1} item.</source>
<target state="translated">{1} 項目内の '{0}' が不正な文字を含んでいます。</target>
<target state="translated">{1} 項目内の '{0}' に不正な文字があります。</target>
<note />
</trans-unit>
<trans-unit id="ImportedProjectFromVSDistribution">

36
src/Build/Resources/xlf/Strings.pl.xlf сгенерированный
Просмотреть файл

@ -43,7 +43,7 @@
</trans-unit>
<trans-unit id="Binlog_ArchiveFile_NotSetAfterAcquire">
<source>ArchiveFile was obtained, but the final edited version was not set.</source>
<target state="translated">Uzyskano plik ArchiveFile, ale nie ustawiono ostatecznej edytowanej wersji.</target>
<target state="translated">Uzyskano plik ArchiveFile, ale nie ustawiono ostatecznej edycji wersji.</target>
<note />
</trans-unit>
<trans-unit id="Binlog_FwdCompatUnsupported">
@ -77,7 +77,7 @@
</trans-unit>
<trans-unit id="Binlog_ReaderUnderRead">
<source>BuildEvent record number {0} was expected to read exactly {1} bytes from the stream, but read {2} instead.</source>
<target state="translated">Oczekiwano, że numer rekordu BuildEvent {0} odczyta ze strumienia liczbę bajtów równą dokładnie {1}, ale zamiast tego odczytał {2}.</target>
<target state="translated">Oczekiwano, że numer rekordu BuildEvent {0} odczyta ze strumienia liczbę bajtów równą dokładnie {1}, ale zamiast tego odczyta {2}.</target>
<note>
LOCALIZATION: {0} is an integer number denoting order. {1} is an integer denoting size. {2} is an integer value indicating number of bytes.
</note>
@ -96,7 +96,7 @@
</trans-unit>
<trans-unit id="Binlog_Source_MultiSubscribeError">
<source>Structured events and raw events cannot be replayed at the same time.</source>
<target state="translated">Nie można ponownie odtwarzać jednocześnie zdarzeń strukturalnych i zdarzeń pierwotnych.</target>
<target state="translated">Nie można jednocześnie odtwarzać zdarzeń strukturalnych i nieprzetworzonych.</target>
<note />
</trans-unit>
<trans-unit id="Binlog_Source_VersionUninitialized">
@ -121,7 +121,7 @@
</trans-unit>
<trans-unit id="Binlog_StreamUtils_UnsupportedSkipOffset">
<source>Attempt to skip {0} bytes, only non-negative offset up to int.MaxValue is allowed.</source>
<target state="translated">Próba pominięcia {0} bajtów, tylko przesunięcie nieujemne do wartości int.MaxValue jest dozwolone.</target>
<target state="translated">Próba pominięcia {0} bajtów, tylko przesunięcie nieujemne do liczby całkowitej. Wartość MaxValue jest dozwolona.</target>
<note>
LOCALIZATION: {0} is integer number denoting number of bytes. 'int.MaxValue' should not be translated.
</note>
@ -173,17 +173,17 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0201_MessageFmt">
<source>Property: '{0}' was accessed, but it was never initialized.</source>
<target state="translated">Uzyskano dostęp do właściwości: „{0}”, ale nigdy nie zainicjowano jej.</target>
<target state="translated">Właściwość: uzyskano dostęp do „{0}”, ale nigdy nie dokonano inicjacji.</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0201_Title">
<source>A property that is accessed should be declared first.</source>
<target state="translated">Właściwość, do której jest uzyskiwany dostęp, powinna być zadeklarowana jako pierwsza.</target>
<target state="translated">Właściwość, do których jest uzyskiwany dostęp, powinna być zadeklarowana jako pierwsza.</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0202_MessageFmt">
<source>Property: '{0}' first declared/initialized at {1} used before it was initialized.</source>
<target state="translated">Właściwość: „{0}” została najpierw zadeklarowana/zainicjowana w {1} i była używania przed jej zainicjowaniem.</target>
<target state="translated">Właściwość: „{0}” została najpierw zadeklarowana/zainicjowana {1} i była używania przed jej zainicjowaniem.</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0202_Title">
@ -193,7 +193,7 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0203_MessageFmt">
<source>Property: '{0}' was declared/initialized, but it was never used.</source>
<target state="translated">Zadeklarowano/zainicjowano właściwość: „{0}”, ale nigdy nie była używana.</target>
<target state="translated">Właściwość: uzyskano dostęp do „{0}”, ale nigdy nie dokonano inicjacji.</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0203_Title">
@ -284,7 +284,7 @@
</trans-unit>
<trans-unit id="CustomCheckAssemblyNotExist">
<source>Failed to find the specified custom check assembly: '{0}'. Please check if it exists.</source>
<target state="translated">Nie udało się znaleźć określonego niestandardowego zestawu kontroli: „{0}”. Sprawdź, czy istnieje.</target>
<target state="translated">Nie udało się znaleźć określonego niestandardowego zestawu kontrolnego: „{0}”. Sprawdź, czy istnieje.</target>
<note>The message is emitted when the custom check assembly can not be found.</note>
</trans-unit>
<trans-unit id="CouldNotDifferentiateBetweenCompatibleMethods">
@ -294,27 +294,27 @@
</trans-unit>
<trans-unit id="CustomCheckBaseTypeNotAssignable">
<source>Failed to load the custom check type: '{0}' from the assembly: '{1}'. Make sure it inherits the Microsoft.Build.Experimental.BuildCheck.Check base class. If it is not intended to be a custom check, than it should not be exposed. More info: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</source>
<target state="translated">Nie udało się załadować niestandardowego typu kontroli: „{0}” z zestawu: „{1}”. Upewnij się, że dziedziczy klasę bazową Microsoft.Build.Experimental.BuildCheck.Check. Jeśli nie ma to być kontrola niestandardowa, to nie powinna być ona ujawniana. Więcej informacji: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<target state="translated">Nie udało się załadować niestandardowego typu kontrolnego: „{0}” z zestawu: „{1}”. Upewnij się, że dziedziczy po klasie bazowej Microsoft.Build.Experimental.BuildCheck.Check. Jeśli nie ma to być kontrola niestandardowa, to nie powinna być ona ujawniana. Więcej informacji: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<note>The message is emitted when the custom check assembly can not be successfully registered.</note>
</trans-unit>
<trans-unit id="CustomCheckFailedAcquisition">
<source>Failed to register the custom check: '{0}'.</source>
<target state="translated">Nie można zarejestrować niestandardowej kontroli: „{0}”.</target>
<target state="translated">Nie można zarejestrować niestandardowego kontrolera: „{0}”.</target>
<note>The message is emitted on failed loading of the custom check in process.</note>
</trans-unit>
<trans-unit id="CustomCheckFailedRuleLoading">
<source>Failed to instantiate the custom check rule with the following exception: '{0}'.</source>
<target state="translated">Nie udało się utworzyć wystąpienia niestandardowej reguły kontroli z następującym wyjątkiem: „{0}”.</target>
<target state="translated">Nie udało się utworzyć niestandardowej reguły utworzenia wystąpienia z następującym wyjątkiem: „{0}”.</target>
<note>The message is emitted on failed loading of the custom check rule in process.</note>
</trans-unit>
<trans-unit id="CustomCheckRegistered">
<source>The custom check: '{0}' is registered for the build from the location: '{1}'.</source>
<target state="translated">Kontrola niestandardowa: „{0}” jest zarejestrowany dla kompilacji z lokalizacji: „{1}”.</target>
<target state="translated">Kontroler niestandardowy „{0}” jest zarejestrowany dla kompilacji z lokalizacji: „{1}”.</target>
<note />
</trans-unit>
<trans-unit id="CustomCheckSuccessfulAcquisition">
<source>Custom check rule: '{0}' has been registered successfully.</source>
<target state="translated">Niestandardowa reguła kontroli: „{0}” została pomyślnie zarejestrowana.</target>
<target state="translated">Niestandardowa reguła kontrolera: „{0}” została pomyślnie zarejestrowana.</target>
<note>The message is emitted on successful loading of the custom check rule in process.</note>
</trans-unit>
<trans-unit id="DefaultSDKResolverError">
@ -362,7 +362,7 @@
<trans-unit id="FatalErrorWhileLoggingWithInnerException">
<source>MSB4017: The build stopped unexpectedly because of an unexpected logger failure.
{0}</source>
<target state="translated">MSB4017: kompilacja została nieoczekiwanie zatrzymana z powodu nieoczekiwanego błędu rejestratora.
<target state="translated">MSB4017: Kompilacja została nieoczekiwanie zatrzymana z powodu nieoczekiwanego błędu rejestratora.
{0}</target>
<note>{StrBegin="MSB4017: "}UE: This message is used for a special exception that is thrown when a logger fails while logging an event (most
likely because of a programming error in the logger). When a logger dies, we cannot proceed with the build, and we throw a
@ -380,7 +380,7 @@
</trans-unit>
<trans-unit id="IllegalCharactersInFileOrDirectory">
<source>There are illegal characters in '{0}' in the {1} item.</source>
<target state="translated">Element {1} zawiera niedozwolone znaki w „{0}”.</target>
<target state="translated">Element {0} zawiera niedozwolone znaki w „{1}”.</target>
<note />
</trans-unit>
<trans-unit id="ImportedProjectFromVSDistribution">
@ -710,7 +710,7 @@ Błędy: {3}</target>
</trans-unit>
<trans-unit id="SucceededToResolveSDK">
<source>The SDK "{0}" was successfully resolved by the "{1}" resolver to location "{2}" and version "{3}".</source>
<target state="translated">Zestaw SDK „{0}” został pomyślnie rozpoznany przez narzędzie Resolver „{1}” w lokalizacji „{2}” i w wersji „{3}”.</target>
<target state="translated">Zestaw SDK „{0}” został pomyślnie rozpoznany przez narzędzie Resolver „{1}” do lokalizacji „{2}” i wersji „{3}”.</target>
<note />
</trans-unit>
<trans-unit id="TaskAcquiredCores">
@ -759,7 +759,7 @@ Błędy: {3}</target>
<trans-unit id="UnhandledMSBuildError">
<source>This is an unhandled exception in MSBuild -- PLEASE UPVOTE AN EXISTING ISSUE OR FILE A NEW ONE AT https://aka.ms/msbuild/unhandled
{0}</source>
<target state="translated">Jest to nieobsługiwany wyjątek na platformie MSBuild -- ZAGŁOSUJ NA ISTNIEJĄCY PROBLEM LUB ZAREJESTRUJ NOWY W WITRYNIE https://aka.ms/msbuild/unhandled.
<target state="translated">Jest to nieobsługiwany wyjątek w aplikacji MSBuild -- ZAGŁOSUJ NA ISTNIEJĄCY PROBLEM LUB ZAGŁOSUJ NA NOWY NA https://aka.ms/msbuild/unhandled.
{0}</target>
<note />
</trans-unit>

14
src/Build/Resources/xlf/Strings.pt-BR.xlf сгенерированный
Просмотреть файл

@ -173,7 +173,7 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0201_MessageFmt">
<source>Property: '{0}' was accessed, but it was never initialized.</source>
<target state="translated">Propriedade: '{0}' foi acessada, mas nunca foi inicializada.</target>
<target state="translated">Propriedade: "{0}" foi acessada, mas nunca foi inicializada.</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0201_Title">
@ -284,7 +284,7 @@
</trans-unit>
<trans-unit id="CustomCheckAssemblyNotExist">
<source>Failed to find the specified custom check assembly: '{0}'. Please check if it exists.</source>
<target state="translated">Falha ao localizar o assembly de verificação personalizada especificado: '{0}'. Verifique se existe.</target>
<target state="translated">Falha ao localizar o assembly de verificação personalizado especificado: '{0}'. Verifique se existe.</target>
<note>The message is emitted when the custom check assembly can not be found.</note>
</trans-unit>
<trans-unit id="CouldNotDifferentiateBetweenCompatibleMethods">
@ -294,7 +294,7 @@
</trans-unit>
<trans-unit id="CustomCheckBaseTypeNotAssignable">
<source>Failed to load the custom check type: '{0}' from the assembly: '{1}'. Make sure it inherits the Microsoft.Build.Experimental.BuildCheck.Check base class. If it is not intended to be a custom check, than it should not be exposed. More info: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</source>
<target state="translated">Falha ao carregar o tipo de verificação personalizado: '{0}' do assembly: '{1}'. Verifique se ele herda a classe base Microsoft.Build.Experimental.BuildCheck.Check. Se não se destina a ser uma verificação personalizada, ela não deve ser exposta. Mais informações: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<target state="translated">Falha ao carregar o tipo de verificação personalizada: '{0}' do assembly: '{1}'. Certifique-se de que ele herda a classe base Microsoft.Build.Experimental.BuildCheck.Check. Se não for destinado a ser uma verificação personalizada, então não deve ser exposto. Mais informações: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<note>The message is emitted when the custom check assembly can not be successfully registered.</note>
</trans-unit>
<trans-unit id="CustomCheckFailedAcquisition">
@ -309,12 +309,12 @@
</trans-unit>
<trans-unit id="CustomCheckRegistered">
<source>The custom check: '{0}' is registered for the build from the location: '{1}'.</source>
<target state="translated">A verificação personalizada: '{0}' está registrada para a compilação do local: '{1}'.</target>
<target state="translated">A verificação personalizada: '{0}' está registrada para a compilação a partir do local: '{1}'.</target>
<note />
</trans-unit>
<trans-unit id="CustomCheckSuccessfulAcquisition">
<source>Custom check rule: '{0}' has been registered successfully.</source>
<target state="translated">Regra de verificação personalizada: '{0}' foi registrada com êxito.</target>
<target state="translated">Regra de verificação personalizada: '{0}' foi registrada com sucesso.</target>
<note>The message is emitted on successful loading of the custom check rule in process.</note>
</trans-unit>
<trans-unit id="DefaultSDKResolverError">
@ -362,7 +362,7 @@
<trans-unit id="FatalErrorWhileLoggingWithInnerException">
<source>MSB4017: The build stopped unexpectedly because of an unexpected logger failure.
{0}</source>
<target state="translated">MSB4017: a compilação parou inesperadamente devido a uma falha do agente.
<target state="translated">MSB4017: A compilação parou inesperadamente devido a uma falha do agente de log.
{0}</target>
<note>{StrBegin="MSB4017: "}UE: This message is used for a special exception that is thrown when a logger fails while logging an event (most
likely because of a programming error in the logger). When a logger dies, we cannot proceed with the build, and we throw a
@ -759,7 +759,7 @@ Erros: {3}</target>
<trans-unit id="UnhandledMSBuildError">
<source>This is an unhandled exception in MSBuild -- PLEASE UPVOTE AN EXISTING ISSUE OR FILE A NEW ONE AT https://aka.ms/msbuild/unhandled
{0}</source>
<target state="translated">Essa é uma exceção não tratada no MSBuild -- POR FAVOR, ATUALIZE UMA QUESTÃO EXISTENTE OU ENCAMINHE UMA NOVA EM https://aka.ms/msbuild/unhandled
<target state="translated">Esta é uma exceção não tratada no MSBuild -- POR FAVOR, APOIE UM PROBLEMA EXISTENTE OU ARQUIVE UM NOVO EM https://aka.ms/msbuild/unhandled
{0}</target>
<note />
</trans-unit>

2
src/Build/Resources/xlf/Strings.ru.xlf сгенерированный
Просмотреть файл

@ -759,7 +759,7 @@ Errors: {3}</source>
<trans-unit id="UnhandledMSBuildError">
<source>This is an unhandled exception in MSBuild -- PLEASE UPVOTE AN EXISTING ISSUE OR FILE A NEW ONE AT https://aka.ms/msbuild/unhandled
{0}</source>
<target state="translated">Это необработанное исключение в MSBuild. ПРОГОЛОСУЙТЕ ЗА СУЩЕСТВУЮЩУЮ ПРОБЛЕМУ ИЛИ СООБЩИТЕ О НОВУЙ НА https://aka.ms/msbuild/unhandled
<target state="translated">Это необработанное исключение в MSBuild. Проголосуйте за существующую проблему или сообщите о новой по адресу https://aka.ms/msbuild/unhandled
{0}</target>
<note />
</trans-unit>

2
src/Build/Resources/xlf/Strings.tr.xlf сгенерированный
Просмотреть файл

@ -759,7 +759,7 @@ Hatalar: {3}</target>
<trans-unit id="UnhandledMSBuildError">
<source>This is an unhandled exception in MSBuild -- PLEASE UPVOTE AN EXISTING ISSUE OR FILE A NEW ONE AT https://aka.ms/msbuild/unhandled
{0}</source>
<target state="translated">Bu, MSBuild'de işlenmeyen bir istisnadır -- LÜTFEN MEVCUT BİR SORUNU OYLAYIN VEYA https://aka.ms/msbuild/unhandled ADRESİNDE YENİ BİR SORUN OLUŞTURUN
<target state="translated">Bu, MSBuild'de işlenmeyen bir istisnadır -- LÜTFEN MEVCUT BİR SORUNU OYLAYIN VEYA https://aka.ms/msbuild/unhandled ADRESİNDE YENİ BİR SORUN DOSYALAYIN
{0}</target>
<note />
</trans-unit>

30
src/Build/Resources/xlf/Strings.zh-Hans.xlf сгенерированный
Просмотреть файл

@ -158,7 +158,7 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0103_MessageAddendum">
<source>'{0}' with value: '{1}'</source>
<target state="translated">'{0}'，值为 '{1}'</target>
<target state="translated">值为“{1}”的“{0}”</target>
<note>Will be used as a parameter {0} in previous message.</note>
</trans-unit>
<trans-unit id="BuildCheck_BC0103_MessageFmt">
@ -168,22 +168,22 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0103_Title">
<source>No implicit property derived from an environment variable should be used during the build.</source>
<target state="translated">在生成过程中，不应使用派生自环境变量的任何隐式属性。</target>
<target state="translated">在生成过程中，不应使用派生自环境变量的隐式属性。</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0201_MessageFmt">
<source>Property: '{0}' was accessed, but it was never initialized.</source>
<target state="translated">已访问属性 '{0}'，但从未将其初始化。</target>
<target state="translated">已访问属性“{0}”，但从未将其初始化过。</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0201_Title">
<source>A property that is accessed should be declared first.</source>
<target state="translated">应首先声明所访问的属性。</target>
<target state="translated">应首先声明访问的属性。</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0202_MessageFmt">
<source>Property: '{0}' first declared/initialized at {1} used before it was initialized.</source>
<target state="translated">属性: '{0}' 在 {1} 处使用时先声明/初始化，然后再进行初始化。</target>
<target state="translated">属性“{0}”在 {1} 使用时首先声明/初始化，再进行初始化。</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0202_Title">
@ -193,7 +193,7 @@
</trans-unit>
<trans-unit id="BuildCheck_BC0203_MessageFmt">
<source>Property: '{0}' was declared/initialized, but it was never used.</source>
<target state="translated">属性: '{0}' 已声明/初始化，但从未使用过。</target>
<target state="translated">属性“{0}”已声明/初始化，但从未使用过。</target>
<note />
</trans-unit>
<trans-unit id="BuildCheck_BC0203_Title">
@ -284,7 +284,7 @@
</trans-unit>
<trans-unit id="CustomCheckAssemblyNotExist">
<source>Failed to find the specified custom check assembly: '{0}'. Please check if it exists.</source>
<target state="translated">找不到指定的自定义检查程序集: '{0}'。请检查它是否存在。</target>
<target state="translated">找不到指定的自定义检查程序集: {0}。请检查它是否存在。</target>
<note>The message is emitted when the custom check assembly can not be found.</note>
</trans-unit>
<trans-unit id="CouldNotDifferentiateBetweenCompatibleMethods">
@ -294,27 +294,27 @@
</trans-unit>
<trans-unit id="CustomCheckBaseTypeNotAssignable">
<source>Failed to load the custom check type: '{0}' from the assembly: '{1}'. Make sure it inherits the Microsoft.Build.Experimental.BuildCheck.Check base class. If it is not intended to be a custom check, than it should not be exposed. More info: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</source>
<target state="translated">未能从程序集 '{1}' 加载自定义检查类型 '{0}'。请确保它继承 Microsoft.Build.Experimental.BuildCheck.Check 基类。如果它不旨在作为自定义检查，则不应将其公开。详细信息: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<target state="translated">未能从程序集“{1}”加载自定义检查类型“{0}”。请确保它继承 Microsoft.Build.Experimental.BuildCheck.Check 基类。如果不打算将其作为自定义检查，则不应将其公开。详细信息: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition</target>
<note>The message is emitted when the custom check assembly can not be successfully registered.</note>
</trans-unit>
<trans-unit id="CustomCheckFailedAcquisition">
<source>Failed to register the custom check: '{0}'.</source>
<target state="translated">未能注册自定义检查: '{0}'。</target>
<target state="translated">未能注册自定义检查: {0}。</target>
<note>The message is emitted on failed loading of the custom check in process.</note>
</trans-unit>
<trans-unit id="CustomCheckFailedRuleLoading">
<source>Failed to instantiate the custom check rule with the following exception: '{0}'.</source>
<target state="translated">未能实例化自定义检查规则，出现以下异常: '{0}'。</target>
<target state="translated">未能实例化自定义检查规则，出现以下异常: {0}。</target>
<note>The message is emitted on failed loading of the custom check rule in process.</note>
</trans-unit>
<trans-unit id="CustomCheckRegistered">
<source>The custom check: '{0}' is registered for the build from the location: '{1}'.</source>
<target state="translated">已从位置 '{1}' 为内部版本注册自定义检查 '{0}'。</target>
<target state="translated">已从位置“{1}”为内部版本注册自定义检查“{0}”。</target>
<note />
</trans-unit>
<trans-unit id="CustomCheckSuccessfulAcquisition">
<source>Custom check rule: '{0}' has been registered successfully.</source>
<target state="translated">已成功注册自定义检查规则 '{0}'。</target>
<target state="translated">已成功注册自定义检查规则“{0}”。</target>
<note>The message is emitted on successful loading of the custom check rule in process.</note>
</trans-unit>
<trans-unit id="DefaultSDKResolverError">
@ -380,7 +380,7 @@
</trans-unit>
<trans-unit id="IllegalCharactersInFileOrDirectory">
<source>There are illegal characters in '{0}' in the {1} item.</source>
<target state="translated">'{1}' 项中的 '{0}' 中存在非法字符。</target>
<target state="translated">{1} 项中的“{0}”中存在非法字符。</target>
<note />
</trans-unit>
<trans-unit id="ImportedProjectFromVSDistribution">
@ -400,7 +400,7 @@
</trans-unit>
<trans-unit id="IsolatedContextDoesNotSupportFileSystem">
<source>EvaluationContext objects created with SharingPolicy.Isolated or SharingPolicy.SharedSDKCache do not support being passed an MSBuildFileSystemBase file system.</source>
<target state="translated">使用 SharingPolicy.Isolated 创建的 EvaluationContext 对象。SharingPolicy.SharedSDKCache 不支持被传递 MSBuildFileSystemBase 文件系统。</target>
<target state="translated">使用 SharingPolicy.Isolated 或 SharingPolicy.SharedSDKCache 创建的 EvaluationContext 对象不支持被传递 MSBuildFileSystemBase 文件系统。</target>
<note />
</trans-unit>
<trans-unit id="ItemReferencingSelfInTarget">
@ -2688,7 +2688,7 @@ Utilization: {0} Average Utilization: {1:###.0}</source>
</trans-unit>
<trans-unit id="InvalidSdkFormat">
<source>MSB4229: The value "{0}" is not valid for an Sdk specification. The attribute should be a semicolon-delimited list of Sdk-name/minimum-version pairs, separated by a forward slash.</source>
<target state="translated">MSB4229: 值“{0}”对 Sdk 规范无效。此属性应该是以分号分隔的Sdk-name/minimum-version 对 (用正斜杠分隔) 的列表。</target>
<target state="translated">MSB4229: 值“{0}”对 Sdk 规范无效。此属性应该是以分号分隔的Sdk-name/minimum-version 对（用正斜杠分隔）的列表。</target>
<note>{StrBegin="MSB4229: "}</note>
</trans-unit>
<trans-unit id="TaskInstantiationFailureNotSupported">

2
src/Build/Resources/xlf/Strings.zh-Hant.xlf сгенерированный
Просмотреть файл

@ -362,7 +362,7 @@
<trans-unit id="FatalErrorWhileLoggingWithInnerException">
<source>MSB4017: The build stopped unexpectedly because of an unexpected logger failure.
{0}</source>
<target state="translated">MSB4017: 由於發生未預期的記錄器失敗，因此已中止組建。
<target state="translated">MSB4017: 因為未預期的記錄器失敗，建置未預期停止。
{0}</target>
<note>{StrBegin="MSB4017: "}UE: This message is used for a special exception that is thrown when a logger fails while logging an event (most
likely because of a programming error in the logger). When a logger dies, we cannot proceed with the build, and we throw a

94
src/MSBuild/Resources/xlf/Strings.cs.xlf сгенерированный
Просмотреть файл

@ -34,14 +34,14 @@
</trans-unit>
<trans-unit id="BuildResult_FailedWithErrors">
<source>failed with {0} error(s)</source>
<target state="translated">selhalo s {0} chybou/chybami.</target>
<target state="translated">selhalo s {0} chybami.</target>
<note>
Part of Terminal Logger summary message: "Build {BuildResult_X} in {duration}s"
</note>
</trans-unit>
<trans-unit id="BuildResult_FailedWithErrorsAndWarnings">
<source>failed with {0} error(s) and {1} warning(s)</source>
<target state="translated">selhalo s chybami (celkem {0}) a upozorněními (celkem {1})</target>
<target state="translated">selhalo s {0} chybami a {1} upozorněními.</target>
<note>
Part of Terminal Logger summary message: "Build {BuildResult_X} in {duration}s"
</note>
@ -62,7 +62,7 @@
</trans-unit>
<trans-unit id="BuildResult_SucceededWithWarnings">
<source>succeeded with {0} warning(s)</source>
<target state="translated">uspělo s {0} upozorněním(i).</target>
<target state="translated">akce proběhla úspěšně s {0} upozorněním(i).</target>
<note>
Part of Terminal Logger summary message: "Build {BuildResult_X} in {duration}s"
</note>
@ -321,10 +321,10 @@
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</source>
<target state="needs-review-translation"> -check
Povolí během sestavení BuildChecks.
BuildCheck umožňuje vyhodnocovat pravidla, aby se zajistily vlastnosti
sestavení. Další informace viz aka.ms/buildcheck
<target state="new"> -check
Enables BuildChecks during the build.
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</target>
<note>
{Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"}
@ -642,7 +642,7 @@ Když se nastaví na MessageUponIsolationViolation (nebo jeho krátký
<target state="translated"> -warnNotAsError[:code[;code2]]
Seznam kódů upozornění, které se nemají považovat za chyby.
K oddělení
více kódů upozornění použijte středník
více kódů upozornění použijte středník
nebo čárku. Nemá žádný vliv, pokud přepínač -warnaserror
není nastavený.
@ -709,9 +709,9 @@ Když se nastaví na MessageUponIsolationViolation (nebo jeho krátký
<target state="translated"> @&lt;soubor&gt; Vložení nastavení příkazového řádku z textového souboru. Chcete-li zadat
více souborů odpovědí, uveďte každý soubor
odpovědí zvlášť.
Automaticky jsou použity všechny soubory s názvem msbuild.rsp
nacházející se v následujících umístěních:
Automaticky jsou použity všechny soubory s názvem msbuild.rsp
nacházející se v následujících umístěních:
(1) adresář nástroje msbuild.exe
(2) adresář prvního sestaveného projektu nebo řešení
</target>
@ -772,7 +772,7 @@ Když se nastaví na MessageUponIsolationViolation (nebo jeho krátký
</source>
<target state="translated"> -property:&lt;n&gt;=&lt;v&gt; Nastavení nebo potlačení daných vlastností na úrovni
projektu. &lt;n&gt; je název vlastnosti a &lt;v&gt; je její hodnota. Více
vlastností oddělte středníkem či čárkou nebo zadejte
vlastností oddělte středníkem či čárkou nebo zadejte
každou vlastnost zvlášť. (Krátký tvar: -p)
Příklad:
-property:WarningLevel=2;OutDir=bin\Debug\
@ -802,17 +802,20 @@ Když se nastaví na MessageUponIsolationViolation (nebo jeho krátký
-logger:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
-logger:XMLLogger,C:\Loggers\MyLogger.dll;OutputAsHTML
</source>
<target state="translated"> -logger:&lt;logger&gt; Použít daný protokolovací nástroj k protokolování událostí nástroje MSBuild. Pokud chcete zadat
více protokolovacích nástrojů, musíte je zadat jednotlivě.
Syntaxe hodnoty &lt;logger&gt; je:
[&lt;class&gt;,]&lt;assembly&gt;[,&lt;options&gt;][;&lt;parameters&gt;]
Syntaxe hodnoty &lt;logger class&gt; je:
[&lt;partial or full namespace&gt;.]&lt;logger class name&gt;
Syntaxe hodnoty &lt;logger assembly&gt; je:
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
<target state="translated"> -logger:&lt;protok_nást&gt; Použít daný protokolovací nástroj k protokolování
událostí nástroje MSBuild. Chcete-li zadat více protokolovacích.
nástrojů, musíte je zadat jednotlivě.
Syntaxe hodnoty &lt;protok_nást&gt;:
[&lt;třída_protok_nást&gt;,]&lt;sestavení_protok_nást&gt;
[;&lt;param_protok_nást&gt;]
Syntaxe hodnoty &lt;třída_protok_nást&gt;:
[&lt;část/úpl_obor_názvů&gt;.]&lt;náz_tř_protok_nást&gt;
Syntaxe hodnoty &lt;sestavení_protok_nást&gt;:
{&lt;název_sestavení&gt;[,&lt;strong name&gt;] | &lt;soubor_sestavení&gt;}
Parametry protokolovacího nástroje určují, jak MSBuild vytvoří protokolovací nástroj.
Parametry &lt;logger parameters&gt; jsou volitelné a předávají se
protokolovacímu nástroji přesně v tom tvaru, v jakém byly zadány. (Krátký tvar: -l)
Parametry &lt;param_protok_nást&gt; jsou volitelné a předávají se
protokolovacímu nástroji přesně v tom tvaru, v jakém
byly zadány. (Krátký tvar: -l)
Příklady:
-logger:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
-logger:XMLLogger,C:\Loggers\MyLogger.dll;OutputAsHTML
@ -920,7 +923,7 @@ Když se nastaví na MessageUponIsolationViolation (nebo jeho krátký
režimu.
EnableMPLogging – povolí víceprocesorový styl výstupu
protokolování i při práci v jiném
režimu. Tento styl protokolování je výchozí.
režimu. Tento styl protokolování je výchozí.
ForceConsoleColor – použije barvy konzoly ANSI,
i když to konzola nepodporuje.
PreferConsoleColor– použije barvy konzoly ANSI, pouze pokud
@ -965,10 +968,10 @@ Když se nastaví na MessageUponIsolationViolation (nebo jeho krátký
Example:
-validate:MyExtendedBuildSchema.xsd
</source>
<target state="translated"> -validate Ověřit projekt podle výchozího schématu.
<target state="translated"> -validate Ověřit projekt podle výchozího schématu.
(Krátký tvar: -val)
-validate:&lt;schéma&gt; Ověřit projekt podle zadaného schématu.
-validate:&lt;schéma&gt; Ověřit projekt podle zadaného schématu.
(Krátký tvar: -val)
Příklad:
-validate:MyExtendedBuildSchema.xsd
@ -1081,20 +1084,23 @@ Když se nastaví na MessageUponIsolationViolation (nebo jeho krátký
-dl:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
-dl:MyLogger,C:\My.dll*ForwardingLogger,C:\Logger.dll
</source>
<target state="translated"> -distributedLogger:&lt;central logger&gt;*&lt;forwarding logger&gt;
Použít zadaný protokolovací nástroj pro protokolování událostí z nástroje MSBuild; ke každému uzlu připojit
jinou instanci protokolovacího nástroje. Pokud chcete zadat více
<target state="translated"> -distributedlogger:&lt;centr_protok_nást&gt;*&lt;předáv_protok_nást&gt;
Použít zadaný protokolovací nástroj pro protokolování událostí
z nástroje MSBuild; ke každému uzlu připojit jinou instanci
protokolovacího nástroje. Chcete-li zadat více
protokolovacích nástrojů, uveďte je jednotlivě.
(Krátký tvar: -dl)
Syntaxe hodnoty &lt;logger&gt; je:
[&lt;class&gt;,]&lt;assembly&gt;[,&lt;options&gt;][;&lt;parameters&gt;]
Syntaxe hodnoty &lt;logger class&gt; je:
[&lt;partial or full namespace&gt;.]&lt;logger class name&gt;
Syntaxe hodnoty &lt;logger assembly&gt; je:
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
Syntaxe hodnoty &lt;protok_nást&gt;:
[&lt;třída_protok_nást&gt;,]&lt;sestav_protok_nást&gt;
[;&lt;param_protok_nást&gt;]
Syntaxe hodnoty &lt;třída_protok_nást&gt;:
[&lt;část/úpl_obor_názvů&gt;.]&lt;náz_tř_protok_nást&gt;
Syntaxe hodnoty &lt;sestav_protok_nást&gt;:
{&lt;název_sestavení&gt;[,&lt;strong name&gt;] | &lt;soubor_sestavení&gt;}
Parametry protokolovacího nástroje určují, jak MSBuild vytvoří protokolovací nástroj.
Parametry &lt;param_protok_nást&gt; jsou volitelné a předávají se
protokolovacímu nástroji přesně v zadaném tvaru. (Krátký tvar: -l)
protokolovacímu nástroji přesně v zadaném tvaru.
(Krátký tvar: -l)
Příklady:
-dl:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
-dl:MyLogger,C:\My.dll*ForwardingLogger,C:\Logger.dll
@ -1146,7 +1152,7 @@ Když se nastaví na MessageUponIsolationViolation (nebo jeho krátký
<target state="translated"> -toolsversion:&lt;verze&gt;
Verze sady nástrojů MSBuild (úloh, cílů apod.), která má být
použita při sestavení. Tato verze má přednost před verzemi
uvedenými v jednotlivých projektech.
uvedenými v jednotlivých projektech.
(Krátký tvar: -tv)
Příklad:
-toolsversion:3.5
@ -1264,24 +1270,24 @@ Když se nastaví na MessageUponIsolationViolation (nebo jeho krátký
popis přepínače -distributedFileLogger.
(Krátký tvar: -flp[n])
K dispozici jsou stejné parametry jako ty,
které jsou uvedeny u protokolovacího nástroje
které jsou uvedeny u protokolovacího nástroje
konzoly. Některé další dostupné parametry:
LogFile – cesta k souboru protokolu, do nějž bude zapsán
protokol sestavení
protokol sestavení
Append – určuje, zda bude protokol sestavení připojen
k souboru protokolu, nebo jej přepíše. Při nastavení
k souboru protokolu, nebo jej přepíše. Při nastavení
přepínače bude protokol sestavení připojen k souboru
protokolu. Není-li přepínač nastaven, bude obsah
existujícího souboru protokolu přepsán.
protokolu. Není-li přepínač nastaven, bude obsah
existujícího souboru protokolu přepsán.
Podle výchozího nastavení je soubor protokolu přepsán.
Encoding – určuje kódování souboru, například
Encoding – určuje kódování souboru, například
UTF-8, Unicode nebo ASCII.
Výchozí úroveň podrobností je Detailed.
Příklady:
-fileLoggerParameters:LogFile=MyLog.log;Append;
Verbosity=diagnostic;Encoding=UTF-8
-flp:Summary;Verbosity=minimal;LogFile=msbuild.sum
-flp:Summary;Verbosity=minimal;LogFile=msbuild.sum
-flp1:warningsonly;logfile=msbuild.wrn
-flp2:errorsonly;logfile=msbuild.err
</target>
@ -2371,4 +2377,4 @@ Když se nastaví na MessageUponIsolationViolation (nebo jeho krátký
</trans-unit>
</body>
</file>
</xliff>
</xliff>

123
src/MSBuild/Resources/xlf/Strings.de.xlf сгенерированный
Просмотреть файл

@ -121,11 +121,12 @@
This flag is experimental and may not work as intended.
</source>
<target state="translated"> -reportFileAccesses[:True|False]
Führt dazu, dass MSBuild Dateizugriffe auf ein beliebiges konfiguriertes
Projektcache-Plug-In meldet.
<target state="translated"> -reportFileAccesses[:True|Falsch]
Führt dazu, dass MSBuild Dateizugriffe an alle konfigurierten
meldet
Projektcache-Plug-Ins.
Dieses Flag ist experimentell und funktioniert möglicherweise nicht wie vorgesehen.
Dieses Kennzeichen ist experimentell und funktioniert möglicherweise nicht wie vorgesehen.
</target>
<note>
LOCALIZATION: "-reportFileAccesses" should not be localized.
@ -176,7 +177,7 @@
the specified targets will be executed.
</source>
<target state="translated"> -getTargetResult:targetName,...
Schreiben Sie den Ausgabewert eines oder mehrerer Ziele aus, und
Schreiben Sie den Ausgabewert eines oder mehrerer Ziele aus und
die angegebenen Ziele werden ausgeführt.
</target>
<note>
@ -204,15 +205,15 @@
Überprüft die Verfügbarkeit von Features. Das Ergebnis ist eine der
Zeichenfolgen "Undefined", "Available", "NotAvailable" und
"Preview".
– Undefinied: Die Verfügbarkeit des Features ist nicht definiert
–Undefinied: Die Verfügbarkeit des Features ist nicht definiert
(der Featurename ist für den Prüfer der Featureverfügbarkeit
unbekannt)
– NotAvailable: Das Feature ist nicht verfügbar (im Gegensatz zu
-NotAvailable: Das Feature ist nicht verfügbar (im Gegensatz zu
"Undefined", wo der Featurename für den Prüfer der Featureverfügbarkeit
bekannt ist und er weiß, dass das Feature von der
aktuellen MSBuild-Engine nicht unterstützt wird)
– Available: Das Feature ist verfügbar
– Preview: Das Feature befindet sich in der Vorschau (nicht stabil)
-Available: Das Feature ist verfügbar
-Preview: Das Feature befindet sich in der Vorschau (nicht stabil)
(Kurzform: -fa)
</target>
<note>
@ -234,15 +235,15 @@
(Short form: -tl)
</source>
<target state="translated"> -terminalLogger[:auto,on,off]
Aktiviert oder deaktiviert die Terminalprotokollierung. Terminalprotokollierung
Aktiviert oder deaktiviert die Terminalprotokollierung. Terminal-Logger
bietet verbesserte Buildausgabe auf der Konsole in Echtzeit,
logisch nach Projekt organisiert und entwickelt, um
verwertbare Informationen hervorzuheben. Geben Sie "auto" an (oder verwenden Sie die Option
ohne Argumente), um die Terminalprotokollierung nur zu verwenden, wenn die
Standardausgabe nicht umgeleitet wird. Analysieren Sie die Ausgabe nicht,
ohne Argumente), um den Terminal-Logger nur zu verwenden, wenn die
Standardausgabe nicht umgeleitet wird. Analysieren Sie die Ausgabe nicht
oder vertrauen Sie darauf, dass sie in zukünftigen
Versionen unverändert bleibt. Diese Option ist in MSBuild 17.8 und
höher verfügbar.
später verfügbar.
(Kurzform: -tl)
</target>
<note>
@ -271,22 +272,22 @@
-tlp:default=auto;verbosity=diag;shownCommandLine
</source>
<target state="translated"> -terminalLoggerParameters: &lt;parameters&gt;
Parameter für die Terminalprotokollierung. (Kurzform: -tlp)
Parameter für Terminal-Logger. (Kurzform: -tlp)
Die verfügbaren Parameter.
default: Gibt das Standardverhalten der
Terminalprotokollierung an. Erfordert einen der folgenden Werte:
default: Gibt das Standardverhalten des Terminal-
Loggers an. Erfordert einen der folgenden Werte:
– "on", "true" erzwingt die Verwendung von TerminalLogger, auch
bei einer Deaktivierung.
wenn er deaktiviert werden sollte.
– "off", "true" erzwingt die Nichtverwendung von TerminalLogger, auch
bei einer Aktivierung.
wenn er aktiviert werden sollte.
– "auto" aktiviert TerminalLogger, wenn das Terminal
dies unterstützt, und die Sitzung nicht umgeleitet wurde
stdout/stderr
verbosity: Überschreiben Sie die Einstellung "-verbosity" für diese
Protokollierung
verbosity: Überschreiben Sie die Einstellung "-verbosity" für diesen
Logger
showCommandLine: TaskCommandLineEvent-Meldungen anzeigen
Beispiel:
Beispiel:
-tlp:default=auto;verbosity=diag;shownCommandLine
</target>
<note>
@ -305,7 +306,7 @@
<target state="translated"> -getResultOutputFile:file
Leiten Sie die Ausgabe von get* in eine Datei um.
Beispiel:
Beispiel:
-getProperty:Bar -getResultOutputFile:Biz.txt
Dadurch wird der Wert der Eigenschaftsleiste in Biz.txt geschrieben.
</target>
@ -320,10 +321,10 @@
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</source>
<target state="needs-review-translation"> -check
Aktiviert BuildChecks während des Builds.
BuildCheck ermöglicht die Regelauswertung, um Eigenschaften
des Builds sicherzustellen. Weitere Infos: aka.ms/buildcheck
<target state="new"> -check
Enables BuildChecks during the build.
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</target>
<note>
{Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"}
@ -468,7 +469,7 @@
value that comes from a response file.
</source>
<target state="translated"> -interactive[:True|False]
Weist darauf hin, dass für Aktionen im Build eine
Weist darauf hin, dass für Aktionen im Build eine
Interaktion mit dem Benutzer zugelassen ist. Verwenden Sie dieses Argument
in einem automatisierten Szenario, in dem keine Interaktivität
erwartet wird.
@ -637,7 +638,7 @@ Dies ist ein restriktiverer Modus von MSBuild, da er erfordert,
</source>
<target state="translated"> -warnNotAsError[:code[;code2]]
Liste der Warnungscodes, die nicht als Fehler behandelt werden.
Semikolon oder Komma zum Trennen
Semikolon oder Komma zum Trennen
mehrerer Warnungscodes verwenden. Hat keine Auswirkungen, wenn der Switch -warnaserror
nicht festgelegt ist.
@ -705,8 +706,8 @@ Dies ist ein restriktiverer Modus von MSBuild, da er erfordert,
Antwortdateien anzugeben, geben Sie jede Antwortdatei
gesondert an.
Alle Antwortdateien mit dem Name "msbuild.rsp" werden automatisch
in den folgenden Speicherorten verwendet:
Alle Antwortdateien mit dem Name "msbuild.rsp" werden automatisch
in den folgenden Speicherorten verwendet:
(1) Verzeichnis von "msbuild.exe"
(2) Verzeichnis des ersten erstellten Projekts oder Projektmappe
</target>
@ -797,16 +798,16 @@ Dies ist ein restriktiverer Modus von MSBuild, da er erfordert,
-logger:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
-logger:XMLLogger,C:\Loggers\MyLogger.dll;OutputAsHTML
</source>
<target state="translated"> -logger:&lt;Protokollierung&gt; Mithilfe dieser Protokollierung werden Ereignisse von MSBuild protokolliert. Um mehrere Protokollierungen anzugeben,
<target state="translated"> -logger:&lt;Protokollierung&gt; Mithilfe dieser Protokollierung werden Ereignisse von MSBuild protokolliert. Um mehrere Protokollierungen anzugeben,
wird jede Protokollierung gesondert angegeben.
Die Syntax für die &lt;Protokollierung&gt; lautet:
[&lt;Klasse&gt;,]&lt;assembly&gt;[,&lt;Optionen&gt;][;&lt;Parameter&gt;]
[&lt;Klasse&gt;,]&lt;Assembly&gt;[,&lt;Optionen&gt;][;&lt;Parameter&gt;]
Die Syntax für die &lt;Protokollierungsklasse&gt; lautet:
[&lt;Teilweiser oder vollständiger Namespace&gt;.]&lt;Name der Protokollierungsklasse&gt;
Die Syntax für die &lt;Protokollierungsassembly&gt; lautet:
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
{&lt;Assemblyname&gt;[,&lt;strong name&gt;] | &lt;Assemblydatei&gt;}
Die Protokollierungsoptionen geben an, wie MSBuild die Protokollierung erstellt.
Die &lt;Protokollierungsparameter&gt; sind optional und werden genau
Die &lt;Protokollierungsparameter&gt; sind optional und werden genau
so an die Protokollierung übergeben, wie sie eingegeben wurden. (Kurzform: -l)
Beispiele:
-logger:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
@ -901,7 +902,7 @@ Hinweis: Ausführlichkeit der Dateiprotokollierungen
WarningsOnly: Zeigt nur Warnungen an.
NoItemAndPropertyList: Zeigt keine Liste der Elemente
und Eigenschaften am Anfang jeder Projekterstellung an.
ShowCommandLine: Zeigt TaskCommandLineEvent-Meldungen an.
ShowCommandLine: Zeigt TaskCommandLineEvent-Meldungen an.
ShowTimestamp: Zeigt den Timestamp als Präfix einer
Meldung an.
ShowEventId: Zeigt die eventId für gestartete
@ -1077,18 +1078,18 @@ Dieses Protokollierungsformat ist standardmäßig aktiviert.
-dl:MyLogger,C:\My.dll*ForwardingLogger,C:\Logger.dll
</source>
<target state="translated"> -distributedlogger:&lt;Zentrale Protokollierung&gt;*&lt;Weiterleitende Protokollierung&gt;
Mithilfe dieser Protokollierung werden Ereignisse von MSBuild protokolliert, wobei an jeden Knoten eine andere
Protokollierungsinstanz angefügt wird. Um mehrere Protokollierungen anzugeben, wird jede Protokollierung
Mithilfe dieser Protokollierung werden Ereignisse von MSBuild protokolliert, wobei an jeden Knoten eine andere
Protokollierungsinstanz angefügt wird. Um mehrere Protokollierungen anzugeben, wird jede Protokollierung
gesondert angegeben.
(Kurzform -dl)
Die Syntax für die &lt;Protokollierung&gt; lautet:
[&lt;Klasse&gt;,]&lt;assembly&gt;[,&lt;Optionen&gt;][;&lt;Parameter&gt;]
[&lt;Klasse&gt;,]&lt;Assembly&gt;[,&lt;Optionen&gt;][;&lt;Parameter&gt;]
Die Syntax für die &lt;Protokollierungsklasse&gt; lautet:
[&lt;Teilweiser oder vollständiger Namespace&gt;.]&lt;Name der Protokollierungsklasse&gt;
Die Syntax für die &lt;Protokollierungsassembly&gt; lautet:
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
{&lt;Assemblyname&gt;[,&lt;strong name&gt;] | &lt;Assemblydatei&gt;}
Die Protokollierungsoptionen geben an, wie MSBuild die Protokollierung erstellt.
Die &lt;Protokollierungsparameter&gt; sind optional und werden genau
Die &lt;Protokollierungsparameter&gt; sind optional und werden genau
so an die Protokollierung übergeben, wie sie eingegeben wurden. (Kurzform: -l)
Beispiele:
-dl:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
@ -1113,8 +1114,8 @@ Dieses Protokollierungsformat ist standardmäßig aktiviert.
-ignoreProjectExtensions:.sln
</source>
<target state="translated"> -ignoreprojectextensions:&lt;Erweiterungen&gt;
Liste der zu ignorierenden Erweiterungen, wenn die zu erstellende
Projektdatei ermittelt wird. Verwenden Sie ein Semikolon oder ein Komma,
Liste der zu ignorierenden Erweiterungen, wenn die zu erstellende
Projektdatei ermittelt wird. Verwenden Sie ein Semikolon oder ein Komma,
um mehrere Erweiterungen voneinander zu trennen.
(Kurzform: -ignore)
Beispiel:
@ -1140,8 +1141,8 @@ Dieses Protokollierungsformat ist standardmäßig aktiviert.
</source>
<target state="translated"> -toolsversion:&lt;Version&gt;
Die Version des MSBuild-Toolsets (Aufgaben, Ziele usw.),
die während des Erstellens zu verwenden ist. Diese Version überschreibt die
von einzelnen Projekten angegebenen Versionen. (Kurzform:
die während des Erstellens zu verwenden ist. Diese Version überschreibt die
von einzelnen Projekten angegebenen Versionen. (Kurzform:
-tv)
Beispiel:
-toolsversion:3.5
@ -1200,14 +1201,14 @@ Dieses Protokollierungsformat ist standardmäßig aktiviert.
<target state="translated"> -distributedFileLogger
Protokolliert die Erstellungsausgabe in mehrere Dateien, eine Protokolldatei
pro MSBuild-Knoten. Der anfängliche Speicherort für diese Dateien ist
das aktuelle Verzeichnis. Standardmäßig werden die Dateien
das aktuelle Verzeichnis. Standardmäßig werden die Dateien
"MSBuild&lt;Knoten-ID&gt;.log" benannt. Der Speicherort der Datei und
andere Parameter für fileLogger können durch das Hinzufügen
andere Parameter für fileLogger können durch das Hinzufügen
des Schalters "-fileLoggerParameters" angegeben werden.
Wenn mithilfe des fileLoggerParameters-Parameters ein Protokolldateiname festgelegt wurde,
verwendet die verteilte Protokollierung den Dateinamen als
Vorlage und fügt die Knoten-ID an diesen Dateinamen an,
verwendet die verteilte Protokollierung den Dateinamen als
Vorlage und fügt die Knoten-ID an diesen Dateinamen an,
um für jeden Knoten eine Protokolldatei zu erstellen.
</target>
<note>
@ -1251,31 +1252,31 @@ Dieses Protokollierungsformat ist standardmäßig aktiviert.
</source>
<target state="translated"> -fileLoggerParameters[n]:&lt;Parameter&gt;
Gibt zusätzliche Parameter für Dateiprotokollierungen an.
Dieser Schalter bedeutet, dass der entsprechende
Dieser Schalter bedeutet, dass der entsprechende
Schalter "-fileLogger[n]" ebenfalls vorhanden ist.
"n" (optional) kann eine Zahl von 1–9 sein.
"-fileLoggerParameters" wird auch von verteilten
"-fileLoggerParameters" wird auch von verteilten
Dateiprotokollierungen verwendet (siehe Beschreibung zu "-distributedFileLogger").
(Kurzform: -flp[n])
Es sind dieselben Parameter wie für die Konsolenprotokollierung
verfügbar. Einige zusätzliche Parameter:
LogFile: Pfad der Protokolldatei, in die das
LogFile: Pfad der Protokolldatei, in die das
Buildprotokoll geschrieben wird.
Append: Gibt an, ob das Buildprotokoll erweitert oder
Append: Gibt an, ob das Buildprotokoll erweitert oder
oder überschrieben wird. Mit diesem Schalter
wird das Buildprotokoll an die Protokolldatei angefügt;
Ohne diesen Schalter wird der Inhalt
der vorhandenen Protokolldatei überschrieben.
Ohne diesen Schalter wird der Inhalt
der vorhandenen Protokolldatei überschrieben.
Standardmäßig wird die Protokolldatei nicht erweitert.
Encoding: Gibt die Codierung der Datei an,
Encoding: Gibt die Codierung der Datei an,
z. B. UTF-8, Unicode oder ASCII.
Die Standardeinstellung für "verbosity" ist "Detailed".
Beispiele:
-fileLoggerParameters:LogFile=MyLog.log;Append;
Verbosity=diagnostic;Encoding=UTF-8
-flp:Summary;Verbosity=minimal;LogFile=msbuild.sum
-flp1:warningsonly;logfile=msbuild.wrn
-flp:Summary;Verbosity=minimal;LogFile=msbuild.sum
-flp1:warningsonly;logfile=msbuild.wrn
-flp2:errorsonly;logfile=msbuild.err
</target>
<note>
@ -1301,7 +1302,7 @@ Dieses Protokollierungsformat ist standardmäßig aktiviert.
<target state="translated"> -nodeReuse:&lt;Parameter&gt;
Aktiviert oder deaktiviert die Wiederverwendung von MSBuild-Knoten.
Die Parameter lauten:
True: Knoten bleiben nach dem Abschluss der Erstellung
True: Knoten bleiben nach dem Abschluss der Erstellung
erhalten und werden bei folgenden Erstellungen wiederverwendet (Standardeinstellung).
False: Knoten bleiben nach dem Abschluss der Erstellung nicht erhalten.
(Kurzform: -nr)
@ -1833,12 +1834,12 @@ Dieses Protokollierungsformat ist standardmäßig aktiviert.
</trans-unit>
<trans-unit id="SAC_Enforcement">
<source>1: in enforcement</source>
<target state="translated">1: bei der Durchsetzung</target>
<target state="translated">1: bei der Erzwingung</target>
<note />
</trans-unit>
<trans-unit id="SAC_Evaluation">
<source>2: in evaluation. It is recommended to turn off Smart App Control in development environemnt as otherwise performance might be impacted</source>
<target state="translated">2: in Auswertung. Es wird empfohlen, Smart App Control in der Entwicklungsumgebung zu deaktivieren, da andernfalls die Leistung beeinträchtigt werden könnte</target>
<target state="translated">2: in Auswertung. Es wird empfohlen, Smart App Control in der Entwicklungsumgebung zu deaktivieren, da andernfalls die Leistung beeinträchtigt werden könnte.</target>
<note>Smart App Control, "VerifiedAndReputablePolicyState" should not be localized</note>
</trans-unit>
<trans-unit id="SAC_Off">
@ -2364,4 +2365,4 @@ Dieses Protokollierungsformat ist standardmäßig aktiviert.
</trans-unit>
</body>
</file>
</xliff>
</xliff>

49
src/MSBuild/Resources/xlf/Strings.es.xlf сгенерированный
Просмотреть файл

@ -125,7 +125,7 @@
Hace que MSBuild informe de los accesos a los archivos a cualquier
complemento de caché de proyectos.
Esta marca es experimental y puede que no funcione según lo previsto.
Esta marca es experimental y puede que no funcione según lo previsto.
</target>
<note>
LOCALIZATION: "-reportFileAccesses" should not be localized.
@ -320,10 +320,10 @@
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</source>
<target state="needs-review-translation"> -check
Habilita BuildChecks durante la compilación.
BuildCheck permite evaluar reglas para garantizar que las propiedades
de la compilación. Para obtener más información, consulte aka.ms/buildcheck
<target state="new"> -check
Enables BuildChecks during the build.
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</target>
<note>
{Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"}
@ -798,14 +798,18 @@
-logger:XMLLogger,C:\Loggers\MyLogger.dll;OutputAsHTML
</source>
<target state="translated"> -logger:&lt;registrador&gt; Use este registrador para registrar eventos
de MSBuild. Para especificar varios registradores, especifique cada uno de ellos por separado.
de MSBuild. Para especificar varios registradores, especifique
cada uno de ellos por separado.
La sintaxis de &lt;registrador&gt; es:
[&lt;clase&gt;,]&lt;assembly&gt;[,&lt;opciones&gt;][;&lt;parámetros&gt;]
[&lt;clase&gt;,]&lt;ensamblado&gt;[,&lt;opciones&gt;][;&lt;parámetros&gt;]
La sintaxis de &lt;clase del registrador&gt; es:
[&lt;espacio de nombres parcial o completo&gt;.]&lt;nombre de clase del registrador&gt;
La sintaxis de &lt;ensamblado del registrador&gt; es:
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
Las opciones del registrador especifican cómo crea MSBuild el registrador.
[&lt;espacio de nombres parcial o completo&gt;.]&lt;nombre de
clase del registrador&gt;
La sintaxis de &lt;ensamblado del registrador&gt; es:
{&lt;nombre del ensamblado&gt;[,&lt;strong name&gt;] | &lt;archivo
de ensamblado&gt;}
Las opciones del registrador especifican cómo crea MSBuild
el registrador.
Los &lt;parámetros del registrador&gt; son opcionales y se pasan
al registrador tal como se escriben. (Forma corta: -l)
Ejemplos:
@ -904,7 +908,7 @@
ShowCommandLine: muestra los mensajes de TaskCommandLineEvent
ShowTimestamp: muestra la marca de tiempo como un prefijo en los
mensajes.
ShowEventId: muestra el identificador de evento para los eventos iniciados, los eventos
ShowEventId: muestra el identificador de evento para los eventos iniciados, los eventos
finalizados y los mensajes.
ForceNoAlign: no alinea el texto al tamaño del
búfer de la consola
@ -1082,12 +1086,15 @@
Para especificar varios registradores, especifique cada uno
de ellos por separado. (Forma corta: -dl)
La sintaxis de &lt;registrador&gt; es:
[&lt;clase&gt;,]&lt;assembly&gt;[,&lt;opciones&gt;][;&lt;parámetros&gt;]
[&lt;clase&gt;,]&lt;ensamblado&gt;[,&lt;opciones&gt;][;&lt;parámetros&gt;]
La sintaxis de &lt;clase del registrador&gt; es:
[&lt;espacio de nombres parcial o completo&gt;.]&lt;nombre de la clase del registrador&gt;
[&lt;espacio de nombres parcial o completo&gt;.]&lt;nombre
de la clase del registrador&gt;
La sintaxis de &lt;ensamblado del registrador&gt; es:
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
Las opciones del registrador especifican cómo crea MSBuild el registrador.
{&lt;nombre del ensamblado&gt;[,&lt;strong name&gt;] | &lt;archivo
de ensamblado&gt;}
Las opciones del registrador especifican cómo crea MSBuild
el registrador.
Los &lt;parámetros del registrador&gt; son opcionales y se pasan
al registrador tal como se escriben. (Forma corta: -l)
Ejemplos:
@ -1113,8 +1120,8 @@
-ignoreProjectExtensions:.sln
</source>
<target state="translated"> -ignoreProjectExtensions:&lt;extensiones&gt;
Lista de extensiones que se omiten al determinar el
archivo del proyecto que se va a compilar. Use el carácter de
Lista de extensiones que se omiten al determinar el
archivo del proyecto que se va a compilar. Use el carácter de
punto y coma o coma para separar varias extensiones.
(Forma corta: -ignore)
Ejemplo:
@ -1265,9 +1272,9 @@
sobrescribirá el archivo de registro. Si se establece el
modificador, se adjunta el registro de compilación al archivo de registro;
Si no se especifica el modificador, se sobrescribe
el contenido del archivo de registro existente.
el contenido del archivo de registro existente.
El valor predeterminado es adjuntar el archivo de registro.
Encoding: especifica la codificación del archivo,
Encoding: especifica la codificación del archivo,
por ejemplo, UTF-8, Unicode o ASCII
El nivel de detalle predeterminado es Detailed.
Ejemplos:
@ -2362,4 +2369,4 @@
</trans-unit>
</body>
</file>
</xliff>
</xliff>

57
src/MSBuild/Resources/xlf/Strings.fr.xlf сгенерированный
Просмотреть файл

@ -123,7 +123,7 @@
</source>
<target state="translated"> -reportFileAccesses[:True|False]
Entraîne le signalement par MSBuild des accès par fichiers aux plug-ins
de cache de projet configurés.
cache de projet configurés.
Cet indicateur est expérimental et peut ne pas fonctionner comme prévu.
</target>
@ -143,7 +143,7 @@
Notez la valeur d’une ou de plusieurs propriétés spécifiées
après l’évaluation, sans exécuter la build, ou si
l’option -targets ou l’option -getTargetResult est
utilisée, écrivez les valeurs après la build.
utilisé, écrivez les valeurs après la génération.
</target>
<note>
LOCALIZATION: "-getProperty", "-targets" and "-getTargetResult" should not be localized.
@ -163,7 +163,7 @@
leurs métadonnées associées après l’évaluation sans
l’exécution de la build, ou si l’option -targets
ou l’option -getTargetResult est utilisée, écrivez
les valeurs après la build.
les valeurs après la génération.
</target>
<note>
LOCALIZATION: "-getItem", "targets" and "getTargetResult" should not be localized.
@ -202,14 +202,14 @@
</source>
<target state="translated"> -featureAvailability:featureName,...
Vérifiez la disponibilité des fonctionnalités. Le résultat est l’une des
chaînes « Non défini », « Disponible », « Indisponible » et
« Préversion ».
chaînes « Undefined », « Available », « NotAvailable » et
« Aperçu ».
- Non défini : la disponibilité de la fonctionnalité n’est pas définie
(le nom de la fonctionnalité est inconnu du vérificateur de la disponibilité
des fonctionnalités)
- Indisponible : la fonctionnalité n’est pas disponible (contrairement à
Non défini, le nom de la fonctionnalité est connu du vérificateur de la fonctionnalité
et il sait que la fonctionnalité n’est pas
(le nom de la fonctionnalité est inconnu de la disponibilité des fonctionnalités
vérificateur)
- NotAvailable : la fonctionnalité n’est pas disponible (contrairement à
Non défini, le nom de la fonctionnalité est connu de la fonctionnalité
et sait que la fonctionnalité n’est pas
prise en charge par le moteur MSBuild actuel)
- Disponible : la fonctionnalité est disponible
- Préversion : la fonctionnalité est en préversion (non stable)
@ -236,13 +236,14 @@
<target state="translated"> -terminalLogger[:auto,on,off]
Activez ou désactivez l’enregistreur d’événements du terminal. Enregistreur d’événements terminal
fournit une sortie de build améliorée sur la console en temps réel,
organisée logiquement par projet et conçu pour mettre en évidence
organisé logiquement par projet et conçu pour mettre en évidence
les informations exploitables. Spécifier automatiquement (ou utiliser l’option
sans arguments) pour utiliser l’enregistreur d’événements de terminal uniquement si la
sortie standard n’est pas redirigée. N’analysez pas la sortie
et ne vous attendez pas à ce qu’elle reste inchangée dans les futures
sans arguments) pour utiliser l’enregistreur d’événements de terminal uniquement si le
la sortie standard n’est pas redirigée. N’analysez pas la sortie
ou reposez-vous sur le fait qu’il reste inchangé dans les
futures
versions. Cette option est disponible dans MSBuild 17.8 et
versions ultérieures.
ultérieures.
(Forme abrégée : -tl)
</target>
<note>
@ -273,8 +274,8 @@
<target state="translated"> -terminalLoggerParameters: &lt;parameters&gt;
Paramètres de l’enregistreur d’événements de terminal. (Forme abrégée : -tlp)
Paramètres disponibles.
default --Spécifie le comportement par défaut de l’enregistreur
de terminal. Elle nécessite l’une des valeurs suivantes :
default --Spécifie le comportement par défaut du terminal
enregistreur. Elle nécessite l’une des valeurs suivantes :
- 'on', 'true' force TerminalLogger à être utilisé même
quand il serait désactivé.
- 'off', 'false' force TerminalLogger à ne pas être utilisé
@ -320,10 +321,10 @@
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</source>
<target state="translated"> -check
Active BuildChecks pendant la build.
BuildCheck permet d'évaluer les règles pour garantir les propriétés
de la build. Pour plus d'informations, consultez aka.ms/buildcheck
<target state="new"> -check
Enables BuildChecks during the build.
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</target>
<note>
{Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"}
@ -804,7 +805,7 @@ Cet indicateur est expérimental et peut ne pas fonctionner comme prévu.
Syntaxe de &lt;classe de journalisation&gt; :
[&lt;espace de noms partiels ou complets&gt;.]&lt;nom de la classe de journalisation&gt;
Syntaxe de &lt;assembly de journalisation&gt; :
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
{&lt;nom d'assembly&gt;[,&lt;strong name&gt;] | &lt;fichier d'assembly&gt;}
Les options de journalisation spécifient la façon dont MSBuild crée le journaliseur.
Les &lt;paramètres de journalisation&gt; sont facultatifs. Ils sont passés
au journaliseur tels que vous les avez tapés. (Forme abrégée : -l)
@ -1086,7 +1087,7 @@ Remarque : verbosité des enregistreurs d’événements de fichiers
Syntaxe de &lt;classe de journalisation&gt; :
[&lt;espace de noms partiels ou complets&gt;.]&lt;nom de la classe de journalisation&gt;
Syntaxe de &lt;assembly de journalisation&gt; :
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
{&lt;nom d'assembly&gt;[,&lt;strong name&gt;] | &lt;fichier d'assembly&gt;}
Les options de journalisation spécifient la façon dont MSBuild crée le journaliseur.
Les &lt;paramètres de journalisation&gt; sont facultatifs. Ils sont passés
au journaliseur tels que vous les avez tapés. (Forme abrégée : -l)
@ -1559,7 +1560,7 @@ Remarque : verbosité des enregistreurs d’événements de fichiers
</trans-unit>
<trans-unit id="MissingGetItemError">
<source>MSBUILD : error MSB1014: Must provide an item name for the getItem switch.</source>
<target state="translated">MSBUILD : error MSB1014: Doit fournir un nom d'élément pour le commutateur getItem.</target>
<target state="new">MSBUILD : error MSB1014: Must provide an item name for the getItem switch.</target>
<note>
{StrBegin="MSBUILD : error MSB1014: "}UE: This happens if the user does something like "msbuild.exe -getItem". The user must pass in an actual item name
following the switch, as in "msbuild.exe -getItem:blah".
@ -1568,7 +1569,7 @@ Remarque : verbosité des enregistreurs d’événements de fichiers
</trans-unit>
<trans-unit id="MissingGetPropertyError">
<source>MSBUILD : error MSB1010: Must provide a property name for the getProperty switch.</source>
<target state="translated">MSBUILD : error MSB1010: Doit fournir un nom de propriété pour le commutateur getProperty.</target>
<target state="new">MSBUILD : error MSB1010: Must provide a property name for the getProperty switch.</target>
<note>
{StrBegin="MSBUILD : error MSB1010: "}UE: This happens if the user does something like "msbuild.exe -getProperty". The user must pass in an actual property name
following the switch, as in "msbuild.exe -getProperty:blah".
@ -1586,7 +1587,7 @@ Remarque : verbosité des enregistreurs d’événements de fichiers
</trans-unit>
<trans-unit id="MissingGetTargetResultError">
<source>MSBUILD : error MSB1017: Must provide a target name for the getTargetResult switch.</source>
<target state="translated">MSBUILD : error MSB1017: Doit fournir un nom de cible pour le commutateur getTargetResult.</target>
<target state="new">MSBUILD : error MSB1017: Must provide a target name for the getTargetResult switch.</target>
<note>
{StrBegin="MSBUILD : error MSB1017: "}UE: This happens if the user does something like "msbuild.exe -getTargetResult". The user must pass in an actual target name
following the switch, as in "msbuild.exe -getTargetResult:blah".
@ -1838,7 +1839,7 @@ Remarque : verbosité des enregistreurs d’événements de fichiers
</trans-unit>
<trans-unit id="SAC_Evaluation">
<source>2: in evaluation. It is recommended to turn off Smart App Control in development environemnt as otherwise performance might be impacted</source>
<target state="translated">2 : en évaluation. Il est recommandé de désactiver smart App Control dans l’environnement de développement, car les performances risquent d’être affectées dans le cas contraire</target>
<target state="translated">2 : en évaluation Il est recommandé de désactiver smart App Control dans l’environnement de développement, car les performances risquent d’être affectées dans le cas contraire</target>
<note>Smart App Control, "VerifiedAndReputablePolicyState" should not be localized</note>
</trans-unit>
<trans-unit id="SAC_Off">
@ -1875,7 +1876,7 @@ Remarque : verbosité des enregistreurs d’événements de fichiers
</trans-unit>
<trans-unit id="SolutionBuildInvalidForCommandLineEvaluation">
<source>MSBUILD : error MSB1063: Cannot access properties or items when building solution files or solution filter files. This feature is only available when building individual projects.</source>
<target state="translated">MSBUILD : error MSB1063: Impossible d'accéder aux propriétés ou aux éléments lors de la création de fichiers de solution ou de fichiers de filtre de solution. Cette fonctionnalité est disponible uniquement lors de la génération de projets individuels.</target>
<target state="new">MSBUILD : error MSB1063: Cannot access properties or items when building solution files or solution filter files. This feature is only available when building individual projects.</target>
<note>
{StrBegin="MSBUILD : error MSB1063: "}UE: This happens if the user passes in a solution file when trying to access individual properties or items. The user must pass in a project file.
LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.

121
src/MSBuild/Resources/xlf/Strings.it.xlf сгенерированный
Просмотреть файл

@ -122,10 +122,10 @@
This flag is experimental and may not work as intended.
</source>
<target state="translated"> -reportFileAccesses[:True|False]
Fa in modo che MSBuild segnali gli accessi ai file a qualsiasi
Fa in modo che MSBuild segnali gli accessi ai file a qualsiasi file configurato
plug-in della cache del progetto.
Questo flag è sperimentale e potrebbe non funzionare come previsto.
Questo flag è sperimentale e potrebbe non funzionare come previsto.
</target>
<note>
LOCALIZATION: "-reportFileAccesses" should not be localized.
@ -140,10 +140,10 @@
used, write out the values after the build.
</source>
<target state="translated"> -getProperty:propertyName,...
Scrive il valore di una o più proprietà specificate
dopo la valutazione, senza eseguire la compilazione oppure, se
usa l'opzione -targets o l’opzione -getTargetResult
scrive i valori dopo la compilazione.
Scrivere il valore di una o più proprietà specificate
dopo la valutazione, senza eseguire la compilazione o se
si usa sia l'opzione -targets che l’opzione -getTargetResult
scrivere i valori dopo la compilazione.
</target>
<note>
LOCALIZATION: "-getProperty", "-targets" and "-getTargetResult" should not be localized.
@ -159,10 +159,10 @@
the values after the build.
</source>
<target state="translated"> -getItem:itemName,...
Scrive il valore di uno o più elementi specificati e
Scrivere il valore di uno o più elementi specificati e
i metadati associati dopo la valutazione senza
eseguire la compilazione oppure, se si usa l’opzione -targets
o l'opzione -getTargetResult, scrive
eseguire la compilazione o in caso si usi l’opzione -targets
oppure l'opzione -getTargetResult, scrivere
i valori dopo la compilazione.
</target>
<note>
@ -176,7 +176,7 @@
the specified targets will be executed.
</source>
<target state="translated"> -getTargetResult:targetName,...
Scrive il valore di output di una o più destinazioni
Scrivere il valore di output di una o più destinazioni
per eseguire le destinazioni specificate.
</target>
<note>
@ -201,18 +201,19 @@
(Short form: -fa)
</source>
<target state="translated"> -featureAvailability:featureName,...
Verifica la disponibilità delle funzionalità. Il risultato è una delle
stringhe "Undefined", "Available", "NotAvailable" e
"Preview".
- Undefined: la disponibilità della funzionalità non è definita
(il nome della funzionalità non è noto al controllo
Verificare la disponibilità delle funzionalità. Il risultato è uno delle
stringhe "Non definito", "Disponibile", "Non disponibile" e
"Anteprima".
- Non definito: la disponibilità della funzionalità non è definita
(Il nome della funzionalità non è noto al controllo
della disponibilità delle funzionalità)
- NotAvailable: la funzionalità non è disponibile (a differenza di
Undefined, il nome della funzionalità è noto al controllo
della disponibilità della funzionalità, che sa che la funzionalità non è
- Non disponibile: la funzionalità non è disponibile (a differenza di
Non definito, dove il nome della funzionalità è noto al controllo della disponibilità della funzionalità
,
che sa che la funzionalità non è
supportata dal motore MSBuild corrente)
- Available: la funzionalità è disponibile
- Preview : la funzionalità è in anteprima (non stabile)
- Disponibile: la funzionalità è disponibile
- Anteprima : la funzionalità è in anteprima (non stabile)
(Forma breve: -fa)
</target>
<note>
@ -233,17 +234,17 @@
later.
(Short form: -tl)
</source>
<target state="translated"> -terminalLogger[:auto,on,off]
Abilita o disabilita il logger del terminale. Il logger del terminale
fornisce output di compilazione avanzato nella console in tempo reale,
con dati organizzati in maniera logica in base al progetto ed evidenziando
le informazioni che richiedono intervento. Specificare auto (o usare l'opzione
senza argomenti) per usare il logger del terminale solo se
l'output standard non viene reindirizzato. Non eseguire il parsing dell'output
oppure fare affidamento sul fatto che rimarrà invariato nelle future
<target state="translated"> -terminalLogger[:automatico, attivato, disattivato]
Abilitare o disabilitare il logger del terminale. Logger del terminale
fornisce output di compilazione avanzati in tempo reale sulla console,
organizzato in maniera logica in base al progetto e progettato per evidenziare
dati analitici interattivi. Specificare automatico (o usare l'opzione
senza argomenti) per usare il logger del terminale solo se l’
output standard non viene reindirizzato. Non analizzare l'output
oppure affidarsi al fatto che non verrà modificato nelle future
versioni. Questa opzione è disponibile in MSBuild 17.8 e
versioni successive.
(Forma breve: -tl)
Forma breve: -tl)
</target>
<note>
LOCALIZATION: "-terminalLogger", "-tl", and "auto" should not be localized.
@ -271,18 +272,18 @@
-tlp:default=auto;verbosity=diag;shownCommandLine
</source>
<target state="translated"> -terminalLoggerParameters: &lt;parameters&gt;
Parametri per il logger del terminale. (Forma breve: -tlp)
Parametri per il logger del terminale. Forma breve: -tlp)
Parametri disponibili.
default- Specifica il comportamento predefinito del terminale
impostazione predefinita- Specifica il comportamento predefinito del terminale
logger. Richiede uno dei valori seguenti:
- 'on', 'true' impone l'uso di TerminalLogger anche
- 'attivato', 'vero' forza l'uso di TerminalLogger anche
se venisse disabilitato.
- 'off', 'false' impone l'uso di TerminalLogger anche
- 'disattivato', 'falso' forza l'uso di TerminalLogger anche
se venisse abilitato.
- 'auto' abilita TerminalLogger quando il terminale
- 'automatico' abilita TerminalLogger quando il terminale
lo supporta e la sessione non ha reindirizzato il livello di dettaglio
stdout/stderr
verbosity--Ignora l'impostazione -verbosity per questo
-- Eseguire l'override dell'impostazione del livello di dettaglio per questo
logger
showCommandLine--Mostra i messaggi TaskCommandLineEvent
@ -303,11 +304,11 @@
This writes the value of property Bar into Biz.txt.
</source>
<target state="translated"> -getResultOutputFile:file
Reindirizza l'output di get* in un file.
Reindirizza l'output da get* in un file.
Esempio:
-getProperty:Bar -getResultOutputFile:Biz.txt
Il valore della proprietà Bar viene scritto in Biz.txt.
-getProperty:barra -getResultOutputFile:Biz.txt
Il valore della barra delle proprietà viene scritto in Biz.txt.
</target>
<note>
LOCALIZATION: "-getResultOutputFile", "get*" and "-getProperty" should not be localized.
@ -320,10 +321,10 @@
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</source>
<target state="needs-review-translation"> -check
Abilita BuildChecks durante la compilazione.
BuildCheck consente di valutare le regole per garantire le proprietà
della compilazione. Per altre informazioni, vedere aka.ms/buildcheck
<target state="new"> -check
Enables BuildChecks during the build.
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</target>
<note>
{Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"}
@ -713,7 +714,7 @@ Questo flag è sperimentale e potrebbe non funzionare come previsto.
separatamente.
Qualsiasi file di risposta denominato "msbuild.rsp" viene usato
automaticamente dai percorsi seguenti:
automaticamente dai percorsi seguenti:
(1) la directory di msbuild.exe
(2) la directory della prima compilazione di soluzione o progetto
</target>
@ -810,8 +811,8 @@ Questo flag è sperimentale e potrebbe non funzionare come previsto.
[&lt;classe&gt;,]&lt;assembly&gt;[,&lt;opzioni&gt;][;&lt;parametri&gt;]
La sintassi di &lt;classe logger&gt; è la seguente:
[&lt;spazio dei nomi parziale o completo&gt;.]&lt;nome classe logger&gt;
La sintassi di &lt;logger assembly&gt; è la seguente:
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
La sintassi di &lt;assembly logger&gt; è la seguente:
{&lt;nome assembly&gt;[,&lt;strong name&gt;] | &lt;file di assembly&gt;}
Le opzioni di logger consentono di specificare in che modo MSBuild crea il logger.
I &lt;parametri logger&gt; sono facoltativi e vengono passati al
logger così come vengono digitati. Forma breve: -l.
@ -1092,8 +1093,8 @@ Nota: livello di dettaglio dei logger di file
[&lt;classe&gt;,]&lt;assembly&gt;[,&lt;opzioni&gt;][;&lt;parametri&gt;]
La sintassi di &lt;classe logger&gt; è la seguente:
[&lt;spazio dei nomi parziale o completo&gt;.]&lt;nome classe logger&gt;
La sintassi di &lt;logger assembly&gt; è la seguente:
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
La sintassi di &lt;assembly logger&gt; è la seguente:
{&lt;nome assembly&gt;[,&lt;strong name&gt;] | &lt;file di assembly&gt;}
Le opzioni di logger consentono di specificare in che modo MSBuild crea il logger.
I &lt;parametri logger&gt; sono facoltativi e vengono passati al
logger così come vengono digitati. Forma breve: -l
@ -1212,8 +1213,9 @@ Nota: livello di dettaglio dei logger di file
è la directory corrente. Per impostazione predefinita, ai
file viene assegnato il nome "MSBuild&lt;idnodo&gt;.log". Il
percorso dei file e altri parametri di fileLogger possono
essere specificati aggiungendo l'opzione "-fileLoggerParameters".
essere specificati aggiungendo l'opzione
"-fileLoggerParameters".
Se il nome di un file di log viene impostato con l'opzione
fileLoggerParameters, il logger distribuito userà il nome
file come modello e aggiungerà l'ID del nodo per creare un
@ -1560,7 +1562,7 @@ Nota: livello di dettaglio dei logger di file
</trans-unit>
<trans-unit id="MissingFeatureAvailabilityError">
<source>MSBUILD : error MSB1067: Must provide a feature name for the featureAvailability switch.</source>
<target state="translated">MSBUILD : error MSB1067: È necessario fornire un nome di funzionalità per l’opzione featureAvailability.</target>
<target state="translated">MSBUILD : error MSB1067: È necessario fornire un nome funzionalità per l’opzione featureAvailability.</target>
<note>
{StrBegin="MSBUILD : error MSB1067: "}UE: This happens if the user does something like "msbuild.exe -featureAvailability". The user must pass in an actual feature name
following the switch, as in "msbuild.exe -featureAvailability:blah".
@ -2351,15 +2353,16 @@ Esegue la profilatura della valutazione di MSBuild e scrive
-restoreProperty:IsRestore=true;MyProperty=value
</source>
<target state="translated"> -restoreProperty:&lt;n&gt;=&lt;v&gt;
Imposta queste proprietà a livello di progetto o ne esegue
l'override solo durante il ripristino e non usa le
proprietà specificate con l'argomento -property.
&lt;v&gt; rappresenta il nome della proprietà e &lt;v&gt; il
valore della proprietà. Usare il punto e virgola o la
virgola per delimitare più proprietà o specificare ogni proprietà separatamente.
(Forma breve: -rp)
Esempio:
-restoreProperty:IsRestore=true;MyProperty=value
Imposta queste proprietà a livello di progetto o ne esegue
l'override solo durante il ripristino e non usa le
proprietà specificate con l'argomento -property.
&lt;v&gt; rappresenta il nome della proprietà e &lt;v&gt; il
valore della proprietà. Usare il punto e virgola o la
virgola per delimitare più proprietà o specificare ogni
proprietà separatamente.
Forma breve: -rp.
Esempio:
-restoreProperty:IsRestore=true;MyProperty=value
</target>
<note>
LOCALIZATION: "-restoreProperty" and "-rp" should not be localized.
@ -2378,4 +2381,4 @@ Esegue la profilatura della valutazione di MSBuild e scrive
</trans-unit>
</body>
</file>
</xliff>
</xliff>

148
src/MSBuild/Resources/xlf/Strings.ja.xlf сгенерированный
Просмотреть файл

@ -123,7 +123,7 @@
</source>
<target state="translated"> -reportFileAccesses[:True|False]
MSBuild が、構成されているプロジェクト キャッシュ プラグインへの
ファイル アクセスを報告するようにします。
ファイル アクセスを報告します。
このフラグは実験的なものであり、意図したとおりに動作しない可能性があります。
</target>
@ -140,11 +140,11 @@
used, write out the values after the build.
</source>
<target state="translated"> -getProperty:propertyName,...
評価後にビルドを実行せずに、1 つ以上の
指定されたプロパティの値を書き出します。
または、-targets オプションまたは -getTargetResult オプションが
使用されている場合は、ビルド後に値を書き出します。
</target>
1 つ以上の指定されたプロパティの値を書き出し
評価後、ビルドを実行せずに、または
-targets オプションまたは -getTargetResult オプションが
使用して、ビルド後に値を書き出します。
</target>
<note>
LOCALIZATION: "-getProperty", "-targets" and "-getTargetResult" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -159,12 +159,12 @@
the values after the build.
</source>
<target state="translated"> -getItem:itemName,...
評価後にビルドを実行せずに、1 つ以上の指定された項目の値と
関連付けられたメタデータを書き出します。
または、-targets オプションまたは -getTargetResult オプションが
使用されている場合は、ビルド後に
値を書き出します。
</target>
1 つ以上の指定された項目の値を書き出し、
評価後に関連付けられたメタデータを
ビルドを実行せずに、または -targets オプション
または -getTargetResult オプションが使用されている場合は、書き込み
ビルド後の値。
</target>
<note>
LOCALIZATION: "-getItem", "targets" and "getTargetResult" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -176,9 +176,9 @@
the specified targets will be executed.
</source>
<target state="translated"> -getTargetResult:targetName,...
1 つ以上のターゲットの出力値を書き出し、
指定したターゲットが実行されます。
</target>
1 つ以上のターゲットの出力値を書き出し、
指定したターゲットが実行されます。
</target>
<note>
LOCALIZATION: "-getTargetResult" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -201,20 +201,20 @@
(Short form: -fa)
</source>
<target state="translated"> -featureAvailability:featureName,...
機能の可用性を確認します。結果は、文字列 "Undefined"、
"Available"、"NotAvailable"、"Preview" の
いずれかになります。
- Undefined - 機能の可用性は未定義です
(機能名は機能の可用性チェッカーに対して
不明です)
- NotAvailable - この機能は使用できません
Undefined とは異なり、機能名は機能の可用性チェッカーが
認識しており、このチェッカーは、この機能が現在の MSBuild エンジンで
サポートされていないことを理解しています)
- Available - この機能は使用可能です
- Preview - 機能はプレビュー段階です (安定していません)
(短い形式: -fa)
</target>
機能の可用性を確認します。結果は、次のいずれかになります。
文字列 "Undefined"、"Available"、"NotAvailable"、および
"Preview" です。
- Undefined - 機能の可用性は未定義です
(機能名が機能の可用性に関して不明です
チェッカー)
- NotAvailable - この機能は使用できません
Undefined とは異なり、機能名は機能に認識されています
可用性チェッカーは、この機能が
現在の MSBuild エンジンでサポートされていないことを理解しています)
- Available - この機能は使用可能です
- Preview - 機能はプレビュー段階です (安定していません)
(短い形式: -fa)
</target>
<note>
LOCALIZATION: "-featureAvailability", "-fa", "Undefined", "Available" "NotAvailable" and "Preview"should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -234,17 +234,17 @@
(Short form: -tl)
</source>
<target state="translated"> -terminalLogger[:auto,on,off]
ターミナル ロガーを有効または無効にします。ターミナル ロガーは、
本体で強化されたビルド出力をリアルタイムに提供します。
この出力は、プロジェクトごとに論理的に整理されており、アクション可能な情報を
強調表示するように設計されています。標準出力がリダイレクトされない場合のみ、
auto を指定 (または引数を指定せずにオプションを使用) して、
ターミナル ロガーを使用します。出力を解析しないでください。
別の方法で出力を利用してください。残りの部分は将来のバージョンで
変更されずに残ります。このオプションは、MSBuild 17.8 以降で
利用可能です。
(短い形式: -tl)
</target>
ターミナル ロガーを有効または無効にします。ターミナル ロガーは
本体のビルド出力がリアルタイムで強化され、
プロジェクトごとに論理的に整理され、強調表示するように設計されています
アクション可能な情報です。auto を指定する (またはオプションを使用する)
引数を指定せずに) ターミナル ロガーを使用する場合は、
標準出力はリダイレクトされません。出力を解析しないでください
それ以外の場合は、将来変更されずに残っている
バージョン。このオプションは、MSBuild 17.8 以降で利用可能です
以降で。
(短い形式: -tl)
</target>
<note>
LOCALIZATION: "-terminalLogger", "-tl", and "auto" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -271,24 +271,25 @@
-tlp:default=auto;verbosity=diag;shownCommandLine
</source>
<target state="translated"> -terminalLoggerParameters: &lt;parameters&gt;
ターミナル ロガーへのパラメーター。(短い形式: -tlp)
使用可能なパラメーター。
default -- ターミナル ロガーの既定の動作を
指定します。次のいずれかの値が必要です。
- `on`、`true` の場合、TerminalLogger が無効である場合も
TerminalLogger を強制的に使用します。
- `off`、`false` の場合、TerminalLogger が有効である場合も
TerminalLogger を使用しないように強制します。
- `auto` の場合、ターミナルで TerminalLogger がサポートされており、
セッションが stdout/stderr をリダイレクトしていない場合、
TerminalLogger を有効にします
verbosity-- このロガーの -verbosity 設定を
オーバーライドします
showCommandLine -- TaskCommandLineEvent メッセージを表示します
ターミナル ロガーへのパラメーター。(短い形式: -tlp)
使用可能なパラメーター。
default -- ターミナル
の既定の動作を指定します
ロガー。次のいずれかの値が必要です:
- `on`、`true` は TerminalLogger を強制的に使用します
無効である場合も同様です。
- `off`、`false` は TerminalLogger を使用しないように強制します
有効である場合も同様です。
- `auto` は、次の場合にターミナルで TerminalLogger を有効にします
サポートされており、セッションがリダイレクトされていない場合です
stdout/stderr
verbosity-- 下記の verbosity 設定をオーバーライドします
logger
showCommandLine -- TaskCommandLineEvent メッセージを表示します
例:
-tlp:default=auto;verbosity=diag;shownCommandLine
</target>
例:
-tlp:default=auto;verbosity=diag;shownCommandLine
</target>
<note>
LOCALIZATION: "-terminalLoggerParameters", "-tlp", "default", "on", "true", "off", "false", "auto", "verbosity", "showCommandLine" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -303,12 +304,12 @@
This writes the value of property Bar into Biz.txt.
</source>
<target state="translated"> -getResultOutputFile:file
get* からの出力をファイルにリダイレクトします。
get* からの出力をファイルにリダイレクトします。
例:
-getProperty:Bar -getResultOutputFile:Biz.txt
これにより、プロパティ Bar の値が Biz.txt に書き込まれます。
</target>
例:
-getProperty:Bar -getResultOutputFile:Biz.txt
これにより、プロパティ Bar の値が Biz.txt に書き込まれます。
</target>
<note>
LOCALIZATION: "-getResultOutputFile", "get*" and "-getProperty" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -320,11 +321,10 @@
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</source>
<target state="needs-review-translation"> -check
ビルド中に BuildChecks を有効にします。
BuildCheck を使用すると、ビルドのプロパティ
を保証するための
ルールを評価できます。詳細については、aka.ms/buildcheck を参照してください
<target state="new"> -check
Enables BuildChecks during the build.
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</target>
<note>
{Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"}
@ -343,7 +343,7 @@
</trans-unit>
<trans-unit id="InvalidTerminalLoggerValue">
<source>MSBUILD : error MSB1065: Terminal logger value is not valid. It should be one of 'auto', 'true', or 'false'. {0}</source>
<target state="translated">MSBUILD : error MSB1065: ターミナル ロガーの値が無効です。'auto'、'true'、または 'false' のいずれかである必要があります。{0}</target>
<target state="translated">MSBUILD : error MSB1065: ターミナル ロガーの値が無効です。'auto'、'true'、または 'false' のいずれかである必要があります。 {0}</target>
<note>
{StrBegin="MSBUILD : error MSB1065: "}
UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
@ -576,7 +576,7 @@
</source>
<target state="translated"> -targets[:file]
使用可能なターゲットの一覧を、実際のビルド処理を
実行せずに出力します。既定では、出力はコンソール
実行せずに出力します。既定では、出力はコンソール
ウィンドウに書き込まれます。出力ファイルへのパスを
指定した場合は、代わりにそのファイルが使用されます。
(短い形式:-ts)
@ -836,7 +836,7 @@
<target state="translated"> -verbosity:&lt;level&gt; この量の情報をイベント ログに表示します。
利用可能な詳細レベル: q[uiet], m[inimal]、
n[ormal], d[etailed]、および diag[nostic]。(短縮形: -v)
例:
例:
-verbosity:quiet
注意: ファイル ロガーの詳細度は
@ -892,7 +892,7 @@
</source>
<target state="translated"> -consoleLoggerParameters:&lt;parameters&gt;
コンソール ロガーへのパラメーターです。(短縮形: -clp)
利用可能なパラメーター:
利用可能なパラメーター:
PerformanceSummary--タスク、ターゲット、プロジェクトにかかった時間を
表示します。
Summary--最後にエラーと警告の概要を表示します。
@ -1829,7 +1829,7 @@
</trans-unit>
<trans-unit id="SAC">
<source>Based on the Windows registry key VerifiedAndReputablePolicyState, SAC state = {0}.</source>
<target state="translated">Windows レジストリ キー VerifiedAndReputablePolicyState に基づいており、SAC 状態 = {0} です。</target>
<target state="translated">Windows レジストリ キー VerifiedAndReputablePolicyState に基づいて、SAC 状態 = {0}。</target>
<note>"Windows" is the OS, SAC is the Smart App Control, "VerifiedAndReputablePolicyState" should not be localized</note>
</trans-unit>
<trans-unit id="SAC_Enforcement">
@ -2277,7 +2277,7 @@
(Short form: -r)
</source>
<target state="translated"> -restore[:True|False]
他のターゲットをビルドする前に Restore
他のターゲットをビルドする前に Restore
という名前のターゲットを実行し、これらのターゲットのビルドが
最新の復元ビルド ロジックを使用するようにします。
これは、パッケージ ツリーでパッケージをビルド
@ -2365,4 +2365,4 @@
</trans-unit>
</body>
</file>
</xliff>
</xliff>

175
src/MSBuild/Resources/xlf/Strings.ko.xlf сгенерированный
Просмотреть файл

@ -141,7 +141,7 @@
</source>
<target state="translated"> -getProperty:propertyName,...
빌드를 실행하지 않고 평가 후
하나 이상의 지정된 속성 값을 작성하거나,
지정된 속성 중 하나 이상의 값을 작성하거나,
-targets 옵션 또는 -getTargetResult 옵션을 사용하는 경우
빌드 후 값을 작성합니다.
</target>
@ -160,8 +160,8 @@
</source>
<target state="translated"> -getItem:itemName,...
빌드를 실행하지 않고 평가 후
하나 이상의 지정된 항목 및
관련 메타데이터의 값을 작성하거나
지정된 항목 중 하나 이상의 값 및
연결된 해당 메타데이터를 작성하거나,
-targets 옵션 또는 -getTargetResult 옵션을 사용하는 경우
빌드 후 값을 작성합니다.
</target>
@ -176,7 +176,7 @@
the specified targets will be executed.
</source>
<target state="translated"> -getTargetResult:targetName,...
하나 이상의 대상의 출력 값을 작성하면
대상 하나 이상의 출력 값을 작성하면
지정된 대상이 실행됩니다.
</target>
<note>
@ -204,11 +204,11 @@
기능 가용성을 확인합니다. 결과는
문자열 "Undefined", "Available", "NotAvailable" 및
"Preview" 중 하나입니다.
- Undefined - 기능의 가용성이 정의되지 않았습니다
- 정의되지 않음 - 기능의 가용성이 정의되지 않았습니다
(기능 가용성 검사기에서 기능 이름을 인식할 수
없음).
- NotAvailable - 기능을 사용할 수 없습니다(
Undefined와 달리, 기능 가용성 검사가에서 기능 이름을
정의되지 않음과는 달리, 기능 가용성 검사가에서 기능 이름을
인식할 수 있으며 기능이 현재 MSBuild 엔진에서 지원되지
않는 것으로 인식하고 있음).
- Available - 기능을 사용할 수 있습니다.
@ -234,14 +234,14 @@
(Short form: -tl)
</source>
<target state="translated"> -terminalLogger[:auto,on,off]
터미널 로거를 사용하거나 사용하지 않도록 설정합니다. 터미널 로거는
콘솔에서 향상된 빌드 출력을 실시간으로 제공하고
프로젝트별로 논리적으로 구성되며 실행 가능한 정보를
강조 표시하도록 설계되어 있습니다. 표준 출력이 리디렉션되지 않는
경우에만 터미널 로거를 사용하려면 auto를 지정하거나
인수 없이 옵션을 사용합니다. 출력을 구문 분석하지 않으면
향후 버전에서도 변경되지 않은 상태로 유지될 것이라고
기대하지 마세요. 이 옵션은 MSBuild 17.8 이상 버전에서
터미널 로거를 사용하거나 사용하지 않도록 설정합니다. 터미널 로거
는 콘솔에서 향상된 빌드 출력을 실시간으로 제공합니다.
이러한 출력은 프로젝트별로 논리적으로 구성되고 실행 가능한 정보를
강조 표시하도록 설계되어 있습니다. 자동을 지정(또는 인수 없이 옵션
사용)하여 터미널 로거를 사용합니다. 단, 이 경우
표준 출력이 리디렉션되지 않아야 합니다. 출력을 구문 분석하지 않습니다.
그렇지 않을 경우 이후 버전에서 변경되지 않은 상태로
유지됩니다. 이 옵션은 MSBuild 17.8 이상 버전에서
제공됩니다.
(약식: -tl)
</target>
@ -273,20 +273,21 @@
<target state="translated"> -terminalLoggerParameters: &lt;parameters&gt;
터미널 로거에 대한 매개 변수입니다. (약식: -tlp)
사용 가능한 매개 변수입니다.
default--터미널 로거의 기본 동작을
지정합니다. 다음 값 중 하나가 필요합니다.
- 'on', 'true'는 비활성화된 경우에도 terminalLogger를
사용하도록 강제합니다.
- 'off', 'false'는 활성화된 경우에도 terminalLogger를
사용하지 않도록 강제합니다.
- 'auto'는 터미널이 지원하고 세션이
리디렉션되지 않을 때 TerminalLogger를 활성화합니다.
default--터미널의 기본 동작을 지정합니다.
로거입니다. 다음 값 중 하나가 필요합니다.
- 'on', 'true'는 terminalLogger를 사용하도록 강제하며,
이는 사용하지 않도록 설정된 경우에도 마찬가지입니다.
- 'off', 'false'는 terminalLogger를 사용하지 않도록 강제하며,
이는 사용하도록 설정된 경우에도 마찬가지입니다.
- 'auto'는 터미널이
지원하고 세션이 리디렉션되지 않을 때 TerminalLogger를 사용하도록 설정합니다.
stdout/stderr
verbosity--이 로거에 대한 -verbosity 설정을
verbosity--이
로거에 대한 -verbosity 설정을
재정의합니다.
showCommandLine--TaskCommandLineEvent 메시지를 표시합니다.
예:
예:
-tlp:default=auto;verbosity=diag;shownCommandLine
</target>
<note>
@ -305,7 +306,7 @@
<target state="translated"> -getResultOutputFile:file
get*에서 파일로 출력을 리디렉션합니다.
예:
예:
-getProperty:Bar -getResultOutputFile:Biz.txt
그러면 속성 Bar의 값이 Biz.txt에 기록됩니다.
</target>
@ -320,10 +321,10 @@
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</source>
<target state="needs-review-translation"> -check
빌드하는 동안 BuildChecks를 사용하도록 설정합니다.
BuildCheck를 사용하면 규칙을 평가하여 빌드의 속성을
확인할 수 있습니다. 자세한 내용은 aka.ms/buildcheck를 참조하세요.
<target state="new"> -check
Enables BuildChecks during the build.
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</target>
<note>
{Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"}
@ -468,12 +469,12 @@
value that comes from a response file.
</source>
<target state="translated"> -interactive[:True|False]
빌드의 작업이 사용자와 상호 작용할 수
있음을 나타냅니다. 상호 작용이 필요하지
않은 자동화된 시나리오에서는 이 인수를
빌드의 작업이 사용자와 상호 작용할 수
있음을 나타냅니다. 상호 작용이 필요하지
않은 자동화된 시나리오에서는 이 인수를
사용하지 마세요.
-interactive를 지정하는 것은 -interactive:true를
지정하는 것과 같습니다. 매개 변수를
지정하는 것과 같습니다. 매개 변수를
사용하여 지시 파일에서 가져오는 값을 재정의합니다.
</target>
<note>
@ -543,9 +544,9 @@
<target state="translated"> -graphBuild[:True|False]
MSBuild가 프로젝트 그래프를 생성 및 빌드하도록 합니다.
그래프 생성에는 종속성을 형성하기 위한 프로젝트
참조 식별이 관련됩니다. 해당 그래프 빌드에는 프로젝트
참조를 참조하는 프로젝트 전에 프로젝트 참조를
그래프 생성에는 종속성을 형성하기 위한 프로젝트
참조 식별이 관련됩니다. 해당 그래프 빌드에는 프로젝트
참조를 참조하는 프로젝트 전에 프로젝트 참조를
빌드하는 시도가 관련되며, 이는 기존 MSBuild
예약과 다릅니다.
(약식: -graph)
@ -599,7 +600,7 @@
<target state="translated"> -lowPriority[:True|False]
MSBuild가 낮은 프로세스 우선 순위로 실행됩니다.
-lowPriority를 지정하는 것은
-lowPriority를 지정하는 것은
-lowPriority:True를 지정하는 것과 같습니다.
(약식: -low)
</target>
@ -701,11 +702,11 @@
(1) the directory of msbuild.exe
(2) the directory of the first project or solution built
</source>
<target state="translated"> @&lt;file&gt; 텍스트 파일에서 명령줄 설정을 삽입합니다.
여러 지시 파일을 지정하려면 각 지시 파일을 개별적으로
<target state="translated"> @&lt;file&gt; 텍스트 파일에서 명령줄 설정을 삽입합니다.
여러 지시 파일을 지정하려면 각 지시 파일을 개별적으로
지정합니다.
"msbuild.rsp"라는 지시 파일이 다음 위치에서
"msbuild.rsp"라는 지시 파일이 다음 위치에서
자동으로 사용됩니다.
(1) msbuild.exe의 디렉터리
(2) 빌드된 첫 번째 프로젝트 또는 솔루션의 디렉터리
@ -742,8 +743,8 @@
Example:
-target:Resources;Compile
</source>
<target state="translated"> -target:&lt;targets&gt; 이 프로젝트에서 대상을 빌드합니다. 세미콜론 또는 쉼표를 사용하여
여러 대상을 구분하거나, 각 대상을
<target state="translated"> -target:&lt;targets&gt; 이 프로젝트에서 대상을 빌드합니다. 세미콜론 또는 쉼표를 사용하여
여러 대상을 구분하거나, 각 대상을
개별적으로 지정합니다. (약식: -t)
예:
-target:Resources;Compile
@ -765,9 +766,9 @@
Example:
-property:WarningLevel=2;OutDir=bin\Debug\
</source>
<target state="translated"> -property:&lt;n&gt;=&lt;v&gt; 프로젝트 수준 속성을 설정하거나 재정의합니다. &lt;n&gt;은
속성 이름이고 &lt;v&gt;는 속성 값입니다.
세미콜론 또는 쉼표를 사용하여 여러 속성을 구분하거나,
<target state="translated"> -property:&lt;n&gt;=&lt;v&gt; 프로젝트 수준 속성을 설정하거나 재정의합니다. &lt;n&gt;은
속성 이름이고 &lt;v&gt;는 속성 값입니다.
세미콜론 또는 쉼표를 사용하여 여러 속성을 구분하거나,
각 속성을 개별적으로 지정합니다. (약식: -p)
예:
-property:WarningLevel=2;OutDir=bin\Debug\
@ -800,11 +801,11 @@
<target state="translated"> -logger:&lt;로거&gt; 이 로거를 사용하여 MSBuild의 이벤트를 기록합니다. 여러
로거를 지정하려면 각 로거를 개별적으로 지정합니다.
&lt;로거&gt; 구문은 다음과 같습니다.
[&lt;클래스&gt;,]&lt;assembly&gt;[,&lt;옵션&gt;][;&lt;매개 변수&gt;]
[&lt;클래스&gt;,]&lt;어셈블리&gt;[,&lt;옵션&gt;][;&lt;매개 변수&gt;]
&lt;로거 클래스&gt; 구문은 다음과 같습니다.
[&lt;부분 또는 전체 네임스페이스&gt;.]&lt;로거 클래스 이름&gt;
&lt;로거 어셈블리&gt; 구문은 다음과 같습니다.
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
{&lt;어셈블리 이름&gt;[,&lt;strong name&gt;] | &lt;어셈블리 파일&gt;}
로거 옵션은 MSBuild가 로거를 만드는 방법을 지정합니다.
&lt;로거 매개 변수&gt;는 선택 사항이고 입력한 대로 정확히
로거에 전달됩니다. (약식: -l)
@ -892,26 +893,26 @@
<target state="translated"> -consoleLoggerParameters:&lt;parameters&gt;
콘솔 로거에 대한 매개 변수입니다. (약식: -clp)
사용 가능한 매개 변수는 다음과 같습니다.
PerformanceSummary--작업, 대상, 프로젝트에서 소요된 시간을
PerformanceSummary--작업, 대상, 프로젝트에서 소요된 시간을
표시합니다.
Summary--종료 시 오류 및 경고 요약을 표시합니다.
NoSummary--종료 시 오류 및 경고 요약을 표시하지
않습니다.
ErrorsOnly--오류만 표시합니다.
WarningsOnly--경고만 표시합니다.
NoItemAndPropertyList--각 프로젝트 빌드를 시작할 때 항목 및 속성 목록을
NoItemAndPropertyList--각 프로젝트 빌드를 시작할 때 항목 및 속성 목록을
표시하지 않습니다.
ShowCommandLine--TaskCommandLineEvent 메시지를 표시합니다.
ShowTimestamp--메시지 접두사로 타임스탬프를
ShowTimestamp--메시지 접두사로 타임스탬프를
표시합니다.
ShowEventId--시작된 이벤트, 완료된 이벤트, 메시지의 eventId를
ShowEventId--시작된 이벤트, 완료된 이벤트, 메시지의 eventId를
표시합니다.
ForceNoAlign--콘솔 버퍼 크기에 텍스트를 맞추지
ForceNoAlign--콘솔 버퍼 크기에 텍스트를 맞추지
않습니다.
DisableConsoleColor--모든 로깅 메시지에 기본 콘솔 색을
사용합니다.
DisableMPLogging--다중 프로세서가 아닌 모드에서 실행할 경우
출력의 다중 프로세서 로깅 스타일을
출력의 다중 프로세서 로깅 스타일을
사용하지 않도록 설정합니다.
EnableMPLogging--다중 프로세서가 아닌 모드에서 실행할 경우에도
다중 프로세서 로깅 스타일을 사용하도록 설정합니다.
@ -920,7 +921,7 @@
사용합니다
PreferConsoleColor--대상 콘솔에서 지원되는 경우에만
ANSI 콘솔 색을 사용합니다.
Verbosity--이 로거에 대한 -verbosity 설정을
Verbosity--이 로거에 대한 -verbosity 설정을
재정의합니다.
예:
-consoleLoggerParameters:PerformanceSummary;NoSummary;
@ -960,10 +961,10 @@
Example:
-validate:MyExtendedBuildSchema.xsd
</source>
<target state="translated"> -validate 기본 스키마를 기준으로 프로젝트의 유효성을 검사합니다.
<target state="translated"> -validate 기본 스키마를 기준으로 프로젝트의 유효성을 검사합니다.
(약식: -val)
-validate:&lt;schema&gt; 지정된 스키마를 기준으로 프로젝트의 유효성을 검사합니다.
-validate:&lt;schema&gt; 지정된 스키마를 기준으로 프로젝트의 유효성을 검사합니다.
(약식: -val)
예:
-validate:MyExtendedBuildSchema.xsd
@ -1082,11 +1083,11 @@
로거를 지정하려면 각 로거를 개별적으로 지정합니다.
(약식 -dl)
&lt;로거&gt; 구문은 다음과 같습니다.
[&lt;클래스&gt;,]&lt;assembly&gt;[,&lt;옵션&gt;][;&lt;매개 변수&gt;]
[&lt;클래스&gt;,]&lt;어셈블리&gt;[,&lt;옵션&gt;][;&lt;매개 변수&gt;]
&lt;로거 클래스&gt; 구문은 다음과 같습니다.
[&lt;부분 또는 전체 네임스페이스&gt;.]&lt;로거 클래스 이름&gt;
&lt;로거 어셈블리&gt; 구문은 다음과 같습니다.
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
{&lt;어셈블리 이름&gt;[,&lt;strong name&gt;] | &lt;어셈블리 파일&gt;}
로거 옵션은 MSBuild가 로거를 만드는 방법을 지정합니다.
&lt;로거 매개 변수&gt;는 선택 사항이고
입력한 대로 정확히 로거에 전달됩니다. (약식: -l)
@ -1113,8 +1114,8 @@
-ignoreProjectExtensions:.sln
</source>
<target state="translated"> -ignoreProjectExtensions:&lt;extensions&gt;
빌드할 프로젝트 파일을 결정할 때
무시할 확장 목록입니다. 여러 확장을 구분하는 데는
빌드할 프로젝트 파일을 결정할 때
무시할 확장 목록입니다. 여러 확장을 구분하는 데는
세미콜론 또는 쉼표를 사용합니다.
(약식: -ignore)
예:
@ -1140,7 +1141,7 @@
</source>
<target state="translated"> -toolsVersion:&lt;version&gt;
빌드 중에 사용할 MSBuild 도구 세트(작업, 대상 등)의 버전입니다.
이 버전은 개별 프로젝트에서 지정한 버전을
이 버전은 개별 프로젝트에서 지정한 버전을
재정의합니다. (약식:
-tv)
예:
@ -1169,9 +1170,9 @@
파일은 현재 디렉터리에 있고
"msbuild[n].log"로 이름이 지정되어 있습니다. 모든 노드의 이벤트는 단일 로그로
결합됩니다. 파일의 위치 및 fileLogger의
다른 매개 변수는 "-fileLoggerParameters[n]" 스위치를
다른 매개 변수는 "-fileLoggerParameters[n]" 스위치를
추가하여 지정할 수 있습니다.
"n"은 1-9 사이의 숫자일 수 있으며 최대 10개의
"n"은 1-9 사이의 숫자일 수 있으며 최대 10개의
파일 로거가 추가될 수 있습니다. (약식: -fl[n])
</target>
<note>
@ -1198,16 +1199,16 @@
create a log file for each node.
</source>
<target state="translated"> -distributedFileLogger
MSBuild 노드당 로그 파일 하나씩, 여러 로그 파일에 빌드 출력을
기록합니다. 해당 파일의 초기 위치는
현재 디렉터리입니다. 기본적으로 해당 파일을
"MSBuild&lt;nodeid&gt;.log"라고 합니다. 파일 위치 및 fileLogger의 기타 매개 변수는
"-fileLoggerParameters" 스위치를 추가해서
MSBuild 노드당 로그 파일 하나씩, 여러 로그 파일에 빌드 출력을
기록합니다. 해당 파일의 초기 위치는
현재 디렉터리입니다. 기본적으로 해당 파일을
"MSBuild&lt;nodeid&gt;.log"라고 합니다. 파일 위치 및 fileLogger의 기타 매개 변수는
"-fileLoggerParameters" 스위치를 추가해서
지정할 수 있습니다.
로그 파일 이름이 fileLoggerParameters 스위치를 통해 설정되면
배포된 로거가 fileName을 템플릿으로 사용하고
노드 ID를 이 fileName에 추가하여
로그 파일 이름이 fileLoggerParameters 스위치를 통해 설정되면
배포된 로거가 fileName을 템플릿으로 사용하고
노드 ID를 이 fileName에 추가하여
각 노드의 로그 파일을 만듭니다.
</target>
<note>
@ -1251,20 +1252,20 @@
</source>
<target state="translated"> -fileLoggerParameters[n]:&lt;parameters&gt;
파일 로거의 추가 매개 변수를 제공합니다.
이 스위치가 있다는 것은
이 스위치가 있다는 것은
해당 fileLogger[n] 스위치를 의미합니다.
"n"(있는 경우)은 1~9의 숫자일 수 있습니다.
-fileLoggerParameters는 배포된 파일 로거에서도
-fileLoggerParameters는 배포된 파일 로거에서도
사용됩니다. -distributedFileLogger에 대한 설명을 참조하세요.
(약식: -flp[n])
콘솔 로거용으로 나열된 동일한 매개 변수를 사용할 수 있습니다.
다음과 같은 몇 가지 추가 매개 변수를 사용할 수 있습니다.
LogFile--빌드 로그가 기록되는
LogFile--빌드 로그가 기록되는
로그 파일의 경로입니다.
Append--빌드 로그가 로그 파일에 추가되는지,
아니면 로그 파일을 덮어쓰는지 여부를 결정합니다.
Append--빌드 로그가 로그 파일에 추가되는지,
아니면 로그 파일을 덮어쓰는지 여부를 결정합니다.
스위치를 설정하면 빌드 로그가 로그 파일에 추가됩니다.
스위치를 설정하지 않으면 기존 로그 파일의
스위치를 설정하지 않으면 기존 로그 파일의
콘텐츠를 덮어씁니다.
기본값은 로그 파일에 추가하지 않는 것입니다.
Encoding--파일의 인코딩을 지정합니다
@ -1301,7 +1302,7 @@
<target state="translated"> -nodeReuse:&lt;parameters&gt;
MSBuild 노드를 다시 사용하거나 다시 사용하지 않도록 설정합니다.
매개 변수는 다음가 같습니다.
True --빌드 완료 후 노드가 유지되고
True --빌드 완료 후 노드가 유지되고
후속 빌드에서 다시 사용됩니다(기본값).
False--빌드 완료 후 노드가 유지되지 않습니다.
(약식: -nr)
@ -2277,10 +2278,10 @@
</source>
<target state="translated"> -restore[:True|False]
다른 대상을 빌드하기 전에 Restore라는 대상을
실행하고 이러한 대상의 빌드에 최신 복원된
빌드 논리가 사용되는지 확인합니다.
프로젝트 트리를 빌드하기 전에
프로젝트 트리에서 패키지를 복원해야 하는
실행하고 이러한 대상의 빌드에 최신 복원된
빌드 논리가 사용되는지 확인합니다.
프로젝트 트리를 빌드하기 전에
프로젝트 트리에서 패키지를 복원해야 하는
경우에 유용합니다. -restore를 지정하는 것은
-restore:True를 지정하는 것과 동일합니다. 이 매개 변수를 사용하여
지시 파일에서 가져오는 값을 재정의할 수 있습니다.
@ -2318,7 +2319,7 @@
</source>
<target state="translated"> -profileEvaluation:&lt;file&gt;
MSBuild 평가를 프로파일링하고 결과를 지정된 파일에 기록합니다.
지정된 파일의 확장명이 '.md'이면
지정된 파일의 확장명이 '.md'이면
결과가 Markdown 형식으로 생성됩니다.
그렇지 않으면 탭으로 구분된 파일이 생성됩니다.
</target>
@ -2337,9 +2338,9 @@
-restoreProperty:IsRestore=true;MyProperty=value
</source>
<target state="translated"> -restoreProperty:&lt;n&gt;=&lt;v&gt;
복원하는 동안 프로젝트 수준 속성만 설정하거나
재정의하고, -property 인수로 지정된 속성을
사용하지 않습니다. &lt;n&gt;은 속성 이름이고
복원하는 동안 프로젝트 수준 속성만 설정하거나
재정의하고, -property 인수로 지정된 속성을
사용하지 않습니다. &lt;n&gt;은 속성 이름이고
&lt;v&gt;는 속성 값입니다.
세미콜론 또는 쉼표를 사용하여 여러 속성을 구분하거나,
각 속성을 개별적으로 지정합니다.
@ -2364,4 +2365,4 @@
</trans-unit>
</body>
</file>
</xliff>
</xliff>

83
src/MSBuild/Resources/xlf/Strings.pl.xlf сгенерированный
Просмотреть файл

@ -122,10 +122,10 @@
This flag is experimental and may not work as intended.
</source>
<target state="translated"> -reportFileAccesses[:True|False]
Powoduje, że platforma MSBuild zgłasza dostępy do wszystkich skonfigurowanych
Powoduje, że program MSBuild zgłasza dostępy do wszystkich skonfigurowanych plików
wtyczek pamięci podręcznej projektu.
Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami.
Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami.
</target>
<note>
LOCALIZATION: "-reportFileAccesses" should not be localized.
@ -205,8 +205,8 @@
ciągów „Undefined”, „Available”, „NotAvailable” i
„Preview”.
— Undefined — dostępność funkcji jest niezdefiniowana
(nazwa funkcji jest nieznana dla kontrolera dostępności
funkcji)
(nazwa funkcji jest nieznana dla dostępności funkcji
kontroler)
— NotAvailable — funkcja jest niedostępna (w przeciwieństwie do
Undefined, nazwa funkcji jest znana kontrolerowi
dostępności funkcji i wie on, że funkcja nie jest
@ -237,12 +237,12 @@
Włącz lub wyłącz rejestrator terminali. Rejestrator terminali
udostępnia ulepszone dane wyjściowe kompilacji na konsoli w czasie rzeczywistym,
uporządkowane logicznie według projektu i zaprojektowane do wyróżniania
informacji umożliwiających podejmowanie działań. Określ automatycznie (lub użyj opcji
informacji umożliwiających podejmowanie działań. Określ auto (lub użyj opcji
bez argumentów), aby używać rejestratora terminali tylko wtedy, gdy
standardowe dane wyjściowe nie są przekierowywane. Nie analizuj danych wyjściowych
albo w przeciwnym razie poleganie na nich pozostanie niezmienione w przyszłych
standardowe dane wyjściowe nie są przekierowywane. Nie analizowanie danych wyjściowych
lub inaczej – poleganie na nich pozostanie niezmienione w przyszłych
wersjach. Ta opcja jest dostępna w wersji MSBuild 17.8 i
nowszych.
późniejszych.
(Krótka forma: -tl)
</target>
<note>
@ -274,17 +274,17 @@
Parametry rejestratora terminali. (Krótka forma: -tlp)
Dostępne parametry.
default-- określa domyślne zachowanie rejestratora
terminali. Wymaga jednej z następujących wartości:
— „on”, „true” wymusza użycie elementu TerminalLogger, nawet
terminalu. Wymaga jednej z następujących wartości:
— „on”, „true” wymusza użycie elementu TerminalLogger nawet
kiedy zostanie on wyłączony.
— „off”, „false” wymusza nieużywanie elementu TerminalLogger
nawet wtedy, gdy zostanie on włączony.
— „auto” włącza element TerminalLogger, gdy terminal
go obsługuje, a sesja nie została przekierowana
stdout/stderr
verbosity-- zastępuje ustawienie -verbosity dla tego
verbosity-- zastąp ustawienie -verbosity dla tego
rejestratora
showCommandLine-- pokazuje komunikaty TaskCommandLineEvent
showCommandLine-- pokaż komunikaty TaskCommandLineEvent
Przykład:
-tlp:default=auto;verbosity=diag;shownCommandLine
@ -320,10 +320,10 @@
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</source>
<target state="needs-review-translation"> -check
Włącza funkcję BuildChecks podczas kompilacji.
Funkcja BuildCheck umożliwia ocenę reguł w celu zapewnienia właściwości
kompilacji. Aby uzyskać więcej informacji, zobacz aka.ms/buildcheck
<target state="new"> -check
Enables BuildChecks during the build.
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</target>
<note>
{Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"}
@ -474,7 +474,7 @@
interakcyjność nie jest oczekiwana.
Podanie parametru -interactive jest równoznaczne
z podaniem parametru -interactive:true. Użyj tego
parametru, aby przesłonić wartość pochodzącą z pliku
parametru, aby przesłonić wartość pochodzącą z pliku
odpowiedzi.
</target>
<note>
@ -509,7 +509,7 @@
Po ustawieniu na wartość „MessageUponIsolationViolation” (lub jej skróconą
formę „Message”), serializowane są tylko wyniki z celów najwyższego poziomu
, jeśli przełącznik -outputResultsCache jest
dostarczony. Ma to na celu zmniejszenie szans na to, że cel
dostarczony. Ma to na celu zmniejszenie szans na to, że cel
naruszy izolację w projekcie zależnym przy użyciu
nieprawidłowego stanu z powodu jego zależności od buforowanego celu
którego efekty uboczne nie byłyby brane pod uwagę.
@ -543,7 +543,7 @@
This flag is experimental and may not work as intended.
</source>
<target state="translated"> -graphBuild[:True|False]
Powoduje, że program MSBuild tworzy i kompiluje graf
Powoduje, że program MSBuild tworzy i kompiluje graf
projektu.
Tworzenie grafu obejmuje identyfikowanie odwołań do
@ -711,7 +711,7 @@
osobno.
Wszelkie pliki odpowiedzi o nazwie „msbuild.rsp” będą automatycznie
wykorzystywane z następujących lokalizacji:
wykorzystywane z następujących lokalizacji:
(1) katalog programu msbuild.exe
(2) katalog pierwszej kompilacji projektu lub rozwiązania
</target>
@ -802,14 +802,17 @@
-logger:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral
-logger:XMLLogger,C:\Loggers\MyLogger.dll;OutputAsHTML
</source>
<target state="translated"> -logger:&lt;rejestrator&gt; Umożliwia użycie podanego rejestratora do rejestrowania zdarzeń pochodzących
z programu MSBuild. Aby określić wiele rejestratorów, określ każdy z nich osobno.
<target state="translated"> -logger:&lt;rejestrator&gt; Umożliwia użycie podanego rejestratora do rejestrowania
zdarzeń pochodzących z programu MSBuild. Aby określić
wiele rejestratorów, określ każdy z nich osobno.
Składnia elementu &lt;rejestrator&gt;:
[&lt;klasa rejestratora&gt;,]&lt;assembly&gt; [;&lt;parametry rejestratora&gt;]
[&lt;klasa rejestratora&gt;,]&lt;zestaw rejestratora&gt;
[;&lt;parametry rejestratora&gt;]
Składnia elementu &lt;klasa rejestratora&gt;:
[&lt;częściowa lub pełna przestrzeń nazw&gt;.] &lt;nazwa klasy rejestratora&gt;
[&lt;częściowa lub pełna przestrzeń nazw&gt;.]
&lt;nazwa klasy rejestratora&gt;
Składnia elementu &lt;zestaw rejestratora&gt;:
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
{&lt;nazwa zestawu&gt;[,&lt;strong name&gt;] | &lt;plik zestawu&gt;}
Wartości &lt;parametry rejestratora&gt; są opcjonalne i są
przekazywane do rejestratora dokładnie tak, jak zostały
wpisane. (Krótka wersja: -l)
@ -1030,7 +1033,7 @@
to False, this sets it to True. (short form: -irc)
</source>
<target state="translated"> -inputResultsCaches:&lt;cacheFile&gt;...
Rozdzielona średnikami lista wejściowych plików pamięci podręcznej, z których MSBuild
Rozdzielona średnikami lista wejściowych plików pamięci podręcznej, z których MSBuild
odczyta wyniki kompilacji. Jeśli jest ustawione -isolateProjects
na wartość Fałsz, ta opcja ustawia ją na wartość Prawda. (skrócona forma: -irc)
</target>
@ -1088,11 +1091,11 @@
wiele rejestratorów, określ każdy z nich osobno.
(Krótka wersja: -dl)
Składnia elementu &lt;rejestrator&gt;:
[&lt;klasa rejestratora&gt;,]&lt;assembly&gt;[;&lt;parametry rejestratora&gt;]
[&lt;klasa rejestratora&gt;,]&lt;zestaw rejestratora&gt;[;&lt;parametry rejestratora&gt;]
Składnia elementu &lt;klasa rejestratora&gt;:
[&lt;częściowa lub pełna przestrzeń nazw&gt;.]&lt;nazwa klasy rejestratora&gt;
Składnia elementu &lt;zestaw rejestratora&gt;:
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
{&lt;nazwa zestawu&gt;[,&lt;strong name&gt;] | &lt;plik zestawu&gt;}
Wartości &lt;parametry rejestratora&gt; są opcjonalne i są
przekazywane do rejestratora dokładnie tak, jak zostały
wpisane. (Krótka wersja: -l)
@ -1204,11 +1207,13 @@
create a log file for each node.
</source>
<target state="translated"> -distributedFileLogger
Rejestruje dane wyjściowe kompilacji w wielu plikach dziennika,po jednym pliku
na węzeł programu MSBuild. Początkową lokalizacją tych plików
jest bieżący katalog. Domyślnie pliki mają nazwę
Rejestruje dane wyjściowe kompilacji w wielu plikach
dziennika, po jednym pliku na węzeł programu MSBuild.
Początkową lokalizacją tych plików jest bieżący katalog.
Domyślnie pliki mają nazwę
„MSBuild&lt;identyfikator węzła&gt;.log”. Lokalizację plików
i inne parametry rejestratora plików można określić
przez dodanie przełącznika „-fileLoggerParameters”.
Jeśli nazwa pliku zostanie ustawiona za pomocą przełącznika
@ -1266,7 +1271,7 @@
Dostępne są parametry takie same, jak podane dla rejestratora
konsoli. Dostępne są również dodatkowe parametry:
LogFile — ścieżka do pliku dziennika, w którym będzie
zapisywany dziennik kompilacji.
zapisywany dziennik kompilacji.
Append — określa, czy plik dziennika kompilacji zostanie
dołączony do pliku dziennika, czy go zastąpi.
Ustawienie tego przełącznika powoduje dołączenie dziennika kompilacji
@ -1280,8 +1285,8 @@
-fileLoggerParameters:LogFile=MyLog.log;Append;
Verbosity=diagnostic;Encoding=UTF-8
-flp:Summary;Verbosity=minimal;LogFile=msbuild.sum
-flp1:warningsonly;logfile=msbuild.wrn
-flp:Summary;Verbosity=minimal;LogFile=msbuild.sum
-flp1:warningsonly;logfile=msbuild.wrn
-flp2:errorsonly;logfile=msbuild.err
</target>
<note>
@ -2283,10 +2288,10 @@ dzienników tekstowych i wykorzystać w innych narzędziach
</source>
<target state="translated"> -restore[:True|False]
Uruchamia element docelowy o nazwie Restore przed skompilowaniem
innych elementów docelowych i zapewnia, że kompilacja tych
elementów docelowych korzysta z najnowszej logiki przywróconej
kompilacji. Jest to przydatne, gdy drzewo projektu wymaga
przywrócenia pakietów przed ich skompilowaniem. Podanie parametru
innych elementów docelowych i zapewnia, że kompilacja tych
elementów docelowych korzysta z najnowszej logiki przywróconej
kompilacji. Jest to przydatne, gdy drzewo projektu wymaga
przywrócenia pakietów przed ich skompilowaniem. Podanie parametru
-restore jest równoznaczne z podaniem parametru -restore:True.
Za pomocą tego parametru można przesłonić wartość pochodzącą
z pliku odpowiedzi.
@ -2370,4 +2375,4 @@ dzienników tekstowych i wykorzystać w innych narzędziach
</trans-unit>
</body>
</file>
</xliff>
</xliff>

37
src/MSBuild/Resources/xlf/Strings.pt-BR.xlf сгенерированный
Просмотреть файл

@ -122,9 +122,8 @@
This flag is experimental and may not work as intended.
</source>
<target state="translated"> -reportFileAccesses[:True|False]
Faz com que o MSBuild relate acessos a arquivos a qualquer
configurado
plug-ins de cache do projeto.
Faz com que o MSBuild relate acessos a arquivos para qualquer plug-in
de cache de projeto configurado.
Este sinalizador é experimental e pode não funcionar conforme o esperado.
</target>
@ -202,7 +201,7 @@
(Short form: -fa)
</source>
<target state="translated"> -featureAvailability:featureName,...
Verifica a disponibilidade do recurso. O resultado é uma das
Verifica a disponibilidade do recurso. O resultado é uma das
cadeias de caracteres "Indefinido", "Disponível", "Não Disponível" e
"Visualizar".
- Indefinido - a disponibilidade do recurso é indefinida
@ -303,7 +302,7 @@
-getProperty:Bar -getResultOutputFile:Biz.txt
This writes the value of property Bar into Biz.txt.
</source>
<target state="translated"> -getResultOutputFile:arquivo
<target state="translated"> -getResultOutputFile:file
Redirecionar a saída de get* para um arquivo.
Exemplo:
@ -321,10 +320,10 @@
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</source>
<target state="needs-review-translation"> -check
Habilita BuildChecks durante o build.
BuildCheck habilita a avaliação de regras para garantir que as propriedades
do build. Para obter mais informações, confira aka.ms/buildcheck
<target state="new"> -check
Enables BuildChecks during the build.
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</target>
<note>
{Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"}
@ -986,10 +985,10 @@ arquivo de resposta.
MSBuild will use up to the number of processors on the
computer. (Short form: -m[:n])
</source>
<target state="translated"> -maxCpuCount[:n] Especifica o número máximo de processos simultâneos a serem
<target state="translated"> -maxCpuCount[:n] Especifica o número máximo de processos simultâneos a serem
compilados. Se a opção não for usada, o valor padrão
usado será 1. Se a opção for usada sem um valor, o
MSBuild usará o número de processadores do
MSBuild usará o número de processadores do
computador. (Forma abreviada: -m[:n])
</target>
<note>
@ -1007,7 +1006,7 @@ arquivo de resposta.
<target state="translated">Exemplos:
MSBuild MyApp.sln -t:Rebuild -p:Configuration=Release
MSBuild MyApp.csproj -t:Clean
MSBuild MyApp.csproj -t:Clean
-p:Configuration=Debug;TargetFrameworkVersion=v3.5
</target>
<note>
@ -1168,12 +1167,12 @@ arquivo de resposta.
10 file loggers to be attached. (Short form: -fl[n])
</source>
<target state="translated"> -fileLogger[n] Registra a saída do build em um arquivo. Por padrão,
o arquivo está no diretório atual e tem o nome
o arquivo está no diretório atual e tem o nome
"msbuild[n].log". Os eventos de todos os nós são combinados em
um único log. A localização do arquivo e outros
parâmetros do fileLogger pode ser especificada por meio
parâmetros do fileLogger pode ser especificada por meio
do acréscimo da opção "-fileLoggerParameters[n]".
"n", se presente, pode ser um dígito de 1 a 9, permitindo que até
"n", se presente, pode ser um dígito de 1 a 9, permitindo que até
10 agentes de arquivo sejam anexados. (Forma abreviada: -fl[n])
</target>
<note>
@ -1326,14 +1325,14 @@ arquivo de resposta.
Example:
-pp:out.txt
</source>
<target state="translated"> -preprocess[:arquivo]
<target state="translated"> -preprocess[:arquivo]
Cria um arquivo de projeto único e agregado
embutindo todos os arquivos que poderiam ser importados durante um
build, com seus limites marcados. Isso pode ser
útil para descobrir quais arquivos são importados,
de qual localização e como contribuirão para
o build. Por padrão, a saída é gravada na
janela do console. Se o caminho de um arquivo de saída
janela do console. Se o caminho de um arquivo de saída
for fornecido, ele será usado.
(Forma abreviada: -pp)
Exemplo:
@ -2124,7 +2123,7 @@ arquivo de resposta.
-warnAsError:MSB4130
Quando um aviso for tratado como um erro, o destino continuará
a ser executado como se ele fosse um aviso, mas o
a ser executado como se ele fosse um aviso, mas o
build geral falhará.
</target>
<note>
@ -2366,4 +2365,4 @@ arquivo de resposta.
</trans-unit>
</body>
</file>
</xliff>
</xliff>

20
src/MSBuild/Resources/xlf/Strings.ru.xlf сгенерированный
Просмотреть файл

@ -87,7 +87,7 @@
</trans-unit>
<trans-unit id="DurationDisplay">
<source>({0:F1}s)</source>
<target state="needs-review-translation">({0:F1}s)</target>
<target state="needs-review-translation">({0:F1} c)</target>
<note>
{0}: duration in seconds with 1 decimal point
's' should reflect the localized abbreviation for seconds
@ -202,7 +202,7 @@
</source>
<target state="translated"> -featureAvailability:featureName,...
Проверьте доступность функции. Результатом является одна из
строк "Не определено", "Доступно", "Недоступно" и
строк "Неопределено", "Доступно", "Недоступно" и
"Предварительный просмотр".
- Не определено — доступность функции не определена
(имя функции неизвестно средству проверки доступности
@ -275,11 +275,11 @@
Доступные параметры.
по умолчанию — определяет поведение логгера
терминала. Требуется одно из следующих значений:
- "on", "true" заставляет использовать TerminalLogger даже
- `on`, `true` заставляет использовать TerminalLogger даже
когда он будет отключен.
- "off", "false" запрещает использование TerminalLogger
- `off`, `false` запрещает использование TerminalLogger
даже если бы он был включен.
- "auto" включает TerminalLogger, когда терминал
- `auto` включает TerminalLogger, когда терминал
поддерживает это, и в сеансе нет перенаправления
stdout/stderr
verbosity – Переопределить параметр -verbosity для этого
@ -320,10 +320,10 @@
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</source>
<target state="needs-review-translation"> -check
Включает BuildChecks во время сборки.
BuildCheck дает оценивать правила для проверки свойств
сборки. Дополнительные сведения см. на странице aka.ms/buildcheck
<target state="new"> -check
Enables BuildChecks during the build.
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</target>
<note>
{Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"}
@ -1576,7 +1576,7 @@
</trans-unit>
<trans-unit id="MissingGetResultFileError">
<source>MSBUILD : error MSB1068: Must provide a file for the getResultOutputFile switch.</source>
<target state="translated">MSBUILD : error MSB1068: необходимо предоставить файл для переключателя getResultOutputFile.</target>
<target state="translated">MSBUILD : error MSB1068: необходимо указать файл для параметра getResultOutputFile.</target>
<note>
{StrBegin="MSBUILD : error MSB1068: "}UE: This happens if the user does something like "msbuild.exe -getResultOutputFile". The user must pass in an actual file
following the switch, as in "msbuild.exe -getTargetResult:blah -getResultOutputFile:blah.txt".

31
src/MSBuild/Resources/xlf/Strings.tr.xlf сгенерированный
Просмотреть файл

@ -320,11 +320,10 @@
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</source>
<target state="needs-review-translation"> -check
Derleme sırasında BuildChecks'i sağlar.
BuildCheck, derleme özelliklerinin
güvenliğini sağlamak için
kuralların değerlendirilmesini sağlar. Daha fazla bilgi için bkz. aka.ms/buildcheck
<target state="new"> -check
Enables BuildChecks during the build.
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</target>
<note>
{Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"}
@ -801,11 +800,11 @@
<target state="translated"> -logger:&lt;günlükçü&gt; MSBuild'deki olayları günlüğe almak için bu günlükçüyü kullanın. Birden fazla
günlükçü belirtmek için her günlükçüyü ayrı ayrı belirtin.
&lt;günlükçü&gt; söz dizimi şöyledir:
[&lt;class&gt;,]&lt;assembly&gt;[,&lt;options&gt;][;&lt;parameters&gt;]
[&lt;sınıf&gt;,]&lt;derleme&gt;[,&lt;seçenekler&gt;][;&lt;parametreler&gt;]
&lt;günlükçü sınıfı &gt; söz dizimi şöyledir:
[&lt;kısmi veya tam ad alanı &gt;.]&lt;günlükçü sınıfı adı&gt;
&lt;günlükçü derlemesi&gt; söz dizimi şöyledir:
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
{&lt;derleme adı&gt;[,&lt;strong name&gt;] | &lt;derleme dosyası&gt;}
Günlükçü seçenekleri, MSBuild'in günlükçüyü oluşturma biçimini belirtir.
&lt;günlükçü parametreleri &gt; isteğe bağlıdır ve tam olarak
yazdığınız şekliyle günlükçüye geçirilir. (Kısa biçim: -l)
@ -1083,11 +1082,11 @@
günlükçü belirtmek için her günlükçüyü ayrı ayrı belirtin.
(Kısa biçim -dl)
&lt;günlükçü&gt; söz dizimi şöyledir:
[&lt;sınıf&gt;,]&lt;assembly&gt;[,&lt;seçenekler&gt;][;&lt;parametreler&gt;]
[&lt;sınıf&gt;,]&lt;derleme&gt;[,&lt;seçenekler&gt;][;&lt;parametreler&gt;]
&lt;günlükçü sınıfı&gt; söz dizimi şöyledir:
[&lt;kısmi veya tam ad alanı&gt;.]&lt;günlükçü sınıfı adı&gt;
&lt;günlükçü derlemesi&gt; söz dizimi şöyledir:
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
{&lt;derleme adı&gt;[,&lt;strong name&gt;] | &lt;derleme dosyası&gt;}
Günlükçü seçenekleri, MSBuild'in günlükçüyü oluşturma biçimini belirtir.
&lt;günlükçü parametreleri&gt; isteğe bağlıdır ve tam olarak
yazdığınız şekliyle günlükçüye geçirilir. (Kısa biçim: -l)
@ -1116,7 +1115,8 @@
<target state="translated"> -ignoreProjectExtensions:&lt;uzantılar&gt;
Hangi proje dosyasının oluşturulacağı belirlenirken
yoksayılacak uzantıların listesi. Birden çok uzantıyı
birbirinden ayırmak için noktalı virgül veya virgül kullanın.
birbirinden ayırmak için noktalı virgül veya
virgül kullanın.
(Kısa biçim: -ignore)
Örnek:
-ignoreProjectExtensions:.sln
@ -1206,6 +1206,7 @@
Dosyaların konumu ve fileLogger'ın diğer parametreleri
"/fileLoggerParameters" anahtarının eklenmesi yoluyla
belirtilebilir.
Günlük dosyası adı fileLoggerParameters anahtarı
aracılığıyla ayarlanırsa dağıtılmış günlükçü fileName
değerini şablon olarak kullanıp her düğümün günlük dosyasını
@ -1256,7 +1257,8 @@
anahtarının olduğu anlamına gelir.
"n" varsa, 1-9 arasında bir rakam olabilir.
Dağıtılmış dosya günlükçüleri varsa -fileLoggerParameters
bunlar tarafından da kullanılır; -distributedFileLogger açıklamasına bakın.
bunlar tarafından da kullanılır; -distributedFileLogger
açıklamasına bakın.
(Kısa biçim: -flp[n])
Konsol günlükçüsü için listelenenlerle aynı parametreler
kullanılabilir. Kullanılabilecek bazı ek parametreler:
@ -1300,7 +1302,8 @@
-nr:true
</source>
<target state="translated"> -nodeReuse:&lt;parametreler&gt;
MSBuild düğümlerinin yeniden kullanımını etkinleştirir veya devre dışı bırakır.
MSBuild düğümlerinin yeniden kullanımını etkinleştirir
veya devre dışı bırakır.
Parametreler:
True --Derleme tamamlandıktan sonra düğümler kalır ve
izleyen derlemelerde yeniden kullanılır (varsayılan)
@ -1649,7 +1652,7 @@
</trans-unit>
<trans-unit id="MissingTerminalLoggerParameterError">
<source>MSBUILD : error MSB1066: Specify one or more parameters for the terminal logger if using the -terminalLoggerParameters switch</source>
<target state="translated">MSBUILD : error MSB1066: terminalLoggerParameters anahtarı kullanılıyorsa terminal günlükçüsü için bir veya birden çok parametre belirtin</target>
<target state="translated">MSBUILD : error MSB1066: -terminalLoggerParameters anahtarı kullanılıyorsa terminal günlükçüsü için bir veya birden çok parametre belirtin</target>
<note>
{StrBegin="MSBUILD : error MSB1066: "}
UE: This happens if the user does something like "msbuild.exe -terminalLoggerParameters:". The user must pass in one or more parameters
@ -1839,7 +1842,7 @@
</trans-unit>
<trans-unit id="SAC_Evaluation">
<source>2: in evaluation. It is recommended to turn off Smart App Control in development environemnt as otherwise performance might be impacted</source>
<target state="translated">2: değerlendirmede. Aksi takdirde performans etkilenebileceği için geliştirme ortamında Akıllı Uygulama Denetiminin kapatılması önerilir</target>
<target state="translated">2: değerlendirmede. Aksi takdirde performansın etkilenebileceği için geliştirme ortamında Akıllı Uygulama Denetimi’nin kapatılması önerilir</target>
<note>Smart App Control, "VerifiedAndReputablePolicyState" should not be localized</note>
</trans-unit>
<trans-unit id="SAC_Off">

130
src/MSBuild/Resources/xlf/Strings.zh-Hans.xlf сгенерированный
Просмотреть файл

@ -140,11 +140,11 @@
used, write out the values after the build.
</source>
<target state="translated"> -getProperty:propertyName,...
在计算后写出一个或多个指定属性的值，
但不执行生成，或者如果使用的是
-targets 选项或 -getTargetResult 选项，
则在生成后写出这些值。
</target>
在计算后写出一个或多个指定属性的值，
但不执行生成，或者如果使用的是
-targets 选项或 -getTargetResult 选项，
则在生成后写出这些值。
</target>
<note>
LOCALIZATION: "-getProperty", "-targets" and "-getTargetResult" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -159,12 +159,12 @@
the values after the build.
</source>
<target state="translated"> -getItem:itemName,...
在计算后写出一个或多个指定项的值及其
关联的元数据，但不
执行生成，或者如果使用的是 -targets 选项
或 -getTargetResult 选项，则在生成后写出
这些值。
</target>
在计算后写出一个或多个指定项的值及其
关联的元数据，但不
执行生成，或者如果使用的是 -targets 选项
或 -getTargetResult 选项，则在生成后写出
这些值。
</target>
<note>
LOCALIZATION: "-getItem", "targets" and "getTargetResult" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -176,9 +176,9 @@
the specified targets will be executed.
</source>
<target state="translated"> -getTargetResult:targetName,...
写出一个或多个目标的输出值，
并且将执行指定的目标。
</target>
写出一个或多个目标的输出值，
并且将执行指定的目标。
</target>
<note>
LOCALIZATION: "-getTargetResult" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -201,20 +201,20 @@
(Short form: -fa)
</source>
<target state="translated"> -featureAvailability:featureName,...
检查功能可用性。结果是以下字符串之一:
"Undefined"、"Available"、"NotAvailable" 和
"Preview"。
- Undefined - 未定义功能的可用性
(功能可用性检查器不知道
该功能名称)
- NotAvailable - 功能不可用(不同于
Undefined，功能可用性检查器知道
该功能名称，并且还知道该功能不
受当前 MSBuild 引擎支持)
- Available - 功能可用
- Preview - 功能处于预览状态(不稳定)
(缩写: -fa)
</target>
检查功能可用性。结果是以下字符串之一:
"Undefined"、"Available"、"NotAvailable" 和
"Preview"。
- Undefined - 未定义功能的可用性
(功能可用性检查器不知道
该功能名称)
- NotAvailable - 功能不可用(不同于
Undefined，功能可用性检查器知道
该功能名称，并且还知道该功能不
受当前 MSBuild 引擎支持)
- Available - 功能可用
- Preview - 功能处于预览状态(不稳定)
(缩写: -fa)
</target>
<note>
LOCALIZATION: "-featureAvailability", "-fa", "Undefined", "Available" "NotAvailable" and "Preview"should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -234,17 +234,17 @@
(Short form: -tl)
</source>
<target state="translated"> -terminalLogger[:auto,on,off]
启用或禁用终端记录器。终端记录器
在控制台上实时提供增强的生成输出，
这些输出在逻辑上按项目进行整理，旨在突出显示
可操作信息。指定 auto (或使用
不带参数的选项)，仅在标准输出未重定向的情况下
使用终端记录器。不要分析输出，
也不要依赖于它在将来的版本中保持
不变。此选项在 MSBuild 17.8 和
更高版本中提供。
(缩写: -tl)
</target>
启用或禁用终端记录器。终端记录器
在控制台上实时提供增强的生成输出，
这些输出在逻辑上按项目进行整理，旨在突出显示
可操作信息。指定 auto (或使用
不带参数的选项)，仅在标准输出未重定向的情况下
使用终端记录器。不要分析输出，
也不要依赖于它在将来的版本中保持
不变。此选项在 MSBuild 17.8 和
更高版本中提供。
(缩写: -tl)
</target>
<note>
LOCALIZATION: "-terminalLogger", "-tl", and "auto" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -271,24 +271,24 @@
-tlp:default=auto;verbosity=diag;shownCommandLine
</source>
<target state="translated"> -terminalLoggerParameters: &lt;parameters&gt;
终端记录器的参数。(缩写: -tlp)
可用参数。
default - 指定终端
记录器的默认行为。它需要以下值之一:
- `on`、`true` 可强制使用 TerminalLogger，
即使它已禁用也是如此。
- `off`、`false` 可强制不使用 TerminalLogger，
即使它已启用也是如此。
- `auto` 可在终端支持 TerminalLogger
且会话没有重定向的 stdout/stderr 时
启用 TerminalLogger
verbosity - 替代此记录器的 -verbosity
设置
showCommandLine - 显示 TaskCommandLineEvent 消息
终端记录器的参数。(缩写: -tlp)
可用参数。
default - 指定终端
记录器的默认行为。它需要以下值之一:
- `on`、`true` 可强制使用 TerminalLogger，
即使它已禁用也是如此。
- `off`、`false` 可强制不使用 TerminalLogger，
即使它已启用也是如此。
- `auto` 可在终端支持 TerminalLogger
且会话没有重定向的 stdout/stderr 时
启用 TerminalLogger
verbosity - 替代此记录器的 -verbosity
设置
showCommandLine - 显示 TaskCommandLineEvent 消息
示例:
-tlp:default=auto;verbosity=diag;shownCommandLine
</target>
示例:
-tlp:default=auto;verbosity=diag;shownCommandLine
</target>
<note>
LOCALIZATION: "-terminalLoggerParameters", "-tlp", "default", "on", "true", "off", "false", "auto", "verbosity", "showCommandLine" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -303,12 +303,12 @@
This writes the value of property Bar into Biz.txt.
</source>
<target state="translated"> -getResultOutputFile:file
将 get* 的输出重定向到文件中。
将 get* 的输出重定向到文件中。
示例:
-getProperty:Bar -getResultOutputFile:Biz.txt
这会将属性 Bar 的值写入 Biz.txt。
</target>
示例:
-getProperty:Bar -getResultOutputFile:Biz.txt
这会将属性 Bar 的值写入 Biz.txt。
</target>
<note>
LOCALIZATION: "-getResultOutputFile", "get*" and "-getProperty" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -320,10 +320,10 @@
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</source>
<target state="needs-review-translation"> -check
在生成中启用 BuildChecks。
BuildCheck 允许评估规则以确保生成的
属性。有关详细信息，请参阅 aka.ms/buildcheck
<target state="new"> -check
Enables BuildChecks during the build.
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</target>
<note>
{Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"}

148
src/MSBuild/Resources/xlf/Strings.zh-Hant.xlf сгенерированный
Просмотреть файл

@ -140,11 +140,11 @@
used, write out the values after the build.
</source>
<target state="translated"> -getProperty:propertyName,...
於評估後，寫出一或多個指定屬性的值，以及
但不執行建置；如有使用
-targets 選項或 -getTargetResult 選項，
便於建置之後，再寫出這些值。
</target>
於評估後，寫出一或多個指定屬性的值，以及
但不執行建置；如有使用
-targets 選項或 -getTargetResult 選項，
便於建置之後，再寫出這些值。
</target>
<note>
LOCALIZATION: "-getProperty", "-targets" and "-getTargetResult" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -159,12 +159,12 @@
the values after the build.
</source>
<target state="translated"> -getItem:itemName,...
於評估後，寫出一或多個指定項目的值，以及
其相關的中繼資料，但不
執行建置；如有使用 -targets 選項
或 -getTargetResult 選項，
便於建置之後，再寫出這些值。
</target>
於評估後，寫出一或多個指定項目的值，以及
其相關的中繼資料，但不
執行建置；如有使用 -targets 選項
或 -getTargetResult 選項，
便於建置之後，再寫出這些值。
</target>
<note>
LOCALIZATION: "-getItem", "targets" and "getTargetResult" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -176,9 +176,9 @@
the specified targets will be executed.
</source>
<target state="translated"> -getTargetResult:targetName,...
寫出一或多個目標的輸出值，然後
執行指定的目標。
</target>
寫出一或多個目標的輸出值，然後
執行指定的目標。
</target>
<note>
LOCALIZATION: "-getTargetResult" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -201,20 +201,20 @@
(Short form: -fa)
</source>
<target state="translated"> -featureAvailability:featureName,...
檢查功能可用性。結果會是下列其中一個字串:
“Undefined”、“Available”、“NotAvailable” 和
"Preview"。
- Undefined - 功能的可用性未定義
(功能可用性檢查程式不知道
該功能名稱)
- NotAvailable - 此功能無法使用 (不同於
Undefined，功能可用性檢查程式知道該功能名稱，
並知道功能目前的
MSBuild 引擎不支援該功能)
- Available - 此功能可以使用
- Preview - 此功能目前為預覽狀態 (不穩定)
(簡短形式: -fa)
</target>
檢查功能可用性。結果會是下列其中一個字串:
“Undefined”、“Available”、“NotAvailable” 和
"Preview"。
- Undefined - 功能的可用性未定義
(功能可用性檢查程式不知道
該功能名稱)
- NotAvailable - 此功能無法使用 (不同於
Undefined，功能可用性檢查程式知道該功能名稱，
並知道功能目前的
MSBuild 引擎不支援該功能)
- Available - 此功能可以使用
- Preview - 此功能目前為預覽狀態 (不穩定)
(簡短形式: -fa)
</target>
<note>
LOCALIZATION: "-featureAvailability", "-fa", "Undefined", "Available" "NotAvailable" and "Preview"should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -234,17 +234,17 @@
(Short form: -tl)
</source>
<target state="translated"> -terminalLogger[:auto,on,off]
啟用或停用終端機記錄器。終端機記錄器
會即時在主機上，提供更進一步的組建輸出，
並依照專案的邏輯編排，並會醒目提示
可採取動作的資訊。指定自動 (或只使用選項，
不使用引數) 只在使用標準輸出
未重新導向時，才使用終端機記錄器。不剖析輸出，
或以其他方式據此在
未來的版本中保持不變。此選項可在 MSBuild 17.8 和
更新版本中使用。
(簡短形式: -tl)
</target>
啟用或停用終端機記錄器。終端機記錄器
會即時在主機上，提供更進一步的組建輸出，
並依照專案的邏輯編排，並會醒目提示
可採取動作的資訊。指定自動 (或只使用選項，
不使用引數) 只在使用標準輸出
未重新導向時，才使用終端機記錄器。不剖析輸出，
或以其他方式據此在
未來的版本中保持不變。此選項可在 MSBuild 17.8 和
更新版本中使用。
(簡短形式: -tl)
</target>
<note>
LOCALIZATION: "-terminalLogger", "-tl", and "auto" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -271,24 +271,24 @@
-tlp:default=auto;verbosity=diag;shownCommandLine
</source>
<target state="translated"> -terminalLoggerParameters: &lt;parameters&gt;
終端機記錄器的參數。(簡短形式: -tlp)
可用的參數。
default -- 指定終端機記錄器的預設值
。其需要下列其中一值:
終端機記錄器的參數。(簡短形式: -tlp)
可用的參數。
default -- 指定終端機記錄器的預設值。
其需要下列其中一值:
。
- 'on'、'true' 會強制使用 TerminalLogger，即使
其之後可能會停用。
- 'off'、'false' 會強制使用 TerminalLogger，即使
其之後可能會啟用。
- `auto` 會啟用 terminalLogger，但終端機必須能夠
提供支援，且工作階段未經重新導向
stdout/stderr
verbosity -- 覆寫上記錄器的
-verbosity
showCommandLine -- 顯示 TaskCommandLineEvent 訊息
- 'on'、'true' 會強制使用 TerminalLogger，即使
其之後可能會停用。
- 'off'、'false' 會強制使用 TerminalLogger，即使
其之後可能會啟用。
- `auto` 會啟用 terminalLogger，但終端機必須能夠
提供支援，且工作階段未經重新導向
stdout/stderr
verbosity -- 覆寫上記錄器的
-verbosity
showCommandLine -- 顯示 TaskCommandLineEvent 訊息
範例:
-tlp:default=auto;verbosity=diag;shownCommandLine
範例:
-tlp:default=auto;verbosity=diag;shownCommandLine
</target>
<note>
LOCALIZATION: "-terminalLoggerParameters", "-tlp", "default", "on", "true", "off", "false", "auto", "verbosity", "showCommandLine" should not be localized.
@ -304,12 +304,12 @@
This writes the value of property Bar into Biz.txt.
</source>
<target state="translated"> -getResultOutputFile:file
將輸出從 get* 重新導向至檔案。
將輸出從 get* 重新導向至檔案。
範例:
-getProperty:Bar -getResultOutputFile:Biz.txt
這會將屬性列的值寫入 Biz.txt。
</target>
範例:
-getProperty:Bar -getResultOutputFile:Biz.txt
這會將屬性列的值寫入 Biz.txt。
</target>
<note>
LOCALIZATION: "-getResultOutputFile", "get*" and "-getProperty" should not be localized.
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars.
@ -321,10 +321,10 @@
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</source>
<target state="needs-review-translation"> -check
在建置期間啟用 BuildChecks。
BuildCheck 會啟用評估規則以確保組建的
屬性。如需詳細資訊，請參閱 aka.ms/buildcheck
<target state="new"> -check
Enables BuildChecks during the build.
BuildCheck enables evaluating rules to ensure properties
of the build. For more info see aka.ms/buildcheck
</target>
<note>
{Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"}
@ -506,8 +506,8 @@
<target state="translated"> -isolateProjects[:True|MessageUponIsolationViolation|False]
導致 MSBuild 在隔離中建置每個專案。
設定為 "MessageUponIsolationViolation"
(或其簡短形式 "Message") 時，如果提供
設定為 "MessageUponIsolationViolation"
(或其簡短形式 "Message") 時，如果提供
-outputResultsCache 切換，則只會序列化來自
頂層目標的結果。這是為了降低相依性專案上，
由於其相依性位於快取目標上 (其副作用
@ -801,11 +801,11 @@
<target state="translated"> -logger:&lt;記錄器&gt; 使用此記錄器可記錄 MSBuild 的事件。
若要指定多個記錄器，請各別指定每個記錄器。
&lt;記錄器&gt; 語法為:
[&lt;class&gt;,]&lt;assembly&gt;[,&lt;options&gt;][;&lt;parameters&gt;]
[&lt;類別&gt;,]&lt;組件&gt;[,&lt;選項&gt;][;&lt;參數&gt;]
&lt;記錄器類別&gt; 語法為:
[&lt;一部分或完整的命名空間&gt;.]&lt;記錄器類別名稱&gt;
&lt;記錄器組件&gt; 語法為:
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
{&lt;組件名稱&gt;[,&lt;strong name&gt;] | &lt;組件檔案&gt;}
記錄器選項會指定 MSBuild 建立記錄器的方式。
&lt;記錄器參數&gt; 是選擇性參數，其會依您輸入的內容，
完全一樣地傳遞到記錄器。(簡短形式: -l)
@ -1083,11 +1083,11 @@
若要指定多個記錄器，請各別指定每個記錄器。
(簡短形式 -dl)
&lt;記錄器&gt; 語法為:
[&lt;class&gt;,]&lt;assembly&gt;[,&lt;options&gt;][;&lt;parameters&gt;]
[&lt;類別&gt;,]&lt;組件&gt;[,&lt;選項&gt;][;&lt;參數&gt;]
&lt;記錄器類別&gt; 語法為:
[&lt;一部分或完整的命名空間&gt;.]&lt;記錄器類別名稱&gt;
&lt;記錄器組件&gt; 語法為:
{&lt;assembly name&gt;[,&lt;strong name&gt;] | &lt;assembly file&gt;}
{&lt;組件名稱&gt;[,&lt;strong name&gt;] | &lt;組件檔案&gt;}
記錄器選項會指定 MSBuild 建立記錄器的方式。
&lt;記錄器參數&gt; 是選擇性參數，其會依您輸入的內容，
完全一樣地傳遞到記錄器。(簡短形式: -l)
@ -1141,8 +1141,8 @@
</source>
<target state="translated"> -toolsversion:&lt;版本&gt;
建置期間所使用的 MSBuild 工具組 (工作、目標等)
版本。此版本將會覆寫
個別專案所指定的版本。(簡短形式:
版本。此版本將會覆寫
個別專案所指定的版本。(簡短形式:
-tv)
範例:
-toolsVersion:3.5
@ -1839,7 +1839,7 @@
</trans-unit>
<trans-unit id="SAC_Evaluation">
<source>2: in evaluation. It is recommended to turn off Smart App Control in development environemnt as otherwise performance might be impacted</source>
<target state="translated">2: 評估中。建議關閉開發環境中的智慧型應用程式控制，否則效能可能會受到影響</target>
<target state="translated">2: 評估中。建議關閉開發環境中的智慧型手機應用程式控制件，否則效能可能會受到影響</target>
<note>Smart App Control, "VerifiedAndReputablePolicyState" should not be localized</note>
</trans-unit>
<trans-unit id="SAC_Off">
@ -2365,4 +2365,4 @@
</trans-unit>
</body>
</file>
</xliff>
</xliff>

2
src/Shared/Resources/xlf/Strings.shared.cs.xlf сгенерированный
Просмотреть файл

@ -325,7 +325,7 @@
</trans-unit>
<trans-unit id="WildcardResultsInDriveEnumeration">
<source>MSB5029: The value "{0}" of the "{1}" attribute in element &lt;{2}&gt; in file "{3}" is a wildcard that results in enumerating all files on the drive, which was likely not intended. Check that referenced properties are always defined and that the project and current working directory are not at the drive root.</source>
<target state="translated">MSB5029: Hodnota {0} atributu {1} v elementu &lt;{2}&gt; v souboru {3} je zástupný znak, jehož výsledkem je výčet všech souborů na jednotce, což pravděpodobně nebylo zamýšleno. Zkontrolujte, zda jsou odkazované vlastnosti vždy definovány a zda projekt a aktuální pracovní adresář nejsou v kořenovém adresáři jednotky.</target>
<target state="translated">MSB5029: Hodnota {0} atributu {1} v elementu &lt;{2}&gt; v souboru {3}je zástupný znak, jehož výsledkem je výčet všech souborů na jednotce, což pravděpodobně nebylo zamýšleno. Zkontrolujte, zda jsou odkazované vlastnosti vždy definovány a zda projekt a aktuální pracovní adresář nejsou v kořenovém adresáři jednotky.</target>
<note>{StrBegin="MSB5029: "}UE: This is a generic message that is displayed when we find a project element that has a drive enumerating wildcard value for one of its
attributes e.g. &lt;Compile Include="$(NotAlwaysDefined)\**\*.cs"&gt; -- if the property is undefined, the value of Include should not result in enumerating all files on drive.</note>
</trans-unit>

24
src/Tasks/Resources/xlf/Strings.es.xlf сгенерированный
Просмотреть файл

@ -128,7 +128,7 @@
</trans-unit>
<trans-unit id="AxTlbBaseTask.StrongNameUtils.NoPublicKeySpecified">
<source>MSB3654: Delay signing requires that at least a public key be specified. Please either supply a public key using the KeyFile or KeyContainer properties, or disable delay signing.</source>
<target state="translated">MSB3654: La firma retrasada requiere que se especifique al menos una clave pública. Proporcione una clave pública mediante las propiedades KeyFile o KeyContainer, o deshabilite la firma retrasada.</target>
<target state="translated">MSB3654: La firma retardada requiere que se especifique al menos una clave pública. Proporcione una clave pública mediante las propiedades KeyFile o KeyContainer, o deshabilite la firma retardada.</target>
<note>{StrBegin="MSB3654: "}</note>
</trans-unit>
<trans-unit id="CombineTargetFrameworkInfoProperties.NotNullAndEmptyRootElementName">
@ -358,7 +358,7 @@
</trans-unit>
<trans-unit id="Delete.Error">
<source>MSB3061: Unable to delete file "{0}". {1} {2}</source>
<target state="translated">MSB3061: no se puede eliminar el archivo "{0}". {1} {2}</target>
<target state="translated">MSB3061: No se puede eliminar el archivo "{0}". {1} {2}</target>
<note>{StrBegin="MSB3061: "}</note>
</trans-unit>
<trans-unit id="Delete.InvalidRetryCount">
@ -373,7 +373,7 @@
</trans-unit>
<trans-unit id="Delete.Retrying">
<source>MSB3062: Could not delete file "{0}". Beginning retry {1} in {2}ms. {3} {4}</source>
<target state="translated">MSB3062: no se pudo eliminar el archivo "{0}". Iniciando el reintento {1} en {2} ms. {3} {4}</target>
<target state="translated">MSB3062: No se pudo eliminar el archivo "{0}". Iniciando reintento{1} en {2}ms. {3} {4}</target>
<note>{StrBegin="MSB3062: "} LOCALIZATION: {0} are paths. {1} and {2} are numbers. {3} is an optional localized message, {4} is message from LockCheck.</note>
</trans-unit>
<trans-unit id="Delete.SkippingNonexistentFile">
@ -1520,7 +1520,7 @@
</trans-unit>
<trans-unit id="Move.Error">
<source>MSB3677: Unable to move file "{0}" to "{1}". {2} {3}</source>
<target state="translated">MSB3677: no es posible mover el archivo "{0}" a "{1}". {2} {3}</target>
<target state="translated">MSB3677: No se puede mover el archivo "{0}" a "{1}". {2} {3}</target>
<note>{StrBegin="MSB3677: "}</note>
</trans-unit>
<trans-unit id="Move.ExactlyOneTypeOfDestination">
@ -2352,7 +2352,7 @@
</trans-unit>
<trans-unit id="ResolveComReference.LoadingDelaySignedAssemblyWithStrongNameVerificationEnabled">
<source>MSB3295: Failed to load an assembly. Please make sure you have disabled strong name verification for your public key if you want to generate delay signed wrappers. {0}</source>
<target state="translated">MSB3295: No se pudo cargar un ensamblado. Asegúrese de que deshabilitó la comprobación de nombres seguros para su clave pública si desea generar contenedores de firma con retraso. {0}</target>
<target state="translated">MSB3295: No se pudo cargar un ensamblado. Asegúrese de que deshabilitó la comprobación de nombres seguros para su clave pública si desea generar contenedores de firma retardada. {0}</target>
<note>{StrBegin="MSB3295: "}</note>
</trans-unit>
<trans-unit id="ResolveComReference.MissingOrUnknownComReferenceAttribute">
@ -2561,7 +2561,7 @@
</trans-unit>
<trans-unit id="StrongNameUtils.NoPublicKeySpecified">
<source>MSB3353: Public key necessary for delay signing was not specified.</source>
<target state="translated">MSB3353: No se especificó la clave pública necesaria para la firma con retraso.</target>
<target state="translated">MSB3353: No se especificó la clave pública necesaria para la firma retardada.</target>
<note>{StrBegin="MSB3353: "}</note>
</trans-unit>
<trans-unit id="TaskRequiresFrameworkFailure">
@ -2586,7 +2586,7 @@
</trans-unit>
<trans-unit id="Touch.CannotMakeFileWritable">
<source>MSB3372: The file "{0}" cannot be made writable. {1} {2}</source>
<target state="translated">MSB3372: el archivo "{0}" no se puede hacer grabable. {1} {2}</target>
<target state="translated">MSB3372: El archivo "{0}" no se puede escribir. {1} {2}</target>
<note>{StrBegin="MSB3372: "}</note>
</trans-unit>
<trans-unit id="Touch.CannotRestoreAttributes">
@ -2596,7 +2596,7 @@
</trans-unit>
<trans-unit id="Touch.CannotTouch">
<source>MSB3374: The last access/last write time on file "{0}" cannot be set. {1} {2}</source>
<target state="translated">MSB3374: no se puede establecer la hora de último acceso o última escritura en el archivo "{0}". {1} {2}</target>
<target state="translated">MSB3374: No se puede establecer la hora de último acceso o última escritura en el archivo "{0}". {1} {2}</target>
<note>{StrBegin="MSB3374: "}</note>
</trans-unit>
<trans-unit id="Touch.CreatingFile">
@ -2691,7 +2691,7 @@
</trans-unit>
<trans-unit id="Unzip.ErrorCouldNotMakeFileWriteable">
<source>MSB3935: Failed to unzip file "{0}" because destination file "{1}" is read-only and could not be made writable. {2} {3}</source>
<target state="translated">MSB3935: no se pudo descomprimir el archivo "{0}" porque el archivo de destino "{1}" es de solo lectura y no se pudo hacer grabable. {2} {3}</target>
<target state="translated">MSB3935: No se pudo descomprimir el archivo "{0}" porque el archivo de destino "{1}" es de solo lectura y no se pudo escribir. {2} {3}</target>
<note>{StrBegin="MSB3935: "}</note>
</trans-unit>
<trans-unit id="Unzip.ErrorCouldNotOpenFile">
@ -2776,7 +2776,7 @@
</trans-unit>
<trans-unit id="WriteLinesToFile.ErrorOrWarning">
<source>MSB3491: Could not write lines to file "{0}". {1} {2}</source>
<target state="translated">MSB3491: no se pudieron escribir líneas en el archivo "{0}". {1} {2}</target>
<target state="translated">MSB3491: No se pudieron escribir líneas en el archivo "{0}". {1} {2}</target>
<note>{StrBegin="MSB3491: "}</note>
</trans-unit>
<trans-unit id="GetReferenceAssemblyPaths.InvalidTargetFrameworkMoniker">
@ -3046,7 +3046,7 @@
</trans-unit>
<trans-unit id="WriteCodeFragment.CouldNotWriteOutput">
<source>MSB3713: The file "{0}" could not be created. {1} {2}</source>
<target state="translated">MSB3713: no se pudo crear el archivo "{0}". {1} {2}</target>
<target state="translated">MSB3713: No se pudo crear el archivo "{0}". {1} {2}</target>
<note>{StrBegin="MSB3713: "}</note>
</trans-unit>
<trans-unit id="WriteCodeFragment.SkippedNumberedParameter">
@ -3496,7 +3496,7 @@
</trans-unit>
<trans-unit id="ZipDirectory.ErrorFailed">
<source>MSB3943: Failed to zip directory "{0}" to file "{1}". {2} {3}</source>
<target state="translated">MSB3943: no se pudo comprimir el directorio "{0}" en el archivo "{1}". {2} {3}</target>
<target state="translated">MSB3943: No se pudo comprimir el directorio "{0}" en el archivo "{1}". {2} {3}</target>
<note>{StrBegin="MSB3943: "}</note>
</trans-unit>
<trans-unit id="ZipDirectory.ErrorFileExists">

4
src/Tasks/Resources/xlf/Strings.it.xlf сгенерированный
Просмотреть файл

@ -133,12 +133,12 @@
</trans-unit>
<trans-unit id="CombineTargetFrameworkInfoProperties.NotNullAndEmptyRootElementName">
<source>MSB3991: '{0}' is not set or empty. When {1} is false, make sure to set a non-empty value for '{0}'.</source>
<target state="translated">MSB3991: “{0}” non è impostato o è vuoto. Quando {1} è false, assicurarsi di impostare un valore non vuoto per "{0}".</target>
<target state="translated">MSB3991: '{0}' non è impostato o è vuoto. Quando {1} è false, assicurarsi di impostare un valore non vuoto per '{0}'.</target>
<note>{StrBegin="MSB3991: "}</note>
</trans-unit>
<trans-unit id="CombineTargetFrameworkInfoProperties.NotNullRootElementName">
<source>MSB3992: '{0}' is not set. When {1} is true, make sure to set a value for '{0}'.</source>
<target state="translated">MSB3992: "{0}" non impostato. Quando {1} è true, assicurarsi di impostare un valore per "{0}".</target>
<target state="translated">MSB3992: '{0}' non è impostato. Quando {1} è true, assicurarsi di impostare un valore per '{0}'.</target>
<note>{StrBegin="MSB3992: "}</note>
</trans-unit>
<trans-unit id="CommonTarget.NoWin32ManifestAndPreferNativeArm64Enabled">

2
src/Tasks/Resources/xlf/Strings.pl.xlf сгенерированный
Просмотреть файл

@ -1102,7 +1102,7 @@
<trans-unit id="GenerateResource.BinaryFormatterUse">
<source>MSB3825: Resource "{0}" of type "{1}" may be deserialized via BinaryFormatter at runtime. BinaryFormatter is deprecated due to known security risks and is removed from .NET 9+. If you wish to continue using it, set property "GenerateResourceWarnOnBinaryFormatterUse" to false.
More information: https://aka.ms/binaryformatter-migration-guide</source>
<target state="translated">MSB3825: zasób „{0}” typu „{1}” może być deserializowany za pośrednictwem elementu BinaryFormatter w czasie wykonywania. Element BinaryFormatter jest przestarzały ze względu na znane zagrożenia bezpieczeństwa i został usunięty z platformy .NET 9. Jeśli chcesz nadal go używać, ustaw właściwość „GenerateResourceWarnOnBinaryFormatterUse” na wartość false.
<target state="translated">MSB3825: zasób „{0}” typu „{1}” może być deserializowany za pośrednictwem elementu BinaryFormatter w czasie wykonywania. Element BinaryFormatter jest przestarzały ze względu na znane zagrożenia bezpieczeństwa i został usunięty z platformy .NET 9 lub nowszej. Jeśli chcesz nadal go używać, ustaw właściwość „GenerateResourceWarnOnBinaryFormatterUse” na false.
Więcej informacji: https://aka.ms/binaryformatter-migration-guide</target>
<note>{StrBegin="MSB3825: "}</note>
</trans-unit>

2
src/Tasks/Resources/xlf/Strings.pt-BR.xlf сгенерированный
Просмотреть файл

@ -1102,7 +1102,7 @@
<trans-unit id="GenerateResource.BinaryFormatterUse">
<source>MSB3825: Resource "{0}" of type "{1}" may be deserialized via BinaryFormatter at runtime. BinaryFormatter is deprecated due to known security risks and is removed from .NET 9+. If you wish to continue using it, set property "GenerateResourceWarnOnBinaryFormatterUse" to false.
More information: https://aka.ms/binaryformatter-migration-guide</source>
<target state="translated">MSB3825: O recurso “{0}” do tipo “{1}” pode ser desserializado por meio do BinaryFormatter em runtime. O BinaryFormatter foi preterido devido a riscos de segurança conhecidos e foi removido do .NET 9+. Se quiser continuar a usá-lo, defina a propriedade “GenerateResourceWarnOnBinaryFormatterUse” como false.
<target state="translated">MSB3825: O recurso "{0}" do tipo "{1}" pode ser desserializado via BinaryFormatter em tempo de execução. O BinaryFormatter foi preterido devido a riscos de segurança conhecidos e foi removido do .NET 9+. Se desejar continuar usando, defina a propriedade "GenerateResourceWarnOnBinaryFormatterUse" como false.
Mais informações: https://aka.ms/binaryformatter-migration-guide</target>
<note>{StrBegin="MSB3825: "}</note>
</trans-unit>

2
src/Tasks/Resources/xlf/Strings.ru.xlf сгенерированный
Просмотреть файл

@ -1103,7 +1103,7 @@
<source>MSB3825: Resource "{0}" of type "{1}" may be deserialized via BinaryFormatter at runtime. BinaryFormatter is deprecated due to known security risks and is removed from .NET 9+. If you wish to continue using it, set property "GenerateResourceWarnOnBinaryFormatterUse" to false.
More information: https://aka.ms/binaryformatter-migration-guide</source>
<target state="translated">MSB3825: для ресурса "{0}" с типом "{1}" может быть выполнена десериализация с помощью BinaryFormatter во время выполнения. BinaryFormatter является нерекомендуемым из-за известных рисков безопасности и удален из .NET 9+. Если вы хотите продолжить использовать его, задайте для свойства GenerateResourceWarnOnBinaryFormatterUse значение false.
Дополнительные сведения: https://aka.ms/binaryformatter-migration-guide</target>
Дополнительные сведения см. в руководстве по миграции по ссылке https://aka.ms/binaryformatter.</target>
<note>{StrBegin="MSB3825: "}</note>
</trans-unit>
<trans-unit id="GenerateResource.CoreSupportsLimitedScenarios">

4
src/Tasks/Resources/xlf/Strings.zh-Hans.xlf сгенерированный
Просмотреть файл

@ -1102,8 +1102,8 @@
<trans-unit id="GenerateResource.BinaryFormatterUse">
<source>MSB3825: Resource "{0}" of type "{1}" may be deserialized via BinaryFormatter at runtime. BinaryFormatter is deprecated due to known security risks and is removed from .NET 9+. If you wish to continue using it, set property "GenerateResourceWarnOnBinaryFormatterUse" to false.
More information: https://aka.ms/binaryformatter-migration-guide</source>
<target state="translated">MSB3825: 可在运行时通过 BinaryFormatter 反序列化类型为“{1}”的资源“{0}”。由于已知的安全风险，BinaryFormatter 已被弃用，并从 .NET 9+ 中删除。如果要继续使用它，请将属性 "GenerateResourceWarnOnBinaryFormatterUse" 设置为 false。
有关详细信息，请参阅:https://aka.ms/binaryformatter-migration-guide</target>
<target state="translated">MSB3825: 可在运行时通过 BinaryFormatter 反序列化类型为“{1}”的资源“{0}”。由于已知的安全风险，BinaryFormatter 已被弃用，并从 .NET 9+ 中删除。如果要继续使用它，请将属性“GenerateResourceWarnOnBinaryFormatterUse”设置为 false。
有关详细信息，请参阅：https://aka.ms/binaryformatter-migration-guide</target>
<note>{StrBegin="MSB3825: "}</note>
</trans-unit>
<trans-unit id="GenerateResource.CoreSupportsLimitedScenarios">

4
src/Tasks/Resources/xlf/Strings.zh-Hant.xlf сгенерированный
Просмотреть файл

@ -1102,8 +1102,8 @@
<trans-unit id="GenerateResource.BinaryFormatterUse">
<source>MSB3825: Resource "{0}" of type "{1}" may be deserialized via BinaryFormatter at runtime. BinaryFormatter is deprecated due to known security risks and is removed from .NET 9+. If you wish to continue using it, set property "GenerateResourceWarnOnBinaryFormatterUse" to false.
More information: https://aka.ms/binaryformatter-migration-guide</source>
<target state="translated">MSB3825: 類型為 "{1}" 的資源 "{0}" 可以在執行階段透過 BinaryFormatter 進行還原序列化。BinaryFormatter 已因已知的安全性風險遭到取代，且已從 .NET 9+ 中移除。如果您想要繼續使用它，請將屬性 "GenerateResourceWarnOnBinaryFormatterUse" 設為 false。
詳細資訊 (英文): https://aka.ms/binaryformatter-migration-guide</target>
<target state="translated">MSB3825: 在執行階段，可能會透過 BinaryFormatter 將類型為「{1}」的資源「{0}」取消初始化。BinaryFormatter 已因已知的安全性風險而被棄用，且已從 .NET 9+ 中移除。如果您想要繼續使用它，請將屬性 "GenerateResourceWarnOnBinaryFormatterUse" 設為 false。
詳細資訊: https://aka.ms/binaryformatter-migration-guide</target>
<note>{StrBegin="MSB3825: "}</note>
</trans-unit>
<trans-unit id="GenerateResource.CoreSupportsLimitedScenarios">