diff --git a/src/Build/Resources/xlf/Strings.cs.xlf b/src/Build/Resources/xlf/Strings.cs.xlf index 2a17c8ea8cf..0ecc3a1e420 100644 --- a/src/Build/Resources/xlf/Strings.cs.xlf +++ b/src/Build/Resources/xlf/Strings.cs.xlf @@ -218,12 +218,12 @@ Project {0} specifies 'TargetFramework(s)' property '{1}', which does not use the .NET SDK. Those properties are not understood by projects that import C# targets directly. - Project {0} určuje vlastnost TargetFramework(s) '{1}', která nepoužívá sadu .NET SDK. Tyto vlastnosti nejsou srozumitelné pro projekty, které přímo importují cíle jazyka C#. + Projekt {0} určuje vlastnost TargetFramework/TargetFrameworks {1}, která nepoužívá sadu .NET SDK. Tyto vlastnosti nejsou srozumitelné projektům, které přímo importují cíle jazyka C#. Terms in quotes are not to be translated. 'TargetFramework' and 'TargetFrameworks' properties are not respected and should not be specified in projects that do not use the .NET SDK. - Vlastnosti TargetFramework a TargetFrameworks se nedodržují a neměly by se zadává v projektech, které nepoužívají sadu .NET SDK. + Vlastnosti TargetFramework a TargetFrameworks se nezohledňují a neměly by být zadané v projektech, které nepoužívají sadu .NET SDK. Terms in quotes are not to be translated. @@ -268,12 +268,12 @@ Location: '{0}' cannot be fully trusted, place your projects outside of that folder (Project: {1}). - Umístění: '{0}' nelze plně považovat za důvěryhodné, umístěte projekty mimo danou složku (Projekt: {1}). + Umístění {0}nemůže být plně důvěryhodné. Umístěte projekty mimo danou složku (projekt: {1}). Downloads folder is untrusted for projects building. - Složka Stažené soubory není důvěryhodná pro sestavování projektů. + Složka Stažené soubory není pro sestavování projektů důvěryhodná. @@ -468,7 +468,7 @@ DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. - DOTNET_HOST_PATH není nastaven. Nelze určit umístění modulu runtime pro spuštění hostitele aplikace. Tato možnost by se měla nastavit vždy při spuštění v sadě .NET SDK. + DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. @@ -1111,7 +1111,7 @@ Chyby: {3} Logging type {0} is not understood by {1}. - {1} nerozumí {0} typu protokolování. + Typ protokolování {0} není pro {1}srozumitelný. @@ -2113,7 +2113,7 @@ Chyby: {3} 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=<value> to the command line. Currently web projects only support Debug and Release configurations. - 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=<hodnota> do příkazového řádku. Webové projekty nyní podporují pouze konfigurace Debug a Release. + 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=<hodnota> do příkazového řádku. Webové projekty nyní podporují pouze konfigurace Debug a Release. UE: This is not an error, so doesn't need an error code. LOCALIZATION: Do NOT localize "AspNetConfiguration", "Debug", "Release". diff --git a/src/Build/Resources/xlf/Strings.de.xlf b/src/Build/Resources/xlf/Strings.de.xlf index a0afccd7157..15284b67dff 100644 --- a/src/Build/Resources/xlf/Strings.de.xlf +++ b/src/Build/Resources/xlf/Strings.de.xlf @@ -218,12 +218,12 @@ Project {0} specifies 'TargetFramework(s)' property '{1}', which does not use the .NET SDK. Those properties are not understood by projects that import C# targets directly. - Project {0} gibt die Eigenschaft "TargetFramework(s)" '{1}' an, die nicht das .NET SDK verwendet. Diese Eigenschaften werden von Projekten, die C#-Ziele direkt importieren, nicht verstanden. + Projekt {0} gibt die „TargetFramework(s)“-Eigenschaft „{1}“ an, die nicht das .NET-SDK verwendet. Projekte, die C#-Ziele direkt importieren können diese Eigenschaften nicht verarbeiten. Terms in quotes are not to be translated. 'TargetFramework' and 'TargetFrameworks' properties are not respected and should not be specified in projects that do not use the .NET SDK. - Die Eigenschaften "TargetFramework" und "TargetFrameworks" werden nicht berücksichtigt und sollten nicht in Projekten angegeben werden, die nicht das .NET SDK verwenden. + Die Eigenschaften „TargetFramework“ und „TargetFrameworks“ werden nicht berücksichtigt und sollten nicht in Projekten angegeben werden, die nicht das .NET-SDK verwenden. Terms in quotes are not to be translated. @@ -268,12 +268,12 @@ Location: '{0}' cannot be fully trusted, place your projects outside of that folder (Project: {1}). - Speicherort: '{0}' kann nicht vollständig vertrauenswürdig sein. Platzieren Sie Ihre Projekte außerhalb dieses Ordners (Projekt: {1}). + Der Speicherort: „{0}“ kann nicht vollständig vertrauenswürdig sein. Platzieren Sie Ihre Projekte außerhalb dieses Ordners (Projekt: {1}). Downloads folder is untrusted for projects building. - Der Ordner "Downloads" ist für die Projekterstellung nicht vertrauenswürdig. + Der Ordner „Downloads“ ist für die Projekterstellung nicht vertrauenswürdig. @@ -428,7 +428,7 @@ 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 - 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 + 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 The message is emitted when the custom check assembly can not be successfully registered. @@ -443,7 +443,7 @@ The custom check: '{0}' is registered for the build from the location: '{1}'. - Dies benutzerdefinierte Überprüfung „{0}“ ist für den Build vom Folgenden aus registriert: „{1}”. + Dies benutzerdefinierte Überprüfung „{0}“ ist für den Build von folgendem Speicherort aus registriert: „{1}”. @@ -468,7 +468,7 @@ DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. - DOTNET_HOST_PATH ist nicht festgelegt. Der Laufzeitpfad für den App-Host-Bootstrap kann nicht ermittelt werden. Diese Einstellung sollte immer gesetzt sein, wenn die Ausführung unter dem .NET SDK erfolgt. + DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. @@ -547,7 +547,7 @@ There are illegal characters in '{0}' in the {1} item. - Unzulässige Zeichen in „{0}“ im {1}-Element. + Unzulässige Zeichen in „{0}“ im Element {1}. @@ -887,7 +887,7 @@ The "{0}" resolver attempted to resolve the SDK "{1}". Warnings: {2} Errors: {3} - Der Konfliktlöser „{0}“ hat versucht, das SDK „{1}“ aufzulösen. + Der Konfliktlöser "{0}" hat versucht, das SDK "{1}" aufzulösen. Warnungen: {2} Fehler: {3} @@ -1100,7 +1100,7 @@ Fehler: {3} This is an unhandled exception in MSBuild -- PLEASE UPVOTE AN EXISTING ISSUE OR FILE A NEW ONE AT https://aka.ms/msbuild/unhandled {0} - 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 + Dies ist ein Ausnahmefehler in MSBuild. STIMMEN SIE EINEM VORHANDENEN ISSUE ZU, ODER ERSTELLEN SIE EIN NEUES ISSUE UNTER https://aka.ms/msbuild/unhandled {0} diff --git a/src/Build/Resources/xlf/Strings.es.xlf b/src/Build/Resources/xlf/Strings.es.xlf index 4ffb1eaeee4..65b485cab74 100644 --- a/src/Build/Resources/xlf/Strings.es.xlf +++ b/src/Build/Resources/xlf/Strings.es.xlf @@ -218,12 +218,12 @@ Project {0} specifies 'TargetFramework(s)' property '{1}', which does not use the .NET SDK. Those properties are not understood by projects that import C# targets directly. - El {0} de proyecto especifica la propiedad "TargetFramework(s)" '{1}', que no usa el SDK de .NET. Los proyectos que importan destinos de C# no entienden esas propiedades directamente. + El proyecto {0} especifica la propiedad de "TargetFramework(s)" "{1}", que no usa el SDK de .NET. Los proyectos que importan destinos de C# directamente no entienden esas propiedades. Terms in quotes are not to be translated. 'TargetFramework' and 'TargetFrameworks' properties are not respected and should not be specified in projects that do not use the .NET SDK. - Las propiedades "TargetFramework" y "TargetFrameworks" no se respetan y no deben especificarse en proyectos que no usen el SDK de .NET. + Las propiedades "TargetFramework" y "TargetFrameworks" no se respetan, y no deben especificarse en proyectos que no usan el SDK de .NET. Terms in quotes are not to be translated. @@ -268,12 +268,12 @@ Location: '{0}' cannot be fully trusted, place your projects outside of that folder (Project: {1}). - Ubicación: '{0}' no puede ser de plena confianza, coloque los proyectos fuera de esa carpeta (proyecto: {1}). + Ubicación: "{0}" no puede ser de plena confianza; coloque los proyectos fuera de esa carpeta (Proyecto: {1}). Downloads folder is untrusted for projects building. - La carpeta descargas no es de confianza para la compilación de proyectos. + La carpeta Descargas no es de confianza para la compilación de proyectos. @@ -428,7 +428,7 @@ 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 - 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 + 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 The message is emitted when the custom check assembly can not be successfully registered. @@ -468,7 +468,7 @@ DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. - DOTNET_HOST_PATH no está establecido. No se puede determinar la ubicación en tiempo de ejecución para el arranque del host de la aplicación. Esto siempre debe establecerse cuando se ejecuta en el SDK de .NET. + DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. @@ -547,7 +547,7 @@ There are illegal characters in '{0}' in the {1} item. - Hay caracteres no válidos en '{0}' en el elemento {1}. + Hay caracteres no válidos en "{0}" en el elemento {1}. @@ -605,7 +605,7 @@ The task failed to load because it requires the MSBuild .NET Runtime Task Host, but the .NET Runtime Task Host could not be found for the specified version. See https://aka.ms/nettaskhost for details on how to resolve this error. - No se pudo cargar la tarea porque requiere el host de tareas en tiempo de ejecución de .NET de MSBuild, pero no se encontró el host de tareas en tiempo de ejecución de .NET para la versión especificada. + Error al cargar la tarea porque requiere el host de tareas en tiempo de ejecución de .NET de MSBuild, pero no se encontró el host de tareas en tiempo de ejecución de .NET para la versión especificada. Consulte https://aka.ms/nettaskhost para obtener más información sobre cómo resolver este error. @@ -887,7 +887,7 @@ The "{0}" resolver attempted to resolve the SDK "{1}". Warnings: {2} Errors: {3} - El resolvedor "{0}" intentó resolver el SDK "{1}". + El solucionador "{0}" intentó resolver el SDK "{1}". Advertencias: {2} Errores: {3} @@ -1111,7 +1111,7 @@ Errores: {3} Logging type {0} is not understood by {1}. - {1} no entiende el tipo de registro {0}. + El tipo de registro {0} no se entiende mediante {1}. diff --git a/src/Build/Resources/xlf/Strings.fr.xlf b/src/Build/Resources/xlf/Strings.fr.xlf index 32010d4dfc0..3a2ad7b63f7 100644 --- a/src/Build/Resources/xlf/Strings.fr.xlf +++ b/src/Build/Resources/xlf/Strings.fr.xlf @@ -4,7 +4,7 @@ Attempting to cancel the build... - Tentative d'annulation de la génération en cours... + Tentative d'annulation de la build en cours... @@ -138,7 +138,7 @@ The BuildCheck is enabled for this build. - BuildCheck est activé pour cette build. + Le BuildCheck est activé pour cette build. @@ -153,7 +153,7 @@ Tasks {0} and {1} from projects {2} and {3} write the same file: {4}. - Tâches {0} et {1} de projets {2} et {3} écrivez le même fichier : {4}. + Tâches {0} et {1} des projets {2} et {3} écrivent le même fichier : {4}. @@ -163,7 +163,7 @@ '{0}' with value: '{1}' - '{0}' avec valeur : '{1}' + « {0} » avec la valeur « {1} » Will be used as a parameter {0} in previous message. @@ -173,7 +173,7 @@ No implicit property derived from an environment variable should be used during the build. - Aucune propriété implicite dérivée d'une variable d'environnement ne doit être utilisée pendant la construction. + Aucune propriété implicite dérivée d'une variable d'environnement ne doit être utilisée pendant la build. @@ -188,7 +188,7 @@ Project {0} specifies 'EmbeddedResource' item '{1}', that has possibly a culture denoting extension ('{2}'), but explicit 'Culture' nor 'WithCulture=false' metadata are not specified. - Project {0} spécifie l’élément « EmbeddedResource »{1}« qui a éventuellement une extension de culture indiquant ( »{2}« ), mais les métadonnées explicites « Culture » et « WithCulture=false » ne sont pas spécifiées. + Project {0} spécifie l’élément « EmbeddedResource » '{1}', qui a peut-être une extension de création de culture ('{2}'), mais les métadonnées explicites « Culture » et « WithCulture=false » ne sont pas spécifiées. Terms in quotes are not to be translated. @@ -218,12 +218,12 @@ Project {0} specifies 'TargetFramework(s)' property '{1}', which does not use the .NET SDK. Those properties are not understood by projects that import C# targets directly. - Project {0} spécifie la propriété « TargetFramework(s) » '{1}', qui n’utilise pas le SDK .NET. Ces propriétés ne sont pas comprises par les projets qui importent directement des cibles C#. + Le projet {0} spécifie la propriété 'TargetFramework(s)' '{1}', qui n’utilise pas le kit de développement logiciel (SDK) .NET. Ces propriétés ne sont pas comprises par les projets qui importent directement des cibles C#. Terms in quotes are not to be translated. 'TargetFramework' and 'TargetFrameworks' properties are not respected and should not be specified in projects that do not use the .NET SDK. - Les propriétés 'TargetFramework' et 'TargetFrameworks' ne sont pas respectées et ne doivent pas être spécifiées dans les projets qui n’utilisent pas le SDK .NET. + Les propriétés 'TargetFramework' et 'TargetFrameworks' ne sont pas respectées et ne doivent pas être spécifiées dans les projets qui n’utilisent pas le kit de développement logiciel (SDK) .NET. Terms in quotes are not to be translated. @@ -238,7 +238,7 @@ Property: '{0}' was accessed, but it was never initialized. - Propriété : « {0} » a été consultée, mais elle n'a jamais été initialisée. + La propriété « {0} » a été consultée, mais elle n'a jamais été initialisée. @@ -248,7 +248,7 @@ Property: '{0}' first declared/initialized at {1} used before it was initialized. - Propriété : '{0}' déclarée/initialisée pour la première fois à l'utilisation de {1} avant d'être initialisée. + 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. @@ -258,7 +258,7 @@ Property: '{0}' was declared/initialized, but it was never used. - Propriété : '{0}' a été déclarée/initialisée, mais elle n'a jamais été utilisée. + La propriété « {0} » a été déclarée/initialisée, mais elle n'a jamais été utilisée. @@ -268,12 +268,12 @@ Location: '{0}' cannot be fully trusted, place your projects outside of that folder (Project: {1}). - Emplacement : '{0}' ne peut pas être entièrement fiable. Placez vos projets en dehors de ce dossier (Projet : {1}). + Emplacement : '{0}' ne peut pas être entièrement approuvé, placez vos projets en dehors de ce dossier (Projet : {1}). Downloads folder is untrusted for projects building. - Le dossier des téléchargements n’est pas approuvé pour la génération de projets. + Le dossier Téléchargements n’est pas approuvé pour la génération de projets. @@ -418,7 +418,7 @@ Failed to find the specified custom check assembly: '{0}'. Please check if it exists. - Impossible de trouver l’assembly de vérification personnalisé spécifié : «{0}». Veuillez vérifier s’il existe. + Impossible de trouver l’assembly de vérification personnalisé spécifié : « {0} ». Veuillez vérifier s’il existe. The message is emitted when the custom check assembly can not be found. @@ -428,27 +428,27 @@ 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 - É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 + É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 The message is emitted when the custom check assembly can not be successfully registered. Failed to register the custom check: '{0}'. - Échec de l’inscription de la vérification personnalisée : «{0}». + Échec de l’inscription de la vérification personnalisée : « {0} ». The message is emitted on failed loading of the custom check in process. Failed to instantiate the custom check rule with the following exception: '{0}'. - Échec de l’instanciation de la règle de vérification personnalisée avec l’exception suivante : «{0}». + Échec de l’instanciation de la règle de vérification personnalisée avec l’exception suivante : « {0} ». The message is emitted on failed loading of the custom check rule in process. The custom check: '{0}' is registered for the build from the location: '{1}'. - La vérification personnalisée «{0}» est inscrite pour la build à partir de l’emplacement : «{1}». + La vérification personnalisée « {0} » est inscrite pour la build à partir de l’emplacement : « {1} ». Custom check rule: '{0}' has been registered successfully. - Règle de vérification personnalisée : «{0}» a été correctement inscrite. + Règle de vérification personnalisée : « {0} » a été correctement inscrite. The message is emitted on successful loading of the custom check rule in process. @@ -468,7 +468,7 @@ DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. - La variable d'environnement DOTNET_HOST_PATH n'est pas définie. Impossible de déterminer l'emplacement d'exécution du bootstrap de l'hôte de l'application. Ce paramètre doit toujours être défini lors de l'exécution sous le SDK .NET. + DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. @@ -605,8 +605,8 @@ The task failed to load because it requires the MSBuild .NET Runtime Task Host, but the .NET Runtime Task Host could not be found for the specified version. See https://aka.ms/nettaskhost for details on how to resolve this error. - La tâche n’a pas pu être chargée, car elle nécessite l’hôte de tâches du runtime MSBuild .NET, mais l’hôte de tâches du runtime .NET est introuvable pour la version spécifiée. - Pour plus d’informations sur la résolution de cette erreur, consultez https://aka.ms/nettaskhost. + Nous n’avons pas pu charger la tâche, car elle nécessite l’hôte de tâches du runtime MSBuild .NET, mais l’hôte de tâches du runtime .NET est introuvable pour la version spécifiée. + Pour découvrir plus d’informations sur la résolution de cette erreur, consultez https://aka.ms/nettaskhost. @@ -1100,7 +1100,7 @@ Erreurs : {3} This is an unhandled exception in MSBuild -- PLEASE UPVOTE AN EXISTING ISSUE OR FILE A NEW ONE AT https://aka.ms/msbuild/unhandled {0} - 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. + 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 {0} diff --git a/src/Build/Resources/xlf/Strings.it.xlf b/src/Build/Resources/xlf/Strings.it.xlf index 4a0a49af8a2..f19b5d499ea 100644 --- a/src/Build/Resources/xlf/Strings.it.xlf +++ b/src/Build/Resources/xlf/Strings.it.xlf @@ -153,7 +153,7 @@ Tasks {0} and {1} from projects {2} and {3} write the same file: {4}. - Le attività {0} e {1} dai progetti {2} e {3} scrivere lo stesso file: {4}. + Le attività {0} e {1} dai progetti {2} e {3} scrivono lo stesso file: {4}. @@ -218,12 +218,12 @@ Project {0} specifies 'TargetFramework(s)' property '{1}', which does not use the .NET SDK. Those properties are not understood by projects that import C# targets directly. - Project {0} specifica la proprietà 'TargetFramework(s)' '{1}', che non usa .NET SDK. Queste proprietà non sono comprese dai progetti che importano direttamente destinazioni C#. + Il progetto {0} specifica la proprietà “TargetFramework(s)” “{1}”, che non utilizza il SDK di .NET. Queste proprietà non vengono riconosciute dai progetti che importano direttamente destinazioni C#. Terms in quotes are not to be translated. 'TargetFramework' and 'TargetFrameworks' properties are not respected and should not be specified in projects that do not use the .NET SDK. - Le proprietà 'TargetFramework' e 'TargetFrameworks' non vengono rispettate e non devono essere specificate nei progetti che non usano .NET SDK. + Le proprietà “TargetFramework” e “TargetFrameworks” non vengono rispettate e non devono essere specificate nei progetti che non utilizzano il SDK di.NET. Terms in quotes are not to be translated. @@ -268,12 +268,12 @@ Location: '{0}' cannot be fully trusted, place your projects outside of that folder (Project: {1}). - Percorso: '{0}' non può essere considerato completamente attendibile. Inserire i progetti all'esterno di tale cartella (Progetto: {1}). + Percorso: '{0}' non può essere completamente attendibile. Posizionare i progetti all'esterno di tale cartella (Progetto: {1}). Downloads folder is untrusted for projects building. - La cartella Dei download non è attendibile per la compilazione di progetti. + La cartella Download non è attendibile per la creazione di progetti. @@ -418,7 +418,7 @@ Failed to find the specified custom check assembly: '{0}'. Please check if it exists. - Impossibile trovare l'assembly di controllo personalizzato specificato: “{0}”. Verificare se esiste. + Non è possibile trovare l'assembly del controllo personalizzato specificato: '{0}'. Verificare se esiste. The message is emitted when the custom check assembly can not be found. @@ -428,27 +428,27 @@ 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 - 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 + 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 The message is emitted when the custom check assembly can not be successfully registered. Failed to register the custom check: '{0}'. - Impossibile registrare il controllo personalizzato: “{0}”. + Non è possibile registrare il controllo personalizzato: '{0}'. The message is emitted on failed loading of the custom check in process. Failed to instantiate the custom check rule with the following exception: '{0}'. - Non è stato possibile creare un'istanza della regola di controllo personalizzata con l'eccezione seguente: “{0}”. + Non è possibile creare un'istanza della regola del controllo personalizzato con l'eccezione seguente: '{0}'. The message is emitted on failed loading of the custom check rule in process. The custom check: '{0}' is registered for the build from the location: '{1}'. - Il controllo personalizzato “{0}” è registrato per la compilazione dal percorso “{1}”. + Il controllo personalizzato '{0}' è registrato per la compilazione dal percorso '{1}'. Custom check rule: '{0}' has been registered successfully. - La regola di controllo personalizzata “{0}” è stata registrata correttamente. + La regola del controllo personalizzato '{0}' è stata registrata correttamente. The message is emitted on successful loading of the custom check rule in process. @@ -468,7 +468,7 @@ DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. - DOTNET_HOST_PATH non è impostato. Non è possibile determinare il percorso di runtime per il bootstrap dell'host dell'app. Deve sempre essere impostato quando viene eseguito con .NET SDK. + DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. @@ -605,7 +605,7 @@ The task failed to load because it requires the MSBuild .NET Runtime Task Host, but the .NET Runtime Task Host could not be found for the specified version. See https://aka.ms/nettaskhost for details on how to resolve this error. - Non è possibile caricare l'attività perché richiede l'host attività di runtime .NET di MSBuild, ma non è possibile trovare l'host attività di runtime .NET per la versione specificata. + Il caricamento dell'attività non è riuscita perché richiede l'host dell’attività di runtime .NET di MSBuild, ma non è possibile trovare l'host dell'attività di runtime .NET per la versione specificata. Per informazioni dettagliate su come risolvere l'errore, vedere https://aka.ms/nettaskhost. @@ -887,7 +887,7 @@ The "{0}" resolver attempted to resolve the SDK "{1}". Warnings: {2} Errors: {3} - Il resolver "{0}" ha provato a risolvere l'SDK "{1}". + Il resolver "{0}" ha tentato di risolvere l'SDK "{1}". Avvisi: {2} Errori: {3} diff --git a/src/Build/Resources/xlf/Strings.ja.xlf b/src/Build/Resources/xlf/Strings.ja.xlf index cc1a03df410..7fd75e1aa84 100644 --- a/src/Build/Resources/xlf/Strings.ja.xlf +++ b/src/Build/Resources/xlf/Strings.ja.xlf @@ -4,7 +4,7 @@ Attempting to cancel the build... - ビルドを取り消そうとしています... + ビルドの取り消を試みています... @@ -143,17 +143,17 @@ Projects {0} and {1} have conflicting output paths: {2}. - プロジェクト {0} と {1} の出力パスが競合しています: {2}。 + プロジェクト {0} と {1} で、出力パス: {2} が競合しています。 Two projects should not share their 'OutputPath' nor 'IntermediateOutputPath' locations. - 2 つのプロジェクトで 'OutputPath' と 'IntermediateOutputPath' の場所を共有することはできません。 + 2 つのプロジェクトで、'OutputPath' と 'IntermediateOutputPath' の場所の、どちらも共有することはできません。 'OutputPath' and 'IntermediateOutputPath' not to be translated. Tasks {0} and {1} from projects {2} and {3} write the same file: {4}. - プロジェクト {2} と {3} のタスク {0} と {1} は、同じファイルを書き込みます: {4}。 + プロジェクト {2} と {3} のタスク {0} と {1} が、同じファイル: {4} に書き込んでいます。 @@ -163,17 +163,17 @@ '{0}' with value: '{1}' - '{0}' (値 '{1}') + 値が '{1}' の '{0}' Will be used as a parameter {0} in previous message. Property is derived from environment variable: {0}. Properties should be passed explicitly using the /p option. - プロパティは環境変数から派生しています: {0}。プロパティは、/p オプションを使用して明示的に渡す必要があります。 + プロパティは環境変数: {0} から派生しています。プロパティは、/p オプションを使用して明示的に渡す必要があります。 No implicit property derived from an environment variable should be used during the build. - ビルド中に環境変数から派生した暗黙的なプロパティを使用しないでください。 + 環境変数から派生した暗黙的なプロパティをビルド中に使用しないでください。 @@ -223,7 +223,7 @@ 'TargetFramework' and 'TargetFrameworks' properties are not respected and should not be specified in projects that do not use the .NET SDK. - 'TargetFramework' プロパティと 'TargetFrameworks' プロパティは優先されないため、.NET SDK を使用しないプロジェクトでは指定しないでください。 + 'TargetFramework' と 'TargetFrameworks' プロパティは考慮されず、.NET SDK を使用しないプロジェクトでは指定しないでください。 Terms in quotes are not to be translated. @@ -238,17 +238,17 @@ Property: '{0}' was accessed, but it was never initialized. - プロパティ: '{0}' にアクセスしましたが、初期化されませんでした。 + プロパティ: '{0}' は、初期化されないままアクセスされました。 A property that is accessed should be declared first. - アクセスされるプロパティを、まず宣言する必要があります。 + アクセスされるプロパティを、最初に宣言する必要があります。 Property: '{0}' first declared/initialized at {1} used before it was initialized. - {1} で最初に宣言/初期化されたプロパティ: '{0}' は初期化前に使用されました。 + {1} で最初に宣言/初期化されたプロパティ: '{0}' が初期化前に使用されました。 @@ -258,22 +258,22 @@ Property: '{0}' was declared/initialized, but it was never used. - プロパティ: '{0}' は宣言または初期化されましたが、使用されませんでした。 + プロパティ: '{0}' は宣言/初期化されましたが、使用されたことがありません。 A property that is not used should not be declared. - 使用されていないプロパティは宣言しないでください。 + 使用されないプロパティを宣言する必要はありません。 Location: '{0}' cannot be fully trusted, place your projects outside of that folder (Project: {1}). - 場所: '{0}' を完全に信頼することはできません。プロジェクトをそのフォルダーの外に配置してください (プロジェクト: {1})。 + 場所: '{0}' を完全に信頼することはできません。プロジェクトをそのフォルダー外に配置してください (プロジェクト: {1})。 Downloads folder is untrusted for projects building. - ダウンロード フォルダーは、プロジェクトのビルドに対して信頼されていません。 + Downloads フォルダーは、プロジェクトのビルドに対して信頼されません。 @@ -418,7 +418,7 @@ Failed to find the specified custom check assembly: '{0}'. Please check if it exists. - 指定されたカスタム チェック アセンブリが見つかりませんでした: '{0}'。存在するかどうか確認してください。 + 指定されたカスタム チェック アセンブリ: '{0}' が見つかりませんでした。これが存在することを確認してください。 The message is emitted when the custom check assembly can not be found. @@ -428,12 +428,12 @@ 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 - カスタム チェックの種類を読み込めませんでした: アセンブリ '{1}' の '{0}'。Microsoft.Build.Experimental.BuildCheck.Check 基底クラスを継承していることを確認してください。カスタム チェックを意図していない場合は、公開しないでください。詳細情報: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition + アセンブリ: '{1}' から、カスタム チェックの種類: '{0}'を読み込めませんでした。Microsoft.Build.Experimental.BuildCheck.Check の基底クラスを継承していることを確認してください。カスタム チェックを意図していない場合は、公開しないでください。詳細情報: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition The message is emitted when the custom check assembly can not be successfully registered. Failed to register the custom check: '{0}'. - カスタム チェックを登録できませんでした: '{0}'。 + カスタム チェック: '{0}'を登録できませんでした。 The message is emitted on failed loading of the custom check in process. @@ -443,7 +443,7 @@ The custom check: '{0}' is registered for the build from the location: '{1}'. - カスタム チェック '{0}' は、場所 '{1}' からビルドに登録されています。 + カスタム チェック: '{0}' は、場所: '{1}' からビルドに登録されています。 @@ -468,7 +468,7 @@ DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. - DOTNET_HOST_PATH が設定されていません。アプリ ホストのブートストラップに必要なランタイムの場所を特定できません。.NET SDK で実行する場合は、必ず設定してください。 + DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. @@ -547,7 +547,7 @@ There are illegal characters in '{0}' in the {1} item. - {1} 項目内の '{0}' に不正な文字があります。 + {1} 項目内の '{0}' が不正な文字を含んでいます。 @@ -611,7 +611,7 @@ SDK version {0} is below the minimum required version of {1}. The .NET Runtime Task Host is supported only when using .NET SDK 10.0.100-rc1 or later. - SDK バージョン {0} は、必要最低限のバージョン {1} を下回っています。.NET ランタイム タスク ホストは、.NET SDK 10.0.100-rc1 以降を使用する場合にのみサポートされます。 + SDK バージョン {0} が、必要最小限のバージョン {1} を下回っています。.NET ランタイム タスク ホストは、.NET SDK 10.0.100-rc1 以降が使用されている場合にのみサポートされます。 @@ -1111,7 +1111,7 @@ Errors: {3} Logging type {0} is not understood by {1}. - ログの種類 {0} は {1} では認識されません。 + ログの種類 {0} は、{1} では認識されません。 diff --git a/src/Build/Resources/xlf/Strings.ko.xlf b/src/Build/Resources/xlf/Strings.ko.xlf index 907dd46d818..578f814d225 100644 --- a/src/Build/Resources/xlf/Strings.ko.xlf +++ b/src/Build/Resources/xlf/Strings.ko.xlf @@ -218,12 +218,12 @@ Project {0} specifies 'TargetFramework(s)' property '{1}', which does not use the .NET SDK. Those properties are not understood by projects that import C# targets directly. - 프로젝트 {0} .NET SDK를 사용하지 않는 'TargetFramework' 속성 '{1}' 지정합니다. 이러한 속성은 C# 대상을 직접 가져오는 프로젝트에서 이해할 수 없습니다. + 프로젝트 {0}은(는) .NET SDK를 사용하지 않는 'TargetFramework' 속성 '{1}'을(를) 지정합니다. 이러한 속성은 C# 대상을 직접 가져오는 프로젝트에서는 이해되지 않습니다. Terms in quotes are not to be translated. 'TargetFramework' and 'TargetFrameworks' properties are not respected and should not be specified in projects that do not use the .NET SDK. - 'TargetFramework' 및 'TargetFrameworks' 속성은 사용되지 않으며 .NET SDK를 사용하지 않는 프로젝트에서 지정해서는 안 됩니다. + 'TargetFramework' 및 'TargetFrameworks' 속성은 적용되지 않으므로 .NET SDK를 사용하지 않는 프로젝트에서 지정해서는 안 됩니다. Terms in quotes are not to be translated. @@ -268,12 +268,12 @@ Location: '{0}' cannot be fully trusted, place your projects outside of that folder (Project: {1}). - 위치: '{0}' 완전히 신뢰할 수 없습니다. 프로젝트를 해당 폴더 외부에 배치하세요(프로젝트: {1}). + 위치: '{0}'은(는) 완전히 신뢰할 수 없으므로 프로젝트를 해당 폴더 외부에 배치합니다(프로젝트: {1}). Downloads folder is untrusted for projects building. - 프로젝트 빌드에 대해 다운로드 폴더를 신뢰할 수 없습니다. + 다운로드 폴더는 프로젝트 빌드에 대해 신뢰할 수 없습니다. @@ -468,7 +468,7 @@ DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. - DOTNET_HOST_PATH가 설정되어 있지 않습니다. 앱 호스트 부트스트랩의 런타임 위치를 확인할 수 없습니다. .NET SDK에서 실행할 때는 이를 항상 설정해야 합니다. + DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. @@ -1111,7 +1111,7 @@ Errors: {3} Logging type {0} is not understood by {1}. - 로깅 유형 {0} {1} 이해할 수 없습니다. + 로깅 유형 {0}은(는) {1}에서는 이해되지 않습니다. diff --git a/src/Build/Resources/xlf/Strings.pl.xlf b/src/Build/Resources/xlf/Strings.pl.xlf index f21ad0b9af1..43dab72e371 100644 --- a/src/Build/Resources/xlf/Strings.pl.xlf +++ b/src/Build/Resources/xlf/Strings.pl.xlf @@ -48,7 +48,7 @@ ArchiveFile was obtained, but the final edited version was not set. - Uzyskano plik ArchiveFile, ale nie ustawiono ostatecznej edycji wersji. + Uzyskano plik ArchiveFile, ale nie ustawiono ostatecznej edytowanej wersji. @@ -82,7 +82,7 @@ BuildEvent record number {0} was expected to read exactly {1} bytes from the stream, but read {2} instead. - Oczekiwano, że numer rekordu BuildEvent {0} odczyta ze strumienia liczbę bajtów równą dokładnie {1}, ale zamiast tego odczyta {2}. + Oczekiwano, że numer rekordu BuildEvent {0} odczyta ze strumienia liczbę bajtów równą dokładnie {1}, ale zamiast tego odczytał {2}. LOCALIZATION: {0} is an integer number denoting order. {1} is an integer denoting size. {2} is an integer value indicating number of bytes. @@ -101,7 +101,7 @@ Structured events and raw events cannot be replayed at the same time. - Nie można jednocześnie odtwarzać zdarzeń strukturalnych i nieprzetworzonych. + Nie można ponownie odtwarzać jednocześnie zdarzeń strukturalnych i zdarzeń pierwotnych. @@ -126,7 +126,7 @@ Attempt to skip {0} bytes, only non-negative offset up to int.MaxValue is allowed. - Próba pominięcia {0} bajtów, tylko przesunięcie nieujemne do liczby całkowitej. Wartość MaxValue jest dozwolona. + Próba pominięcia {0} bajtów, tylko przesunięcie nieujemne do wartości int.MaxValue jest dozwolone. LOCALIZATION: {0} is integer number denoting number of bytes. 'int.MaxValue' should not be translated. @@ -218,12 +218,12 @@ Project {0} specifies 'TargetFramework(s)' property '{1}', which does not use the .NET SDK. Those properties are not understood by projects that import C# targets directly. - Program Project {0} określa właściwość "TargetFramework(s)" '{1}', która nie używa zestawu .NET SDK. Te właściwości nie są rozpoznane przez projekty, które importują bezpośrednio elementy docelowe języka C#. + Projekt {0} określa właściwość „TargetFramework(s)” „{1}”, która nie używa zestawu SDK platformy .NET. Te właściwości nie są zrozumiałe dla projektów, które bezpośrednio importują elementy docelowe języka C#. Terms in quotes are not to be translated. 'TargetFramework' and 'TargetFrameworks' properties are not respected and should not be specified in projects that do not use the .NET SDK. - Właściwości "TargetFramework" i "TargetFrameworks" nie są respektowane i nie należy ich określać w projektach, w których nie jest używany zestaw .NET SDK. + Właściwości „TargetFramework” i „TargetFrameworks” nie są przestrzegane i nie należy ich określać w projektach, które nie używają zestawu SDK platformy .NET. Terms in quotes are not to be translated. @@ -238,17 +238,17 @@ Property: '{0}' was accessed, but it was never initialized. - Właściwość: uzyskano dostęp do „{0}”, ale nigdy nie dokonano inicjacji. + Uzyskano dostęp do właściwości: „{0}”, ale nigdy nie zainicjowano jej. A property that is accessed should be declared first. - Właściwość, do których jest uzyskiwany dostęp, powinna być zadeklarowana jako pierwsza. + Właściwość, do której jest uzyskiwany dostęp, powinna być zadeklarowana jako pierwsza. Property: '{0}' first declared/initialized at {1} used before it was initialized. - Właściwość: „{0}” została najpierw zadeklarowana/zainicjowana {1} i była używania przed jej zainicjowaniem. + Właściwość: „{0}” została najpierw zadeklarowana/zainicjowana w {1} i była używania przed jej zainicjowaniem. @@ -258,7 +258,7 @@ Property: '{0}' was declared/initialized, but it was never used. - Właściwość: uzyskano dostęp do „{0}”, ale nigdy nie dokonano inicjacji. + Zadeklarowano/zainicjowano właściwość: „{0}”, ale nigdy nie była używana. @@ -268,12 +268,12 @@ Location: '{0}' cannot be fully trusted, place your projects outside of that folder (Project: {1}). - Lokalizacja: '{0}' nie można w pełni zaufać. Umieść projekty poza tym folderem (projekt: {1}). + Lokalizacja: nie można w pełni zaufać „{0}”. Umieść swoje projekty poza tym folderem (Projekt: {1}). Downloads folder is untrusted for projects building. - Folder Pobrane nie jest zaufany do kompilowania projektów. + Folder Pobrane nie jest zaufany w przypadku kompilowania projektów. @@ -418,7 +418,7 @@ Failed to find the specified custom check assembly: '{0}'. Please check if it exists. - Nie udało się znaleźć określonego niestandardowego zestawu kontrolnego: „{0}”. Sprawdź, czy istnieje. + Nie udało się znaleźć określonego niestandardowego zestawu kontroli: „{0}”. Sprawdź, czy istnieje. The message is emitted when the custom check assembly can not be found. @@ -428,27 +428,27 @@ 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 - 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 + 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 The message is emitted when the custom check assembly can not be successfully registered. Failed to register the custom check: '{0}'. - Nie można zarejestrować niestandardowego kontrolera: „{0}”. + Nie można zarejestrować niestandardowej kontroli: „{0}”. The message is emitted on failed loading of the custom check in process. Failed to instantiate the custom check rule with the following exception: '{0}'. - Nie udało się utworzyć niestandardowej reguły utworzenia wystąpienia z następującym wyjątkiem: „{0}”. + Nie udało się utworzyć wystąpienia niestandardowej reguły kontroli z następującym wyjątkiem: „{0}”. The message is emitted on failed loading of the custom check rule in process. The custom check: '{0}' is registered for the build from the location: '{1}'. - Kontroler niestandardowy „{0}” jest zarejestrowany dla kompilacji z lokalizacji: „{1}”. + Kontrola niestandardowa: „{0}” jest zarejestrowany dla kompilacji z lokalizacji: „{1}”. Custom check rule: '{0}' has been registered successfully. - Niestandardowa reguła kontrolera: „{0}” została pomyślnie zarejestrowana. + Niestandardowa reguła kontroli: „{0}” została pomyślnie zarejestrowana. The message is emitted on successful loading of the custom check rule in process. @@ -468,7 +468,7 @@ DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. - DOTNET_HOST_PATH nie jest ustawiona. Nie można określić lokalizacji środowiska uruchomieniowego dla ładowania początkowego hosta aplikacji. Należy to zawsze ustawić podczas uruchamiania w zestawie .NET SDK. + DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. @@ -524,7 +524,7 @@ MSB4017: The build stopped unexpectedly because of an unexpected logger failure. {0} - MSB4017: Kompilacja została nieoczekiwanie zatrzymana z powodu nieoczekiwanego błędu rejestratora. + MSB4017: kompilacja została nieoczekiwanie zatrzymana z powodu nieoczekiwanego błędu rejestratora. {0} {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 @@ -547,7 +547,7 @@ There are illegal characters in '{0}' in the {1} item. - Element {0} zawiera niedozwolone znaki w „{1}”. + Element {1} zawiera niedozwolone znaki w „{0}”. @@ -605,7 +605,7 @@ The task failed to load because it requires the MSBuild .NET Runtime Task Host, but the .NET Runtime Task Host could not be found for the specified version. See https://aka.ms/nettaskhost for details on how to resolve this error. - Nie można załadować zadania, ponieważ wymaga ono hosta zadań środowiska uruchomieniowego programu MSBuild .NET, ale nie można odnaleźć hosta zadań środowiska uruchomieniowego platformy .NET dla określonej wersji. + Nie można załadować zadania, ponieważ wymaga ono hosta zadań narzędzi MSBuild środowiska uruchomieniowego platformy .NET, ale nie można odnaleźć hosta zadań środowiska uruchomieniowego platformy .NET dla określonej wersji. Zobacz witrynę https://aka.ms/nettaskhost, aby uzyskać szczegółowe informacje na temat sposobu rozwiązania tego błędu. @@ -984,7 +984,7 @@ Błędy: {3} The SDK "{0}" was successfully resolved by the "{1}" resolver to location "{2}" and version "{3}". - Zestaw SDK „{0}” został pomyślnie rozpoznany przez narzędzie Resolver „{1}” do lokalizacji „{2}” i wersji „{3}”. + Zestaw SDK „{0}” został pomyślnie rozpoznany przez narzędzie Resolver „{1}” w lokalizacji „{2}” i w wersji „{3}”. @@ -1100,7 +1100,7 @@ Błędy: {3} This is an unhandled exception in MSBuild -- PLEASE UPVOTE AN EXISTING ISSUE OR FILE A NEW ONE AT https://aka.ms/msbuild/unhandled {0} - 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. + 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. {0} @@ -1111,7 +1111,7 @@ Błędy: {3} Logging type {0} is not understood by {1}. - {1} nie {0} typu rejestrowania. + Typ rejestrowania {0} nie jest rozpoznawany przez {1}. diff --git a/src/Build/Resources/xlf/Strings.pt-BR.xlf b/src/Build/Resources/xlf/Strings.pt-BR.xlf index 5f2af03c19a..26f1b7f56a5 100644 --- a/src/Build/Resources/xlf/Strings.pt-BR.xlf +++ b/src/Build/Resources/xlf/Strings.pt-BR.xlf @@ -178,12 +178,12 @@ Project {0} references output of a project {1}. Referenced path: {2}. ProjectReference should be used instead. - O projeto {0} faz referência à saída de um projeto {1}. Caminho referenciado: {2}. Em vez disso, ProjectReference deve ser usado. + O {0} faz referência à saída de um projeto {1}. Caminho referenciado: {2}. ProjectReference deve ser usado em vez disso. A project should not be referenced via 'Reference' to its output, but rather directly via 'ProjectReference'. - Um projeto não deve ser referenciado por meio de "Referência" à sua saída, mas diretamente por meio de "ProjectReference". + Um projeto não deve ser referenciado via 'Reference' para sua saída, mas diretamente via 'ProjectReference'. @@ -218,12 +218,12 @@ Project {0} specifies 'TargetFramework(s)' property '{1}', which does not use the .NET SDK. Those properties are not understood by projects that import C# targets directly. - O {0} especifica a propriedade 'TargetFramework(s)' '{1}', que não usa o SDK do .NET. Essas propriedades não são compreendidas pelos projetos que importam diretamente os destinos C#. + O Projeto {0} especifica a propriedade 'TargetFramework(s)' '{1}', que não usa o SDK do .NET. Essas propriedades não são compreendidas por projetos que importam diretamente os destinos do C#. Terms in quotes are not to be translated. 'TargetFramework' and 'TargetFrameworks' properties are not respected and should not be specified in projects that do not use the .NET SDK. - As propriedades 'TargetFramework' e 'TargetFrameworks' não são respeitadas e não devem ser especificadas em projetos que não usam o SDK do .NET. + As propriedades 'TargetFramework' e 'TargetFrameworks' não são respeitadas e não devem ser especificadas em projetos que não usam o SDK do .NET. Terms in quotes are not to be translated. @@ -238,7 +238,7 @@ Property: '{0}' was accessed, but it was never initialized. - Propriedade: "{0}" foi acessada, mas nunca foi inicializada. + Propriedade: '{0}' foi acessada, mas nunca foi inicializada. @@ -268,12 +268,12 @@ Location: '{0}' cannot be fully trusted, place your projects outside of that folder (Project: {1}). - Local: '{0}' não é totalmente confiável, coloque seus projetos fora dessa pasta (Projeto: {1}). + Localização: '{0}' não pode ser totalmente confiável, coloque seus projetos fora dessa pasta (Projeto: {1}). Downloads folder is untrusted for projects building. - A pasta Downloads não é confiável para a compilação de projetos. + A pasta Downloads não é confiável para a criação de projetos. @@ -418,7 +418,7 @@ Failed to find the specified custom check assembly: '{0}'. Please check if it exists. - Falha ao localizar o assembly de verificação personalizado especificado: '{0}'. Verifique se existe. + Falha ao localizar o assembly de verificação personalizada especificado: '{0}'. Verifique se existe. The message is emitted when the custom check assembly can not be found. @@ -428,7 +428,7 @@ 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 - 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 + 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 The message is emitted when the custom check assembly can not be successfully registered. @@ -443,12 +443,12 @@ The custom check: '{0}' is registered for the build from the location: '{1}'. - A verificação personalizada: '{0}' está registrada para a compilação a partir do local: '{1}'. + A verificação personalizada: '{0}' está registrada para a compilação do local: '{1}'. Custom check rule: '{0}' has been registered successfully. - Regra de verificação personalizada: '{0}' foi registrada com sucesso. + Regra de verificação personalizada: '{0}' foi registrada com êxito. The message is emitted on successful loading of the custom check rule in process. @@ -468,7 +468,7 @@ DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. - DOTNET_HOST_PATH não está definido. Não é possível determinar o local de runtime para a inicialização do host do aplicativo. Isso sempre deve ser definido durante a execução no SDK do .NET. + DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. @@ -524,7 +524,7 @@ MSB4017: The build stopped unexpectedly because of an unexpected logger failure. {0} - MSB4017: A compilação parou inesperadamente devido a uma falha do agente de log. + MSB4017: a compilação parou inesperadamente devido a uma falha do agente. {0} {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 @@ -1100,7 +1100,7 @@ Erros: {3} This is an unhandled exception in MSBuild -- PLEASE UPVOTE AN EXISTING ISSUE OR FILE A NEW ONE AT https://aka.ms/msbuild/unhandled {0} - 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 + 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 {0} @@ -1111,7 +1111,7 @@ Erros: {3} Logging type {0} is not understood by {1}. - O tipo {0} registro em log não é compreendido por {1}. + O tipo de log {0} não é compreendido por {1}. diff --git a/src/Build/Resources/xlf/Strings.ru.xlf b/src/Build/Resources/xlf/Strings.ru.xlf index a4420a5f842..b23b249e7fa 100644 --- a/src/Build/Resources/xlf/Strings.ru.xlf +++ b/src/Build/Resources/xlf/Strings.ru.xlf @@ -218,12 +218,12 @@ Project {0} specifies 'TargetFramework(s)' property '{1}', which does not use the .NET SDK. Those properties are not understood by projects that import C# targets directly. - В {0} проекта указано свойство "TargetFramework(s)", '{1}', который не использует пакет SDK для .NET. Эти свойства не распознаются проектами, которые импортют целевые объекты C# напрямую. + Проект {0} указывает свойство "TargetFramework(s)" "{1}", которое не использует пакет SDK для .NET. Эти свойства непонятны проектам, которые импортируют целевые объекты C# напрямую. Terms in quotes are not to be translated. 'TargetFramework' and 'TargetFrameworks' properties are not respected and should not be specified in projects that do not use the .NET SDK. - Свойства TargetFramework и TargetFrameworks не учитываются и не должны указываться в проектах, не использующих пакет SDK для .NET. + Свойства "TargetFramework" и "TargetFrameworks" не учитываются и не должны указываться в проектах, которые не используют пакет SDK для .NET. Terms in quotes are not to be translated. @@ -268,12 +268,12 @@ Location: '{0}' cannot be fully trusted, place your projects outside of that folder (Project: {1}). - Расположение: '{0}' быть полностью доверенным. Поместите проекты за пределы этой папки (проект: {1}). + Расположение "{0}" не может быть полностью доверенным, разместите свои проекты за пределами этой папки (проект: {1}). Downloads folder is untrusted for projects building. - Папка "Загрузки" недоверена для сборки проектов. + Папка "Загрузки" не является доверенной для создания проектов. @@ -468,7 +468,7 @@ DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. - DOTNET_HOST_PATH не настроен. Невозможно определить расположение среды выполнения для начальной загрузки хоста приложений. Этот параметр всегда должен быть настроен при запуске в пакете SDK для .NET. + DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. @@ -478,7 +478,7 @@ ({0:F1}s) - ({0:F1}s) + ({0:F1}с) {0}: duration in seconds with 1 decimal point 's' should reflect the localized abbreviation for seconds @@ -1100,7 +1100,7 @@ Errors: {3} This is an unhandled exception in MSBuild -- PLEASE UPVOTE AN EXISTING ISSUE OR FILE A NEW ONE AT https://aka.ms/msbuild/unhandled {0} - Это необработанное исключение в MSBuild. Проголосуйте за существующую проблему или сообщите о новой по адресу https://aka.ms/msbuild/unhandled + Это необработанное исключение в MSBuild. ПРОГОЛОСУЙТЕ ЗА СУЩЕСТВУЮЩУЮ ПРОБЛЕМУ ИЛИ СООБЩИТЕ О НОВУЙ НА https://aka.ms/msbuild/unhandled {0} @@ -1111,7 +1111,7 @@ Errors: {3} Logging type {0} is not understood by {1}. - Тип {0} не распознан {1}. + Тип ведения журнала {0} не понятен для {1}. diff --git a/src/Build/Resources/xlf/Strings.tr.xlf b/src/Build/Resources/xlf/Strings.tr.xlf index d4b684016ae..81d2eaf2b34 100644 --- a/src/Build/Resources/xlf/Strings.tr.xlf +++ b/src/Build/Resources/xlf/Strings.tr.xlf @@ -218,12 +218,12 @@ Project {0} specifies 'TargetFramework(s)' property '{1}', which does not use the .NET SDK. Those properties are not understood by projects that import C# targets directly. - Project {0}, .NET SDK'sını '{1}' 'TargetFramework(s)' özelliğini belirtir. Bu özellikler doğrudan C# hedeflerini içeri aktaran projeler tarafından anlaşılmaz. + Proje {0}, .NET SDK'yı kullanmayan 'TargetFramework(s)' özelliği şunu belirtir: '{1}'. Bu özellikler, C# hedeflerini doğrudan içe aktaran projeler tarafından anlaşılmıyor.. Terms in quotes are not to be translated. 'TargetFramework' and 'TargetFrameworks' properties are not respected and should not be specified in projects that do not use the .NET SDK. - 'TargetFramework' ve 'TargetFrameworks' özellikleri dikkate alınmaz ve .NET SDK kullanmayan projelerde belirtilmeli. + .NET SDK kullanmayan projelerde 'TargetFramework' ve 'TargetFrameworks' özellikleri dikkate alınmaz ve belirtilmemelidir. Terms in quotes are not to be translated. @@ -273,7 +273,7 @@ Downloads folder is untrusted for projects building. - İndirmeler klasörü, proje oluşturma için güvenilir değil. + İndirmeler klasörü, proje oluşturma için güvenilmiyor. @@ -468,7 +468,7 @@ DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. - DOTNET_HOST_PATH ayarlanmadı. Uygulama ana işlemi önyüklemesi için çalışma zamanı konumu belirlenemiyor. .NET SDK altında çalışırken bu her zaman ayarlanmalıdır. + DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. @@ -478,7 +478,7 @@ ({0:F1}s) - ({0:F1}s) + ({0:F1} sn) {0}: duration in seconds with 1 decimal point 's' should reflect the localized abbreviation for seconds @@ -1100,7 +1100,7 @@ Hatalar: {3} This is an unhandled exception in MSBuild -- PLEASE UPVOTE AN EXISTING ISSUE OR FILE A NEW ONE AT https://aka.ms/msbuild/unhandled {0} - 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 + 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 {0} @@ -1111,7 +1111,7 @@ Hatalar: {3} Logging type {0} is not understood by {1}. - Günlük kaydı {0} günlük kaydı türü {1}. + {0} günlüğe kaydetme türü, {1} tarafından anlaşılmıyor. diff --git a/src/Build/Resources/xlf/Strings.zh-Hans.xlf b/src/Build/Resources/xlf/Strings.zh-Hans.xlf index da371088b6a..92ddc65d489 100644 --- a/src/Build/Resources/xlf/Strings.zh-Hans.xlf +++ b/src/Build/Resources/xlf/Strings.zh-Hans.xlf @@ -163,7 +163,7 @@ '{0}' with value: '{1}' - 值为“{1}”的“{0}” + '{0}'，值为 '{1}' Will be used as a parameter {0} in previous message. @@ -173,7 +173,7 @@ No implicit property derived from an environment variable should be used during the build. - 在生成过程中，不应使用派生自环境变量的隐式属性。 + 在生成过程中，不应使用派生自环境变量的任何隐式属性。 @@ -218,12 +218,12 @@ Project {0} specifies 'TargetFramework(s)' property '{1}', which does not use the .NET SDK. Those properties are not understood by projects that import C# targets directly. - Project {0} 指定“TargetFramework()”属性 '{1}'，该属性不使用 .NET SDK。直接导入 C# 目标的项目不理解这些属性。 + 项目 {0} 指定了 “TargetFramework” 属性“{1}”，它不使用 .NET SDK。直接导入 C# 目标的项目无法理解这些属性。 Terms in quotes are not to be translated. 'TargetFramework' and 'TargetFrameworks' properties are not respected and should not be specified in projects that do not use the .NET SDK. - 不考虑 “TargetFramework” 和 “TargetFrameworks” 属性，不应在不使用 .NET SDK 的项目中指定这些属性。 + 在不使用 .NET SDK 的项目中，'TargetFramework' 和 'TargetFrameworks' 属性不会生效，并且不应被指定。 Terms in quotes are not to be translated. @@ -238,17 +238,17 @@ Property: '{0}' was accessed, but it was never initialized. - 已访问属性“{0}”，但从未将其初始化过。 + 已访问属性 '{0}'，但从未将其初始化。 A property that is accessed should be declared first. - 应首先声明访问的属性。 + 应首先声明所访问的属性。 Property: '{0}' first declared/initialized at {1} used before it was initialized. - 属性“{0}”在 {1} 使用时首先声明/初始化，再进行初始化。 + 属性: '{0}' 在 {1} 处使用时先声明/初始化，然后再进行初始化。 @@ -258,7 +258,7 @@ Property: '{0}' was declared/initialized, but it was never used. - 属性“{0}”已声明/初始化，但从未使用过。 + 属性: '{0}' 已声明/初始化，但从未使用过。 @@ -268,12 +268,12 @@ Location: '{0}' cannot be fully trusted, place your projects outside of that folder (Project: {1}). - 位置： '{0}' 不能完全受信任，请将项目置于项目 (文件夹之外 {1})。 + 位置: 无法完全信任“{0}”，请将项目置于该文件夹之外(项目: {1})。 Downloads folder is untrusted for projects building. - 生成项目不信任下载文件夹。 + 下载文件夹不受信任，无法用于项目生成。 @@ -418,7 +418,7 @@ Failed to find the specified custom check assembly: '{0}'. Please check if it exists. - 找不到指定的自定义检查程序集: {0}。请检查它是否存在。 + 找不到指定的自定义检查程序集: '{0}'。请检查它是否存在。 The message is emitted when the custom check assembly can not be found. @@ -428,27 +428,27 @@ 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 - 未能从程序集“{1}”加载自定义检查类型“{0}”。请确保它继承 Microsoft.Build.Experimental.BuildCheck.Check 基类。如果不打算将其作为自定义检查，则不应将其公开。详细信息: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition + 未能从程序集 '{1}' 加载自定义检查类型 '{0}'。请确保它继承 Microsoft.Build.Experimental.BuildCheck.Check 基类。如果它不旨在作为自定义检查，则不应将其公开。详细信息: https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck-Architecture.md#acquisition The message is emitted when the custom check assembly can not be successfully registered. Failed to register the custom check: '{0}'. - 未能注册自定义检查: {0}。 + 未能注册自定义检查: '{0}'。 The message is emitted on failed loading of the custom check in process. Failed to instantiate the custom check rule with the following exception: '{0}'. - 未能实例化自定义检查规则，出现以下异常: {0}。 + 未能实例化自定义检查规则，出现以下异常: '{0}'。 The message is emitted on failed loading of the custom check rule in process. The custom check: '{0}' is registered for the build from the location: '{1}'. - 已从位置“{1}”为内部版本注册自定义检查“{0}”。 + 已从位置 '{1}' 为内部版本注册自定义检查 '{0}'。 Custom check rule: '{0}' has been registered successfully. - 已成功注册自定义检查规则“{0}”。 + 已成功注册自定义检查规则 '{0}'。 The message is emitted on successful loading of the custom check rule in process. @@ -468,7 +468,7 @@ DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. - 未设置 DOTNET_HOST_PATH。无法确定应用托管进程启动的运行时位置。在 .NET SDK 下运行时，应始终设置此项。 + DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. @@ -547,7 +547,7 @@ There are illegal characters in '{0}' in the {1} item. - {1} 项中的“{0}”中存在非法字符。 + '{1}' 项中的 '{0}' 中存在非法字符。 @@ -567,7 +567,7 @@ EvaluationContext objects created with SharingPolicy.Isolated or SharingPolicy.SharedSDKCache do not support being passed an MSBuildFileSystemBase file system. - 使用 SharingPolicy.Isolated 或 SharingPolicy.SharedSDKCache 创建的 EvaluationContext 对象不支持被传递 MSBuildFileSystemBase 文件系统。 + 使用 SharingPolicy.Isolated 创建的 EvaluationContext 对象。SharingPolicy.SharedSDKCache 不支持被传递 MSBuildFileSystemBase 文件系统。 @@ -606,7 +606,7 @@ The task failed to load because it requires the MSBuild .NET Runtime Task Host, but the .NET Runtime Task Host could not be found for the specified version. See https://aka.ms/nettaskhost for details on how to resolve this error. 无法加载该任务，因为它需要 MSBuild .NET 运行时任务主机，但找不到指定版本的 .NET 运行时任务主机。 - 有关如何解决此错误的详细信息，请参阅 https://aka.ms/nettaskhost。 + 若要详细了解如何解决此错误，请参阅 https://aka.ms/nettaskhost。 @@ -3034,7 +3034,7 @@ Utilization: {0} Average Utilization: {1:###.0} 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. - MSB4229: 值“{0}”对 Sdk 规范无效。此属性应该是以分号分隔的Sdk-name/minimum-version 对（用正斜杠分隔）的列表。 + MSB4229: 值“{0}”对 Sdk 规范无效。此属性应该是以分号分隔的Sdk-name/minimum-version 对 (用正斜杠分隔) 的列表。 {StrBegin="MSB4229: "} diff --git a/src/Build/Resources/xlf/Strings.zh-Hant.xlf b/src/Build/Resources/xlf/Strings.zh-Hant.xlf index a124d491633..d267961afd0 100644 --- a/src/Build/Resources/xlf/Strings.zh-Hant.xlf +++ b/src/Build/Resources/xlf/Strings.zh-Hant.xlf @@ -218,12 +218,12 @@ Project {0} specifies 'TargetFramework(s)' property '{1}', which does not use the .NET SDK. Those properties are not understood by projects that import C# targets directly. - Project {0} 指定未使用 .NET SDK 的 'TargetFramework(s)' 属性 '{1}'。直接匯入 C# 目標的項目無法瞭解這些屬性。 + 專案 {0} 指定 'TargetFramework(s)' 屬性 '{1}'，該屬性未使用 .NET SDK。這些屬性無法被直接匯入 C# 目標的專案理解。 Terms in quotes are not to be translated. 'TargetFramework' and 'TargetFrameworks' properties are not respected and should not be specified in projects that do not use the .NET SDK. - 未遵守 『TargetFramework』 和 『TargetFrameworks』 屬性，且不應在未使用 .NET SDK 的專案中指定。 + 未遵守 'TargetFramework' 和 'TargetFrameworks' 屬性，且不應在未使用 .NET SDK 的專案中指定。 Terms in quotes are not to be translated. @@ -268,12 +268,12 @@ Location: '{0}' cannot be fully trusted, place your projects outside of that folder (Project: {1}). - 位置： '{0}' 無法完全信任，請將您的專案放在該資料夾之外 (Project： {1})。 + 位置: '{0}' 無法完全信任，請將您的專案放在該資料夾之外 (專案: {1})。 Downloads folder is untrusted for projects building. - 專案建置不受信任的下載資料夾。 + 下載資料夾對於建置專案來說不受信任。 @@ -468,7 +468,7 @@ DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. - DOTNET_HOST_PATH 未設定。無法判斷應用程式主機啟動程序的執行階段位置。在 .NET SDK 下執行時，應一律設定此項目。 + DOTNET_HOST_PATH is not set. Cannot determine runtime location for app host bootstrap. This should always be set when running under the .NET SDK. @@ -524,7 +524,7 @@ MSB4017: The build stopped unexpectedly because of an unexpected logger failure. {0} - MSB4017: 因為未預期的記錄器失敗，建置未預期停止。 + MSB4017: 由於發生未預期的記錄器失敗，因此已中止組建。 {0} {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 @@ -1111,7 +1111,7 @@ Errors: {3} Logging type {0} is not understood by {1}. - {1} 無法了解記錄類型 {0}。 + {1} 無法理解記錄類型 {0}。 diff --git a/src/Framework/Resources/xlf/SR.cs.xlf b/src/Framework/Resources/xlf/SR.cs.xlf index 3b7bf110d8b..d93933d7e3d 100644 --- a/src/Framework/Resources/xlf/SR.cs.xlf +++ b/src/Framework/Resources/xlf/SR.cs.xlf @@ -59,47 +59,47 @@ The string "{0}" cannot be converted to a boolean (true/false) value. - Řetězec {0} nelze převést na logickou hodnotu (true/false). + The string "{0}" cannot be converted to a boolean (true/false) value. This collection is read-only. - Tato kolekce je jen pro čtení. + This collection is read-only. When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - Při pokusu o vygenerování cesty odkazovaného sestavení z cesty {0} a monikeru rozhraní {1} došlo k chybě. {2} + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. - Cesta {0} používaná pro protokoly ladění je příliš dlouhá. Nastavte ji na kratší hodnotu pomocí proměnné prostředí MSBUILDDEBUGPATH nebo změňte konfigurace vašeho systému, aby povolovala dlouhé cesty. + The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - Nepodařilo se vytvořit dočasný soubor. Složka dočasných souborů je plná nebo cesta k této složce není správná. {0} + Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - Při rozbalování fileSpec s globs: fileSpec došlo k výjimce: {0}, za předpokladu, že se jedná o název souboru. Výjimka: {1} + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - Položka {0} má atribut {1} s hodnotou {2}, kterou nebylo možné převést na hodnotu {3}. + Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Metadata položky %({0}) nelze použít na cestu {1}. {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. The parameter '{0}' can only be a file name and cannot include a directory. - Parametr {0} může být jenom název souboru a nemůže obsahovat adresář. + The parameter '{0}' can only be a file name and cannot include a directory. @@ -109,22 +109,22 @@ Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Cesta: {0} překračuje maximální limit pro cestu k OS. Plně kvalifikovaný název souboru musí být kratší než {1} znaků. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - Verze {0} rozhraní .NET Framework není podporovaná. Zadejte hodnotu z výčtu Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - Verze {0} rozhraní .NET Framework není podporovaná, pokud je jako cíl explicitně určená sada Windows SDK, která je podporovaná jenom v rozhraní .NET 4.5 nebo novějším. Určete hodnotu Version45 nebo vyšší z výčtu Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - Verze {0} sady Visual Studio není podporovaná. Zadejte hodnotu z výčtu Microsoft.Build.Utilities.VisualStudioVersion. + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. diff --git a/src/Framework/Resources/xlf/SR.de.xlf b/src/Framework/Resources/xlf/SR.de.xlf index b16983f95a3..0d09ef86aef 100644 --- a/src/Framework/Resources/xlf/SR.de.xlf +++ b/src/Framework/Resources/xlf/SR.de.xlf @@ -59,47 +59,47 @@ The string "{0}" cannot be converted to a boolean (true/false) value. - Die Zeichenfolge "{0}" kann nicht in einen booleschen Wert (true/false) konvertiert werden. + The string "{0}" cannot be converted to a boolean (true/false) value. This collection is read-only. - Diese Sammlung ist schreibgeschützt. + This collection is read-only. When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - Fehler beim Versuch, einen Referenzassemblypfad aus dem Pfad "{0}" und dem Frameworkmoniker "{1}" zu generieren. {2} + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. - Der für Debugprotokolle verwendete Pfad "{0}" ist zu lang. Legen Sie den Wert mithilfe der Umgebungsvariablen MSBUILDDEBUGPATH auf einen kürzeren Wert fest, oder ändern Sie die Systemkonfiguration so, dass lange Pfade zulässig sind. + The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - Fehler beim Erstellen einer temporären Datei. Der Ordner für temporäre Dateien ist voll, oder der Pfad ist falsch. {0} + Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - Eine Ausnahme ist beim Erweitern einer fileSpec mit Globs aufgetreten: fileSpec: „{0}“, angenommen, es handelt sich um einen Dateinamen. Ausnahme: {1} + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - Das Element "{0}" enthält das {1}-Attribut mit dem Wert "{2}", der nicht in "{3}" konvertiert werden konnte. + Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Die %({0})-Elementmetadaten können nicht auf den Pfad "{1}" angewendet werden. {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. The parameter '{0}' can only be a file name and cannot include a directory. - Der Parameter '{0}' kann nur ein Dateiname sein und darf kein Verzeichnis enthalten. + The parameter '{0}' can only be a file name and cannot include a directory. @@ -109,22 +109,22 @@ Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Der Pfad "{0}" überschreitet das maximale Pfadlimit des Betriebssystems. Der vollqualifizierte Dateiname muss weniger als {1} Zeichen umfassen. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - Die .NET Framework-Version "{0}" wird nicht unterstützt. Geben Sie einen Wert aus der Enumeration "Microsoft.Build.Utilities.TargetDotNetFrameworkVersion" an. + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - .NET Framework, Version "{0}" wird nicht unterstützt, wenn das Windows SDK das explizite Ziel ist, da dies nur unter .NET 4.5 und höher unterstützt wird. Geben Sie einen Wert aus der Enumeration "Microsoft.Build.Utilities.TargetDotNetFrameworkVersion", Version45 oder höher an. + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - Visual Studio-Version "{0}" wird nicht unterstützt. Geben Sie einen Wert aus der Enumeration "Microsoft.Build.Utilities.VisualStudioVersion" an. + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. diff --git a/src/Framework/Resources/xlf/SR.es.xlf b/src/Framework/Resources/xlf/SR.es.xlf index e8fdc990dcc..a397b2396cb 100644 --- a/src/Framework/Resources/xlf/SR.es.xlf +++ b/src/Framework/Resources/xlf/SR.es.xlf @@ -59,47 +59,47 @@ The string "{0}" cannot be converted to a boolean (true/false) value. - La cadena "{0}" no puede convertirse en un valor booleano (true/false). + The string "{0}" cannot be converted to a boolean (true/false) value. This collection is read-only. - Esta colección es de solo lectura. + This collection is read-only. When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - Error al intentar generar una ruta de acceso de ensamblado de referencia a partir de la ruta de acceso "{0}" y del moniker "{1}" de la versión de .NET Framework. {2} + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. - La ruta de acceso "{0}" usada para los registros de depuración es demasiado larga. Establézcalo en un valor más corto con la variable de entorno MSBUILDDEBUGPATH o cambie la configuración del sistema para permitir rutas de acceso largas. + The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - No se pudo crear un archivo temporal. La carpeta de archivos temporales está llena o su ruta de acceso es incorrecta. {0} + Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - Se produjo una excepción al expandir un fileSpec con globs: fileSpec: "{0}"; suponiendo que es un nombre de archivo. Excepción: {1} + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - El elemento "{0}" tiene el atributo "{1}" con el valor "{2}" que no se pudo convertir a "{3}". + Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Los metadatos "%({0})" del elemento no pueden aplicarse a la ruta de acceso "{1}". {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. The parameter '{0}' can only be a file name and cannot include a directory. - El parámetro "{0}" solo puede ser el nombre de un archivo y no puede incluir un directorio. + The parameter '{0}' can only be a file name and cannot include a directory. @@ -109,22 +109,22 @@ Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - La ruta de acceso {0} supera el límite máximo para la ruta de acceso del sistema operativo. El nombre de archivo completo debe ser inferior a {1} caracteres. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - La versión "{0}" no es compatible. Especifique un valor de la enumeración Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - La versión "{0}" de .NET Framework no es compatible cuando se establece de forma explícita Windows SDK como destino, que solo se admite en .NET 4.5 y posterior. Especifique un valor de la enumeración Microsoft.Build.Utilities.TargetDotNetFrameworkVersion que sea Version45 o posterior. + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - La versión "{0}" de Visual Studio no es compatible. Especifique un valor de la enumeración Microsoft.Build.Utilities.VisualStudioVersion. + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. diff --git a/src/Framework/Resources/xlf/SR.fr.xlf b/src/Framework/Resources/xlf/SR.fr.xlf index 5cb761031a6..2d979a92c4a 100644 --- a/src/Framework/Resources/xlf/SR.fr.xlf +++ b/src/Framework/Resources/xlf/SR.fr.xlf @@ -59,47 +59,47 @@ The string "{0}" cannot be converted to a boolean (true/false) value. - Impossible de convertir la chaîne "{0}" en valeur booléenne (true/false). + The string "{0}" cannot be converted to a boolean (true/false) value. This collection is read-only. - Cette collection est en lecture seule. + This collection is read-only. When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - Une erreur s'est produite lors de la tentative de génération d'un chemin d'assembly de référence à partir du chemin d'accès "{0}" et du moniker du Framework "{1}". {2} + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. - Le chemin d’accès « {0} » utilisé pour les journaux de débogage est trop long. Définissez-la sur une valeur plus courte à l’aide de la variable d’environnement MSBUILDDEBUGPATH ou modifiez votre configuration système pour autoriser les chemins longs. + The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - Échec de la création d’un fichier temporaire. Le dossier de fichiers temporaires est plein ou son chemin est incorrect. {0} + Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - Une exception s’est produite lors du développement d’un fileSpec avec globs: fileSpec: '{0}', en supposant qu’il s’agit d’un nom de fichier. Exception : {1} + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - L'élément "{0}" a l'attribut "{1}" avec la valeur "{2}", qui n'a pas pu être convertie en "{3}". + Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Impossible d'appliquer la métadonnée d'élément "%({0})" au chemin d'accès "{1}". {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. The parameter '{0}' can only be a file name and cannot include a directory. - Le paramètre "{0}" peut uniquement être un nom de fichier et ne peut pas inclure de répertoire. + The parameter '{0}' can only be a file name and cannot include a directory. @@ -109,22 +109,22 @@ Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Le chemin {0} dépasse la limite maximale de chemin du système d'exploitation. Le nom du fichier qualifié complet doit contenir moins de {1} caractères. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - La version "{0}" de .NET Framework n'est pas prise en charge. Spécifiez une valeur de l'énumération Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - La version "{0}" de .NET Framework n'est pas prise en charge lors du ciblage explicite du SDK Windows, qui est pris en charge uniquement par .NET 4.5 et ultérieur. Spécifiez une valeur de l'énumération Microsoft.Build.Utilities.TargetDotNetFrameworkVersion correspondant à la version 4.5 (Version45) ou ultérieure. + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - La version "{0}" de Visual Studio n'est pas prise en charge. Spécifiez une valeur de l'énumération Microsoft.Build.Utilities.VisualStudioVersion. + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. diff --git a/src/Framework/Resources/xlf/SR.it.xlf b/src/Framework/Resources/xlf/SR.it.xlf index 6ebb060c611..1ddb97f680d 100644 --- a/src/Framework/Resources/xlf/SR.it.xlf +++ b/src/Framework/Resources/xlf/SR.it.xlf @@ -59,47 +59,47 @@ The string "{0}" cannot be converted to a boolean (true/false) value. - Non è possibile convertire la stringa "{0}" in un valore booleano (true/false). + The string "{0}" cannot be converted to a boolean (true/false) value. This collection is read-only. - Raccolta di sola lettura. + This collection is read-only. When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - Si è verificato un errore durante il tentativo di generare un percorso dell'assembly di riferimento dal "{0}" e dal moniker del framework "{1}". {2} + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. - Il percorso "{0}" usato per i log di debug è troppo lungo. Impostarlo su un valore più breve usando la variabile dell'ambiente MSBUILDDEBUGPATH o modificare la configurazione del sistema per consentire percorsi lunghi. + The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - Non è stato possibile creare un file temporaneo. La cartella dei file temporanei è piena oppure il percorso è errato. {0} + Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - Si è verificata un'eccezione durante l'espansione di un fileSpec con GLOBS: fileSpec: "{0}", presupponendo che si tratti di un nome di file. Eccezione: {1} + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - L'elemento "{0}" include l'attributo "{1}" con il valore "{2}" che non è stato possibile convertire in "{3}". + Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Non è possibile applicare i metadati dell'elemento "%({0})" al percorso "{1}". {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. The parameter '{0}' can only be a file name and cannot include a directory. - Il parametro '{0}' può solo essere un nome file e non può includere una directory. + The parameter '{0}' can only be a file name and cannot include a directory. @@ -109,22 +109,22 @@ Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Il percorso {0} supera il limite massimo dei percorsi del sistema operativo. Il nome completo del file deve essere composto da meno di {1}. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - La versione "{0}" di .NET Framework non è supportata. Specificare un valore dall'enumerazione Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - La versione "{0}" di .NET Framework non è supportata se è destinata in modo esplicito a Windows SDK, che è supportato solo da .NET 4.5 e versioni successive. Specificare un valore dell'enumerazione Microsoft.Build.Utilities.TargetDotNetFrameworkVersion che sia Version45 o successivo. + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - La versione "{0}" di Visual Studio non è supportata. Specificare un valore dall'enumerazione Microsoft.Build.Utilities.VisualStudioVersion. + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. diff --git a/src/Framework/Resources/xlf/SR.ja.xlf b/src/Framework/Resources/xlf/SR.ja.xlf index 800dbc3f2cd..61b234b461a 100644 --- a/src/Framework/Resources/xlf/SR.ja.xlf +++ b/src/Framework/Resources/xlf/SR.ja.xlf @@ -59,47 +59,47 @@ The string "{0}" cannot be converted to a boolean (true/false) value. - 文字列 "{0}" をブール値 (true/false) に変換することはできません。 + The string "{0}" cannot be converted to a boolean (true/false) value. This collection is read-only. - このコレクションは読み取り専用です。 + This collection is read-only. When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - 参照アセンブリ パスをパス "{0}" とフレームワーク モニカー "{1}" から生成しようとしたときに、エラーが発生しました。{2} + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. - デバッグ ログに使用されるパス "{0}" が長すぎます。MSBUILDDEBUGPATH 環境変数を使用して短い値に設定するか、長いパスを許可するようにシステム構成を変更してください。 + The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - 一時ファイルを作成できませんでした。一時ファイル フォルダーがいっぱいであるか、またはそのパスが正しくありません。{0} + Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - glob を使用して fileSpec を展開中に例外が発生しました: fileSpec: "{0}"、これはファイル名であると仮定します。例外: {1} + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - 項目 "{0}" は、"{3}" に変換できなかった値 "{2}" を伴う属性 "{1}" を含んでいます。 + Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". The item metadata "%({0})" cannot be applied to the path "{1}". {2} - 項目メタデータ "%({0})" をパス "{1}" に適用できません。{2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. The parameter '{0}' can only be a file name and cannot include a directory. - パラメーター '{0}' に使用できるのはファイル名のみで、ディレクトリを含めることはできません。 + The parameter '{0}' can only be a file name and cannot include a directory. @@ -109,22 +109,22 @@ Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - パス: {0} は OS のパスの上限を越えています。完全修飾のファイル名は {1} 文字以下にする必要があります。 + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - .NET Framework のバージョン "{0}" はサポートされていません。列挙 Microsoft.Build.Utilities.TargetDotNetFrameworkVersion から値を指定してください。 + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - Windows SDK を明示的にターゲットとする場合、.NET Framework のバージョン "{0}" はサポートされません。Windows SDK は、.NET 4.5 以降でのみサポートされています。列挙 Microsoft.Build.Utilities.TargetDotNetFrameworkVersion から Version45 以上の値を指定してください。 + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - Visual Studio のバージョン "{0}" はサポートされていません。列挙 Microsoft.Build.Utilities.VisualStudioVersion から値を指定してください。 + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. diff --git a/src/Framework/Resources/xlf/SR.ko.xlf b/src/Framework/Resources/xlf/SR.ko.xlf index f16d86f8415..857e3a4cb69 100644 --- a/src/Framework/Resources/xlf/SR.ko.xlf +++ b/src/Framework/Resources/xlf/SR.ko.xlf @@ -59,47 +59,47 @@ The string "{0}" cannot be converted to a boolean (true/false) value. - "{0}" 문자열을 부울 값(true/false)으로 변환할 수 없습니다. + The string "{0}" cannot be converted to a boolean (true/false) value. This collection is read-only. - 이 컬렉션은 읽기 전용입니다. + This collection is read-only. When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - "{0}" 경로 및 프레임워크 모니커 "{1}"에서 참조 어셈블리 경로를 생성하는 동안 오류가 발생했습니다. {2} + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. - 디버그 로그에 사용된 경로 "{0}"이(가) 너무 깁니다. MSBUILDDEBUGPATH 환경 변수를 사용하여 값을 더 짧게 설정하거나 긴 경로를 허용하도록 시스템 구성을 변경합니다. + The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - 임시 파일을 만들지 못했습니다. 임시 파일 폴더가 꽉 찼거나 경로가 올바르지 않습니다. {0} + Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - glob를 사용하여 fileSpec을 확장하는 동안 예외가 발생했습니다. fileSpec: "{0}", 파일 이름이라고 가정합니다. 예외: {1} + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - "{0}" 항목에 "{3}"(으)로 변환할 수 없는 "{2}" 값이 있는 "{1}" 특성이 있습니다. + Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". The item metadata "%({0})" cannot be applied to the path "{1}". {2} - 항목 메타데이터 "%({0})"을(를) "{1}" 경로에 적용할 수 없습니다. {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. The parameter '{0}' can only be a file name and cannot include a directory. - '{0}' 매개 변수는 파일 이름일 수만 있으며 디렉터리를 포함할 수 없습니다. + The parameter '{0}' can only be a file name and cannot include a directory. @@ -109,22 +109,22 @@ Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - 경로: {0}은(는) OS 최대 경로 제한을 초과합니다. 정규화된 파일 이름은 {1}자 이하여야 합니다. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - .NET Framework 버전 "{0}"이(가) 지원되지 않습니다. Microsoft.Build.Utilities.TargetDotNetFrameworkVersion 열거형에서 값을 지정하세요. + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - .NET 4.5 이상에서만 지원되는 Windows SDK를 명시적으로 대상으로 지정하는 경우 .NET Framework 버전 "{0}"이(가) 지원되지 않습니다. Microsoft.Build.Utilities.TargetDotNetFrameworkVersion 열거형에서 Version45 이상인 값을 지정하세요. + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - Visual Studio 버전 "{0}"이(가) 지원되지 않습니다. Microsoft.Build.Utilities.VisualStudioVersion 열거형에서 값을 지정하세요. + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. diff --git a/src/Framework/Resources/xlf/SR.pl.xlf b/src/Framework/Resources/xlf/SR.pl.xlf index 8ab65f78025..9c79b728fca 100644 --- a/src/Framework/Resources/xlf/SR.pl.xlf +++ b/src/Framework/Resources/xlf/SR.pl.xlf @@ -59,47 +59,47 @@ The string "{0}" cannot be converted to a boolean (true/false) value. - Ciągu „{0}” nie można przekonwertować na wartość logiczną (prawda/fałsz). + The string "{0}" cannot be converted to a boolean (true/false) value. This collection is read-only. - Ta kolekcja jest tylko do odczytu. + This collection is read-only. When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - Wystąpił błąd podczas próby wygenerowania ścieżki zestawu odwołania ze ścieżki „{0}” i monikera struktury „{1}”. {2} + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. - Ścieżka „{0}” używana w dziennikach debugowania jest za długa. Ustaw ją na krótszą wartość przy użyciu zmiennej środowiskowej MSBUILDEBUGPATH lub zmień konfigurację systemu, aby zezwolić na długie ścieżki. + The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - Nie można utworzyć pliku tymczasowego. Folder plików tymczasowych jest zapełniony lub jego ścieżka jest niepoprawna. {0} + Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - Wystąpił wyjątek podczas rozwijania elementu fileSpec za pomocą globów: fileSpec: „{0}”, przy założeniu, że jest to nazwa pliku. Wyjątek: {1} + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - Element „{0}” ma atrybut „{1}” o wartości „{2}”, którego nie można przekonwertować na „{3}”. + Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Elementu metadanych „%({0})” nie można zastosować do ścieżki „{1}”. {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. The parameter '{0}' can only be a file name and cannot include a directory. - Parametr „{0}” może zawierać tylko nazwę pliku i nie może zawierać katalogu. + The parameter '{0}' can only be a file name and cannot include a directory. @@ -109,22 +109,22 @@ Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Ścieżka: {0} przekracza limit maksymalnej długości ścieżki w systemie operacyjnym. W pełni kwalifikowana nazwa pliku musi się składać z mniej niż {1} znaków. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - Program .NET Framework w wersji „{0}” nie jest obsługiwany. Podaj wartość z wyliczenia Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - Program .NET Framework w wersji „{0}” nie jest obsługiwany, jeśli jawnym obiektem docelowym jest zestaw SDK systemu Windows, ponieważ taki zestaw jest obsługiwany tylko na platformie .NET w wersji 4.5 lub nowszej. Podaj wartość z wyliczenia Microsoft.Build.Utilities.TargetDotNetFrameworkVersion, która wynosi co najmniej Version45. + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - Program Visual Studio w wersji „{0}” nie jest obsługiwany. Podaj wartość z wyliczenia Microsoft.Build.Utilities.VisualStudioVersion. + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. diff --git a/src/Framework/Resources/xlf/SR.pt-BR.xlf b/src/Framework/Resources/xlf/SR.pt-BR.xlf index d0265d397b2..94d23654293 100644 --- a/src/Framework/Resources/xlf/SR.pt-BR.xlf +++ b/src/Framework/Resources/xlf/SR.pt-BR.xlf @@ -59,47 +59,47 @@ The string "{0}" cannot be converted to a boolean (true/false) value. - A cadeia de caracteres "{0}" não pode ser convertida em um valor booliano (true/false). + The string "{0}" cannot be converted to a boolean (true/false) value. This collection is read-only. - Esta coleção é somente leitura. + This collection is read-only. When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - Erro ao tentar gerar um caminho de assembly de referência no caminho "{0}" e o moniker de estrutura "{1}". {2} + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. - O caminho "{0}" usado para logs de depuração é muito longo. Defina-o para um valor mais curto usando a variável de ambiente MSBUILDDEBUGPATH ou altere a configuração do sistema para permitir caminhos longos. + The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - Falha ao criar um arquivo temporário. A pasta de arquivos temporários está cheia ou o caminho está incorreto. {0} + Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - Ocorreu uma exceção ao expandir um fileSpec com globs: fileSpec: "{0}", assumindo que se trata de um nome de arquivo. Exceção: {1} + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - O item "{0}" tem atributo "{1}" com valor "{2}" que não pôde ser convertido para "{3}". + Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Os metadados do item "%({0})" não podem ser aplicados ao caminho "{1}". {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. The parameter '{0}' can only be a file name and cannot include a directory. - O parâmetro '{0}' pode ser somente um nome de arquivo e não pode incluir um diretório. + The parameter '{0}' can only be a file name and cannot include a directory. @@ -109,22 +109,22 @@ Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Caminho: {0} excede o limite máximo do caminho do SO. O nome do arquivo totalmente qualificado deve ter menos de {1} caracteres. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - Não há suporte para a versão "{0}" do .NET Framework. Especifique um valor da enumeração Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - Não há suporte para a versão "{0}" do .NET Framework quando o destino for explicitamente o SDK do Windows, que só tem suporte no .NET 4.5 e posterior. Especifique um valor da enumeração Microsoft.Build.Utilities.TargetDotNetFrameworkVersion que seja Version45 ou acima. + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - O Visual Studio versão "{0}" não tem suporte. Especifique um valor da enumeração Microsoft.Build.Utilities.VisualStudioVersion. + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. diff --git a/src/Framework/Resources/xlf/SR.ru.xlf b/src/Framework/Resources/xlf/SR.ru.xlf index 9a075bf2564..559bd661159 100644 --- a/src/Framework/Resources/xlf/SR.ru.xlf +++ b/src/Framework/Resources/xlf/SR.ru.xlf @@ -59,47 +59,47 @@ The string "{0}" cannot be converted to a boolean (true/false) value. - Строка "{0}" не может быть преобразована в логическое значение (истина/ложь). + The string "{0}" cannot be converted to a boolean (true/false) value. This collection is read-only. - Эта коллекция доступна только для чтения. + This collection is read-only. When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - Ошибка при попытке создать ссылочный путь к сборке из пути "{0}" и моникер инфраструктуры "{1}". {2} + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. - Путь "{0}", используемый для журналов отладки, слишком длинный. Установите более короткое значение, используя переменную среду MSBUILDDEBUGPATH, или измените конфигурацию системы, чтобы разрешить длинные пути. + The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - Не удалось создать временный файл. Папка временных файлов переполнена, или указан неверный путь. {0} + Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - Возникло исключение при расширении fileSpec со стандартными масками: fileSpec: "{0}", предполагая, что это имя файла. Исключение: {1} + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - У элемента "{0}" имеется атрибут "{1}" со значением "{2}", который не удалось преобразовать в "{3}". + Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Не удается применить метаданные элемента "%({0})" к пути "{1}". {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. The parameter '{0}' can only be a file name and cannot include a directory. - Параметр "{0}" может быть только именем файла и не может включать в себя каталог. + The parameter '{0}' can only be a file name and cannot include a directory. @@ -109,22 +109,22 @@ Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Длина пути {0} превышает максимально допустимую в ОС. Символов в полном имени файла должно быть не больше {1}. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - .NET Framework версии "{0}" не поддерживается. Укажите значение из перечисления Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - При явном использовании пакета Windows SDK платформа .NET Framework версии "{0}" не поддерживается; она поддерживается только платформой .NET 4.5 и более поздними версиями. Укажите значение из перечисления Microsoft.Build.Utilities.TargetDotNetFrameworkVersion версии Version45 или более поздней. + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - Visual Studio версии "{0}" не поддерживается. Укажите значение из перечисления Microsoft.Build.Utilities.VisualStudioVersion. + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. diff --git a/src/Framework/Resources/xlf/SR.tr.xlf b/src/Framework/Resources/xlf/SR.tr.xlf index 69d567ac46f..cd1c5184bcc 100644 --- a/src/Framework/Resources/xlf/SR.tr.xlf +++ b/src/Framework/Resources/xlf/SR.tr.xlf @@ -59,47 +59,47 @@ The string "{0}" cannot be converted to a boolean (true/false) value. - "{0}" dizesi bir boole (doğru/yanlış) değerine dönüştürülemiyor. + The string "{0}" cannot be converted to a boolean (true/false) value. This collection is read-only. - Bu koleksiyon salt okunur. + This collection is read-only. When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - "{0}" yolundan ve "{1}" framework adından bir başvuru bütünleştirilmiş kod yolu oluşturmaya çalışılırken bir hata oluştu. {2} + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. - Hata ayıklama günlükleri için kullanılan "{0}" yolu çok uzun. MSBUILDDEBUGPATH ortam değişkenini kullanarak yolu daha kısa bir değere ayarlayın veya sistem yapılandırmanızı uzun yollara izin verecek şekilde değiştirin. + The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - Geçici bir dosya oluşturulamadı. Geçici dosyalar klasörü dolu veya yolu hatalı. {0} + Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - globs: fileSpec: "{0}" ile bir fileSpec genişletilirken özel bir durum oluştu, bunun bir dosya adı olduğu varsayıldı. Özel Durum: {1} + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - "{0}" öğesinin, "{3}" değerine dönüştürülemeyen "{2}" değerine sahip "{1}" özniteliği var. + Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". The item metadata "%({0})" cannot be applied to the path "{1}". {2} - "%({0})" öğe meta verisi "{1}" yoluna uygulanamıyor. {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. The parameter '{0}' can only be a file name and cannot include a directory. - '{0}' yalnızca bir dosya adı olabilir ve dizin içeremez. + The parameter '{0}' can only be a file name and cannot include a directory. @@ -109,22 +109,22 @@ Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Yol: {0}, işletim sisteminin en yüksek yol sınırını aşıyor. Tam dosya adı en fazla {1} karakter olmalıdır. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - .NET Framework "{0}" sürümü desteklenmiyor. Lütfen Microsoft.Build.Utilities.TargetDotNetFrameworkVersion sabit listesinden bir değer belirtin. + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - Yalnızca .NET 4.5 ve sonraki sürümlerde desteklenen Windows SDK açıkça hedeflenirken .NET Framework "{0}" sürümü desteklenmez. Lütfen Microsoft.Build.Utilities.TargetDotNetFrameworkVersion sabit listesinden Sürüm 45 veya üzerinde bir değer belirtin. + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - Visual Studio "{0}" sürümü desteklenmiyor. Lütfen Microsoft.Build.Utilities.VisualStudioVersion sabit listesinden bir değer belirtin. + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. diff --git a/src/Framework/Resources/xlf/SR.zh-Hans.xlf b/src/Framework/Resources/xlf/SR.zh-Hans.xlf index b1b11c53f40..ae6f885b622 100644 --- a/src/Framework/Resources/xlf/SR.zh-Hans.xlf +++ b/src/Framework/Resources/xlf/SR.zh-Hans.xlf @@ -59,47 +59,47 @@ The string "{0}" cannot be converted to a boolean (true/false) value. - 无法将字符串“{0}”转换为布尔值(true/false)。 + The string "{0}" cannot be converted to a boolean (true/false) value. This collection is read-only. - 此集合是只读的。 + This collection is read-only. When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - 尝试从路径“{0}”和框架名字对象“{1}”生成引用程序集路径时出错。{2} + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. - 用于调试日志的路径 "{0}" 太长。使用 MSBUILDDEBUGPATH 环境变量将其设置为较短值，或更改系统配置以允许长路径。 + The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - 未能创建临时文件。临时文件文件夹已满或其路径不正确。{0} + Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - 使用 glob 展开 fileSpec 时发生异常: fileSpec:“{0}”，系统假定它是文件名。异常: {1} + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - 项“{0}”具有值为“{2}”的特性“{1}”，该值未能转换为“{3}”。 + Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". The item metadata "%({0})" cannot be applied to the path "{1}". {2} - 无法将项元数据“%({0})”应用于路径“{1}”。{2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. The parameter '{0}' can only be a file name and cannot include a directory. - 参数“{0}”只能是文件名，不能包含目录。 + The parameter '{0}' can only be a file name and cannot include a directory. @@ -109,22 +109,22 @@ Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - 路径: {0} 超过 OS 最大路径限制。完全限定的文件名必须少于 {1} 个字符。 + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - 不支持 .NET Framework 版本“{0}”。请指定枚举 Microsoft.Build.Utilities.TargetDotNetFrameworkVersion 中的某个值。 + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - 当明确以 Windows SDK 为目标时，不支持 .NET Framework 版本“{0}”，Windows SDK 只在 .NET 4.5 及更高版本上受支持。请指定枚举 Microsoft.Build.Utilities.TargetDotNetFrameworkVersion 中 Version45 或以上的值。 + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - 不支持 Visual Studio 版本“{0}”。请指定枚举 Microsoft.Build.Utilities.VisualStudioVersion 中的某个值。 + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. diff --git a/src/Framework/Resources/xlf/SR.zh-Hant.xlf b/src/Framework/Resources/xlf/SR.zh-Hant.xlf index 99900aefdef..fe6055d15dd 100644 --- a/src/Framework/Resources/xlf/SR.zh-Hant.xlf +++ b/src/Framework/Resources/xlf/SR.zh-Hant.xlf @@ -59,47 +59,47 @@ The string "{0}" cannot be converted to a boolean (true/false) value. - 無法將字串 "{0}" 轉換成布林值 (true/false)。 + The string "{0}" cannot be converted to a boolean (true/false) value. This collection is read-only. - 這是一個唯讀集合。 + This collection is read-only. When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - 嘗試從路徑 "{0}" 和架構 Moniker "{1}" 產生參考組件路徑時，發生錯誤。{2} + When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. - 用於偵錯記錄檔 "{0}" 的路徑太長。使用 MSBUILDDEBUGPATH 環境變數將它設定為較短的值，或變更您的系統設定以允許長路徑。 + The path "{0}" used for debug logs is too long. Set it to a shorter value using the MSBUILDDEBUGPATH environment variable or change your system configuration to allow long paths. Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - 無法建立暫存檔案。暫存檔案資料夾已滿或其路徑錯誤。{0} + Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} - 展開具有 glob 的 fileSpec 時發生例外狀況: fileSpec: "{0}" (假設它是檔案名稱)。例外狀況: {1} + An exception occurred while expanding a fileSpec with globs: fileSpec: "{0}", assuming it is a file name. Exception: {1} Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - 項目 "{0}" 的屬性 "{1}" 的值為 "{2}"，不能轉換為 "{3}"。 + Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". The item metadata "%({0})" cannot be applied to the path "{1}". {2} - 無法將項目中繼資料 "%({0})" 套用至路徑 "{1}"。{2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. The parameter '{0}' can only be a file name and cannot include a directory. - 參數 '{0}' 只可以是檔案名稱，不得包含目錄。 + The parameter '{0}' can only be a file name and cannot include a directory. @@ -109,22 +109,22 @@ Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - 路徑: {0} 超過 OS 路徑上限。完整檔案名稱必須少於 {1} 個字元。 + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - 不支援 .NET Framework 版本 "{0}"。請從列舉 Microsoft.Build.Utilities.TargetDotNetFrameworkVersion 中指定值。 + .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - 明確地以 Windows SDK 為目標時，不支援 .NET Framework 版本 "{0}"，只有 .NET 4.5 及更新版本才予以支援。請從 Version45 (含) 以上版本的列舉 Microsoft.Build.Utilities.TargetDotNetFrameworkVersion 中指定值。 + .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - 不支援 Visual Studio 版本 "{0}"。請從列舉 Microsoft.Build.Utilities.VisualStudioVersion 中指定值。 + Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. diff --git a/src/MSBuild/Resources/xlf/Strings.cs.xlf b/src/MSBuild/Resources/xlf/Strings.cs.xlf index b2b3beb0547..e84f28796ba 100644 --- a/src/MSBuild/Resources/xlf/Strings.cs.xlf +++ b/src/MSBuild/Resources/xlf/Strings.cs.xlf @@ -296,7 +296,7 @@ of the build. For more info see https://aka.ms/buildcheck -check - Povolí během sestavování BuildChecks. + Povolí během sestavení BuildChecks. BuildCheck umožňuje vyhodnocovat pravidla, aby se zajistily vlastnosti sestavení. Další informace najdete na https://aka.ms/buildcheck @@ -803,20 +803,17 @@ 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 - -logger:<protok_nást> 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 <protok_nást>: - [<třída_protok_nást>,]<sestavení_protok_nást> - [;<param_protok_nást>] - Syntaxe hodnoty <třída_protok_nást>: - [<část/úpl_obor_názvů>.]<náz_tř_protok_nást> - Syntaxe hodnoty <sestavení_protok_nást>: - {<název_sestavení>[,<strong name>] | <soubor_sestavení>} + -logger:<logger> 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 <logger> je: + [<class>,]<assembly>[,<options>][;<parameters>] + Syntaxe hodnoty <logger class> je: + [<partial or full namespace>.]<logger class name> + Syntaxe hodnoty <logger assembly> je: + {<assembly name>[,<strong name>] | <assembly file>} Parametry protokolovacího nástroje určují, jak MSBuild vytvoří protokolovací nástroj. - Parametry <param_protok_nást> 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 <logger parameters> 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 @@ -1079,23 +1076,20 @@ 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 - -distributedlogger:<centr_protok_nást>*<předáv_protok_nást> - 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ě. + -distributedLogger:<central logger>*<forwarding logger> + 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 + protokolovacích nástrojů, uveďte je jednotlivě. (Krátký tvar: -dl) - Syntaxe hodnoty <protok_nást>: - [<třída_protok_nást>,]<sestav_protok_nást> - [;<param_protok_nást>] - Syntaxe hodnoty <třída_protok_nást>: - [<část/úpl_obor_názvů>.]<náz_tř_protok_nást> - Syntaxe hodnoty <sestav_protok_nást>: - {<název_sestavení>[,<strong name>] | <soubor_sestavení>} + Syntaxe hodnoty <logger> je: + [<class>,]<assembly>[,<options>][;<parameters>] + Syntaxe hodnoty <logger class> je: + [<partial or full namespace>.]<logger class name> + Syntaxe hodnoty <logger assembly> je: + {<assembly name>[,<strong name>] | <assembly file>} Parametry protokolovacího nástroje určují, jak MSBuild vytvoří protokolovací nástroj. Parametry <param_protok_nást> 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 @@ -1283,7 +1277,7 @@ Když se nastaví na MessageUponIsolationViolation (nebo jeho krátký Verbosity=diagnostic;Encoding=UTF-8 -flp:Summary;Verbosity=minimal;LogFile=msbuild.sum - -flp1:warningsonly;logfile=msbuild.wrn + -flp1:warningsonly;logfile=msbuild.wrn -flp2:errorsonly;logfile=msbuild.err @@ -2134,17 +2128,17 @@ Když se nastaví na MessageUponIsolationViolation (nebo jeho krátký souborů, ke kterým došlo během sestavení. Nepovinný přepínač ProjectImports řídí toto chování: - ProjectImports=None – Neshromažďovat importy projektu + ProjectImports=None – neshromažďovat importy projektu . - ProjectImports=Embed – Vložit importy projektu do + ProjectImports=Embed – vložit importy projektu do souboru protokolu. - ProjectImports=ZipFile – Uložit soubory projektu do + ProjectImports=ZipFile – uložit soubory projektu do output.projectimports.zip kde výstup má stejný název jako je název binárního souboru protokolu. Výchozí nastavení pro ProjectImports je Embed. - Poznámka: protokolovací nástroj neshromažďuje zdrojové soubory, které nepocházejí z nástroje MSBuild, + Poznámka: Protokolovací nástroj neshromažďuje zdrojové soubory, které nepocházejí z nástroje MSBuild, jako například .cs, .cpp atd. Soubor .binlog se dá přehrát předáním do diff --git a/src/MSBuild/Resources/xlf/Strings.de.xlf b/src/MSBuild/Resources/xlf/Strings.de.xlf index d7d66ea6ca4..433a72df8a9 100644 --- a/src/MSBuild/Resources/xlf/Strings.de.xlf +++ b/src/MSBuild/Resources/xlf/Strings.de.xlf @@ -66,12 +66,11 @@ This flag is experimental and may not work as intended. - -reportFileAccesses[:True|Falsch] - Führt dazu, dass MSBuild Dateizugriffe an alle konfigurierten - meldet - Projektcache-Plug-Ins. + -reportFileAccesses[:True|False] + Führt dazu, dass MSBuild Dateizugriffe auf ein beliebiges konfiguriertes + Projektcache-Plug-In meldet. - Dieses Kennzeichen ist experimentell und funktioniert möglicherweise nicht wie vorgesehen. + Dieses Flag ist experimentell und funktioniert möglicherweise nicht wie vorgesehen. LOCALIZATION: "-reportFileAccesses" should not be localized. @@ -122,7 +121,7 @@ the specified targets will be executed. -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. @@ -150,15 +149,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) @@ -180,15 +179,15 @@ (Short form: -tl) -terminalLogger[:auto,on,off] - Aktiviert oder deaktiviert die Terminalprotokollierung. Terminal-Logger + Aktiviert oder deaktiviert die Terminalprotokollierung. Terminalprotokollierung 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 den Terminal-Logger nur zu verwenden, wenn die - Standardausgabe nicht umgeleitet wird. Analysieren Sie die Ausgabe nicht + ohne Argumente), um die Terminalprotokollierung 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 - später verfügbar. + höher verfügbar. (Kurzform: -tl) @@ -217,19 +216,19 @@ -tlp:default=auto;verbosity=diag;shownCommandLine -terminalLoggerParameters: <parameters> - Parameter für Terminal-Logger. (Kurzform: -tlp) + Parameter für die Terminalprotokollierung. (Kurzform: -tlp) Die verfügbaren Parameter. - default: Gibt das Standardverhalten des Terminal- - Loggers an. Erfordert einen der folgenden Werte: + default: Gibt das Standardverhalten der + Terminalprotokollierung an. Erfordert einen der folgenden Werte: – "on", "true" erzwingt die Verwendung von TerminalLogger, auch - wenn er deaktiviert werden sollte. + bei einer Deaktivierung. – "off", "true" erzwingt die Nichtverwendung von TerminalLogger, auch - wenn er aktiviert werden sollte. + bei einer Aktivierung. – "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 diesen - Logger + verbosity: Überschreiben Sie die Einstellung "-verbosity" für diese + Protokollierung showCommandLine: TaskCommandLineEvent-Meldungen anzeigen Beispiel: @@ -297,7 +296,7 @@ -check Aktiviert BuildChecks während des Builds. - BuildCheck ermöglicht die Regelauswertung, um Eigenschaften + BuildCheck ermöglicht die Regelauswertung, um Eigenschaften des Builds sicherzustellen. Weitere Informationen finden Sie unter https://aka.ms/buildcheck @@ -802,11 +801,11 @@ Dies ist ein restriktiverer Modus von MSBuild, da er erfordert, -logger:<Protokollierung> Mithilfe dieser Protokollierung werden Ereignisse von MSBuild protokolliert. Um mehrere Protokollierungen anzugeben, wird jede Protokollierung gesondert angegeben. Die Syntax für die <Protokollierung> lautet: - [<Klasse>,]<Assembly>[,<Optionen>][;<Parameter>] + [<Klasse>,]<assembly>[,<Optionen>][;<Parameter>] Die Syntax für die <Protokollierungsklasse> lautet: [<Teilweiser oder vollständiger Namespace>.]<Name der Protokollierungsklasse> Die Syntax für die <Protokollierungsassembly> lautet: - {<Assemblyname>[,<strong name>] | <Assemblydatei>} + {<assembly name>[,<strong name>] | <assembly file>} Die Protokollierungsoptionen geben an, wie MSBuild die Protokollierung erstellt. Die <Protokollierungsparameter> sind optional und werden genau so an die Protokollierung übergeben, wie sie eingegeben wurden. (Kurzform: -l) @@ -888,38 +887,38 @@ Hinweis: Ausführlichkeit der Dateiprotokollierungen -consoleLoggerParameters:PerformanceSummary;NoSummary; Verbosity=minimal - -consoleLoggerParameters:<Parameter> - Parameter für die Konsolenprotokollierung. (Kurz form: -clp) - Verfügbar sind die Parameter: - PerformanceSummary - In Aufgaben, Zielen und Projekten - aufgewendete Zeit anzeigen. - Summary - Fehler- und Warnungszusammenfassung am Ende anzeigen. - NoSummary - Keine Fehler- und Warnungszusammenfassung am Ende - anzeigen. - ErrorsOnly - Nur Fehler anzeigen. - WarningsOnly - Nur Warnungen anzeigen. - NoItemAndPropertyList - Keine Liste der Elemente und - Eigenschaften am Anfang jedes Projektbuilds anzeigen. - ShowCommandLine - TaskCommandLineEvent-Meldungen anzeigen - ShowTimestamp - Zeitstempel als Präfix für eine beliebige - Meldung anzeigen. - ShowEventId- eventId für begonnene, abgeschlossene - Ereignisse und Meldungen anzeigen - ForceNoAlign - Text wird nicht an der Größe des - Konsolenpuffers ausgerichtet - DisableConsoleColor - Standardkonsolenfarben für alle - Protokollierungsmeldungen anzeigen. - EnableMPLogging - Multiprozessor-Protokollierungsstil aktivieren, - auch wenn er im Nicht-Multiprozessormodus - ausgeführt wird. Dieser Protokollierungsstil ist standardmäßig aktiviert. - ForceConsoleColor - ANSI-Konsolenfarben auch dann verwenden, - wenn die Konsole sie nicht unterstützt - PreferConsoleColor - ANSI-Konsolenfarben nur anzeigen, - wenn die Zielkonsole sie unterstützt - Verbosity - überschreibt die Ausführlichkeitseinstellung für diese - Protokollierung. - Beispiel: - -consoleLoggerParameters:PerformanceSummary;NoSummary; + -consoleLoggerParameters:<parameters> + Parameter für die Konsolenprotokollierung. (Kurzform: -clp) + Folgende Parameter sind verfügbar: + PerformanceSummary: Zeigt die in Aufgaben, Zielen und + Projekten verbrachte Zeit an. + Summary: Zeigt abschließend eine Zusammenfassung der Fehler und Warnungen an. + NoSummary: Zeigt keine Fehler- und Warnungsübersicht am + Ende an. + ErrorsOnly: Zeigt nur Fehler an. + WarningsOnly: Zeigt nur Warnungen an. + NoItemAndPropertyList: Zeigt keine Liste der Elemente + und Eigenschaften am Anfang jeder Projekterstellung an. + ShowCommandLine: Zeigt TaskCommandLineEvent-Meldungen an. + ShowTimestamp: Zeigt den Timestamp als Präfix einer + Meldung an. + ShowEventId: Zeigt die eventId für gestartete + Ereignisse, abgeschlossene Ereignisse und Meldungen an. + ForceNoAlign: Richtet den Text nicht an der Größe des + Konsolenpuffers aus. + DisableConsoleColor: Verwendet die Standardkonsolenfarben + für alle Protokollierungsmeldungen. + EnableMPLogging: Aktiviert die Multiprozessorprotokollierungs + -Stil auch bei Ausführung im nicht-multiprozessorbasierten + Modus. Dieser Protokollierungsstil ist standardmäßig aktiviert. + ANSI-Konsolenfarben, wenn + die Konsole dies nicht unterstützt. + PreferConsoleColor: Verwendet die ANSI-Konsolenfarben nur, wenn + die Zielkonsole dies unterstützt. + Verbosity: Überschreibt die Einstellung für -verbosity für + diese Protokollierung. + Beispiel: + -consoleloggerparameters:PerformanceSummary;NoSummary; Verbosity=minimal @@ -1078,11 +1077,11 @@ Hinweis: Ausführlichkeit der Dateiprotokollierungen gesondert angegeben. (Kurzform -dl) Die Syntax für die <Protokollierung> lautet: - [<Klasse>,]<Assembly>[,<Optionen>][;<Parameter>] + [<Klasse>,]<assembly>[,<Optionen>][;<Parameter>] Die Syntax für die <Protokollierungsklasse> lautet: [<Teilweiser oder vollständiger Namespace>.]<Name der Protokollierungsklasse> Die Syntax für die <Protokollierungsassembly> lautet: - {<Assemblyname>[,<strong name>] | <Assemblydatei>} + {<assembly name>[,<strong name>] | <assembly file>} Die Protokollierungsoptionen geben an, wie MSBuild die Protokollierung erstellt. Die <Protokollierungsparameter> sind optional und werden genau so an die Protokollierung übergeben, wie sie eingegeben wurden. (Kurzform: -l) @@ -1778,12 +1777,12 @@ Hinweis: Ausführlichkeit der Dateiprotokollierungen 1: in enforcement - 1: bei der Erzwingung + 1: bei der Durchsetzung 2: in evaluation. It is recommended to turn off Smart App Control in development environemnt as otherwise performance might be impacted - 2: in Auswertung. Es wird empfohlen, Smart App Control in der Entwicklungsumgebung zu deaktivieren, da andernfalls die Leistung beeinträchtigt werden könnte. + 2: in Auswertung. Es wird empfohlen, Smart App Control in der Entwicklungsumgebung zu deaktivieren, da andernfalls die Leistung beeinträchtigt werden könnte Smart App Control, "VerifiedAndReputablePolicyState" should not be localized @@ -2104,23 +2103,23 @@ Hinweis: Ausführlichkeit der Dateiprotokollierungen Standardmäßig befindet sich die Datei im aktuellen Verzeichnis und hat den Namen „msbuild.binlog“. Das binäre Protokoll ist eine detaillierte Beschreibung des Buildprozesses, der später zum Rekonstruieren von - Textprotokollen dient und der von anderen Analysetools verwendet wird. Detaillierte - Textprotokolle auf Diagnoseebene sind in der Regel 10–20-mal so groß wie - binäre Protokolle, letztere enthalten jedoch mehr Informationen. + Textprotokollen dient und der von anderen Analysetools verwendet wird. Ein binäres Protokoll + ist in der Regel 10-20 mal kleiner als das ausführlichste + Text-Protokoll auf Diagnoseebene, enthält aber weitere Informationen. (Kurzform: -bl) Die optionale LogFile gibt den Pfad an, in dem das Binärprotokoll gespeichert wird. Um eine eigene Protokolldatei - für jeden Build zu generieren, kann das Token "{}" zum + für jeden Build zu generieren, kann das Token „{}“ zum Pfad hinzugefügt werden, z. B.: LogFile=output-{}-log.binlog. Jedes - "{}" im Protokollpfad wird durch eine eindeutige Zeichenfolge ersetzt, + „{}“ im Protokollpfad wird durch eine eindeutige Zeichenfolge ersetzt, indem Zeitstempel, ID des ausgeführten Prozesses und ein zufälliger Zeichenfolgenstempel verwendet werden. Die binäre Protokollierung erfasst standardmäßig den Quelltext von Projektdateien, einschließlich aller beim Buildvorgang aufgetretenen - importierten Projekte und Zieldateien. Der optionale Schalter - ProjectImports steuert dieses Verhalten: + importierten Projekte und Zieldateien. Der optionale + ProjectImports-Schalter steuert dieses Verhalten: ProjectImports=None: – Projektimporte nicht erfassen diff --git a/src/MSBuild/Resources/xlf/Strings.es.xlf b/src/MSBuild/Resources/xlf/Strings.es.xlf index 64ed64c1c79..5bd6773f287 100644 --- a/src/MSBuild/Resources/xlf/Strings.es.xlf +++ b/src/MSBuild/Resources/xlf/Strings.es.xlf @@ -70,7 +70,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. LOCALIZATION: "-reportFileAccesses" should not be localized. @@ -296,7 +296,7 @@ Esta marca es experimental y puede que no funcione según lo previsto. -check Habilita BuildChecks durante la compilación. - BuildCheck permite evaluar reglas para garantizar que las propiedades + BuildCheck permite evaluar reglas para garantizar las propiedades de la compilación. Para más información, consulte https://aka.ms/buildcheck @@ -799,18 +799,14 @@ Esta marca es experimental y puede que no funcione según lo previsto. -logger:XMLLogger,C:\Loggers\MyLogger.dll;OutputAsHTML -logger:<registrador> 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 <registrador> es: - [<clase>,]<ensamblado>[,<opciones>][;<parámetros>] + [<clase>,]<assembly>[,<opciones>][;<parámetros>] La sintaxis de <clase del registrador> es: - [<espacio de nombres parcial o completo>.]<nombre de - clase del registrador> - La sintaxis de <ensamblado del registrador> es: - {<nombre del ensamblado>[,<strong name>] | <archivo - de ensamblado>} - Las opciones del registrador especifican cómo crea MSBuild - el registrador. + [<espacio de nombres parcial o completo>.]<nombre de clase del registrador> + La sintaxis de <ensamblado del registrador> es: + {<assembly name>[,<strong name>] | <assembly file>} + Las opciones del registrador especifican cómo crea MSBuild el registrador. Los <parámetros del registrador> son opcionales y se pasan al registrador tal como se escriben. (Forma corta: -l) Ejemplos: @@ -894,23 +890,23 @@ Esta marca es experimental y puede que no funcione según lo previsto. -consoleLoggerParameters:<parameters> Parámetros del registrador de consola. (Forma corta: -clp) Los parámetros disponibles son: - PerformanceSummary: muestra el tiempo empleado en tareas, destinos + PerformanceSummary-- muestra el tiempo empleado en tareas, destinos y proyectos. - Summary: muestra un resumen de errores y advertencias al final. - NoSummary: no muestra el resumen de errores y advertencias al + Summary-- muestra un resumen de errores y advertencias al final. + NoSummary-- no muestra el resumen de errores y advertencias al final. - ErrorsOnly: muestra solo errores. - WarningsOnly: muestra solo advertencias. - NoItemAndPropertyList: no muestra la lista de elementos y + ErrorsOnly-- muestra solo errores. + WarningsOnly-- muestra solo advertencias. + NoItemAndPropertyList-- no muestra la lista de elementos y propiedades al principio de cada compilación del proyecto. - ShowCommandLine: muestra los mensajes de TaskCommandLineEvent - ShowTimestamp: muestra la marca de tiempo como un prefijo en los + 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 eventId para los eventos iniciados, los eventos finalizados y los mensajes - ForceNoAlign: no alinea el texto al tamaño del + ForceNoAlign-- no alinea el texto al tamaño del búfer de la consola - DisableConsoleColor: usa los colores de consola predeterminados + DisableConsoleColor-- usa los colores de consola predeterminados para todos los mensajes de registro. EnableMPLogging: habilita el estilo de registro de multiprocesador aunque se ejecute en el modo de @@ -1081,15 +1077,12 @@ Esta marca es experimental y puede que no funcione según lo previsto. Para especificar varios registradores, especifique cada uno de ellos por separado. (Forma corta: -dl) La sintaxis de <registrador> es: - [<clase>,]<ensamblado>[,<opciones>][;<parámetros>] + [<clase>,]<assembly>[,<opciones>][;<parámetros>] La sintaxis de <clase del registrador> es: - [<espacio de nombres parcial o completo>.]<nombre - de la clase del registrador> + [<espacio de nombres parcial o completo>.]<nombre de la clase del registrador> La sintaxis de <ensamblado del registrador> es: - {<nombre del ensamblado>[,<strong name>] | <archivo - de ensamblado>} - Las opciones del registrador especifican cómo crea MSBuild - el registrador. + {<assembly name>[,<strong name>] | <assembly file>} + Las opciones del registrador especifican cómo crea MSBuild el registrador. Los <parámetros del registrador> son opcionales y se pasan al registrador tal como se escriben. (Forma corta: -l) Ejemplos: @@ -2107,11 +2100,11 @@ Esta marca es experimental y puede que no funcione según lo previsto. -binaryLogger[:[LogFile=]output.binlog[;ProjectImports={None,Embed,ZipFile}]] Serializa todos los eventos de compilación en un archivo binario comprimido. - De forma predeterminada, el archivo está en el directorio actual y se denomina + De manera predeterminada, el archivo está en el directorio actual y se denomina "msbuild.binlog". El registro binario es una descripción detallada del proceso de compilación que se puede usar más adelante para reconstruir registros de texto y ser usado por otras herramientas de análisis. Un registro binario - suele ser 10-20 veces menor que el registro de nivel de diagnóstico + suele ser de 10 a 20 veces menor que el registro de nivel de diagnóstico de texto más detallado, pero contiene más información. (Forma corta: -bl) @@ -2120,32 +2113,32 @@ Esta marca es experimental y puede que no funcione según lo previsto. para cada compilación, el token "{}" se puede agregar a la ruta de acceso, por ejemplo: LogFile=output-{}-log.binlog. Cada "{}" en la ruta de acceso del registro se reemplaza por una cadena única - mediante la marca de tiempo, el identificador de proceso en ejecución y los id. + mediante la marca de tiempo, el identificador del proceso en ejecución y un valor aleatorio y sellos de cadena aleatorios. - De forma predeterminada, el registrador binario recopila el texto de origen de + De manera predeterminada, el registrador binario recopila el texto de origen de archivos de proyecto, incluidos todos los proyectos importados y archivos de destino encontrados durante la compilación. El conmutador opcional ProjectImports controla este comportamiento: - ProjectImports=None - No recopilar las importaciones + ProjectImports=None :no recopilar las importaciones del proyecto. - ProjectImports=Embed - Inserción de importaciones de proyecto en el + ProjectImports=Embed :inserción de importaciones de proyecto en el archivo de registro. - ProjectImports=ZipFile - Guardar archivos de proyecto en + ProjectImports=ZipFile :guardar archivos de proyecto en output.projectimports.zip donde la salida tiene el mismo nombre que el nombre del archivo de registro binario. El valor predeterminado de ProjectImports es Inserción. - Nota: el registrador no recopila archivos de código fuente que no son de MSBuild + Nota: El registrador no recopila archivos de código fuente que no son de MSBuild como .cs, .cpp, etc. Un archivo .binlog se puede "reproducir" pasándolo a msbuild.exe como argumento en lugar de como proyecto o solución. Otros registradores recibirán la información contenida en el archivo de registro como si se estuviera produciendo la compilación original. - Puede obtener más información sobre el registro binario y sus usos en: + Puede obtener más información acerca del registro binario y sus usos en: https://aka.ms/msbuild/binlog Ejemplos: diff --git a/src/MSBuild/Resources/xlf/Strings.fr.xlf b/src/MSBuild/Resources/xlf/Strings.fr.xlf index 58ba63c329c..476a57629e5 100644 --- a/src/MSBuild/Resources/xlf/Strings.fr.xlf +++ b/src/MSBuild/Resources/xlf/Strings.fr.xlf @@ -68,7 +68,7 @@ -reportFileAccesses[:True|False] Entraîne le signalement par MSBuild des accès par fichiers aux plug-ins - cache de projet configurés. + de cache de projet configurés. Cet indicateur est expérimental et peut ne pas fonctionner comme prévu. @@ -88,7 +88,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é, écrivez les valeurs après la génération. + utilisée, écrivez les valeurs après la build. LOCALIZATION: "-getProperty", "-targets" and "-getTargetResult" should not be localized. @@ -108,7 +108,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 génération. + les valeurs après la build. LOCALIZATION: "-getItem", "targets" and "getTargetResult" should not be localized. @@ -147,14 +147,14 @@ -featureAvailability:featureName,... Vérifiez la disponibilité des fonctionnalités. Le résultat est l’une des - chaînes « Undefined », « Available », « NotAvailable » et - « Aperçu ». + chaînes « Non défini », « Disponible », « Indisponible » et + « Préversion ». - Non défini : la disponibilité de la fonctionnalité n’est pas définie - (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 + (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 prise en charge par le moteur MSBuild actuel) - Disponible : la fonctionnalité est disponible - Préversion : la fonctionnalité est en préversion (non stable) @@ -181,14 +181,13 @@ -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é logiquement par projet et conçu pour mettre en évidence + organisée 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 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 + 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 versions. Cette option est disponible dans MSBuild 17.8 et - ultérieures. + versions ultérieures. (Forme abrégée : -tl) @@ -219,8 +218,8 @@ futures -terminalLoggerParameters: <parameters> 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 du terminal - enregistreur. Elle nécessite l’une des valeurs suivantes : + default --Spécifie le comportement par défaut de l’enregistreur + de terminal. 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é @@ -296,9 +295,9 @@ futures of the build. For more info see https://aka.ms/buildcheck -check - Active BuildChecks pendant la construction. - BuildCheck permet d'évaluer les règles pour garantir les propriétés - de la build. Pour plus d'informations, consultez https://aka.ms/build + Active BuildChecks pendant la génération. + BuildCheck permet d’évaluer les règles pour garantir les propriétés + de la build. Pour plus d’informations, consultez https://aka.ms/build {Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"} @@ -806,7 +805,7 @@ Cet indicateur est expérimental et peut ne pas fonctionner comme prévu. Syntaxe de <classe de journalisation> : [<espace de noms partiels ou complets>.]<nom de la classe de journalisation> Syntaxe de <assembly de journalisation> : - {<nom d'assembly>[,<strong name>] | <fichier d'assembly>} + {<assembly name>[,<strong name>] | <assembly file>} Les options de journalisation spécifient la façon dont MSBuild crée le journaliseur. Les <paramètres de journalisation> sont facultatifs. Ils sont passés au journaliseur tels que vous les avez tapés. (Forme abrégée : -l) @@ -888,11 +887,11 @@ Remarque : verbosité des enregistreurs d’événements de fichiers -consoleLoggerParameters:PerformanceSummary;NoSummary; Verbosity=minimal - -consoleLoggerParameters:<paramètres> + -consoleLoggerParameters :<parameters> Paramètres de l’enregistreur d’événements de la console. (Forme abrégée : -clp) Les paramètres disponibles sont : - PerformanceSummary--Afficher la durée des tâches, des cibles - et des projets. + PerformanceSummary--Afficher la durée des tâches, les cibles + et les projets. Summary--Afficher le résumé des erreurs et des avertissements à la fin. NoSummary--Ne pas afficher le résumé des erreurs et des avertissements à la fin. @@ -901,12 +900,12 @@ Remarque : verbosité des enregistreurs d’événements de fichiers NoItemAndPropertyList--Ne pas afficher la liste des éléments et des propriétés au début de chaque build de projet. ShowCommandLine--Afficher les messages de TaskCommandLineEvent - ShowTimestamp--Afficher l'horodatage en tant que préfixe de tout + ShowTimestamp--Afficher l’horodatage sous forme de préfixe pour tout message. ShowEventId--Afficher l’eventId pour les événements démarrés et achevés, ainsi que les messages - ForceNoAlign--Ne pas aligner le texte par rapport à la taille de la - mémoire tampon de la console + ForceNoAlign--Ne pas aligner le texte par rapport à la taille de + la mémoire tampon de la console DisableConsoleColor--Utiliser les couleurs de la console par défaut pour tous les messages de journalisation. EnableMPLogging--Activer le style de journalisation multiprocesseur, @@ -914,7 +913,7 @@ Remarque : verbosité des enregistreurs d’événements de fichiers multiprocesseur. Ce style de journalisation est activé par défaut. ForceConsoleColor--Utiliser les couleurs de la console ANSI même si la console ne les prend pas en charge - PreferConsoleColor--N’utiliser les couleurs de la console ANSI que si + PreferConsoleColor--N’utiliser les couleurs de la console ANSI seulement si la console cible les prend en charge Verbosity--Remplace le paramètre -verbosity pour cet enregistreur d’événement. @@ -1082,7 +1081,7 @@ Remarque : verbosité des enregistreurs d’événements de fichiers Syntaxe de <classe de journalisation> : [<espace de noms partiels ou complets>.]<nom de la classe de journalisation> Syntaxe de <assembly de journalisation> : - {<nom d'assembly>[,<strong name>] | <fichier d'assembly>} + {<assembly name>[,<strong name>] | <assembly file>} Les options de journalisation spécifient la façon dont MSBuild crée le journaliseur. Les <paramètres de journalisation> sont facultatifs. Ils sont passés au journaliseur tels que vous les avez tapés. (Forme abrégée : -l) @@ -1555,7 +1554,7 @@ Remarque : verbosité des enregistreurs d’événements de fichiers MSBUILD : error MSB1014: Must provide an item name for the getItem switch. - MSBUILD : error MSB1014: Must provide an item name for the getItem switch. + MSBUILD : error MSB1014: Doit fournir un nom d'élément pour le commutateur getItem. {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". @@ -1564,7 +1563,7 @@ Remarque : verbosité des enregistreurs d’événements de fichiers MSBUILD : error MSB1010: Must provide a property name for the getProperty switch. - MSBUILD : error MSB1010: Must provide a property name for the getProperty switch. + MSBUILD : error MSB1010: Doit fournir un nom de propriété pour le commutateur getProperty. {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". @@ -1582,7 +1581,7 @@ Remarque : verbosité des enregistreurs d’événements de fichiers MSBUILD : error MSB1017: Must provide a target name for the getTargetResult switch. - MSBUILD : error MSB1017: Must provide a target name for the getTargetResult switch. + MSBUILD : error MSB1017: Doit fournir un nom de cible pour le commutateur getTargetResult. {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". @@ -1783,7 +1782,7 @@ Remarque : verbosité des enregistreurs d’événements de fichiers 2: in evaluation. It is recommended to turn off Smart App Control in development environemnt as otherwise performance might be impacted - 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 + 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 Smart App Control, "VerifiedAndReputablePolicyState" should not be localized @@ -1820,7 +1819,7 @@ Remarque : verbosité des enregistreurs d’événements de fichiers 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. - 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. + 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. {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. @@ -2102,11 +2101,11 @@ Remarque : verbosité des enregistreurs d’événements de fichiers -binaryLogger[:[LogFile=]output.binlog[;ProjectImports={None,Embed,ZipFile}]] Sérialise tous les événements de génération dans un fichier binaire compressé. - Par défaut, le fichier se trouve dans le répertoire actuel et son nom est + Par défaut, le fichier se trouve dans le répertoire actuel et son nom est "msbuild.binlog". Le journal binaire est une description détaillée du processus de génération que vous pouvez utiliser plus tard pour reconstruire des journaux texte et être utilisé par d’autres outils d’analyse. Un journal binaire - est généralement 10 à 20 fois plus petit que le journal au niveau du diagnostic + est généralement 10 à 20 fois plus petit que le journal au niveau du diagnostic du texte le plus détaillé, mais il contient d’autres informations. (Forme abrégée : -bl) diff --git a/src/MSBuild/Resources/xlf/Strings.it.xlf b/src/MSBuild/Resources/xlf/Strings.it.xlf index 1ea94c50c0a..dc1ec23fa7c 100644 --- a/src/MSBuild/Resources/xlf/Strings.it.xlf +++ b/src/MSBuild/Resources/xlf/Strings.it.xlf @@ -67,10 +67,10 @@ This flag is experimental and may not work as intended. -reportFileAccesses[:True|False] - Fa in modo che MSBuild segnali gli accessi ai file a qualsiasi file configurato + Fa in modo che MSBuild segnali gli accessi ai file a qualsiasi plug-in della cache del progetto. -Questo flag è sperimentale e potrebbe non funzionare come previsto. + Questo flag è sperimentale e potrebbe non funzionare come previsto. LOCALIZATION: "-reportFileAccesses" should not be localized. @@ -85,10 +85,10 @@ Questo flag è sperimentale e potrebbe non funzionare come previsto. used, write out the values after the build. -getProperty:propertyName,... - 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. + 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. LOCALIZATION: "-getProperty", "-targets" and "-getTargetResult" should not be localized. @@ -104,10 +104,10 @@ Questo flag è sperimentale e potrebbe non funzionare come previsto. the values after the build. -getItem:itemName,... - Scrivere il valore di uno o più elementi specificati e + Scrive il valore di uno o più elementi specificati e i metadati associati dopo la valutazione senza - eseguire la compilazione o in caso si usi l’opzione -targets - oppure l'opzione -getTargetResult, scrivere + eseguire la compilazione oppure, se si usa l’opzione -targets + o l'opzione -getTargetResult, scrive i valori dopo la compilazione. @@ -121,7 +121,7 @@ Questo flag è sperimentale e potrebbe non funzionare come previsto. the specified targets will be executed. -getTargetResult:targetName,... - Scrivere il valore di output di una o più destinazioni + Scrive il valore di output di una o più destinazioni per eseguire le destinazioni specificate. @@ -146,19 +146,18 @@ Questo flag è sperimentale e potrebbe non funzionare come previsto. (Short form: -fa) -featureAvailability:featureName,... - 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 + 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 della disponibilità delle funzionalità) - - 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 è + - 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 è supportata dal motore MSBuild corrente) - - Disponibile: la funzionalità è disponibile - - Anteprima : la funzionalità è in anteprima (non stabile) + - Available: la funzionalità è disponibile + - Preview : la funzionalità è in anteprima (non stabile) (Forma breve: -fa) @@ -179,17 +178,17 @@ Questo flag è sperimentale e potrebbe non funzionare come previsto. later. (Short form: -tl) - -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 + -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 versioni. Questa opzione è disponibile in MSBuild 17.8 e versioni successive. - Forma breve: -tl) + (Forma breve: -tl) LOCALIZATION: "-terminalLogger", "-tl", and "auto" should not be localized. @@ -217,18 +216,18 @@ Questo flag è sperimentale e potrebbe non funzionare come previsto. -tlp:default=auto;verbosity=diag;shownCommandLine -terminalLoggerParameters: <parameters> - Parametri per il logger del terminale. Forma breve: -tlp) + Parametri per il logger del terminale. (Forma breve: -tlp) Parametri disponibili. - impostazione predefinita- Specifica il comportamento predefinito del terminale + default- Specifica il comportamento predefinito del terminale logger. Richiede uno dei valori seguenti: - - 'attivato', 'vero' forza l'uso di TerminalLogger anche + - 'on', 'true' impone l'uso di TerminalLogger anche se venisse disabilitato. - - 'disattivato', 'falso' forza l'uso di TerminalLogger anche + - 'off', 'false' impone l'uso di TerminalLogger anche se venisse abilitato. - - 'automatico' abilita TerminalLogger quando il terminale + - 'auto' abilita TerminalLogger quando il terminale lo supporta e la sessione non ha reindirizzato il livello di dettaglio stdout/stderr - -- Eseguire l'override dell'impostazione del livello di dettaglio per questo + verbosity--Ignora l'impostazione -verbosity per questo logger showCommandLine--Mostra i messaggi TaskCommandLineEvent @@ -255,13 +254,13 @@ Questo flag è sperimentale e potrebbe non funzionare come previsto. (Short form: -mt) -multithreading - Abilitare la modalità multithread SPERIMENTALE in MSBuild. + Abilita la modalità multithread SPERIMENTALE in MSBuild. Ciò significa che MSBuild userà più thread per creare progetti in parallelo, - invece di più processi. + anziché più processi. Questa opzione non è supportata. - Il numero massimo di thread usati è determinato da - Opzione -maxCpuCount. + Il numero massimo di thread usati è determinato + dall'opzione -maxCpuCount. In caso di modalità multithread su e MSBUILDFORCEALLTASKSOUTOFPROC=1 maxCpuCount non può essere maggiore di 256. @@ -278,11 +277,11 @@ Questo flag è sperimentale e potrebbe non funzionare come previsto. This writes the value of property Bar into Biz.txt. -getResultOutputFile:file - Reindirizza l'output da get* in un file. + Reindirizza l'output di get* in un file. Esempio: - -getProperty:barra -getResultOutputFile:Biz.txt - Il valore della barra delle proprietà viene scritto in Biz.txt. + -getProperty:Bar -getResultOutputFile:Biz.txt + Il valore della proprietà Bar viene scritto in Biz.txt. LOCALIZATION: "-getResultOutputFile", "get*" and "-getProperty" should not be localized. @@ -811,8 +810,8 @@ Questo flag è sperimentale e potrebbe non funzionare come previsto. [<classe>,]<assembly>[,<opzioni>][;<parametri>] La sintassi di <classe logger> è la seguente: [<spazio dei nomi parziale o completo>.]<nome classe logger> - La sintassi di <assembly logger> è la seguente: - {<nome assembly>[,<strong name>] | <file di assembly>} + La sintassi di <logger assembly> è la seguente: + {<assembly name>[,<strong name>] | <assembly file>} Le opzioni di logger consentono di specificare in che modo MSBuild crea il logger. I <parametri logger> sono facoltativi e vengono passati al logger così come vengono digitati. Forma breve: -l. @@ -895,34 +894,34 @@ Nota: livello di dettaglio dei logger di file Verbosity=minimal -consoleLoggerParameters:<parametri> - Parametri per il logger di console. (Forma breve: -clp) + Parametri per il logger della console. (Forma breve: -clp) I parametri disponibili sono: - PerformanceSummary: indica il tempo impiegato per le attività, le destinazioni + PerformanceSummary: indica il tempo impiegato per le attività, le destinazioni e i progetti. Summary: visualizza un riepilogo degli errori e degli avvisi alla fine. - NoSummary: non visualizza un riepilogo degli errori alla + NoSummary: non visualizza un riepilogo degli errori e degli avvisi alla fine. ErrorsOnly: visualizza solo gli errori. WarningsOnly: visualizza solo gli avvisi. NoItemAndPropertyList: non visualizza l'elenco di elementi e - proprietà all'inizio di ogni compilazione del progetto. + proprietà all'inizio di ogni compilazione di progetto. ShowCommandLine: visualizza i messaggi TaskCommandLineEvent - ShowTimestamp: visualizza il timestamp sotto forma di prefisso per ogni + ShowTimestamp: visualizza il timestamp come prefisso per ogni messaggio. ShowEventId: mostra l'ID evento per gli eventi iniziati, - gli eventi finiti e i messaggi + gli eventi terminati e i messaggi ForceNoAlign: non allinea il testo alle dimensioni del buffer della console DisableConsoleColor: usa i colori predefiniti della console per tutti i messaggi di registrazione. EnableMPLogging: abilita lo stile di registrazione multiprocessore anche quando è in esecuzione in modalità - non- multiprocessore. Si tratta dello stile di registrazione predefinito. - ForceConsoleColor: usa i colori della console ANSI anche se + non-multiprocessore. Questo stile di registrazione è attivato per impostazione predefinita. + ForceConsoleColor: usa i colori ANSI per la console anche se non sono supportati dalla console - PreferConsoleColor- Usa i colori della console ANSI solo se - la console di destinazione lo supporta - Verbosity: esegue l'override dell'impostazione -verbosity per questo + PreferConsoleColor: usa i colori ANSI per la console solo se + la console di destinazione li supporta + Verbosity: sostituisce l'impostazione -verbosity per questo logger. Esempio: -consoleLoggerParameters:PerformanceSummary;NoSummary; @@ -1087,8 +1086,8 @@ Nota: livello di dettaglio dei logger di file [<classe>,]<assembly>[,<opzioni>][;<parametri>] La sintassi di <classe logger> è la seguente: [<spazio dei nomi parziale o completo>.]<nome classe logger> - La sintassi di <assembly logger> è la seguente: - {<nome assembly>[,<strong name>] | <file di assembly>} + La sintassi di <logger assembly> è la seguente: + {<assembly name>[,<strong name>] | <assembly file>} Le opzioni di logger consentono di specificare in che modo MSBuild crea il logger. I <parametri logger> sono facoltativi e vengono passati al logger così come vengono digitati. Forma breve: -l @@ -1207,9 +1206,8 @@ Nota: livello di dettaglio dei logger di file è la directory corrente. Per impostazione predefinita, ai file viene assegnato il nome "MSBuild<idnodo>.log". Il percorso dei file e altri parametri di fileLogger possono - essere specificati aggiungendo l'opzione + essere specificati aggiungendo l'opzione "-fileLoggerParameters". - "-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 @@ -1556,7 +1554,7 @@ Nota: livello di dettaglio dei logger di file MSBUILD : error MSB1067: Must provide a feature name for the featureAvailability switch. - MSBUILD : error MSB1067: È necessario fornire un nome funzionalità per l’opzione featureAvailability. + MSBUILD : error MSB1067: È necessario fornire un nome di funzionalità per l’opzione featureAvailability. {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". @@ -2113,24 +2111,23 @@ Nota: livello di dettaglio dei logger di file -binaryLogger[:[LogFile=]output.binlog[;ProjectImports={None,Embed,ZipFile}]] Serializza tutti gli eventi di compilazione in un file binario compresso. - Per impostazione predefinita, il file csi trova nella directory corrente e si chiama + Per impostazione predefinita, il file si trova nella directory corrente ed è denominato "msbuild.binlog". Il log binario è una descrizione - dettagliata del processo di compilazione utilizzabile in - seguito per ricostruire i log di testo e viene usato da altri strumenti di analisi. Un log binario è in genere + dettagliata del processo di compilazione che può essere utilizzato in + seguito per ricostruire i log di testo e da altri strumenti di analisi. Un log binario è in genere 10-20 volte più piccolo del più dettagliato log di testo - di livello diagnostico, ma contiene maggiori informazioni. + di livello diagnostico, ma contiene più informazioni. (Forma breve: -bl) Il LogFile facoltativo specifica il percorso in cui il - il log binario viene salvato. Per generare un file di log distinto - per ogni compilazione, il token "{}" può essere aggiunto al + log binario viene salvato. Per generare un file di log distinto + per ogni compilazione, è possibile aggiungere il token "{}" al percorso, ad esempio: LogFile=output-{}-log.binlog. Ogni "{}" nel percorso del log viene sostituito con una stringa univoca - usando il timestamp, l'ID del processo in esecuzione e -timbro - stringa casuale. + usando il timestamp, l'ID del processo in esecuzione elaborare la + stringa stamp casuale. - Per impostazione predefinita, il logger binario raccoglie il testo di origine di + Per impostazione predefinita, il logger binario raccoglie il testo di origine dei file di progetto, inclusi tutti i progetti importati e i file di destinazione rilevati durante la compilazione. L'opzione facoltativa ProjectImports controlla questo comportamento: @@ -2141,18 +2138,18 @@ timbro file di log. ProjectImports=ZipFile - I file del progetto vengono salvati in output.projectimports.zip - dove output corrisponde allo stesso + dove output ha lo stesso nome del file di log binario. L'impostazione predefinita di ProjectImports è Embed. Nota: il logger non raccoglie i file di origine non-MSBuild, - ad esempio quelli con estensione .cs, .cpp e così via. + ad esempio .cs, .cpp e così via. - È possibile riprodurre un file con estensione binlog - passandolo a msbuild.exe come argomento invece di un progetto o di una soluzione. - Altri logger riceveranno le - informazioni contenute nel file di log come se fosse in corso la compilazione originale. - Per maggiori informazioni sul file di log e su come usarlo, vedere: + È possibile "riprodurre" un file .binlog passandolo a + msbuild.exe come argomento invece di un progetto o di una soluzione. + Gli altri logger riceveranno le informazioni contenute + nel file di log come se fosse in corso la compilazione originale. + Per altre informazioni sul log binario e sui suoi utilizzi, vedere: https://aka.ms/msbuild/binlog Esempi: @@ -2247,16 +2244,15 @@ Esegue la profilatura della valutazione di MSBuild e scrive -restoreProperty:IsRestore=true;MyProperty=value -restoreProperty:<n>=<v> - 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. - <v> rappresenta il nome della proprietà e <v> 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. + <v> rappresenta il nome della proprietà e <v> 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 LOCALIZATION: "-restoreProperty" and "-rp" should not be localized. diff --git a/src/MSBuild/Resources/xlf/Strings.ja.xlf b/src/MSBuild/Resources/xlf/Strings.ja.xlf index f9c088f287a..dbb687058b4 100644 --- a/src/MSBuild/Resources/xlf/Strings.ja.xlf +++ b/src/MSBuild/Resources/xlf/Strings.ja.xlf @@ -68,7 +68,7 @@ -reportFileAccesses[:True|False] MSBuild が、構成されているプロジェクト キャッシュ プラグインへの - ファイル アクセスを報告します。 + ファイル アクセスを報告するようにします。 このフラグは実験的なものであり、意図したとおりに動作しない可能性があります。 @@ -85,11 +85,11 @@ used, write out the values after the build. -getProperty:propertyName,... - 1 つ以上の指定されたプロパティの値を書き出し - 評価後、ビルドを実行せずに、または - -targets オプションまたは -getTargetResult オプションが - 使用して、ビルド後に値を書き出します。 - + 評価後にビルドを実行せずに、1 つ以上の + 指定されたプロパティの値を書き出します。 + または、-targets オプションまたは -getTargetResult オプションが + 使用されている場合は、ビルド後に値を書き出します。 + 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. @@ -104,12 +104,12 @@ the values after the build. -getItem:itemName,... - 1 つ以上の指定された項目の値を書き出し、 - 評価後に関連付けられたメタデータを - ビルドを実行せずに、または -targets オプション - または -getTargetResult オプションが使用されている場合は、書き込み - ビルド後の値。 - + 評価後にビルドを実行せずに、1 つ以上の指定された項目の値と + 関連付けられたメタデータを書き出します。 + または、-targets オプションまたは -getTargetResult オプションが + 使用されている場合は、ビルド後に + 値を書き出します。 + 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. @@ -121,9 +121,9 @@ the specified targets will be executed. -getTargetResult:targetName,... - 1 つ以上のターゲットの出力値を書き出し、 - 指定したターゲットが実行されます。 - + 1 つ以上のターゲットの出力値を書き出し、 + 指定したターゲットが実行されます。 + LOCALIZATION: "-getTargetResult" should not be localized. LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars. @@ -146,20 +146,20 @@ (Short form: -fa) -featureAvailability:featureName,... - 機能の可用性を確認します。結果は、次のいずれかになります。 - 文字列 "Undefined"、"Available"、"NotAvailable"、および - "Preview" です。 - - Undefined - 機能の可用性は未定義です - (機能名が機能の可用性に関して不明です - チェッカー) - - NotAvailable - この機能は使用できません - Undefined とは異なり、機能名は機能に認識されています - 可用性チェッカーは、この機能が - 現在の MSBuild エンジンでサポートされていないことを理解しています) - - Available - この機能は使用可能です - - Preview - 機能はプレビュー段階です (安定していません) - (短い形式: -fa) - + 機能の可用性を確認します。結果は、文字列 "Undefined"、 + "Available"、"NotAvailable"、"Preview" の + いずれかになります。 + - Undefined - 機能の可用性は未定義です + (機能名は機能の可用性チェッカーに対して + 不明です) + - NotAvailable - この機能は使用できません + Undefined とは異なり、機能名は機能の可用性チェッカーが + 認識しており、このチェッカーは、この機能が現在の MSBuild エンジンで + サポートされていないことを理解しています) + - Available - この機能は使用可能です + - Preview - 機能はプレビュー段階です (安定していません) + (短い形式: -fa) + 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. @@ -179,17 +179,17 @@ (Short form: -tl) -terminalLogger[:auto,on,off] - ターミナル ロガーを有効または無効にします。ターミナル ロガーは - 本体のビルド出力がリアルタイムで強化され、 - プロジェクトごとに論理的に整理され、強調表示するように設計されています - アクション可能な情報です。auto を指定する (またはオプションを使用する) - 引数を指定せずに) ターミナル ロガーを使用する場合は、 - 標準出力はリダイレクトされません。出力を解析しないでください - それ以外の場合は、将来変更されずに残っている - バージョン。このオプションは、MSBuild 17.8 以降で利用可能です - 以降で。 - (短い形式: -tl) - + ターミナル ロガーを有効または無効にします。ターミナル ロガーは、 + 本体で強化されたビルド出力をリアルタイムに提供します。 + この出力は、プロジェクトごとに論理的に整理されており、アクション可能な情報を + 強調表示するように設計されています。標準出力がリダイレクトされない場合のみ、 + auto を指定 (または引数を指定せずにオプションを使用) して、 + ターミナル ロガーを使用します。出力を解析しないでください。 + 別の方法で出力を利用してください。残りの部分は将来のバージョンで + 変更されずに残ります。このオプションは、MSBuild 17.8 以降で + 利用可能です。 + (短い形式: -tl) + 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. @@ -216,25 +216,24 @@ -tlp:default=auto;verbosity=diag;shownCommandLine -terminalLoggerParameters: <parameters> - ターミナル ロガーへのパラメーター。(短い形式: -tlp) - 使用可能なパラメーター。 - default -- ターミナル - の既定の動作を指定します - ロガー。次のいずれかの値が必要です: - - `on`、`true` は TerminalLogger を強制的に使用します - 無効である場合も同様です。 - - `off`、`false` は TerminalLogger を使用しないように強制します - 有効である場合も同様です。 - - `auto` は、次の場合にターミナルで TerminalLogger を有効にします - サポートされており、セッションがリダイレクトされていない場合です - stdout/stderr - verbosity-- 下記の verbosity 設定をオーバーライドします - logger - showCommandLine -- TaskCommandLineEvent メッセージを表示します + ターミナル ロガーへのパラメーター。(短い形式: -tlp) + 使用可能なパラメーター。 + default -- ターミナル ロガーの既定の動作を + 指定します。次のいずれかの値が必要です。 + - `on`、`true` の場合、TerminalLogger が無効である場合も + TerminalLogger を強制的に使用します。 + - `off`、`false` の場合、TerminalLogger が有効である場合も + TerminalLogger を使用しないように強制します。 + - `auto` の場合、ターミナルで TerminalLogger がサポートされており、 + セッションが stdout/stderr をリダイレクトしていない場合、 + TerminalLogger を有効にします + verbosity-- このロガーの -verbosity 設定を + オーバーライドします + showCommandLine -- TaskCommandLineEvent メッセージを表示します - 例: - -tlp:default=auto;verbosity=diag;shownCommandLine - + 例: + -tlp:default=auto;verbosity=diag;shownCommandLine + 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. @@ -255,16 +254,16 @@ (Short form: -mt) -multithreaded - MSBuild で試験的なマルチスレッド モードを有効にします。 - つまり、MSBuild は複数のプロセスではなく、 - 複数のスレッドを使用してプロジェクトを - 並列にビルドします。 - このオプションはサポートされていません。 - 使用されるスレッドの最大数は、 - -maxCpuCount スイッチによって決まります。 - マルチスレッド モードが有効で、 + MSBuild の試験的なマルチスレッド モードを有効にします。 + これは、MSBuild でプロジェクトのビルドを + 並列実行する際に、複数のプロセスではなく + 複数のスレッドが使われるモードです。 + このオプションはサポートの対象外です。 + 使われるスレッドの最大数は、 + -maxCpuCount スイッチで指定します。 + マルチスレッド モードを有効にし、かつ MSBUILDFORCEALLTASKSOUTOFPROC=1 の場合、 - maxCpuCount は 256 を超えることはできません。 + maxCpuCount は 256 以下であることが必要です。 (短い形式: -mt) @@ -278,12 +277,12 @@ This writes the value of property Bar into Biz.txt. -getResultOutputFile:file - get* からの出力をファイルにリダイレクトします。 + get* からの出力をファイルにリダイレクトします。 - 例: - -getProperty:Bar -getResultOutputFile:Biz.txt - これにより、プロパティ Bar の値が Biz.txt に書き込まれます。 - + 例: + -getProperty:Bar -getResultOutputFile:Biz.txt + これにより、プロパティ Bar の値が Biz.txt に書き込まれます。 + 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. @@ -298,7 +297,7 @@ -check ビルド中に BuildChecks を有効にします。 BuildCheck を使用すると、ビルドのプロパティを保証するための - 評価ルールが有効になります。詳しくは https://aka.ms/maxmemory を参照してください + ルールを評価できます。詳しくは https://aka.ms/maxmemory を参照してください {Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"} @@ -327,7 +326,7 @@ MSBUILD : error MSB1065: Terminal logger value is not valid. It should be one of 'auto', 'true', or 'false'. {0} - MSBUILD : error MSB1065: ターミナル ロガーの値が無効です。'auto'、'true'、または 'false' のいずれかである必要があります。 {0} + MSBUILD : error MSB1065: ターミナル ロガーの値が無効です。'auto'、'true'、または 'false' のいずれかである必要があります。{0} {StrBegin="MSBUILD : error MSB1065: "} UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg. @@ -889,36 +888,36 @@ Verbosity=minimal -consoleLoggerParameters:<parameters> - コンソール ロガーへのパラメーターです。(短縮形: -clp) - 利用可能なパラメーター: - PerformanceSummary--タスク、ターゲット、プロジェクトにかかった時間を - 表示します。 - Summary--最後にエラーと警告の概要を表示します。 - NoSummary--最後にエラーと警告の概要を表示 - しません。 - ErrorsOnly--エラーのみを表示します。 - WarningsOnly--警告のみを表示します。 - NoItemAndPropertyList--各プロジェクトのビルド開始時に、 - 項目とプロパティのリストを表示しません。 - ShowCommandLine--TaskCommandLineEvent メッセージを表示します - ShowTimestamp--Timestamp を任意のメッセージへのプレフィックスとして + コンソール ロガーへのパラメーター。(短い形式: -clp) + 使用可能なパラメーター: + PerformanceSummary--タスク、ターゲット、プロジェクトに費やされた時間を 表示します。 - ShowEventId--開始されたイベント、終了したイベント、 - メッセージの eventId を表示します。 - ForceNoAlign--テキストを、コンソール バッファーの - サイズに合わせません - DisableConsoleColor--すべてのログ メッセージに対して - 既定のコンソール カラーを使用します。 - EnableMPLogging--非マルチプロセッサ モードで - 実行する場合も、マルチプロセッサのログ形式を有効にします。 - このログ形式は、既定で有効です。 - ForceConsoleColor--コンソールでサポートされていない場合でも、 - ANSI コンソール カラーを使用します - PreferConsoleColor--ターゲット コンソールでサポートしている場合のみ - ANSI コンソール カラーを使用します - Verbosity--このロガーの -verbosity 設定を - 上書きします。 - 例: + Summary--最後にエラーと警告の要約を表示します。 + NoSummary--最後にエラーと警告の要約を + 表示しません。 + ErrorsOnly-- エラーのみを表示します。 + WarningsOnly-- 警告のみを表示します。 + NoItemAndPropertyList--各プロジェクト ビルドの開始時に + アイテムとプロパティの一覧を表示しません。 + showCommandLine--TaskCommandLineEvent メッセージを表示します + ShowTimestamp-- Timestamp をプレフィックスとして任意の + メッセージに表示します。 + ShowEventId-- 開始されたイベント、終了したイベント、メッセージに eventId を + 表示します + ForceNoAlign--テキストをコンソール バッファーのサイズに合わせて + 配置しません + DisableConsoleColor--すべてのログ メッセージに既定のコンソールの色を + 使用します。 + EnableMPLogging--非マルチプロセッサで実行されている場合でも、 + マルチプロセッサ ログ スタイルを + 有効にします。このログ スタイルは既定でオンになっています。 + ForceConsoleColor--コンソールではサポートされていない場合でも、 + ANSI コンソールの色を使用します + PreferConsoleColor--ターゲット コンソールでサポートされていない場合のみ、 + ANSI コンソールの色を使用します + Verbosity--このロガーの -verbosity 設定をオーバーライド + します。 + 例: -consoleLoggerParameters:PerformanceSummary;NoSummary; Verbosity=minimal @@ -1773,7 +1772,7 @@ Based on the Windows registry key VerifiedAndReputablePolicyState, SAC state = {0}. - Windows レジストリ キー VerifiedAndReputablePolicyState に基づいて、SAC 状態 = {0}。 + Windows レジストリ キー VerifiedAndReputablePolicyState に基づいており、SAC 状態 = {0} です。 "Windows" is the OS, SAC is the Smart App Control, "VerifiedAndReputablePolicyState" should not be localized @@ -2117,8 +2116,8 @@ ランダム文字列スタンプを使用して一意の文字列に 置き換えられます。 - バイナリ ロガーでは、既定でプロジェクト ファイルのソース - テキストが収集されます。これには、ビルド中に読み込まれた + バイナリ ロガーでは、既定でプロジェクト ファイルの + ソース テキストが収集されます。これには、ビルド中に読み込まれた すべてのインポート プロジェクトやターゲット ファイルが含まれます。省略可能な ProjectImports スイッチはこの動作を制御します: @@ -2132,8 +2131,8 @@ 同じ名前です。 ProjectImports の既定の設定は Embed です。 - メモ: このロガーは、.cs、.cpp などの MSBuild 以外のソース - ファイルを収集しません。 + メモ: このロガーは、.cs、.cpp などの MSBuild 以外の + ソース ファイルを収集しません。 .binlog ファイルを "再生" するには、プロジェクト/ ソリューションの代わりに引数として msbuild.exe に渡します。 diff --git a/src/MSBuild/Resources/xlf/Strings.ko.xlf b/src/MSBuild/Resources/xlf/Strings.ko.xlf index 163e4fa6a48..0e24ebfd444 100644 --- a/src/MSBuild/Resources/xlf/Strings.ko.xlf +++ b/src/MSBuild/Resources/xlf/Strings.ko.xlf @@ -86,7 +86,7 @@ -getProperty:propertyName,... 빌드를 실행하지 않고 평가 후 - 지정된 속성 중 하나 이상의 값을 작성하거나, + 하나 이상의 지정된 속성 값을 작성하거나, -targets 옵션 또는 -getTargetResult 옵션을 사용하는 경우 빌드 후 값을 작성합니다. @@ -105,8 +105,8 @@ -getItem:itemName,... 빌드를 실행하지 않고 평가 후 - 지정된 항목 중 하나 이상의 값 및 - 연결된 해당 메타데이터를 작성하거나, + 하나 이상의 지정된 항목 및 + 관련 메타데이터의 값을 작성하거나 -targets 옵션 또는 -getTargetResult 옵션을 사용하는 경우 빌드 후 값을 작성합니다. @@ -121,7 +121,7 @@ the specified targets will be executed. -getTargetResult:targetName,... - 대상 하나 이상의 출력 값을 작성하면 + 하나 이상의 대상의 출력 값을 작성하면 지정된 대상이 실행됩니다. @@ -149,11 +149,11 @@ 기능 가용성을 확인합니다. 결과는 문자열 "Undefined", "Available", "NotAvailable" 및 "Preview" 중 하나입니다. - - 정의되지 않음 - 기능의 가용성이 정의되지 않았습니다 + - Undefined - 기능의 가용성이 정의되지 않았습니다 (기능 가용성 검사기에서 기능 이름을 인식할 수 없음). - NotAvailable - 기능을 사용할 수 없습니다( - 정의되지 않음과는 달리, 기능 가용성 검사가에서 기능 이름을 + Undefined와 달리, 기능 가용성 검사가에서 기능 이름을 인식할 수 있으며 기능이 현재 MSBuild 엔진에서 지원되지 않는 것으로 인식하고 있음). - Available - 기능을 사용할 수 있습니다. @@ -179,14 +179,14 @@ (Short form: -tl) -terminalLogger[:auto,on,off] - 터미널 로거를 사용하거나 사용하지 않도록 설정합니다. 터미널 로거 - 는 콘솔에서 향상된 빌드 출력을 실시간으로 제공합니다. - 이러한 출력은 프로젝트별로 논리적으로 구성되고 실행 가능한 정보를 - 강조 표시하도록 설계되어 있습니다. 자동을 지정(또는 인수 없이 옵션 - 사용)하여 터미널 로거를 사용합니다. 단, 이 경우 - 표준 출력이 리디렉션되지 않아야 합니다. 출력을 구문 분석하지 않습니다. - 그렇지 않을 경우 이후 버전에서 변경되지 않은 상태로 - 유지됩니다. 이 옵션은 MSBuild 17.8 이상 버전에서 + 터미널 로거를 사용하거나 사용하지 않도록 설정합니다. 터미널 로거는 + 콘솔에서 향상된 빌드 출력을 실시간으로 제공하고 + 프로젝트별로 논리적으로 구성되며 실행 가능한 정보를 + 강조 표시하도록 설계되어 있습니다. 표준 출력이 리디렉션되지 않는 + 경우에만 터미널 로거를 사용하려면 auto를 지정하거나 + 인수 없이 옵션을 사용합니다. 출력을 구문 분석하지 않으면 + 향후 버전에서도 변경되지 않은 상태로 유지될 것이라고 + 기대하지 마세요. 이 옵션은 MSBuild 17.8 이상 버전에서 제공됩니다. (약식: -tl) @@ -218,21 +218,20 @@ -terminalLoggerParameters: <parameters> 터미널 로거에 대한 매개 변수입니다. (약식: -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 @@ -281,7 +280,7 @@ -getResultOutputFile:file get*에서 파일로 출력을 리디렉션합니다. - 예: + 예: -getProperty:Bar -getResultOutputFile:Biz.txt 그러면 속성 Bar의 값이 Biz.txt에 기록됩니다. @@ -298,7 +297,7 @@ -check 빌드하는 동안 BuildChecks를 사용하도록 설정합니다. - BuildCheck를 사용하면 규칙을 평가하여 빌드의 속성을 + BuildCheck를 사용하면 규칙을 평가하여 빌드의 속성을 확인할 수 있습니다. 자세한 내용은 https://aka.ms/buildcheck 참조 @@ -803,11 +802,11 @@ -logger:<로거> 이 로거를 사용하여 MSBuild의 이벤트를 기록합니다. 여러 로거를 지정하려면 각 로거를 개별적으로 지정합니다. <로거> 구문은 다음과 같습니다. - [<클래스>,]<어셈블리>[,<옵션>][;<매개 변수>] + [<클래스>,]<assembly>[,<옵션>][;<매개 변수>] <로거 클래스> 구문은 다음과 같습니다. [<부분 또는 전체 네임스페이스>.]<로거 클래스 이름> <로거 어셈블리> 구문은 다음과 같습니다. - {<어셈블리 이름>[,<strong name>] | <어셈블리 파일>} + {<assembly name>[,<strong name>] | <assembly file>} 로거 옵션은 MSBuild가 로거를 만드는 방법을 지정합니다. <로거 매개 변수>는 선택 사항이고 입력한 대로 정확히 로거에 전달됩니다. (약식: -l) @@ -890,22 +889,22 @@ Verbosity=minimal -consoleLoggerParameters:<parameters> - 콘솔 로거의 매개 변수. (약식: -clp) + 콘솔 로거에 대한 매개 변수입니다. (약식: -clp) 사용 가능한 매개 변수는 다음과 같습니다. PerformanceSummary--작업, 목표, 프로젝트에 소요된 시간을 표시합니다. - Summary--끝에 오류 및 경고 요약을 표시합니다. - NoSummary--끝에 오류 및 경고 요약을 표시하지 + Summary--오류 및 경고 요약을 마지막에 표시합니다. + NoSummary--오류 및 경고 요약을 마지막에 표시하지 않습니다. ErrorsOnly--오류만 표시합니다. WarningsOnly--경고만 표시합니다. NoItemAndPropertyList--각 프로젝트 빌드를 시작할 때 항목 및 속성 목록을 표시하지 않습니다. - showCommandLine--TaskCommandLineEvent 메시지 표시 + showCommandLine--TaskCommandLineEvent 메시지를 표시합니다. ShowTimestamp--모든 메시지 앞에 타임스탬프를 접두사로 표시합니다. - ShowEventId--시작된 이벤트, 완료된 이벤트 및 메시지의 - 이벤트 ID 표시 + ShowEventId--시작된 이벤트, 완료된 이벤트, 메시지의 + 이벤트 ID를 표시합니다. ForceNoAlign--콘솔 버퍼 크기에 맞게 텍스트를 정렬하지 않습니다. DisableConsoleColor--모든 로깅 메시지에 대해 @@ -1079,11 +1078,11 @@ 로거를 지정하려면 각 로거를 개별적으로 지정합니다. (약식 -dl) <로거> 구문은 다음과 같습니다. - [<클래스>,]<어셈블리>[,<옵션>][;<매개 변수>] + [<클래스>,]<assembly>[,<옵션>][;<매개 변수>] <로거 클래스> 구문은 다음과 같습니다. [<부분 또는 전체 네임스페이스>.]<로거 클래스 이름> <로거 어셈블리> 구문은 다음과 같습니다. - {<어셈블리 이름>[,<strong name>] | <어셈블리 파일>} + {<assembly name>[,<strong name>] | <assembly file>} 로거 옵션은 MSBuild가 로거를 만드는 방법을 지정합니다. <로거 매개 변수>는 선택 사항이고 입력한 대로 정확히 로거에 전달됩니다. (약식: -l) diff --git a/src/MSBuild/Resources/xlf/Strings.pl.xlf b/src/MSBuild/Resources/xlf/Strings.pl.xlf index 05d8a97eb6f..550bf37b305 100644 --- a/src/MSBuild/Resources/xlf/Strings.pl.xlf +++ b/src/MSBuild/Resources/xlf/Strings.pl.xlf @@ -67,10 +67,10 @@ This flag is experimental and may not work as intended. -reportFileAccesses[:True|False] - Powoduje, że program MSBuild zgłasza dostępy do wszystkich skonfigurowanych plików + Powoduje, że platforma MSBuild zgłasza dostępy do wszystkich skonfigurowanych 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. LOCALIZATION: "-reportFileAccesses" should not be localized. @@ -150,8 +150,8 @@ Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami. ciągów „Undefined”, „Available”, „NotAvailable” i „Preview”. — Undefined — dostępność funkcji jest niezdefiniowana - (nazwa funkcji jest nieznana dla dostępności funkcji - kontroler) + (nazwa funkcji jest nieznana dla kontrolera dostępności + funkcji) — 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 @@ -182,12 +182,12 @@ Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami. 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 auto (lub użyj opcji + informacji umożliwiających podejmowanie działań. Określ automatycznie (lub użyj opcji bez argumentów), aby używać rejestratora terminali tylko wtedy, gdy - standardowe dane wyjściowe nie są przekierowywane. Nie analizowanie danych wyjściowych - lub inaczej – poleganie na nich pozostanie niezmienione w przyszłych + standardowe dane wyjściowe nie są przekierowywane. Nie analizuj danych wyjściowych + albo w przeciwnym razie poleganie na nich pozostanie niezmienione w przyszłych wersjach. Ta opcja jest dostępna w wersji MSBuild 17.8 i - późniejszych. + nowszych. (Krótka forma: -tl) @@ -219,17 +219,17 @@ Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami. Parametry rejestratora terminali. (Krótka forma: -tlp) Dostępne parametry. default-- określa domyślne zachowanie rejestratora - terminalu. Wymaga jednej z następujących wartości: - — „on”, „true” wymusza użycie elementu TerminalLogger nawet + terminali. 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ąp ustawienie -verbosity dla tego + verbosity-- zastępuje ustawienie -verbosity dla tego rejestratora - showCommandLine-- pokaż komunikaty TaskCommandLineEvent + showCommandLine-- pokazuje komunikaty TaskCommandLineEvent Przykład: -tlp:default=auto;verbosity=diag;shownCommandLine @@ -254,8 +254,8 @@ Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami. (Short form: -mt) -multithreaded - Włącza tryb EKSPERYMENTALNY wielowątkowości w programie MSBuild. - Oznacza to, że program MSBuild będzie używać wielu wątków + Włącza tryb wielowątkowy EXPERIMENTAL w narzędziach MSBuild. + Oznacza to, że narzędzia MSBuild będą używać wielu wątków do równoległego kompilowania projektów, zamiast wielu procesów. Ta opcja nie jest obsługiwana. @@ -297,7 +297,7 @@ Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami. -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 https://aka.ms/buildcheck + kompilacji. Aby uzyskać więcej informacji, zobacz witrynę https://aka.ms/buildcheck {Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"} @@ -671,7 +671,7 @@ Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami. -noLogo[:true|false] Do not display the startup banner and copyright message. Specify -nologo:false to explicitly show the logo. - -noLogo[:true|false] Nie wyświetlaj baneru startowego ani komunikatu o prawach autorskich. + -noLogo[:true|false] Nie wyświetlaj banera startowego ani komunikatu o prawach autorskich. Użyj -nologo:false, aby wyraźnie pokazać logo. @@ -803,17 +803,14 @@ Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami. -logger:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral -logger:XMLLogger,C:\Loggers\MyLogger.dll;OutputAsHTML - -logger:<rejestrator> 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. + -logger:<rejestrator> 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 <rejestrator>: - [<klasa rejestratora>,]<zestaw rejestratora> - [;<parametry rejestratora>] + [<klasa rejestratora>,]<assembly> [;<parametry rejestratora>] Składnia elementu <klasa rejestratora>: - [<częściowa lub pełna przestrzeń nazw>.] - <nazwa klasy rejestratora> + [<częściowa lub pełna przestrzeń nazw>.] <nazwa klasy rejestratora> Składnia elementu <zestaw rejestratora>: - {<nazwa zestawu>[,<strong name>] | <plik zestawu>} + {<assembly name>[,<strong name>] | <assembly file>} Wartości <parametry rejestratora> są opcjonalne i są przekazywane do rejestratora dokładnie tak, jak zostały wpisane. (Krótka wersja: -l) @@ -898,32 +895,32 @@ Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami. -consoleLoggerParameters:<parameters> Parametry rejestratora konsoli. (Krótka forma: -clp) Dostępne parametry to: - PerformanceSummary — pokaż czas poświęcony na zadania, cele + PerformanceSummary--pokaż czas poświęcony na zadania, grupy docelowe i projekty. - Summary — pokaż podsumowanie błędów i ostrzeżeń na końcu. - NoSummary — nie pokazuj podsumowania błędów i ostrzeżeń na + Summary--pokaż podsumowanie błędów i ostrzeżeń na końcu. + NoSummary--nie pokazuj podsumowania błędów i ostrzeżeń na końcu. - ErrorsOnly — pokaż tylko błędy. - WarningsOnly — pokaż tylko ostrzeżenia. - NoItemAndPropertyList — nie pokazuj listy elementów i + ErrorsOnly--pokaż tylko błędy. + WarningsOnly--pokaż tylko ostrzeżenia. + NoItemAndPropertyList--nie pokazuj listy elementów i właściwości na początku każdej kompilacji projektu. - ShowCommandLine--Show TaskCommandLineEvent wiadomości - ShowTimestamp — wyświetl sygnaturę czasową jako prefiks dowolnej - wiadomości. - ShowEventId — pokaż identyfikator zdarzenia dla rozpoczętych zdarzeń, zakończonych + ShowCommandLine--pokaż komunikaty TaskCommandLineEvent + ShowTimestamp--wyświetl sygnaturę czasową jako prefiks dowolnego + komunikatu. + ShowEventId--pokaż identyfikator zdarzenia dla rozpoczętych zdarzeń, zakończonych zdarzeń i komunikatów - ForceNoAlign — nie powoduje wyrównania tekstu do rozmiaru + ForceNoAlign--nie powoduje wyrównania tekstu do rozmiaru bufora konsoli - DisableConsoleColor — użyj domyślnych kolorów konsoli + DisableConsoleColor--użyj domyślnych kolorów konsoli dla wszystkich komunikatów rejestrowania. EnableMPLogging — włącz styl rejestrowania wieloprocesorowego - nawet w przypadku uruchamiania w środowisku innym niż wieloprocesorowe - tryb. Ten styl rejestrowania jest domyślnie włączony. + nawet w przypadku uruchamiania w trybie innym niż + innym niż wieloprocesorowy. Ten styl rejestrowania jest domyślnie włączony. ForceConsoleColor — użyj kolorów konsoli ANSI, nawet jeśli konsola nie obsługuje tej funkcji PreferConsoleColor — użyj kolorów konsoli ANSI tylko wtedy, gdy konsola docelowa ją obsługuje - Szczegółowość — nadpisuje ustawienie -verbosity dla tego + Verbosity — nadpisuje ustawienie -verbosity dla tego rejestratora. Przykład: -consoleLoggerParameters:PerformanceSummary;NoSummary; @@ -1085,11 +1082,11 @@ Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami. wiele rejestratorów, określ każdy z nich osobno. (Krótka wersja: -dl) Składnia elementu <rejestrator>: - [<klasa rejestratora>,]<zestaw rejestratora>[;<parametry rejestratora>] + [<klasa rejestratora>,]<assembly>[;<parametry rejestratora>] Składnia elementu <klasa rejestratora>: [<częściowa lub pełna przestrzeń nazw>.]<nazwa klasy rejestratora> Składnia elementu <zestaw rejestratora>: - {<nazwa zestawu>[,<strong name>] | <plik zestawu>} + {<assembly name>[,<strong name>] | <assembly file>} Wartości <parametry rejestratora> są opcjonalne i są przekazywane do rejestratora dokładnie tak, jak zostały wpisane. (Krótka wersja: -l) @@ -1201,13 +1198,11 @@ Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami. create a log file for each node. -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<identyfikator węzła>.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 @@ -2108,28 +2103,28 @@ Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami. -bl:..\..\custom.binlog -binaryLogger - -binaryLogger[:[LogFile=]wyjście.binlog[;ProjectImports={None,Embed,ZipFile}]] + -binaryLogger[:[LogFile=]output.binlog[;ProjectImports={None,Embed,ZipFile}]] Serializuje wszystkie zdarzenia kompilacji do skompresowanego pliku binarnego. Domyślnie plik znajduje się w bieżącym katalogu i ma nazwę „msbuild.binlog”. Dziennik binarny to szczegółowy opis procesu kompilacji, którego można później użyć do odtworzenia dzienników tekstowych i wykorzystać w innych narzędziach do analizy. Dziennik binarny - jest zwykle 10–20 razy mniejszy od najbardziej szczegółowych - tekstowych dzienników na poziomie diagnostycznym, ale zawiera więcej informacji. + jest zwykle 10–20 razy mniejszy od najbardziej szczegółowego + dziennika tekstowego na poziomie diagnostycznym, ale zawiera więcej informacji. (Krótka forma: -bl) Opcjonalny LogFile określa ścieżkę, w której zapisany jest dziennik binarny. Aby wygenerować osobny plik dziennika dla każdej kompilacji, można dodać token „{}” do ścieżki, na przykład: LogFile=output-{}-log.binlog. Każdy - „{}” w ścieżce dziennika zostanie zastąpiony unikalnym ciągiem - utworzonym na podstawie znacznika czasu, identyfikatora procesu i losowego - ciągu znaków. + token „{}” w ścieżce dziennika zostanie zastąpiony unikalnym ciągiem + utworzonym na podstawie znacznika czasu, identyfikatora uruchomionego procesu i losowej + sygnatury ciągu. Rejestrator binarny domyślnie zbiera tekst źródłowy plików projektu, w tym wszystkie zaimportowane projekty i pliki - docelowe napotkane podczas kompilowania. Tym zachowaniem - steruje opcjonalny przełącznik ProjectImports: + docelowe napotkane podczas kompilowania. To zachowanie + kontroluje opcjonalny przełącznik ProjectImports: ProjectImports=None — Nie zbieraj importów projektu. @@ -2137,18 +2132,18 @@ Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami. pliku dziennika. ProjectImports=ZipFile — Zapisz pliki projektu w pliku output.projectimports.zip, - gdzie wyjście to ciąg podany - dla nazwy pliku dziennika binarnego. + gdzie wyjście ma taką samą nazwę + jak nazwa pliku dziennika binarnego. Domyślne ustawienie przełącznika ProjectImports to Embed. Uwaga: rejestrator nie zbiera plików źródłowych - niepochodzących z programu MSBuild, np. cs, cpp itd. + narzędzi innych niż MSBuild, np. .cs, .cpp itd. - Plik binlog można „odtworzyć”, przekazując go do programu + Plik .binlog można „odtworzyć”, przekazując go do programu msbuild.exe jako argument zamiast projektu/rozwiązania. Inne rejestratory otrzymają informacje zawarte w pliku - dziennika tak, jak podczas wykonywania pierwotnej kompilacji. - Więcej informacji o dzienniku binarnym i jego zastosowaniach można uzyskać na stronie: + dziennika tak, jakby pierwotna kompilacja wydarzyła się. + Więcej informacji o dzienniku binarnym i jego zastosowaniach można uzyskać w witrynie: https://aka.ms/msbuild/binlog Przykłady: diff --git a/src/MSBuild/Resources/xlf/Strings.pt-BR.xlf b/src/MSBuild/Resources/xlf/Strings.pt-BR.xlf index 88b2c006c88..094b01f2af9 100644 --- a/src/MSBuild/Resources/xlf/Strings.pt-BR.xlf +++ b/src/MSBuild/Resources/xlf/Strings.pt-BR.xlf @@ -67,8 +67,9 @@ This flag is experimental and may not work as intended. -reportFileAccesses[:True|False] - Faz com que o MSBuild relate acessos a arquivos para qualquer plug-in - de cache de projeto configurado. + Faz com que o MSBuild relate acessos a arquivos a qualquer + configurado + plug-ins de cache do projeto. Este sinalizador é experimental e pode não funcionar conforme o esperado. @@ -254,13 +255,13 @@ (Short form: -mt) -multithreaded - Habilita o modo multithread EXPERIMENTAL no MSBuild. + Habilita o modo multithreaded EXPERIMENTAL no MSBuild. Isso significa que o MSBuild usará vários threads para criar projetos em paralelo, em vez de vários processos. Essa opção não tem suporte. O número máximo de threads usados é determinado pela - opção -maxCpuCount. + opção de linha de comando -maxCpuCount. No caso do modo multithread em e MSBUILDFORCEALLTASKSOUTOFPROC=1 maxCpuCount não pode ser maior que 256. @@ -276,7 +277,7 @@ -getProperty:Bar -getResultOutputFile:Biz.txt This writes the value of property Bar into Biz.txt. - -getResultOutputFile:file + -getResultOutputFile:arquivo Redirecionar a saída de get* para um arquivo. Exemplo: @@ -903,7 +904,7 @@ arquivo de resposta. ShowCommandLine--Mostrar mensagens do TaskCommandLineEvent ShowTimestamp--Exibir o Timestamp como prefixo de qualquer mensagem. - ShowEventId--Mostrar eventId para eventos iniciados, + ShowEventId--Mostrar eventId para eventos iniciados eventos concluídos e mensagens ForceNoAlign--Não alinha o texto ao tamanho do buffer do console diff --git a/src/MSBuild/Resources/xlf/Strings.ru.xlf b/src/MSBuild/Resources/xlf/Strings.ru.xlf index 76f95202e52..1ba4bfea7b4 100644 --- a/src/MSBuild/Resources/xlf/Strings.ru.xlf +++ b/src/MSBuild/Resources/xlf/Strings.ru.xlf @@ -147,7 +147,7 @@ -featureAvailability:featureName,... Проверьте доступность функции. Результатом является одна из - строк "Неопределено", "Доступно", "Недоступно" и + строк "Не определено", "Доступно", "Недоступно" и "Предварительный просмотр". - Не определено — доступность функции не определена (имя функции неизвестно средству проверки доступности @@ -220,18 +220,18 @@ Доступные параметры. по умолчанию — определяет поведение логгера терминала. Требуется одно из следующих значений: - - `on`, `true` заставляет использовать TerminalLogger даже + - "on", "true" заставляет использовать TerminalLogger даже когда он будет отключен. - - `off`, `false` запрещает использование TerminalLogger + - "off", "false" запрещает использование TerminalLogger даже если бы он был включен. - - `auto` включает TerminalLogger, когда терминал + - "auto" включает TerminalLogger, когда терминал поддерживает это, и в сеансе нет перенаправления stdout/stderr verbosity – Переопределить параметр -verbosity для этого терминала showCommandLine — Показать сообщения TaskCommandLineEvent - Пример: + Пример: -tlp:default=auto;verbosity=diag;shownCommandLine @@ -261,8 +261,8 @@ Этот параметр не поддерживается. Максимальное количество используемых потоков определяется параметром -maxCpuCount. - Если многопоточный режим включён - и MSBUILDFORCEALLTASKSOUTOFPROC=1 + Если многопоточный режим включен + и MSBUILDFORCEALLTASKSOUTOFPROC=1, maxCpuCount не может быть больше 256. (Краткая форма: -mt) @@ -326,7 +326,7 @@ MSBUILD : error MSB1065: Terminal logger value is not valid. It should be one of 'auto', 'true', or 'false'. {0} - MSBUILD : error MSB1065: недопустимое значение регистратора терминала. Это должно быть одно из значений: "auto", "true" или "false". {0} + MSBUILD : error MSB1065: Недопустимое значение средства ведения журнала терминала. Это должно быть одно из следующих значений: "auto", "ИСТИНА" или "ЛОЖЬ". {0} {StrBegin="MSBUILD : error MSB1065: "} UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg. @@ -666,7 +666,7 @@ Specify -nologo:false to explicitly show the logo. -noLogo[:true|false] Не отображать баннер запуска и сообщение об авторских правах. - Укажите -nologo:false, чтобы явно показать логотип. + Укажите -nologo:false, чтобы явным образом показать логотип. LOCALIZATION: The following should not be localized: @@ -889,8 +889,8 @@ -consoleLoggerParameters:<параметры> Параметры журнала консоли. (Краткая форма: -clp) Доступны следующие параметры: - PerformanceSummary--выводить время, затраченное на выполнение задач, целевых объектов - и проектов. + PerformanceSummary--выводить время, затраченное на выполнение задач, + целевых объектов и проектов. Summary--выводить сводку ошибок и предупреждений по завершении работы. NoSummary--не выводить сводку ошибок и предупреждений по завершении работы. @@ -1571,7 +1571,7 @@ MSBUILD : error MSB1068: Must provide a file for the getResultOutputFile switch. - MSBUILD : error MSB1068: необходимо указать файл для параметра getResultOutputFile. + MSBUILD : error MSB1068: необходимо предоставить файл для переключателя getResultOutputFile. {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". @@ -2127,13 +2127,13 @@ ProjectImports=Embed — внедрять импортированные файлы проекта в файл журнала. ProjectImports=ZipFile — сохранять файлы проекта в - вывод.projectimports.zip, - где вывод — это то же имя, + output.projectimports.zip, + где output — это то же имя, что и у двоичного файла журнала. Значение по умолчанию для ProjectImports — Embed. Примечание: средство ведения журнала не собирает исходные файлы, не от MSBuild, - например с расширениями CS, CPP и др. + например с расширениями CS, CPP и т. д. BINLOG-файл можно "воспроизвести", передав его в msbuild.exe в качестве аргумента вместо проекта или решения. diff --git a/src/MSBuild/Resources/xlf/Strings.tr.xlf b/src/MSBuild/Resources/xlf/Strings.tr.xlf index 9f477ca8464..b8bce363fd1 100644 --- a/src/MSBuild/Resources/xlf/Strings.tr.xlf +++ b/src/MSBuild/Resources/xlf/Strings.tr.xlf @@ -253,7 +253,7 @@ maxCpuCount cannot be greater than 256. (Short form: -mt) - -çok iş parçacıklı + -multithreaded MSBuild’de DENEYSEL çok iş parçacıklı modu etkinleştirir. Bu, MSBuild’in projeleri işlemek için birden çok iş parçacığı kullanacağı, @@ -295,9 +295,9 @@ of the build. For more info see https://aka.ms/buildcheck -check - Derleme sırasında BuildChecks'i sağlar. - BuildCheck, özelliklerin güvenliğini sağlamak için kuralların değerlendirilmesini sağlar - kuralların değerlendirilmesini sağlar. Daha fazla bilgi için bkz. https://aka.ms/buildcheck + Derleme sırasında BuildChecks seçeneğini etkinleştirir. + BuildCheck, derleme özelliklerini sağlamak için kuralların + değerlendirilmesini sağlar. Daha fazla bilgi için bkz. https://aka.ms/buildcheck {Locked="-check"}{Locked="BuildChecks"}{Locked="BuildCheck"} @@ -801,13 +801,13 @@ -logger:<günlükçü> 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. <günlükçü> söz dizimi şöyledir: - [<sınıf>,]<derleme>[,<seçenekler>][;<parametreler>] + [<class>,]<assembly>[,<options>][;<parameters>] <günlükçü sınıfı > söz dizimi şöyledir: [<kısmi veya tam ad alanı >.]<günlükçü sınıfı adı> <günlükçü derlemesi> söz dizimi şöyledir: - {<derleme adı>[,<strong name>] | <derleme dosyası>} + {<assembly name>[,<strong name>] | <assembly file>} Günlükçü seçenekleri, MSBuild'in günlükçüyü oluşturma biçimini belirtir. - <günlükçü parametreleri > isteğe bağlıdır ve tam olarak + <günlükçü parametreleri > isteğe bağlıdır ve tam olarak yazdığınız şekliyle günlükçüye geçirilir. (Kısa biçim: -l) Örnekler: -logger:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral @@ -888,29 +888,29 @@ Verbosity=minimal -consoleLoggerParameters:<parameters> - Konsol günlüğüne parametreler. (Kısa form: -clp) + Konsol günlükçüsüne giden parametreler. (Kısa form: -clp) Kullanılabilir parametreler şunlardır: - PerformanceSummary--Harcanan süreyi göster, görevler - ve projeler. - Summary--Sonunda hata ve uyarı özetini göster. - NoSummary--Hata ve uyarı özetini - sonunda gösterme. + PerformanceSummary--Görevlerde, hedeflerde ve + projelerde harcanan süreyi göster. + Summary--Sonda hata ve uyarı özetini göster. + NoSummary--Sonda hata ve uyarı özetini + gösterme. ErrorsOnly--Yalnızca hataları göster. WarningsOnly--Yalnızca uyarıları göster. NoItemAndPropertyList--Öğe ve özelliklerin listesini her proje derlemesinin başında gösterme. - ShowCommandLine--TaskCommandLineEvent mesajlarını göster - ShowTimestamp--Zaman damgasını herhangi bir - mesajın başına önek olarak göster. + ShowCommandLine--TaskCommandLineEvent iletilerini göster + ShowTimestamp--Zaman damgasını her + iletinin başında önek olarak göster. ShowEventId--Başlatılan olaylar, tamamlanan olaylar - ve mesajlar için olay kimliğini göster - ForceNoAlign--Metni konsol arabelleğinin - boyutuna hizalama yapmaz - DisableConsoleColor--Tüm günlük mesajları için - varsayılan konsol renklerini kullanın. + ve iletiler için olay kimliğini göster + ForceNoAlign--Metni konsol arabelleğinin boyutuna göre + uyarlama + DisableConsoleColor--Tüm günlük iletileri için + varsayılan konsol renklerini kullan. EnableMPLogging--Çok işlemcili modda olmayan sistemlerde bile çok işlemcili günlük kaydı stilini - etkinleştirir. Bu günlük kaydı stili varsayılan olarak açıktır. + etkinleştir. Bu günlük kaydı stili varsayılan olarak açıktır. ForceConsoleColor--Konsol desteklemiyor olsa bile ANSI konsol renklerini kullan PreferConsoleColor--Hedef konsol destekliyorsa @@ -1077,11 +1077,11 @@ günlükçü belirtmek için her günlükçüyü ayrı ayrı belirtin. (Kısa biçim -dl) <günlükçü> söz dizimi şöyledir: - [<sınıf>,]<derleme>[,<seçenekler>][;<parametreler>] + [<sınıf>,]<assembly>[,<seçenekler>][;<parametreler>] <günlükçü sınıfı> söz dizimi şöyledir: [<kısmi veya tam ad alanı>.]<günlükçü sınıfı adı> <günlükçü derlemesi> söz dizimi şöyledir: - {<derleme adı>[,<strong name>] | <derleme dosyası>} + {<assembly name>[,<strong name>] | <assembly file>} Günlükçü seçenekleri, MSBuild'in günlükçüyü oluşturma biçimini belirtir. <günlükçü parametreleri> isteğe bağlıdır ve tam olarak yazdığınız şekliyle günlükçüye geçirilir. (Kısa biçim: -l) @@ -1108,10 +1108,9 @@ -ignoreProjectExtensions:.sln -ignoreProjectExtensions:<uzantılar> - 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. + 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. (Kısa biçim: -ignore) Örnek: -ignoreProjectExtensions:.sln @@ -1201,7 +1200,6 @@ 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ı @@ -1248,32 +1246,31 @@ -fileLoggerParameters[n]:<parametreler> Dosya günlükçüleri için ek parametreler sağlar. - Bu anahtarın olması karşılık gelen -fileLogger[n] + Bu anahtarın olması karşılık gelen -fileLogger[n] 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. + Dağıtılmış dosya günlükçüleri varsa -fileLoggerParameters + 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 + Konsol günlükçüsü için listelenenlerle aynı parametreler kullanılabilir. Kullanılabilecek bazı ek parametreler: - LogFile--Oluşturma günlüğünün yazılacağı günlük + LogFile--Oluşturma günlüğünün yazılacağı günlük dosyasının yolu. - Append--Derleme günlüğünün gün dosyasının sonuna mı - ekleneceğini yoksa üzerine mi yazılacağını - belirler. Anahtar ayarlandığında oluşturma günlüğü - dosyanın sonuna eklenir. Anahtar ayarlanmadığında - varolan günlük dosyasının üzerine yazılır. + Append--Derleme günlüğünün gün dosyasının sonuna mı + ekleneceğini yoksa üzerine mi yazılacağını + belirler. Anahtar ayarlandığında oluşturma günlüğü + dosyanın sonuna eklenir. Anahtar ayarlanmadığında + varolan günlük dosyasının üzerine yazılır. Varsayılan: günlük dosyasının sonuna eklenmez. - Encoding--Dosyanın kodlamasını belirtir; örneğin, + Encoding--Dosyanın kodlamasını belirtir; örneğin, UTF-8, Unicode veya ASCII Varsayılan ayrıntı düzeyi ayarı Detailed'dır. Örnekler: -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 @@ -1297,8 +1294,7 @@ -nr:true -nodeReuse:<parametreler> - 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) @@ -1647,7 +1643,7 @@ MSBUILD : error MSB1066: Specify one or more parameters for the terminal logger if using the -terminalLoggerParameters switch - MSBUILD : error MSB1066: -terminalLoggerParameters anahtarı kullanılıyorsa terminal günlükçüsü için bir veya birden çok parametre belirtin + MSBUILD : error MSB1066: terminalLoggerParameters anahtarı kullanılıyorsa terminal günlükçüsü için bir veya birden çok parametre belirtin {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 @@ -1786,7 +1782,7 @@ 2: in evaluation. It is recommended to turn off Smart App Control in development environemnt as otherwise performance might be impacted - 2: değerlendirmede. Aksi takdirde performansın etkilenebileceği için geliştirme ortamında Akıllı Uygulama Denetimi’nin kapatılması önerilir + 2: değerlendirmede. Aksi takdirde performans etkilenebileceği için geliştirme ortamında Akıllı Uygulama Denetiminin kapatılması önerilir Smart App Control, "VerifiedAndReputablePolicyState" should not be localized diff --git a/src/MSBuild/Resources/xlf/Strings.zh-Hans.xlf b/src/MSBuild/Resources/xlf/Strings.zh-Hans.xlf index b76b30b3932..2825d842949 100644 --- a/src/MSBuild/Resources/xlf/Strings.zh-Hans.xlf +++ b/src/MSBuild/Resources/xlf/Strings.zh-Hans.xlf @@ -85,11 +85,11 @@ used, write out the values after the build. -getProperty:propertyName,... - 在计算后写出一个或多个指定属性的值， - 但不执行生成，或者如果使用的是 - -targets 选项或 -getTargetResult 选项， - 则在生成后写出这些值。 - + 在计算后写出一个或多个指定属性的值， + 但不执行生成，或者如果使用的是 + -targets 选项或 -getTargetResult 选项， + 则在生成后写出这些值。 + 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. @@ -104,12 +104,12 @@ the values after the build. -getItem:itemName,... - 在计算后写出一个或多个指定项的值及其 - 关联的元数据，但不 - 执行生成，或者如果使用的是 -targets 选项 - 或 -getTargetResult 选项，则在生成后写出 - 这些值。 - + 在计算后写出一个或多个指定项的值及其 + 关联的元数据，但不 + 执行生成，或者如果使用的是 -targets 选项 + 或 -getTargetResult 选项，则在生成后写出 + 这些值。 + 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. @@ -121,9 +121,9 @@ the specified targets will be executed. -getTargetResult:targetName,... - 写出一个或多个目标的输出值， - 并且将执行指定的目标。 - + 写出一个或多个目标的输出值， + 并且将执行指定的目标。 + LOCALIZATION: "-getTargetResult" should not be localized. LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars. @@ -146,20 +146,20 @@ (Short form: -fa) -featureAvailability:featureName,... - 检查功能可用性。结果是以下字符串之一: - "Undefined"、"Available"、"NotAvailable" 和 - "Preview"。 - - Undefined - 未定义功能的可用性 - (功能可用性检查器不知道 - 该功能名称) - - NotAvailable - 功能不可用(不同于 - Undefined，功能可用性检查器知道 - 该功能名称，并且还知道该功能不 - 受当前 MSBuild 引擎支持) - - Available - 功能可用 - - Preview - 功能处于预览状态(不稳定) - (缩写: -fa) - + 检查功能可用性。结果是以下字符串之一: + "Undefined"、"Available"、"NotAvailable" 和 + "Preview"。 + - Undefined - 未定义功能的可用性 + (功能可用性检查器不知道 + 该功能名称) + - NotAvailable - 功能不可用(不同于 + Undefined，功能可用性检查器知道 + 该功能名称，并且还知道该功能不 + 受当前 MSBuild 引擎支持) + - Available - 功能可用 + - Preview - 功能处于预览状态(不稳定) + (缩写: -fa) + 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. @@ -179,17 +179,17 @@ (Short form: -tl) -terminalLogger[:auto,on,off] - 启用或禁用终端记录器。终端记录器 - 在控制台上实时提供增强的生成输出， - 这些输出在逻辑上按项目进行整理，旨在突出显示 - 可操作信息。指定 auto (或使用 - 不带参数的选项)，仅在标准输出未重定向的情况下 - 使用终端记录器。不要分析输出， - 也不要依赖于它在将来的版本中保持 - 不变。此选项在 MSBuild 17.8 和 - 更高版本中提供。 - (缩写: -tl) - + 启用或禁用终端记录器。终端记录器 + 在控制台上实时提供增强的生成输出， + 这些输出在逻辑上按项目进行整理，旨在突出显示 + 可操作信息。指定 auto (或使用 + 不带参数的选项)，仅在标准输出未重定向的情况下 + 使用终端记录器。不要分析输出， + 也不要依赖于它在将来的版本中保持 + 不变。此选项在 MSBuild 17.8 和 + 更高版本中提供。 + (缩写: -tl) + 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. @@ -216,24 +216,24 @@ -tlp:default=auto;verbosity=diag;shownCommandLine -terminalLoggerParameters: <parameters> - 终端记录器的参数。(缩写: -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 - + 示例: + -tlp:default=auto;verbosity=diag;shownCommandLine + 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. @@ -278,12 +278,12 @@ This writes the value of property Bar into Biz.txt. -getResultOutputFile:file - 将 get* 的输出重定向到文件中。 + 将 get* 的输出重定向到文件中。 - 示例: - -getProperty:Bar -getResultOutputFile:Biz.txt - 这会将属性 Bar 的值写入 Biz.txt。 - + 示例: + -getProperty:Bar -getResultOutputFile:Biz.txt + 这会将属性 Bar 的值写入 Biz.txt。 + 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. @@ -296,8 +296,8 @@ of the build. For more info see https://aka.ms/buildcheck -check - 在生成期间用 BuildChecks。 - 通过 BuildCheck，可以评估规则以确保生成的 + 在生成期间启用 BuildChecks。 + BuildCheck 支持评估规则以确保生成的 属性。有关详细信息，请参阅 https://aka.ms/buildcheck @@ -899,8 +899,8 @@ ErrorsOnly--仅显示错误。 WarningsOnly--仅显示警告。 NoItemAndPropertyList-- - 在开始生成每个项目时不显示内容和属性列表。 - ShowCommandLine--Show TaskCommandLineEvent messages + 在开始生成每个项目时不显示项和属性的列表。 + ShowCommandLine--显示 TaskCommandLineEvent 消息 ShowTimestamp--将时间戳显示为所有消息的 前缀。 ShowEventId--显示已开始事件、已完成事件和消息 @@ -911,7 +911,7 @@ 用于所有记录消息。 EnableMPLogging--启用多处理器日志记录样式， 即使在非多处理器 - 模式中也一样。默认情况下启用此日志记录样式。 + 日志记录样式。默认情况下启用此日志记录样式。 ForceConsoleColor--使用 ANSI 控制台颜色，即使 控制台不支持它也一样 ForceConsoleColor--尽在目标控制台支持的情况下使用 ANSI 控制台颜色 diff --git a/src/MSBuild/Resources/xlf/Strings.zh-Hant.xlf b/src/MSBuild/Resources/xlf/Strings.zh-Hant.xlf index ceeaa6b7686..dc84d162572 100644 --- a/src/MSBuild/Resources/xlf/Strings.zh-Hant.xlf +++ b/src/MSBuild/Resources/xlf/Strings.zh-Hant.xlf @@ -85,11 +85,11 @@ used, write out the values after the build. -getProperty:propertyName,... - 於評估後，寫出一或多個指定屬性的值，以及 - 但不執行建置；如有使用 - -targets 選項或 -getTargetResult 選項， - 便於建置之後，再寫出這些值。 - + 於評估後，寫出一或多個指定屬性的值，以及 + 但不執行建置；如有使用 + -targets 選項或 -getTargetResult 選項， + 便於建置之後，再寫出這些值。 + 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. @@ -104,12 +104,12 @@ the values after the build. -getItem:itemName,... - 於評估後，寫出一或多個指定項目的值，以及 - 其相關的中繼資料，但不 - 執行建置；如有使用 -targets 選項 - 或 -getTargetResult 選項， - 便於建置之後，再寫出這些值。 - + 於評估後，寫出一或多個指定項目的值，以及 + 其相關的中繼資料，但不 + 執行建置；如有使用 -targets 選項 + 或 -getTargetResult 選項， + 便於建置之後，再寫出這些值。 + 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. @@ -121,9 +121,9 @@ the specified targets will be executed. -getTargetResult:targetName,... - 寫出一或多個目標的輸出值，然後 - 執行指定的目標。 - + 寫出一或多個目標的輸出值，然後 + 執行指定的目標。 + LOCALIZATION: "-getTargetResult" should not be localized. LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars. @@ -146,20 +146,20 @@ (Short form: -fa) -featureAvailability:featureName,... - 檢查功能可用性。結果會是下列其中一個字串: - “Undefined”、“Available”、“NotAvailable” 和 - "Preview"。 - - Undefined - 功能的可用性未定義 - (功能可用性檢查程式不知道 - 該功能名稱) - - NotAvailable - 此功能無法使用 (不同於 - Undefined，功能可用性檢查程式知道該功能名稱， - 並知道功能目前的 - MSBuild 引擎不支援該功能) - - Available - 此功能可以使用 - - Preview - 此功能目前為預覽狀態 (不穩定) - (簡短形式: -fa) - + 檢查功能可用性。結果會是下列其中一個字串: + “Undefined”、“Available”、“NotAvailable” 和 + "Preview"。 + - Undefined - 功能的可用性未定義 + (功能可用性檢查程式不知道 + 該功能名稱) + - NotAvailable - 此功能無法使用 (不同於 + Undefined，功能可用性檢查程式知道該功能名稱， + 並知道功能目前的 + MSBuild 引擎不支援該功能) + - Available - 此功能可以使用 + - Preview - 此功能目前為預覽狀態 (不穩定) + (簡短形式: -fa) + 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. @@ -179,17 +179,17 @@ (Short form: -tl) -terminalLogger[:auto,on,off] - 啟用或停用終端機記錄器。終端機記錄器 - 會即時在主機上，提供更進一步的組建輸出， - 並依照專案的邏輯編排，並會醒目提示 - 可採取動作的資訊。指定自動 (或只使用選項， - 不使用引數) 只在使用標準輸出 - 未重新導向時，才使用終端機記錄器。不剖析輸出， - 或以其他方式據此在 - 未來的版本中保持不變。此選項可在 MSBuild 17.8 和 - 更新版本中使用。 - (簡短形式: -tl) - + 啟用或停用終端機記錄器。終端機記錄器 + 會即時在主機上，提供更進一步的組建輸出， + 並依照專案的邏輯編排，並會醒目提示 + 可採取動作的資訊。指定自動 (或只使用選項， + 不使用引數) 只在使用標準輸出 + 未重新導向時，才使用終端機記錄器。不剖析輸出， + 或以其他方式據此在 + 未來的版本中保持不變。此選項可在 MSBuild 17.8 和 + 更新版本中使用。 + (簡短形式: -tl) + 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. @@ -216,24 +216,24 @@ -tlp:default=auto;verbosity=diag;shownCommandLine -terminalLoggerParameters: <parameters> - 終端機記錄器的參數。(簡短形式: -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 LOCALIZATION: "-terminalLoggerParameters", "-tlp", "default", "on", "true", "off", "false", "auto", "verbosity", "showCommandLine" should not be localized. @@ -261,7 +261,7 @@ 而不是使用多個處理序。 不支援此選項。 使用的執行緒數量上限由 - -maxCpuCount 切換開關決定。 + -maxCpuCount 切換決定。 若啟用多執行緒模式 且 MSBUILDFORCEALLTASKSOUTOFPROC=1， maxCpuCount 不得超過 256。 @@ -278,12 +278,12 @@ This writes the value of property Bar into Biz.txt. -getResultOutputFile:file - 將輸出從 get* 重新導向至檔案。 + 將輸出從 get* 重新導向至檔案。 - 範例: - -getProperty:Bar -getResultOutputFile:Biz.txt - 這會將屬性列的值寫入 Biz.txt。 - + 範例: + -getProperty:Bar -getResultOutputFile:Biz.txt + 這會將屬性列的值寫入 Biz.txt。 + 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. @@ -802,11 +802,11 @@ -logger:<記錄器> 使用此記錄器可記錄 MSBuild 的事件。 若要指定多個記錄器，請各別指定每個記錄器。 <記錄器> 語法為: - [<類別>,]<組件>[,<選項>][;<參數>] + [<class>,]<assembly>[,<options>][;<parameters>] <記錄器類別> 語法為: [<一部分或完整的命名空間>.]<記錄器類別名稱> <記錄器組件> 語法為: - {<組件名稱>[,<strong name>] | <組件檔案>} + {<assembly name>[,<strong name>] | <assembly file>} 記錄器選項會指定 MSBuild 建立記錄器的方式。 <記錄器參數> 是選擇性參數，其會依您輸入的內容， 完全一樣地傳遞到記錄器。(簡短形式: -l) @@ -891,33 +891,33 @@ -consoleLoggerParameters:<parameters> 主控台記錄器的參數。(簡短形式: -clp) 可用的參數為: - PerformanceSummary--顯示工作、目標 - 及專案所花費的時間。 + PerformanceSummary--顯示在工作、目標 + 及專案中所耗費的時間。 Summary--結束時顯示錯誤與警告摘要。 NoSummary--結束時不顯示錯誤 與警告摘要。 ErrorsOnly--只顯示錯誤。 WarningsOnly--只顯示警告。 - NoItemAndPropertyList--不在每個專案開始建置時， - 顯示專案與屬性清單。 + NoItemAndPropertyList--不在每個專案開始建置時 + 顯示項目與屬性清單。 ShowCommandLine--顯示 TaskCommandLineEvent 訊息 - ShowTimestamp--在所有訊息開頭顯示 - 時間戳記。 - ShowEventId--顯示已開始之事件、已完成之事件 + ShowTimestamp--將時間戳記顯示為任何 + 訊息的前置詞。 + ShowEventId--顯示已開始、已完成事件 以及訊息的事件識別碼 ForceNoAlign--不將文字調整成主控台 緩衝區的大小 - DisableConsoleColor--為所有記錄訊息使用預設的 + DisableConsoleColor--針對所有記錄訊息使用預設的 主控台色彩。 - EnableMPLogging--在非多處理器模式下執行時， - 啟用多處理器記錄樣式。 - 此記錄樣式預設為啟用。 - ForceConsoleColor--即使主控台不支援 ANSI 主控台色彩， - 也一律使用該色彩 - PreferConsoleColor--僅在目標主控台目標確實支援 ANSI 主控台色彩時 - 才使用它 + EnableMPLogging--即使在非多處理器模式下 + 執行時，也啟用多處理器記錄樣式 + 。此記錄樣式預設為啟用。 + ForceConsoleColor--即使主控台不支援， + 也使用 ANSI 主控台色彩 + PreferConsoleColor--只有在目標主控台 + 確實支援時，才使用 ANSI 主控台色彩 Verbosity--覆寫此記錄器的 -verbosity - 設定。 + 設定。 範例: -consoleLoggerParameters:PerformanceSummary;NoSummary; Verbosity=minimal @@ -1078,11 +1078,11 @@ 若要指定多個記錄器，請各別指定每個記錄器。 (簡短形式 -dl) <記錄器> 語法為: - [<類別>,]<組件>[,<選項>][;<參數>] + [<class>,]<assembly>[,<options>][;<parameters>] <記錄器類別> 語法為: [<一部分或完整的命名空間>.]<記錄器類別名稱> <記錄器組件> 語法為: - {<組件名稱>[,<strong name>] | <組件檔案>} + {<assembly name>[,<strong name>] | <assembly file>} 記錄器選項會指定 MSBuild 建立記錄器的方式。 <記錄器參數> 是選擇性參數，其會依您輸入的內容， 完全一樣地傳遞到記錄器。(簡短形式: -l) @@ -1783,7 +1783,7 @@ 2: in evaluation. It is recommended to turn off Smart App Control in development environemnt as otherwise performance might be impacted - 2: 評估中。建議關閉開發環境中的智慧型手機應用程式控制件，否則效能可能會受到影響 + 2: 評估中。建議關閉開發環境中的智慧型應用程式控制，否則效能可能會受到影響 Smart App Control, "VerifiedAndReputablePolicyState" should not be localized @@ -2100,45 +2100,45 @@ -binaryLogger -binaryLogger[:[LogFile=]output.binlog[;ProjectImports={None,Embed,ZipFile}]] - 將所有組建活動序列化為壓縮的二進位檔案。 + 將所有組建事件序列化為壓縮的二進位檔案。 根據預設，檔案位於目前的目錄中，且名為 - "msbuild.binlog"。二進位記錄檔是詳細描述 - 說明建組程序，這稍後可用來重新建構 - 文字記錄檔，並用於其他分析工具。二進位記錄檔 - 通常比最詳細文字診斷層級記錄檔小 10-20x + "msbuild.binlog"。二進位記錄檔是建置處理序的 + 詳細描述，稍後可用來重新建構 + 文字記錄檔，並供其他分析工具使用。二進位記錄檔 + 通常比最詳細文字診斷層級記錄檔小 10-20 倍 ，但它包含更多資訊。 (簡短形式: -bl) 選擇性的 LogFile 會指定儲存 - 二進位記錄檔位置的路徑。若要針對每個組建，產生不同的記錄檔 - ，可以將權杖 "{}" 新增至 + 二進位記錄檔位置的路徑。若要針對每個組建產生不同的 + 記錄檔，可以將權杖 "{}" 新增至 路徑，例如: LogFile=output-{}-log.binlog。記錄檔路徑中的 - 每個 "{}" 會使用時間戳記，取代為唯一字串 - 執行程序識別碼和隨機 - 字串戳記。 + 每個 "{}" 會使用時間戳記、 + 執行中處理序識別碼和隨機字串戳記 + 取代為唯一的字串。 - 二進位記錄程式預設會收集專案檔案的來源文字 - ，包括組建期間所發生的所有匯入的專案和目標 - 檔案。選擇性 + 二進位記錄程式預設會收集專案檔案的 + 來源文字，包括建置期間所發生的所有 + 匯入的專案和目標檔案。選用的 ProjectImports 切換可控制此行為: ProjectImports=None - 不要收集專案 匯入。 - ProjectImports=Embed - 記錄檔中的 + ProjectImports=Embed - 在記錄檔中 內嵌專案匯入。 ProjectImports=ZipFile - 將專案檔案儲存至 output.projectimports.zip - 其中輸出與二進位檔案名稱具有 + 其中的輸出為與二進位檔案名稱 相同的名稱。 - ProjectImports 的預設設定為 [內嵌]。 + ProjectImports 的預設設定為 Embed。 注意: 記錄程式不會收集非 MSBuild 來源檔案 例如 .cs、.cpp 等。 .binlog 檔案可以藉由將其傳遞至 - msbuild.exe 作為引數 (而不是專案/解決方案) 來 "回放"。 + msbuild.exe 作為引數 (而不是專案/解決方案) 來「重播」。 其他記錄程式將會收到記錄檔中包含的資訊， - 就像發生原始組建那樣。 + 就像正在發生原始建置一般。 您可以在以下位置閱讀更多關於二進位記錄及其使用方式: https://aka.ms/msbuild/binlog diff --git a/src/MSBuildTaskHost/Resources/xlf/SR.cs.xlf b/src/MSBuildTaskHost/Resources/xlf/SR.cs.xlf index bb7a286e7bb..b8d4469ae10 100644 --- a/src/MSBuildTaskHost/Resources/xlf/SR.cs.xlf +++ b/src/MSBuildTaskHost/Resources/xlf/SR.cs.xlf @@ -4,57 +4,57 @@ MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: Hostitel úlohy nástroje MSBuild nepodporuje spouštění úloh, které provádějí zpětná volání rozhraní IBuildEngine. Pokud chcete tyto operace provádět, spusťte svou úlohu v hlavním procesu nástroje MSBuild. Úloha bude automaticky provedena v hostiteli úlohy, pokud v deklaraci UsingTask byly použity atributy s hodnotami Runtime nebo Architecture nebo pokud pro volání úlohy byly použity atributy s hodnotami MSBuildRuntime nebo MSBuildArchitecture, které neodpovídají aktuálnímu modulu runtime nebo architektuře nástroje MSBuild. + MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: Bylo nalezeno konfliktní sestavení pro sestavení úlohy {0} v umístění {1}. + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - Očekávalo se, že typ události {0} bude možné serializovat pomocí serializátoru .NET. Událost nebylo možné serializovat a byla ignorována. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. Making the following modifications to the environment received from the parent node before applying it to the task host: - Předtím, než bude pro hostitele úlohy použito prostředí přijaté z nadřazeného uzlu, budou provedeny jeho následující úpravy: + Making the following modifications to the environment received from the parent node before applying it to the task host: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - Nastavení proměnné {0} na hodnotu {1} místo hodnoty {2} proměnné prostředí nadřazeného uzlu + Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Cesta: {0} překračuje maximální limit pro cestu k OS. Plně kvalifikovaný název souboru musí být kratší než {1} znaků. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. "{0}" is a reserved item metadata, and cannot be modified or deleted. - "{0}" jsou vyhrazená metadata položky a nemohou být změněna nebo smazána. + "{0}" is a reserved item metadata, and cannot be modified or deleted. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Metadata položky %({0}) nelze použít na cestu {1}. {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: Úloha {0} byla označena atributem LoadInSeparateAppDomain, není ale odvozena od třídy MarshalByRefObject. Zkontrolujte, jestli je úloha odvozena od třídy MarshalByRefObject nebo AppDomainIsolatedTask. + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. Parameter "{0}" cannot be null. - Parametr {0} nesmí mít hodnotu Null. + Parameter "{0}" cannot be null. Parameter "{0}" cannot have zero length. - Parametr {0} nesmí mít nulovou délku. + Parameter "{0}" cannot have zero length. diff --git a/src/MSBuildTaskHost/Resources/xlf/SR.de.xlf b/src/MSBuildTaskHost/Resources/xlf/SR.de.xlf index ce1f99f0250..61d83caab37 100644 --- a/src/MSBuildTaskHost/Resources/xlf/SR.de.xlf +++ b/src/MSBuildTaskHost/Resources/xlf/SR.de.xlf @@ -4,57 +4,57 @@ MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: Der MSBuild-Aufgabenhost unterstützt das Ausführen von Aufgaben nicht, die IBuildEngine-Rückrufe tätigen. Führen Sie Ihre Aufgabe stattdessen im MSBuild-Kernprozess aus, wenn Sie diese Vorgänge durchführen möchten. Wenn UsingTask mit einem Runtime- oder Architecture-Wert oder der Aufgabenaufruf mit einem MSBuildRuntime- oder MSBuildArchitecture-Wert attribuiert wurde, der nicht mit der aktuellen Laufzeit oder Architektur von MSBuild übereinstimmt, wird eine Aufgabe automatisch im Aufgabenhost ausgeführt. + MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: Eine mit der Aufgabenassembly "{0}" in Konflikt stehende Assembly wurde in "{1}" gefunden. + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - Es wurde erwartet, dass der Ereignistyp "{0}" mithilfe des .NET-Serialisierers serialisierbar ist. Das Ereignis war nicht serialisierbar und wurde ignoriert. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. Making the following modifications to the environment received from the parent node before applying it to the task host: - Es werden folgende vom übergeordneten Knoten empfangene Änderungen an der Umgebung vorgenommen, bevor sie auf den Aufgabenhost angewendet wird: + Making the following modifications to the environment received from the parent node before applying it to the task host: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - Festlegen von "{0}" auf "{1}" statt auf den Wert "{2}" der übergeordneten Umgebung. + Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Der Pfad "{0}" überschreitet das maximale Pfadlimit des Betriebssystems. Der vollqualifizierte Dateiname muss weniger als {1} Zeichen umfassen. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. "{0}" is a reserved item metadata, and cannot be modified or deleted. - "{0}" sind reservierte Elementmetadaten, die nicht geändert oder gelöscht werden können. + "{0}" is a reserved item metadata, and cannot be modified or deleted. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Die %({0})-Elementmetadaten können nicht auf den Pfad "{1}" angewendet werden. {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: Die Aufgabe "{0}" wurde mit dem LoadInSeparateAppDomain-Attribut markiert, ist jedoch nicht von MarshalByRefObject abgeleitet. Stellen Sie sicher, dass die Aufgabe von MarshalByRefObject oder AppDomainIsolatedTask abgeleitet wird. + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. Parameter "{0}" cannot be null. - Der Parameter "{0}" darf nicht NULL sein. + Parameter "{0}" cannot be null. Parameter "{0}" cannot have zero length. - Parameter "{0}" darf nicht die Länge NULL haben. + Parameter "{0}" cannot have zero length. diff --git a/src/MSBuildTaskHost/Resources/xlf/SR.es.xlf b/src/MSBuildTaskHost/Resources/xlf/SR.es.xlf index 9b8aa0f86df..fb798693e8a 100644 --- a/src/MSBuildTaskHost/Resources/xlf/SR.es.xlf +++ b/src/MSBuildTaskHost/Resources/xlf/SR.es.xlf @@ -4,57 +4,57 @@ MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: El host de tareas de MSBuild no admite la ejecución de tareas que realizan devoluciones de llamadas de IBuildEngine. Si desea realizar estas operaciones, ejecute la tarea en el proceso de MSBuild principal en su lugar. Se ejecutará una tarea automáticamente en el host de tareas si a UsingTask se le ha agregado un atributo con un valor "Runtime" o "Arquitectura", o bien a la invocación de tareas se le ha agregado un atributo con un valor "MSBuildRuntime" o "MSBuildArchitecture", que no coincide con el runtime o la arquitectura actual de MSBuild. + MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: Se detectó un ensamblado conflictivo para el ensamblado de tarea "{0}" en "{1}". + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - Se esperaba que el tipo de evento "{0}" fuera serializable con el serializador .NET. El evento no era serializable y se ha omitido. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. Making the following modifications to the environment received from the parent node before applying it to the task host: - Se están realizando las siguientes modificaciones en el entorno recibido del nodo primario antes de aplicarlo al host de tareas: + Making the following modifications to the environment received from the parent node before applying it to the task host: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - Estableciendo '{0}' en '{1}' en lugar del valor del entorno primario, '{2}'. + Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - La ruta de acceso {0} supera el límite máximo para la ruta de acceso del sistema operativo. El nombre de archivo completo debe ser inferior a {1} caracteres. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. "{0}" is a reserved item metadata, and cannot be modified or deleted. - "{0}" es un metadato de elemento reservado y no se puede modificar ni eliminar. + "{0}" is a reserved item metadata, and cannot be modified or deleted. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Los metadatos "%({0})" del elemento no pueden aplicarse a la ruta de acceso "{1}". {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: La tarea "{0}" se marcó con el atributo LoadInSeparateAppDomain, pero esta no deriva de MarshalByRefObject. Asegúrese de que la tarea deriva de MarshalByRefObject o de AppDomainIsolatedTask. + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. Parameter "{0}" cannot be null. - El parámetro "{0}" no puede ser NULL. + Parameter "{0}" cannot be null. Parameter "{0}" cannot have zero length. - La longitud del parámetro "{0}" no puede ser cero. + Parameter "{0}" cannot have zero length. diff --git a/src/MSBuildTaskHost/Resources/xlf/SR.fr.xlf b/src/MSBuildTaskHost/Resources/xlf/SR.fr.xlf index aa78715eb49..4fb064c3558 100644 --- a/src/MSBuildTaskHost/Resources/xlf/SR.fr.xlf +++ b/src/MSBuildTaskHost/Resources/xlf/SR.fr.xlf @@ -4,57 +4,57 @@ MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: L'hôte de tâche MSBuild ne prend pas en charge l'exécution de tâches qui effectuent des rappels IBuildEngine. Pour effectuer ces opérations, exécutez plutôt votre tâche dans le processus MSBuild de base. Une tâche s'exécute automatiquement dans l'hôte de tâche si UsingTask a été défini sur la valeur "Runtime" ou "Architecture", ou si l'appel de la tâche a été défini sur la valeur "MSBuildRuntime" ou "MSBuildArchitecture", qui ne correspond pas à l'architecture ou au runtime actuel de MSBuild. + MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: un assembly en conflit avec l'assembly de tâche "{0}" a été trouvé sur "{1}". + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - Le type d'événement "{0}" devait être sérialisable à l'aide du sérialiseur .NET. L'événement n'était pas sérialisable et a été ignoré. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. Making the following modifications to the environment received from the parent node before applying it to the task host: - Modifications suivantes en cours sur l'environnement reçu du nœud parent avant son application à l'hôte de tâche : + Making the following modifications to the environment received from the parent node before applying it to the task host: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - Définition de '{0}' sur '{1}' plutôt que sur la valeur de l'environnement parent, '{2}'. + Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Le chemin {0} dépasse la limite maximale de chemin du système d'exploitation. Le nom du fichier qualifié complet doit contenir moins de {1} caractères. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. "{0}" is a reserved item metadata, and cannot be modified or deleted. - "{0}" est une métadonnée d'élément réservée qui ne peut être ni modifiée ni supprimée. + "{0}" is a reserved item metadata, and cannot be modified or deleted. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Impossible d'appliquer la métadonnée d'élément "%({0})" au chemin d'accès "{1}". {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: la tâche "{0}" a été marquée avec l'attribut LoadInSeparateAppDomain, mais ne dérive pas de MarshalByRefObject. Vérifiez que la tâche dérive de MarshalByRefObject ou de AppDomainIsolatedTask. + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. Parameter "{0}" cannot be null. - Le paramètre "{0}" ne peut pas être null. + Parameter "{0}" cannot be null. Parameter "{0}" cannot have zero length. - La longueur du paramètre "{0}" ne peut pas être égale à zéro. + Parameter "{0}" cannot have zero length. diff --git a/src/MSBuildTaskHost/Resources/xlf/SR.it.xlf b/src/MSBuildTaskHost/Resources/xlf/SR.it.xlf index a4cee485754..b876d843ce8 100644 --- a/src/MSBuildTaskHost/Resources/xlf/SR.it.xlf +++ b/src/MSBuildTaskHost/Resources/xlf/SR.it.xlf @@ -4,57 +4,57 @@ MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: l'host attività MSBuild non supporta l'esecuzione di attività che eseguono callback IBuildEngine. Per eseguire tali operazioni, eseguire l'attività nel processo MSBuild di base. Un'attività verrà automaticamente eseguita nell'host attività se per UsingTask è stato definito un attributo con valore "Runtime" o "Architecture" o se per la chiamata all'attività è stato definito un attributo con valore "MSBuildRuntime" o "MSBuildArchitecture" che non corrisponde al runtime corrente o all'architettura di MSBuild. + MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: rilevato un assembly in conflitto per l'assembly dell'attività "{0}" in "{1}". + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - È previsto un tipo di evento "{0}" serializzabile con il serializzatore .NET. L'evento non era serializzabile ed è stato ignorato. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. Making the following modifications to the environment received from the parent node before applying it to the task host: - Le modifiche seguenti verranno apportate all'ambiente ricevuto dal nodo padre prima dell'applicazione all'host attività: + Making the following modifications to the environment received from the parent node before applying it to the task host: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - Impostazione di '{0}' su '{1}' anziché sul valore dell'ambiente padre, '{2}'. + Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Il percorso {0} supera il limite massimo dei percorsi del sistema operativo. Il nome completo del file deve essere composto da meno di {1}. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. "{0}" is a reserved item metadata, and cannot be modified or deleted. - "{0}" è un metadato di un elemento riservato e pertanto non può essere modificato o eliminato. + "{0}" is a reserved item metadata, and cannot be modified or deleted. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Non è possibile applicare i metadati dell'elemento "%({0})" al percorso "{1}". {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: l'attività "{0}" è stata contrassegnata con l'attributo LoadInSeparateAppDomain, ma non deriva da MarshalByRefObject. Verificare che l'attività derivi da MarshalByRefObject o AppDomainIsolatedTask. + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. Parameter "{0}" cannot be null. - Il parametro "{0}" non può essere Null. + Parameter "{0}" cannot be null. Parameter "{0}" cannot have zero length. - Il parametro "{0}" non può avere lunghezza zero. + Parameter "{0}" cannot have zero length. diff --git a/src/MSBuildTaskHost/Resources/xlf/SR.ja.xlf b/src/MSBuildTaskHost/Resources/xlf/SR.ja.xlf index 9f282723a81..5d5b84a8147 100644 --- a/src/MSBuildTaskHost/Resources/xlf/SR.ja.xlf +++ b/src/MSBuildTaskHost/Resources/xlf/SR.ja.xlf @@ -4,57 +4,57 @@ MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: MSBuild タスク ホストは、IBuildEngine コールバックを実行するタスクの実行をサポートしていません。これらの操作を実行する場合は、タスクをコア MSBuild プロセスで実行してください。UsingTask の属性として設定されている "Runtime" または "Architecture" の値、あるいはタスク呼び出しの属性として設定されている "MSBuildRuntime" または "MSBuildArchitecture" の値が MSBuild の現在のランタイムまたはアーキテクチャと一致しない場合、タスクは自動的にタスク ホストで実行されます。 + MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: タスク アセンブリ "{0}" に対して競合しているアセンブリが "{1}" で見つかりました。 + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - イベントの種類 "{0}" は .NET シリアライザーを使用してシリアル化可能であることが想定されていましたが、シリアル化可能でなかったため無視されました。 + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. Making the following modifications to the environment received from the parent node before applying it to the task host: - 親ノードから受け取った環境をタスク ホストに適用する前に、次の変更を行っています: + Making the following modifications to the environment received from the parent node before applying it to the task host: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - '{0}' を親環境の値 '{2}' ではなく '{1}' に設定しています。 + Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - パス: {0} は OS のパスの上限を越えています。完全修飾のファイル名は {1} 文字以下にする必要があります。 + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. "{0}" is a reserved item metadata, and cannot be modified or deleted. - "{0}" は予約された項目メタデータです。変更または削除することはできません。 + "{0}" is a reserved item metadata, and cannot be modified or deleted. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The item metadata "%({0})" cannot be applied to the path "{1}". {2} - 項目メタデータ "%({0})" をパス "{1}" に適用できません。{2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: "{0}" タスクに属性 LoadInSeparateAppDomain が設定されていますが、MarshalByRefObject から派生していません。そのタスクが MarshalByRefObject または AppDomainIsolatedTask から派生していることを確認してください。 + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. Parameter "{0}" cannot be null. - パラメーター "{0}" を null にすることはできません。 + Parameter "{0}" cannot be null. Parameter "{0}" cannot have zero length. - パラメーター "{0}" の長さを 0 にすることはできません。 + Parameter "{0}" cannot have zero length. diff --git a/src/MSBuildTaskHost/Resources/xlf/SR.ko.xlf b/src/MSBuildTaskHost/Resources/xlf/SR.ko.xlf index 8277e15c84b..3e11305a495 100644 --- a/src/MSBuildTaskHost/Resources/xlf/SR.ko.xlf +++ b/src/MSBuildTaskHost/Resources/xlf/SR.ko.xlf @@ -4,57 +4,57 @@ MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: MSBuild 작업 호스트는 IBuildEngine 콜백을 수행하는 작업의 실행을 지원하지 않습니다. 이러한 작업을 수행하려면 대신 코어 MSBuild 프로세스에서 작업을 실행하세요. UsingTask에 "Runtime" 또는 "Architecture" 값이 사용되었거나 작업 호출에 MSBuild의 현재 런타임 또는 아키텍처와 일치하지 않는 "MSBuildRuntime" 또는 "MSBuildArchitecture" 값이 사용된 경우 작업 호스트에서 작업이 자동으로 실행됩니다. + MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: 작업 어셈블리 "{0}"과(와) 충돌하는 어셈블리가 "{1}"에 있습니다. + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - 이벤트 유형 "{0}"은(는) .NET serializer를 사용하여 serialize할 수 있어야 합니다. 이 이벤트는 serialize할 수 없으므로 무시되었습니다. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. Making the following modifications to the environment received from the parent node before applying it to the task host: - 작업 호스트에 적용하기 전에 부모 노드로부터 받은 환경을 다음과 같이 수정하고 있습니다. + Making the following modifications to the environment received from the parent node before applying it to the task host: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - '{0}'을(를) 부모 환경 값인 '{2}' 대신 '{1}'(으)로 설정하고 있습니다. + Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - 경로: {0}은(는) OS 최대 경로 제한을 초과합니다. 정규화된 파일 이름은 {1}자 이하여야 합니다. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. "{0}" is a reserved item metadata, and cannot be modified or deleted. - "{0}"은(는) 예약된 항목 메타데이터이므로 수정 또는 삭제할 수 없습니다. + "{0}" is a reserved item metadata, and cannot be modified or deleted. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The item metadata "%({0})" cannot be applied to the path "{1}". {2} - 항목 메타데이터 "%({0})"을(를) "{1}" 경로에 적용할 수 없습니다. {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: "{0}" 작업이 LoadInSeparateAppDomain 특성으로 표시되었지만 MarshalByRefObject에서 파생되지 않습니다. 해당 작업이 MarshalByRefObject 또는 AppDomainIsolatedTask에서 파생되는지 확인하십시오. + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. Parameter "{0}" cannot be null. - "{0}" 매개 변수는 null일 수 없습니다. + Parameter "{0}" cannot be null. Parameter "{0}" cannot have zero length. - "{0}" 매개 변수의 길이는 0일 수 없습니다. + Parameter "{0}" cannot have zero length. diff --git a/src/MSBuildTaskHost/Resources/xlf/SR.pl.xlf b/src/MSBuildTaskHost/Resources/xlf/SR.pl.xlf index e6137d07284..2ed366bcc32 100644 --- a/src/MSBuildTaskHost/Resources/xlf/SR.pl.xlf +++ b/src/MSBuildTaskHost/Resources/xlf/SR.pl.xlf @@ -4,57 +4,57 @@ MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: Host zadań programu MSBuild nie obsługuje zadań wykonujących wywołania zwrotne do aparatu IBuildEngine. Jeśli chcesz wykonywać te operacje, uruchom zadanie w podstawowym procesie programu MSBuild. Zadanie będzie automatycznie wykonywane na hoście zadań, jeśli w deklaracji UsingTask ustawiono wartość „Runtime” lub „Architecture” albo w wywołaniu zadania ustawiono wartość „MSBuildRuntime” lub „MSBuildArchitecture”, która nie odpowiada bieżącemu środowisku uruchomieniowemu lub architekturze programu MSBuild. + MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: Zestaw, który wywołuje konflikt z zestawem zadania „{0}”, został znaleziony w „{1}”. + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - Oczekiwano, że zdarzenie typu „{0}” będzie uszeregowane przy użyciu serializatora platformy .NET. Zdarzenie nie może podlegać szeregowaniu, dlatego zostało zignorowane. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. Making the following modifications to the environment received from the parent node before applying it to the task host: - Wymienione zmiany otrzymane z węzła nadrzędnego zostaną wprowadzone w środowisku, a po sprawdzeniu działania zastosowane do hosta zadań: + Making the following modifications to the environment received from the parent node before applying it to the task host: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - Ustawienie dla elementu „{0}” wartości „{1}” zamiast wartości „{2}” obowiązującej w środowisku nadrzędnym. + Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Ścieżka: {0} przekracza limit maksymalnej długości ścieżki w systemie operacyjnym. W pełni kwalifikowana nazwa pliku musi się składać z mniej niż {1} znaków. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. "{0}" is a reserved item metadata, and cannot be modified or deleted. - „{0}” jest zastrzeżonym elementem metadanych i nie może zostać zmodyfikowany ani usunięty. + "{0}" is a reserved item metadata, and cannot be modified or deleted. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Elementu metadanych „%({0})” nie można zastosować do ścieżki „{1}”. {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: Zadanie „{0}” zostało oznaczone atrybutem LoadInSeparateAppDomain, ale nie pochodzi od obiektu MarshalByRefObject. Sprawdź, czy zadanie pochodzi od obiektu MarshalByRefObject lub zadania AppDomainIsolatedTask. + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. Parameter "{0}" cannot be null. - Parametr „{0}” nie może być zerowy. + Parameter "{0}" cannot be null. Parameter "{0}" cannot have zero length. - Parametr „{0}” nie może mieć zerowej długości. + Parameter "{0}" cannot have zero length. diff --git a/src/MSBuildTaskHost/Resources/xlf/SR.pt-BR.xlf b/src/MSBuildTaskHost/Resources/xlf/SR.pt-BR.xlf index 727f4447193..58bb88e992b 100644 --- a/src/MSBuildTaskHost/Resources/xlf/SR.pt-BR.xlf +++ b/src/MSBuildTaskHost/Resources/xlf/SR.pt-BR.xlf @@ -4,57 +4,57 @@ MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: O host de tarefas MSBuild não dá suporte a tarefas em execução que executam chamadas de retorno de IBuildEngine. Se desejar executar essas operações, execute sua tarefa no processo MSBuild principal. Uma tarefa será automaticamente executada no host de tarefas se UsingTask tiver como atributo um valor "Runtime" ou "Architecture" ou se a invocação da tarefa tiver como atributo um valor "MSBuildRuntime" ou "MSBuildArchitecture", que não coincida com o tempo de execução ou arquitetura atual do MSBuild. + MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: Foi encontrado um assembly conflitante no assembly da tarefa "{0}" em "{1}". + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - Era esperado que o tipo de evento "{0}" fosse serializável usando o serializador .NET. O evento não era serializável e foi ignorado. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. Making the following modifications to the environment received from the parent node before applying it to the task host: - Fazendo as seguintes modificações no ambiente recebido do nó pai antes de aplicá-lo ao host de tarefas: + Making the following modifications to the environment received from the parent node before applying it to the task host: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - Definindo "{0}" como "{1}" em vez do valor do ambiente pai, "{2}". + Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Caminho: {0} excede o limite máximo do caminho do SO. O nome do arquivo totalmente qualificado deve ter menos de {1} caracteres. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. "{0}" is a reserved item metadata, and cannot be modified or deleted. - "{0}" são metadados de item reservado e não podem ser modificados ou excluídos. + "{0}" is a reserved item metadata, and cannot be modified or deleted. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Os metadados do item "%({0})" não podem ser aplicados ao caminho "{1}". {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: A tarefa "{0}" foi marcada com o atributo LoadInSeparateAppDomain, mas não é derivada de MarshalByRefObject. Verifique se a tarefa é derivada de MarshalByRefObject ou de AppDomainIsolatedTask. + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. Parameter "{0}" cannot be null. - O parâmetro "{0}" não pode ser nulo. + Parameter "{0}" cannot be null. Parameter "{0}" cannot have zero length. - O parâmetro "{0}" não pode ter comprimento zero. + Parameter "{0}" cannot have zero length. diff --git a/src/MSBuildTaskHost/Resources/xlf/SR.ru.xlf b/src/MSBuildTaskHost/Resources/xlf/SR.ru.xlf index b405bcbdb3f..f747d5becf8 100644 --- a/src/MSBuildTaskHost/Resources/xlf/SR.ru.xlf +++ b/src/MSBuildTaskHost/Resources/xlf/SR.ru.xlf @@ -4,57 +4,57 @@ MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: узел сборки MSBuild не поддерживает задачи, которые выполняют обратные вызовы IBuildEngine. Если необходимо выполнить эти операции, запустите задачу в основном процессе MSBuild. Задача будет автоматически выполнена в узле задач, если для UsingTask был указан атрибут со значением "Runtime" или "Architecture" или для вызова задачи был указан атрибут со значением "MSBuildRuntime" или "MSBuildArchitecture", которые не соответствуют текущей среде выполнения или архитектуре MSBuild. + MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: в "{1}" обнаружена сборка, конфликтующая со сборкой задачи "{0}". + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - Необходимо, чтобы тип события "{0}" был сериализуемым с помощью сериализатора .NET. Событие не было сериализуемым и было пропущено. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. Making the following modifications to the environment received from the parent node before applying it to the task host: - Перед применением окружения, полученного от родительского узла, к серверу задач в нем выполняются следующие изменения: + Making the following modifications to the environment received from the parent node before applying it to the task host: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - Задание для "{0}" значения "{1}", а не значения родительского окружения "{2}". + Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Длина пути {0} превышает максимально допустимую в ОС. Символов в полном имени файла должно быть не больше {1}. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. "{0}" is a reserved item metadata, and cannot be modified or deleted. - "{0}" - зарезервированные метаданные элемента; их изменение или удаление невозможно. + "{0}" is a reserved item metadata, and cannot be modified or deleted. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The item metadata "%({0})" cannot be applied to the path "{1}". {2} - Не удается применить метаданные элемента "%({0})" к пути "{1}". {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: задача "{0}" помечена атрибутом LoadInSeparateAppDomain, но не является производной от MarshalByRefObject. Задача должна быть производной от MarshalByRefObject или AppDomainIsolatedTask. + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. Parameter "{0}" cannot be null. - Параметр "{0}" не может иметь неопределенное (null) значение. + Parameter "{0}" cannot be null. Parameter "{0}" cannot have zero length. - Длина параметра "{0}" не может быть равна нулю. + Parameter "{0}" cannot have zero length. diff --git a/src/MSBuildTaskHost/Resources/xlf/SR.tr.xlf b/src/MSBuildTaskHost/Resources/xlf/SR.tr.xlf index 5628d348936..c4033aee7b6 100644 --- a/src/MSBuildTaskHost/Resources/xlf/SR.tr.xlf +++ b/src/MSBuildTaskHost/Resources/xlf/SR.tr.xlf @@ -4,57 +4,57 @@ MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: MSBuild görev konağı IBuildEngine geri çağırmaları gerçekleştiren görevleri çalıştırmayı desteklemez. Bu işlemleri gerçekleştirmek istiyorsanız lütfen bunun yerine görevinizi çekirdek MSBuild işleminde gerçekleştirin. UsingTask öğesine bir "Runtime" veya "Architecture" değeri atfedilmişse veya görev çağrısına MSBuild’in geçerli çalışma zamanı ya da mimarisi ile eşleşmeyen bir "MSBuildRuntime" veya "MSBuildArchitecture" değeri atfedilmişse görev konağında bir görev otomatik olarak yürütülür. + MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: "{0}" görev derlemesi için "{1}" konumunda çakışan derleme bulundu. + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - "{0}" olay türünün .NET serileştiricisi kullanılarak serileştirilebilir olması bekleniyordu. Olay serileştirilebilir değildi ve yoksayıldı. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. Making the following modifications to the environment received from the parent node before applying it to the task host: - Üst düğümden alınan ortam görev ana bilgisayarına uygulanmadan önce ortamda aşağıdaki değişiklikler yapılıyor: + Making the following modifications to the environment received from the parent node before applying it to the task host: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - '{0}', üst ortamında değeri olan '{2}' yerine '{1}' değerine ayarlanıyor. + Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Yol: {0}, işletim sisteminin en yüksek yol sınırını aşıyor. Tam dosya adı en fazla {1} karakter olmalıdır. + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. "{0}" is a reserved item metadata, and cannot be modified or deleted. - "{0}" ayrılmış bir öğe meta verisi olduğu için değiştirilemez veya silinemez. + "{0}" is a reserved item metadata, and cannot be modified or deleted. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The item metadata "%({0})" cannot be applied to the path "{1}". {2} - "%({0})" öğe meta verisi "{1}" yoluna uygulanamıyor. {2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: "{0}" görevi LoadInSeparateAppDomain özniteliğiyle işaretlenmiş, ancak MarshalByRefObject öğesinden türetilmiyor. Görevin MarshalByRefObject veya AppDomainIsolatedTask öğesinden türetildiğini denetleyin. + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. Parameter "{0}" cannot be null. - "{0}" parametresi null olamaz. + Parameter "{0}" cannot be null. Parameter "{0}" cannot have zero length. - "{0}" parametresinin uzunluğu sıfır olamaz. + Parameter "{0}" cannot have zero length. diff --git a/src/MSBuildTaskHost/Resources/xlf/SR.zh-Hans.xlf b/src/MSBuildTaskHost/Resources/xlf/SR.zh-Hans.xlf index 2c1ed366f5b..f4b013263e4 100644 --- a/src/MSBuildTaskHost/Resources/xlf/SR.zh-Hans.xlf +++ b/src/MSBuildTaskHost/Resources/xlf/SR.zh-Hans.xlf @@ -4,57 +4,57 @@ MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: MSBuild 任务宿主不支持运行执行 IBuildEngine 回调的任务。如果需要执行这些操作，请改为在核心 MSBuild 进程中运行您的任务。如果 UsingTask 已用“Runtime”或“Architecture”值特性化，或者任务调用已用“MSBuildRuntime”或“MSBuildArchitecture”值(与 MSBuild 的当前运行时或体系结构不匹配)特性化，则将自动在任务宿主中执行任务。 + MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: 在“{1}”处发现了与任务程序集“{0}”冲突的程序集。 + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - 事件类型“{0}”应可以使用 .NET 序列化程序进行序列化。此事件不可序列化，已忽略它。 + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. Making the following modifications to the environment received from the parent node before applying it to the task host: - 先对从父节点收到的环境进行以下修改，然后再将其应用于任务宿主: + Making the following modifications to the environment received from the parent node before applying it to the task host: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - 将“{0}”设置为“{1}”，而不是父环境的值“{2}”。 + Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - 路径: {0} 超过 OS 最大路径限制。完全限定的文件名必须少于 {1} 个字符。 + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. "{0}" is a reserved item metadata, and cannot be modified or deleted. - “{0}”是保留的项元数据，不能修改或删除。 + "{0}" is a reserved item metadata, and cannot be modified or deleted. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The item metadata "%({0})" cannot be applied to the path "{1}". {2} - 无法将项元数据“%({0})”应用于路径“{1}”。{2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: “{0}”任务已标记为 LoadInSeparateAppDomain 特性，但未派生自 MarshalByRefObject。请检查该任务是派生自 MarshalByRefObject 还是 AppDomainIsolatedTask。 + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. Parameter "{0}" cannot be null. - 参数“{0}”不能为 null。 + Parameter "{0}" cannot be null. Parameter "{0}" cannot have zero length. - 参数“{0}”的长度不能为零。 + Parameter "{0}" cannot have zero length. diff --git a/src/MSBuildTaskHost/Resources/xlf/SR.zh-Hant.xlf b/src/MSBuildTaskHost/Resources/xlf/SR.zh-Hant.xlf index 43f6f0bb8b0..8bf3616de0d 100644 --- a/src/MSBuildTaskHost/Resources/xlf/SR.zh-Hant.xlf +++ b/src/MSBuildTaskHost/Resources/xlf/SR.zh-Hant.xlf @@ -4,57 +4,57 @@ MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: MSBuild 工作主機不支援會執行 IBuildEngine 回撥的工作。若您想要執行這些作業，請改為在核心 MSBuild 處理序執行您的工作。若 UsingTask 已由 "Runtime" 或 "Architecture" 值賦予屬性，或工作引動過程已由 "MSBuildRuntime" 或 "MSBuildArchitecture" 值賦予屬性 (不符合 MSBuild 的目前執行階段或結構)，則工作將自動在工作主機中執行。 + MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: 已在 "{1}" 中發現工作組件 "{0}" 的衝突組件。 + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - 事件類型 "{0}" 應該可以使用 .NET 序列化程式序列化。此事件不可序列化，已略過。 + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. Making the following modifications to the environment received from the parent node before applying it to the task host: - 在套用到工作主機之前，對從父節點接收的環境進行下列修改: + Making the following modifications to the environment received from the parent node before applying it to the task host: Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - 將 '{0}' 設定為 '{1}' 而非父環境的值 '{2}。 + Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - 路徑: {0} 超過 OS 路徑上限。完整檔案名稱必須少於 {1} 個字元。 + Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. "{0}" is a reserved item metadata, and cannot be modified or deleted. - "{0}" 是保留的項目中繼資料，不能修改或刪除。 + "{0}" is a reserved item metadata, and cannot be modified or deleted. UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. The item metadata "%({0})" cannot be applied to the path "{1}". {2} - 無法將項目中繼資料 "%({0})" 套用至路徑 "{1}"。{2} + The item metadata "%({0})" cannot be applied to the path "{1}". {2} UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: "{0}" 工作已經以屬性 LoadInSeparateAppDomain 標記，但不是衍生自 MarshalByRefObject。請檢查工作是否衍生自 MarshalByRefObject 或 AppDomainIsolatedTask。 + MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. Parameter "{0}" cannot be null. - 參數 "{0}" 不能為 null。 + Parameter "{0}" cannot be null. Parameter "{0}" cannot have zero length. - 參數 "{0}" 長度不能為零。 + Parameter "{0}" cannot have zero length. diff --git a/src/Shared/Resources/xlf/Strings.shared.cs.xlf b/src/Shared/Resources/xlf/Strings.shared.cs.xlf index 7c27da24ffb..0e913ded1e1 100644 --- a/src/Shared/Resources/xlf/Strings.shared.cs.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.cs.xlf @@ -29,7 +29,7 @@ Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - Vlastní typ události '{0}' se nepodporuje, protože všechny vlastní typy událostí jsou zastaralé. Použijte prosím místo toho Extended*EventArgs. Další informace: https://aka.ms/msbuild/eventargs + Vlastní typ události {0} se nepodporuje, protože všechny vlastní typy událostí byly vyřazeny jako zastaralé. Místo toho prosím použijte Extended*EventArgs. Další informace: https://aka.ms/msbuild/eventargs @@ -335,7 +335,7 @@ MSB5029: The value "{0}" of the "{1}" attribute in element <{2}> 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. - MSB5029: Hodnota {0} atributu {1} v elementu <{2}> 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. + MSB5029: Hodnota {0} atributu {1} v elementu <{2}> 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. {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. <Compile Include="$(NotAlwaysDefined)\**\*.cs"> -- if the property is undefined, the value of Include should not result in enumerating all files on drive. diff --git a/src/Shared/Resources/xlf/Strings.shared.de.xlf b/src/Shared/Resources/xlf/Strings.shared.de.xlf index 96e44a116e6..f86019b60ce 100644 --- a/src/Shared/Resources/xlf/Strings.shared.de.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.de.xlf @@ -29,7 +29,7 @@ Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - Der benutzerdefinierte Ereignistyp '{0}' wird nicht unterstützt, weil alle benutzerdefinierten Ereignistypen veraltet waren. Verwenden Sie stattdessen Extended*EventArgs. Weitere Informationen: https://aka.ms/msbuild/eventargs + Der benutzerdefinierte Ereignistyp „{0}“ wird nicht unterstützt, da alle benutzerdefinierten Ereignistypen veraltet sind. Bitte verwenden Sie stattdessen Extended*EventArgs. Weitere Informationen finden Sie unter: https://aka.ms/msbuild/eventargs diff --git a/src/Shared/Resources/xlf/Strings.shared.es.xlf b/src/Shared/Resources/xlf/Strings.shared.es.xlf index 28992cf81d7..e1fc289817d 100644 --- a/src/Shared/Resources/xlf/Strings.shared.es.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.es.xlf @@ -29,7 +29,7 @@ Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - No se admite el tipo de evento personalizado '{0}' porque todos los tipos de eventos personalizados estaban en desuso. Use Extended*EventArgs en su lugar. Más información: https://aka.ms/msbuild/eventargs + El tipo de evento personalizado '{0}' no es compatible, ya que todos los tipos de eventos personalizados han sido descontinuados. Use Extended*EventArgs en su lugar. Más información: https://aka.ms/msbuild/eventargs diff --git a/src/Shared/Resources/xlf/Strings.shared.fr.xlf b/src/Shared/Resources/xlf/Strings.shared.fr.xlf index c33ef71d145..d1e2de83c41 100644 --- a/src/Shared/Resources/xlf/Strings.shared.fr.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.fr.xlf @@ -29,7 +29,7 @@ Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - Le type d’événement personnalisé '{0}' n’est pas pris en charge, car tous les types d’événement personnalisés ont été dépréciés. Utilisez Extended*EventArgs à la place. Plus d’informations : https://aka.ms/msbuild/eventargs + Le type d’événement personnalisé « {0} » n’est pas pris en charge car tous les types d’événements personnalisés ont été supprimés. Utilisez plutôt Extended*EventArgs. Plus d’informations : https://aka.ms/msbuild/eventargs diff --git a/src/Shared/Resources/xlf/Strings.shared.it.xlf b/src/Shared/Resources/xlf/Strings.shared.it.xlf index 13d9fc42900..b5445cac761 100644 --- a/src/Shared/Resources/xlf/Strings.shared.it.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.it.xlf @@ -29,7 +29,7 @@ Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - Il tipo di evento personalizzato '{0}' non è supportato perché tutti i tipi di evento personalizzati sono deprecati. Usare Invece Extended*EventArgs. Altre informazioni: https://aka.ms/msbuild/eventargs + Il tipo di evento personalizzato '{0}' non è supportato poiché tutti i tipi di eventi personalizzati sono stati deprecati. Usa invece Extended*EventArgs. Scopri di più: https://aka.ms/msbuild/eventargs diff --git a/src/Shared/Resources/xlf/Strings.shared.ja.xlf b/src/Shared/Resources/xlf/Strings.shared.ja.xlf index bf5724129aa..7ea09923b80 100644 --- a/src/Shared/Resources/xlf/Strings.shared.ja.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.ja.xlf @@ -29,7 +29,7 @@ Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - カスタム イベントの種類 '{0}' は、すべてのカスタム イベントの種類が非推奨になったため、サポートされていません。代わりに Extended*EventArgs を使用してください。詳細情報: https://aka.ms/msbuild/eventargs + すべてのカスタム イベントの種類が非推奨になったため、カスタム イベントの種類 '{0}' はサポートされていません。代わりに Extended*EventArgs を使用してください。詳細情報: https://aka.ms/msbuild/eventargs diff --git a/src/Shared/Resources/xlf/Strings.shared.ko.xlf b/src/Shared/Resources/xlf/Strings.shared.ko.xlf index f36fecb0d5d..848232e8720 100644 --- a/src/Shared/Resources/xlf/Strings.shared.ko.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.ko.xlf @@ -29,7 +29,7 @@ Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - 모든 사용자 지정 이벤트 유형이 사용되지 않으므로 사용자 지정 이벤트 유형 '{0}' 지원되지 않습니다. 대신 Extended*EventArgs를 사용하세요. 추가 정보: https://aka.ms/msbuild/eventargs + 사용자 지정 이벤트 유형 '{0}'은(는) 일부 사용자 지정 이벤트 형식이 더 이상 사용되지 않으므로 지원되지 않습니다. 대신 Extended*EventArgs를 사용하세요. 추가 정보: https://aka.ms/msbuild/eventargs diff --git a/src/Shared/Resources/xlf/Strings.shared.pl.xlf b/src/Shared/Resources/xlf/Strings.shared.pl.xlf index e0cf71f3188..1ca77d97f6f 100644 --- a/src/Shared/Resources/xlf/Strings.shared.pl.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.pl.xlf @@ -29,7 +29,7 @@ Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - Niestandardowy typ zdarzenia '{0}' nie jest obsługiwany, ponieważ wszystkie typy zdarzeń niestandardowych były przestarzałe. Zamiast tego użyj elementu Extended*EventArgs. Więcej informacji: https://aka.ms/msbuild/eventargs + Niestandardowy typ zdarzenia „{0}” nie jest obsługiwany, ponieważ wszystkie typy zdarzeń niestandardowych były przestarzałe. Zamiast tego użyj elementu Extended*EventArgs. Więcej informacji: https://aka.ms/msbuild/eventargs diff --git a/src/Shared/Resources/xlf/Strings.shared.pt-BR.xlf b/src/Shared/Resources/xlf/Strings.shared.pt-BR.xlf index 01ca48b9f29..462486eb201 100644 --- a/src/Shared/Resources/xlf/Strings.shared.pt-BR.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.pt-BR.xlf @@ -29,7 +29,7 @@ Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - Não há suporte '{0}' tipo de evento personalizado porque todos os tipos de eventos personalizados foram preteridos. Use Extended*EventArgs em vez disso. Mais informações: https://aka.ms/msbuild/eventargs + O tipo de evento personalizado '{0}' não tem suporte, pois todos os tipos de eventos personalizados foram preteridos. Use Extended*EventArgs em vez disso. Mais informações: https://aka.ms/msbuild/eventargs diff --git a/src/Shared/Resources/xlf/Strings.shared.ru.xlf b/src/Shared/Resources/xlf/Strings.shared.ru.xlf index d0f2c1e081f..f72c1232d92 100644 --- a/src/Shared/Resources/xlf/Strings.shared.ru.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.ru.xlf @@ -29,7 +29,7 @@ Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - Настраиваемый тип '{0}' не поддерживается, так как все пользовательские типы событий устарели. Используйте extended*EventArgs. Дополнительные сведения: https://aka.ms/msbuild/eventargs + Настраиваемый тип событий "{0}" не поддерживается, так как все настраиваемые типы событий являются нерекомендуемыми. Вместо этого используйте Extended*EventArgs. Дополнительные сведения: https://aka.ms/msbuild/eventargs diff --git a/src/Shared/Resources/xlf/Strings.shared.tr.xlf b/src/Shared/Resources/xlf/Strings.shared.tr.xlf index 359306dbdc8..25858445e8e 100644 --- a/src/Shared/Resources/xlf/Strings.shared.tr.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.tr.xlf @@ -29,7 +29,7 @@ Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - Tüm özel '{0}' türleri kullanım dışı bırakıldığinden özel olay türü türü desteklenmiyor. Lütfen bunun yerine Extended*EventArgs kullanın. Daha fazla bilgi: https://aka.ms/msbuild/eventargs + '{0}' özel olay türü, tüm özel olay türleri kullanım dışı olduğundan desteklenmiyor. Lütfen bunun yerine Extended*EventArgs kullanın. Daha fazla bilgi için bkz. https://aka.ms/msbuild/eventargs diff --git a/src/Shared/Resources/xlf/Strings.shared.zh-Hans.xlf b/src/Shared/Resources/xlf/Strings.shared.zh-Hans.xlf index 6b1f3ae581e..bd5530d2acc 100644 --- a/src/Shared/Resources/xlf/Strings.shared.zh-Hans.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.zh-Hans.xlf @@ -29,7 +29,7 @@ Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - 不支持自定义事件类型 '{0}'，因为已弃用所有自定义事件类型。请改用 Extended*EventArgs。详细信息： https://aka.ms/msbuild/eventargs + 不支持自定义事件类型“{0}”，因为所有自定义事件类型都已弃用。请改用 Extended*EventArgs。有关详细信息，请访问 :https://aka.ms/msbuild/eventargs diff --git a/src/Shared/Resources/xlf/Strings.shared.zh-Hant.xlf b/src/Shared/Resources/xlf/Strings.shared.zh-Hant.xlf index 518e09fdb4c..4c114485866 100644 --- a/src/Shared/Resources/xlf/Strings.shared.zh-Hant.xlf +++ b/src/Shared/Resources/xlf/Strings.shared.zh-Hant.xlf @@ -29,7 +29,7 @@ Custom event type '{0}' is not supported as all custom event types were deprecated. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs - 不支援自定義事件類型 '{0}'，因為所有自定義事件類型都已過時。請改用 Extended*EventArgs。更多資訊： https://aka.ms/msbuild/eventargs + 不支援自訂事件類型 '{0}'，因為所有自訂事件類型都已淘汰。請改為使用 Extended*EventArgs。詳細資訊: https://aka.ms/msbuild/eventargs diff --git a/src/Tasks/Resources/xlf/Strings.cs.xlf b/src/Tasks/Resources/xlf/Strings.cs.xlf index dde273ca0ae..17fd7f4851b 100644 --- a/src/Tasks/Resources/xlf/Strings.cs.xlf +++ b/src/Tasks/Resources/xlf/Strings.cs.xlf @@ -496,7 +496,7 @@ MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3077: Příkaz {0} byl ukončen s návratovou hodnotou 0, ale během provádění byly zjištěny chyby. Hodnota ExitCode byla nastavena na hodnotu -1. + MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3077: "} @@ -1185,7 +1185,7 @@ MSB3825: Resource "{0}" will 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 - MSB3825: Prostředek {0} bude deserializován přes BinaryFormatter za běhu. BinaryFormatter je kvůli známým bezpečnostním rizikům zastaralý a byl odebrán z rozhraní .NET 9+. Pokud ho chcete dál používat, nastavte vlastnost GenerateResourceWarnOnBinaryFormatterUse na false. + MSB3825: Prostředek {0} bude deserializován přes BinaryFormatter za běhu. BinaryFormatter je zastaralý kvůli známým bezpečnostním rizikům a byl odebrán z rozhraní .NET 9+. Pokud ho chcete dál používat, nastavte vlastnost GenerateResourceWarnOnBinaryFormatterUse na false. Další informace: https://aka.ms/binaryformatter-migration-guide {StrBegin="MSB3825: "} @@ -1271,22 +1271,22 @@ MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. - MSB3828: Přeskakování generování vlastnosti prostředku silného typu pro prostředek {0}: název nelze převést na platný identifikátor. + MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. {StrBegin="MSB3828: "} MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. - MSB3829: Přeskakování generování vlastnosti prostředku silného typu pro prostředek {0}: po normalizaci identifikátoru existuje kolize názvů s prostředkem {1}. + MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. {StrBegin="MSB3829: "} MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. - MSB3827: Přeskakování generování vlastnosti prostředku silného typu pro prostředek {0}: název je v konfliktu s vyhrazeným názvem. Vyhrazené názvy: {1}. + MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. {StrBegin="MSB3827: "} MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. - MSB3830: Přeskakování generování vlastnosti prostředku silného typu pro prostředek {0}: typ hodnoty prostředku je neplatný a nelze použít jako typ vlastnosti. + MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. {StrBegin="MSB3830: "} @@ -2924,7 +2924,7 @@ MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3725: Příkaz {0} byl ukončen s návratovou hodnotou 0, ale během provádění byly zjištěny chyby. Hodnota ExitCode byla nastavena na hodnotu -1. + MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3725: "} diff --git a/src/Tasks/Resources/xlf/Strings.de.xlf b/src/Tasks/Resources/xlf/Strings.de.xlf index 99732a18ae6..debd0cf75dc 100644 --- a/src/Tasks/Resources/xlf/Strings.de.xlf +++ b/src/Tasks/Resources/xlf/Strings.de.xlf @@ -496,7 +496,7 @@ MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3077: Der Befehl „{0}“ wurde mit dem Rückgabewert 0 beendet, jedoch wurden während der Ausführung Fehler festgestellt. ExitCode wurde auf -1 festgelegt. + MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3077: "} @@ -1185,7 +1185,7 @@ MSB3825: Resource "{0}" will 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 - MSB3825: Die Ressource „{0}“ wird während der Laufzeit über BinaryFormatter deserialisiert. BinaryFormatter ist aufgrund bekannter Sicherheitsrisiken veraltet und wird aus .NET 9 und höher entfernt. Wenn Sie ihn weiterhin verwenden möchten, legen Sie die Eigenschaft „GenerateResourceWarnOnBinaryFormatterUse“ auf FALSCH fest. + MSB3825: Die Ressource „{0}“ wird während der Laufzeit über BinaryFormatter deserialisiert. BinaryFormatter ist aufgrund bekannter Sicherheitsrisiken veraltet und wird aus .NET 9 und höher entfernt. Wenn Sie ihn weiterhin verwenden möchten, legen Sie die Eigenschaft "GenerateResourceWarnOnBinaryFormatterUse" auf "false" fest. Weitere Informationen finden Sie unter: https://aka.ms/binaryformatter-migration-guide {StrBegin="MSB3825: "} @@ -1271,22 +1271,22 @@ MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. - MSB3828: Die Generierung stark typisierter Ressourceneigenschaften für die Ressource „{0}“ wird übersprungen: Der Name kann nicht in einen gültigen Bezeichner umgewandelt werden. + MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. {StrBegin="MSB3828: "} MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. - MSB3829: Die Generierung stark typisierter Ressourceneigenschaften für die Ressource „{0}“ wird übersprungen: Nach der Normalisierung des Bezeichners besteht ein Namenskonflikt mit der Ressource „{1}“. + MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. {StrBegin="MSB3829: "} MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. - MSB3827: Die Generierung stark typisierter Ressourceneigenschaften für die Ressource „{0}“ wird übersprungen: Der Name steht im Konflikt mit einem reservierten Namen. Reservierte Namen: {1}. + MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. {StrBegin="MSB3827: "} MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. - MSB3830: Die Generierung stark typisierter Ressourceneigenschaften für die Ressource „{0}“ wird übersprungen: Der Ressourcenwerttyp ist „void“. Er kann nicht als Eigenschaftstyp verwendet werden. + MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. {StrBegin="MSB3830: "} @@ -2924,7 +2924,7 @@ MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3725: Der Befehl „{0}“ wurde mit dem Rückgabewert 0 beendet, jedoch wurden während der Ausführung Fehler festgestellt. ExitCode wurde auf -1 festgelegt. + MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3725: "} diff --git a/src/Tasks/Resources/xlf/Strings.es.xlf b/src/Tasks/Resources/xlf/Strings.es.xlf index 2ba711a7b04..64a98aec2d6 100644 --- a/src/Tasks/Resources/xlf/Strings.es.xlf +++ b/src/Tasks/Resources/xlf/Strings.es.xlf @@ -136,7 +136,7 @@ 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. - 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. + 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. {StrBegin="MSB3654: "} @@ -436,7 +436,7 @@ MSB3061: Unable to delete file "{0}". {1} {2} - MSB3061: No se puede eliminar el archivo "{0}". {1} {2} + MSB3061: no se puede eliminar el archivo "{0}". {1} {2} {StrBegin="MSB3061: "} @@ -451,7 +451,7 @@ MSB3062: Could not delete file "{0}". Beginning retry {1} in {2}ms. {3} {4} - MSB3062: No se pudo eliminar el archivo "{0}". Iniciando reintento{1} en {2}ms. {3} {4} + MSB3062: no se pudo eliminar el archivo "{0}". Iniciando el reintento {1} en {2} ms. {3} {4} {StrBegin="MSB3062: "} LOCALIZATION: {0} are paths. {1} and {2} are numbers. {3} is an optional localized message, {4} is message from LockCheck. @@ -496,7 +496,7 @@ MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3077: el comando "{0}" se cerró con el valor devuelto 0, pero se detectaron errores durante la ejecución. ExitCode se estableció en -1. + MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3077: "} @@ -1185,7 +1185,7 @@ MSB3825: Resource "{0}" will 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 - MSB3825: El recurso "{0}" se deserializará a través de BinaryFormatter en tiempo de ejecución. BinaryFormatter está en desuso debido a riesgos de seguridad conocidos y se ha quitado de.NET 9 y versiones superiores. Si deseas seguir usándolo, establece la propiedad "GenerateResourceWarnOnBinaryFormatterUse" en false. + MSB3825: El recurso "{0}" se deserializará a través de BinaryFormatter en tiempo de ejecución. BinaryFormatter está en desuso debido a riesgos de seguridad conocidos y se ha eliminado de .NET 9+. Si desea seguir usándolo, establezca la propiedad "GenerateResourceWarnOnBinaryFormatterUse" en false. Más información: https://aka.ms/binaryformatter-migration-guide {StrBegin="MSB3825: "} @@ -1271,22 +1271,22 @@ MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. - MSB3828: omitiendo la generación de propiedades de recurso fuertemente tipadas para el recurso "{0}": el nombre no se puede convertir en un identificador válido. + MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. {StrBegin="MSB3828: "} MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. - MSB3829: omitiendo la generación de propiedades de recurso fuertemente tipadas para el recurso "{0}": existe una colisión de nombres con el recurso "{1}" después de la normalización del identificador. + MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. {StrBegin="MSB3829: "} MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. - MSB3827: omitiendo la generación de propiedades de recurso fuertemente tipadas para el recurso "{0}": el nombre entra en conflicto con un nombre reservado. Nombres reservados: {1}. + MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. {StrBegin="MSB3827: "} MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. - MSB3830: omitiendo la generación de propiedades de recurso fuertemente tipadas para el recurso "{0}": el tipo de valor de recurso es void, que no se puede usar como tipo de propiedad. + MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. {StrBegin="MSB3830: "} @@ -1613,7 +1613,7 @@ MSB3677: Unable to move file "{0}" to "{1}". {2} {3} - MSB3677: No se puede mover el archivo "{0}" a "{1}". {2} {3} + MSB3677: no es posible mover el archivo "{0}" a "{1}". {2} {3} {StrBegin="MSB3677: "} @@ -2445,7 +2445,7 @@ 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} - 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} + 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} {StrBegin="MSB3295: "} @@ -2654,7 +2654,7 @@ MSB3353: Public key necessary for delay signing was not specified. - MSB3353: No se especificó la clave pública necesaria para la firma retardada. + MSB3353: No se especificó la clave pública necesaria para la firma con retraso. {StrBegin="MSB3353: "} @@ -2679,7 +2679,7 @@ MSB3372: The file "{0}" cannot be made writable. {1} {2} - MSB3372: El archivo "{0}" no se puede escribir. {1} {2} + MSB3372: el archivo "{0}" no se puede hacer grabable. {1} {2} {StrBegin="MSB3372: "} @@ -2689,7 +2689,7 @@ MSB3374: The last access/last write time on file "{0}" cannot be set. {1} {2} - MSB3374: No se puede establecer la hora de último acceso o última escritura en el archivo "{0}". {1} {2} + MSB3374: no se puede establecer la hora de último acceso o última escritura en el archivo "{0}". {1} {2} {StrBegin="MSB3374: "} @@ -2784,7 +2784,7 @@ MSB3935: Failed to unzip file "{0}" because destination file "{1}" is read-only and could not be made writable. {2} {3} - 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} + 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} {StrBegin="MSB3935: "} @@ -2874,7 +2874,7 @@ MSB3491: Could not write lines to file "{0}". {1} {2} - MSB3491: No se pudieron escribir líneas en el archivo "{0}". {1} {2} + MSB3491: no se pudieron escribir líneas en el archivo "{0}". {1} {2} {StrBegin="MSB3491: "} @@ -2924,7 +2924,7 @@ MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3725: el comando "{0}" se cerró con el valor devuelto 0, pero se detectaron errores durante la ejecución. ExitCode se estableció en -1. + MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3725: "} @@ -3164,7 +3164,7 @@ MSB3713: The file "{0}" could not be created. {1} {2} - MSB3713: No se pudo crear el archivo "{0}". {1} {2} + MSB3713: no se pudo crear el archivo "{0}". {1} {2} {StrBegin="MSB3713: "} @@ -3614,7 +3614,7 @@ MSB3943: Failed to zip directory "{0}" to file "{1}". {2} {3} - MSB3943: No se pudo comprimir el directorio "{0}" en el archivo "{1}". {2} {3} + MSB3943: no se pudo comprimir el directorio "{0}" en el archivo "{1}". {2} {3} {StrBegin="MSB3943: "} diff --git a/src/Tasks/Resources/xlf/Strings.fr.xlf b/src/Tasks/Resources/xlf/Strings.fr.xlf index a1bbc4343c5..3de6c90fb8f 100644 --- a/src/Tasks/Resources/xlf/Strings.fr.xlf +++ b/src/Tasks/Resources/xlf/Strings.fr.xlf @@ -156,7 +156,7 @@ MSB3539: The value of the property "BaseIntermediateOutputPath" was modified after it was used by MSBuild which can lead to unexpected build results. Tools such as NuGet will write outputs to the path specified by the "MSBuildProjectExtensionsPath" instead. To set this property, you must do so before Microsoft.Common.props is imported, for example by using Directory.Build.props. For more information, please visit https://go.microsoft.com/fwlink/?linkid=869650" - MSB3539: la valeur de la propriété « BaseIntermediateOutputPath » a été modifiée après son utilisation par MSBuild, ce qui peut entraîner des résultats de build inattendus. Les outils tels que NuGet écrivent des sorties dans le chemin spécifié par « MSBuildProjectExtensionsPath » à la place. Pour définir cette propriété, il faut vous y prendre avant l'importation de Microsoft.Common.props, par exemple en utilisant Directory.Build.props. Pour plus d’informations, visitez https://go.microsoft.com/fwlink/?linkid=869650 » + MSB3539: La valeur de la propriété « BaseIntermediateOutputPath » a été modifiée après son utilisation par MSBuild, ce qui peut entraîner des résultats de build inattendus. Des outils tels que NuGet écriront les sorties dans le chemin spécifié par « MSBuildProjectExtensionsPath ». Pour définir cette propriété, vous devez le faire avant l'importation de Microsoft.Common.props, par exemple en utilisant Directory.Build.props. Pour plus d'informations, veuillez consulter https://go.microsoft.com/fwlink/?linkid=869650" {StrBegin="MSB3539: "} @@ -186,7 +186,7 @@ MSB3540: The value of the property "MSBuildProjectExtensionsPath" was modified after it was used by MSBuild which can lead to unexpected build results. To set this property, you must do so before Microsoft.Common.props is imported, for example by using Directory.Build.props. For more information, please visit https://go.microsoft.com/fwlink/?linkid=869650 - MSB3540: la valeur de la propriété « MSBuildProjectExtensionsPath » a été modifiée après son utilisation par MSBuild, ce qui peut entraîner des résultats de build inattendus. Pour définir cette propriété, il faut vous y prendre avant l'importation de Microsoft.Common.props, par exemple en utilisant Directory.Build.props. Pour plus d’informations, veuillez consulter https://go.microsoft.com/fwlink/?linkid=869650 + MSB3540: La valeur de la propriété « MSBuildProjectExtensionsPath » a été modifiée après son utilisation par MSBuild, ce qui peut entraîner des résultats de build inattendus. Pour définir cette propriété, vous devez le faire avant l'importation de Microsoft.Common.props, par exemple en utilisant Directory.Build.props. Pour plus d'informations, veuillez consulter https://go.microsoft.com/fwlink/?linkid=869650 {StrBegin="MSB3540: "} @@ -201,7 +201,7 @@ MSB9008: The referenced project {0} does not exist. - MSB9008: le projet {0} référencé n’existe pas. + MSB9008: Le projet référencé {0} n'existe pas. @@ -496,7 +496,7 @@ MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3077: la commande « {0} » s’est terminée avec une valeur de retour 0, mais des erreurs ont été détectées lors de l’exécution. ExitCode a été défini sur -1. + MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3077: "} @@ -1185,8 +1185,8 @@ MSB3825: Resource "{0}" will 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 - MSB3825: la ressource « {0} » sera désérialisée via BinaryFormatter lors de l’exécution. BinaryFormatter est déconseillé en raison de risques de sécurité connus et est supprimé de .NET 9+. Si vous souhaitez continuer à l’utiliser, définissez la propriété « GenerateResourceWarnOnBinaryFormatterUse » sur la valeur false. - Plus découvrir d’informations : https://aka.ms/binaryformatter-migration-guide + MSB3825: La ressource « {0} » sera désérialisée par BinaryFormatter au moment de l’exécution. BinaryFormatter est obsolète en raison de risques de sécurité connus et est supprimé de .NET 9+. Si vous souhaitez continuer à l’utiliser, définissez la propriété « GenerateResourceWarnOnBinaryFormatterUse » sur false. + Plus d’informations : https://aka.ms/binaryformatter-migration-guide {StrBegin="MSB3825: "} @@ -1271,22 +1271,22 @@ MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. - MSB3828: génération de propriété de ressource fortement typée ignorée pour la ressource « {0} » : le nom ne peut pas être converti en identificateur valide. + MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. {StrBegin="MSB3828: "} MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. - MSB3829: génération de propriété de ressource fortement typée ignorée pour la ressource « {0} » : une collision de noms existe avec la ressource « {1} » après la normalisation de l’identificateur. + MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. {StrBegin="MSB3829: "} MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. - MSB3827: génération de propriété de ressource fortement typée ignorée pour la ressource « {0} » : le nom est en conflit avec un nom réservé. Noms réservés : {1}. + MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. {StrBegin="MSB3827: "} MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. - MSB3830: génération de propriété de ressource fortement typée ignorée pour la ressource « {0} » : le type de valeur de la ressource est void, qui ne peut pas être utilisé comme type de propriété. + MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. {StrBegin="MSB3830: "} @@ -2924,7 +2924,7 @@ MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3725: la commande « {0} » s’est terminée avec une valeur de retour 0, mais des erreurs ont été détectées lors de l’exécution. ExitCode a été défini sur -1. + MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3725: "} diff --git a/src/Tasks/Resources/xlf/Strings.it.xlf b/src/Tasks/Resources/xlf/Strings.it.xlf index b5aba491c4a..f2593eae909 100644 --- a/src/Tasks/Resources/xlf/Strings.it.xlf +++ b/src/Tasks/Resources/xlf/Strings.it.xlf @@ -39,7 +39,7 @@ MSB3002: Explicitly set culture "{0}" for item "{1}" was overwritten with inferred culture "{2}", because 'RespectAlreadyAssignedItemCulture' property was not set. - MSB3002: La cultura "{0}" impostata in maniera esplicita per l'elemento "{1}" è stata sovrascritta con la cultura dedotta "{2}" perché la proprietà 'RespectAlreadyAssignedItemCulture' non è stata impostata. + MSB3002: "{0}" impostazioni cultura impostate in modo esplicito per l'elemento "{1}" è stato sovrascritto con le impostazioni cultura dedotte "{2}" perché la proprietà 'RespectAlreadyAssignedItemCulture' non è stata impostata. {StrBegin="MSB3002: "} 'RespectAlreadyAssignedItemCulture' should not be translated @@ -146,12 +146,12 @@ MSB3991: '{0}' is not set or empty. When {1} is false, make sure to set a non-empty value for '{0}'. - MSB3991: '{0}' non è impostato o è vuoto. Quando {1} è false, assicurarsi di impostare un valore non vuoto per '{0}'. + MSB3991: “{0}” non è impostato o è vuoto. Quando {1} è false, assicurarsi di impostare un valore non vuoto per "{0}". {StrBegin="MSB3991: "} MSB3992: '{0}' is not set. When {1} is true, make sure to set a value for '{0}'. - MSB3992: '{0}' non è impostato. Quando {1} è true, assicurarsi di impostare un valore per '{0}'. + MSB3992: "{0}" non impostato. Quando {1} è true, assicurarsi di impostare un valore per "{0}". {StrBegin="MSB3992: "} @@ -496,7 +496,7 @@ MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3077: il comando "{0}" è stato chiuso con il valore restituito 0, ma durante l'esecuzione sono stati rilevati errori. ExitCode è stato impostato su -1. + MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3077: "} @@ -1185,7 +1185,7 @@ MSB3825: Resource "{0}" will 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 - MSB3825: la risorsa "{0}" verrà deserializzata tramite BinaryFormatter al runtime. BinaryFormatter è deprecato a causa di rischi noti per la sicurezza ed è stato rimosso da .NET 9+. Se si desidera continuare a usarlo, impostare la proprietà "GenerateResourceWarnOnBinaryFormatterUse" su false. + MSB3825: la risorsa "{0}" verrà deserializzata tramite BinaryFormatter al runtime. BinaryFormatter è deprecato a causa di rischi noti per la sicurezza ed è stato rimosso da .NET 9+. Per continuare a usarlo, imposta la proprietà "GenerateResourceWarnOnBinaryFormatterUse" su false. Altre informazioni: https://aka.ms/binaryformatter-migration-guide {StrBegin="MSB3825: "} @@ -1271,22 +1271,22 @@ MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. - MSB3828: la generazione di proprietà fortemente tipizzate per la risorsa "{0}" verrà ignorata: non è possibile convertire il nome in un identificatore valido. + MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. {StrBegin="MSB3828: "} MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. - MSB3829: la generazione di proprietà fortemente tipizzate per la risorsa "{0}" verrà ignorata: è presente un conflitto di nomi con la risorsa "{1}" dopo la normalizzazione degli identificatori. + MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. {StrBegin="MSB3829: "} MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. - MSB3827: la generazione di proprietà fortemente tipizzate per la risorsa "{0}" verrà ignorata: il nome è in conflitto con un nome riservato. Nomi riservati: {1}. + MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. {StrBegin="MSB3827: "} MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. - MSB3830: la generazione di proprietà fortemente tipizzate per la risorsa "{0}" verrà ignorata: il tipo di valore della risorsa è void, che non può essere usato come tipo di proprietà. + MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. {StrBegin="MSB3830: "} @@ -2924,7 +2924,7 @@ MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3725: il comando "{0}" è stato chiuso con il valore restituito 0, ma durante l'esecuzione sono stati rilevati errori. ExitCode è stato impostato su -1. + MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3725: "} diff --git a/src/Tasks/Resources/xlf/Strings.ja.xlf b/src/Tasks/Resources/xlf/Strings.ja.xlf index 1c9a490b7e7..6dae41b02f3 100644 --- a/src/Tasks/Resources/xlf/Strings.ja.xlf +++ b/src/Tasks/Resources/xlf/Strings.ja.xlf @@ -496,7 +496,7 @@ MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3077: コマンド "{0}" は戻り値 0 で終了しましたが、実行中にエラーが検出されました。ExitCode は -1 に設定されました。 + MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3077: "} @@ -1271,22 +1271,22 @@ MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. - MSB3828: リソース "{0}" の厳密な型付きリソース プロパティの生成をスキップしています。名前を有効な識別子に変換できません。 + MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. {StrBegin="MSB3828: "} MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. - MSB3829: リソース "{0}" の厳密な型付きリソース プロパティの生成をスキップしています。識別子の正規化後にリソース "{1}" と名前の競合が発生します。 + MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. {StrBegin="MSB3829: "} MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. - MSB3827: リソース "{0}" の厳密な型付きリソース プロパティの生成をスキップしています。名前が予約語と競合しています。予約された名前: {1}。 + MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. {StrBegin="MSB3827: "} MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. - MSB3830: リソース "{0}" の厳密な型付きリソース プロパティの生成をスキップしています。リソース値の型が void であり、プロパティの型として使用できません。 + MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. {StrBegin="MSB3830: "} @@ -2924,7 +2924,7 @@ MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3725: コマンド "{0}" は戻り値 0 で終了しましたが、実行中にエラーが検出されました。ExitCode は -1 に設定されました。 + MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3725: "} diff --git a/src/Tasks/Resources/xlf/Strings.ko.xlf b/src/Tasks/Resources/xlf/Strings.ko.xlf index 5a2d828cb01..7882dd8b421 100644 --- a/src/Tasks/Resources/xlf/Strings.ko.xlf +++ b/src/Tasks/Resources/xlf/Strings.ko.xlf @@ -496,7 +496,7 @@ MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3077: 명령 "{0}"이(가) 반환 값 0으로 종료되었지만 실행 중 오류가 감지되었습니다. ExitCode가 -1로 설정되었습니다. + MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3077: "} @@ -1185,7 +1185,7 @@ MSB3825: Resource "{0}" will 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 - MSB3825: 리소스 "{0}"은(는) 런타임 시 BinaryFormatter를 통해 역직렬화됩니다. BinaryFormatter는 알려진 보안 위험으로 인해 사용되지 않으며 .NET 9 이상에서 제거됩니다. 계속 사용하려면 "GenerateResourceWarnOnBinaryFormatterUse" 속성을 false로 설정하세요. + MSB3825: 리소스 "{0}"은(는) 런타임 시 BinaryFormatter를 통해 역직렬화됩니다. BinaryFormatter는 알려진 보안 위험으로 인해 사용되지 않으며 .NET 9 이상에서 제거됩니다. 계속 사용하려면 "GenerateResourceWarnOnBinaryFormatterUse" 속성을 false로 설정합니다. 추가 정보: https://aka.ms/binaryformatter-migration-guide {StrBegin="MSB3825: "} @@ -1271,22 +1271,22 @@ MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. - MSB3828: 리소스 "{0}"에 대해 강력한 형식의 리소스 속성 생성을 건너뛰는 중: 이름을 올바른 식별자로 변환할 수 없습니다. + MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. {StrBegin="MSB3828: "} MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. - MSB3829: 리소스 "{0}"에 대해 강력한 형식의 리소스 속성 생성을 건너뛰는 중: 식별자 정규화 후 리소스 "{1}"과(와) 이름이 충돌합니다. + MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. {StrBegin="MSB3829: "} MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. - MSB3827: 리소스 "{0}"에 대해 강력한 형식의 리소스 속성 생성을 건너뛰는 중: 이름이 예약된 이름과 충돌합니다. 예약된 이름: {1}. + MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. {StrBegin="MSB3827: "} MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. - MSB3830: 리소스 "{0}"에 대해 강력한 형식의 리소스 속성 생성을 건너뛰는 중: 리소스 값 형식이 void이므로 속성 형식으로 사용할 수 없습니다. + MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. {StrBegin="MSB3830: "} @@ -2924,7 +2924,7 @@ MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3725: 명령 "{0}"이(가) 반환 값 0으로 종료되었지만 실행 중 오류가 감지되었습니다. ExitCode가 -1로 설정되었습니다. + MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3725: "} diff --git a/src/Tasks/Resources/xlf/Strings.pl.xlf b/src/Tasks/Resources/xlf/Strings.pl.xlf index 8e8b2953fcb..9aee1b0712a 100644 --- a/src/Tasks/Resources/xlf/Strings.pl.xlf +++ b/src/Tasks/Resources/xlf/Strings.pl.xlf @@ -496,7 +496,7 @@ MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3077: polecenie „{0}” zakończyło się z wartością zwracaną 0, ale podczas wykonywania wykryto błędy. Parametr ExitCode został ustawiony na -1. + MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3077: "} @@ -1185,7 +1185,7 @@ MSB3825: Resource "{0}" will 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 - MSB3825: zasób „{0}” może być deserializowany za pośrednictwem funkcji BinaryFormatter w czasie wykonywania. Funkcja BinaryFormatter jest przestarzała ze względu na znane zagrożenia bezpieczeństwa i została usunięta z platformy .NET 9 lub nowszej. Jeśli chcesz nadal jej używać, ustaw właściwość „GenerateResourceWarnOnBinaryFormatterUse” na wartość false. + MSB3825: zasób „{0}” może być deserializowany za pośrednictwem narzędzia BinaryFormatter w środowisku uruchomieniowym. Narzędzie BinaryFormatter jest przestarzałe ze względu na znane zagrożenia bezpieczeństwa i zostało usunięte z platformy .NET 9+. Jeśli chcesz nadal go używać, ustaw właściwość „GenerateResourceWarnOnBinaryFormatterUse” na wartość false. Więcej informacji: https://aka.ms/binaryformatter-migration-guide {StrBegin="MSB3825: "} @@ -1271,22 +1271,22 @@ MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. - MSB3828: pominięcie generowania silnie typowanej właściwości zasobu dla zasobu „{0}”: nazwa nie może zostać przekształcona w prawidłowy identyfikator. + MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. {StrBegin="MSB3828: "} MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. - MSB3829: pominięcie generowania silnie typowanej właściwości zasobu dla zasobu „{0}”: po normalizacji identyfikatora wystąpiła kolizja nazw z zasobem „{1}”. + MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. {StrBegin="MSB3829: "} MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. - MSB3827: pominięcie generowania silnie typowanej właściwości zasobu dla zasobu „{0}”: nazwa koliduje z nazwą zarezerwowaną. Nazwy zarezerwowane: {1}. + MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. {StrBegin="MSB3827: "} MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. - MSB3830: pominięcie generowania silnie typowanej właściwości zasobu dla zasobu „{0}”: typ wartości zasobu jest nieważny i nie może być użyty jako typ właściwości. + MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. {StrBegin="MSB3830: "} @@ -2924,7 +2924,7 @@ MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3725: polecenie „{0}” zakończyło się z wartością zwracaną 0, ale podczas wykonywania wykryto błędy. Parametr ExitCode został ustawiony na -1. + MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3725: "} diff --git a/src/Tasks/Resources/xlf/Strings.pt-BR.xlf b/src/Tasks/Resources/xlf/Strings.pt-BR.xlf index bdbc7054eee..11af8fea5c4 100644 --- a/src/Tasks/Resources/xlf/Strings.pt-BR.xlf +++ b/src/Tasks/Resources/xlf/Strings.pt-BR.xlf @@ -496,7 +496,7 @@ MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3077: O comando "{0}" foi encerrado com valor retornado 0, mas erros foram detectados durante a execução. ExitCode foi definido como -1. + MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3077: "} @@ -1185,7 +1185,7 @@ MSB3825: Resource "{0}" will 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 - MSB3825: O recurso "{0}" será desserializado via BinaryFormatter em tempo de execução. BinaryFormatter foi preterido devido a riscos de segurança conhecidos e foi removido do .NET 9+. Se você quiser continuar a usá-lo, defina a propriedade "GenerateResourceWarnOnBinaryFormatterUse" como falso. + MSB3825: O recurso "{0}" 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 você quiser continuar a usá-lo, defina a propriedade "GenerateResourceWarnOnBinaryFormatterUse" como false. Mais informações: https://aka.ms/binaryformatter-migration-guide {StrBegin="MSB3825: "} @@ -1271,22 +1271,22 @@ MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. - MSB3828: ignorando a geração de propriedade de recurso fortemente tipada para o recurso "{0}": o nome não pode ser convertido em um identificador válido. + MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. {StrBegin="MSB3828: "} MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. - MSB3829: ignorando a geração de propriedade de recurso fortemente tipada para o recurso "{0}": existe uma colisão de nomes com o recurso "{1}" após a normalização do identificador. + MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. {StrBegin="MSB3829: "} MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. - MSB3827: ignorando a geração de propriedade de recurso fortemente tipada para o recurso "{0}": o nome está em conflito com um nome reservado. Nomes reservados: {1}. + MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. {StrBegin="MSB3827: "} MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. - MSB3830: ignorando a geração de propriedade de recurso fortemente tipada para o recurso "{0}": o tipo do valor do recurso é nulo e não pode ser usado como tipo de propriedade. + MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. {StrBegin="MSB3830: "} @@ -2924,7 +2924,7 @@ MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3725: O comando "{0}" foi encerrado com valor retornado 0, mas erros foram detectados durante a execução. ExitCode foi definido como -1. + MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3725: "} diff --git a/src/Tasks/Resources/xlf/Strings.ru.xlf b/src/Tasks/Resources/xlf/Strings.ru.xlf index f5fedc7bcbe..53631c4d8b7 100644 --- a/src/Tasks/Resources/xlf/Strings.ru.xlf +++ b/src/Tasks/Resources/xlf/Strings.ru.xlf @@ -141,7 +141,7 @@ MSB3752: The "{0}" attribute of the <{1}> element in the task "{2}" has been set but is empty. Make sure the attribute has a proper value. - MSB3752: атрибут "{0}" элемента <{1}> в задаче "{2}" установлен, но пуст. Предоставьте правильное значение атрибута. + MSB3752: "{0}" элемента <{1}> в задаче "{2}", но пуст. Убедитесь, что атрибут имеет правильное значение. {StrBegin="MSB3752: "} @@ -496,7 +496,7 @@ MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3077: команда "{0}" завершилась со значением возврата 0, но во время выполнения были обнаружены ошибки. Значение ExitCode задано как -1. + MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3077: "} @@ -1185,8 +1185,8 @@ MSB3825: Resource "{0}" will 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 - MSB3825: для ресурса "{0}" будет выполнена десериализация с помощью BinaryFormatter во время выполнения. Сериализация BinaryFormatter упразднена из-за известных рисков безопасности и удалена из .NET 9 и более поздних версий. Чтобы продолжить использовать эту сериализацию, задайте для свойства "GenerateResourceWarnOnBinaryFormatterUse" значение false. - Подробнее: https://aka.ms/binaryformatter-migration-guide + MSB3825: для ресурса "{0}" будет выполнена десериализация с помощью BinaryFormatter во время выполнения. BinaryFormatter является нерекомендуемым из-за известных рисков безопасности и удален из .NET 9+. Если вы хотите продолжить использовать его, задайте для свойства GenerateResourceWarnOnBinaryFormatterUse значение false. + Дополнительные сведения: https://aka.ms/binaryformatter-migration-guide {StrBegin="MSB3825: "} @@ -1271,22 +1271,22 @@ MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. - MSB3828: пропуск создания свойства ресурса со строгой типизацией для ресурса "{0}": имя невозможно преобразовать в допустимый идентификатор. + MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. {StrBegin="MSB3828: "} MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. - MSB3829: пропуск создания свойства ресурса со строгой типизацией для ресурса "{0}": после нормализации идентификатора возникает конфликт имен с ресурсом "{1}". + MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. {StrBegin="MSB3829: "} MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. - MSB3827: пропуск создания свойства ресурса со строгой типизацией для ресурса "{0}": имя конфликтует с зарезервированным именем. Зарезервированные имена: {1}. + MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. {StrBegin="MSB3827: "} MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. - MSB3830: пропуск создания свойства ресурса со строгой типизацией для ресурса "{0}": тип значения ресурса — void, который нельзя использовать в качестве типа свойства. + MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. {StrBegin="MSB3830: "} @@ -2924,7 +2924,7 @@ MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3725: команда "{0}" завершилась со значением возврата 0, но во время выполнения были обнаружены ошибки. Значение ExitCode задано как -1. + MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3725: "} diff --git a/src/Tasks/Resources/xlf/Strings.tr.xlf b/src/Tasks/Resources/xlf/Strings.tr.xlf index 88671129bf6..3f4b584e115 100644 --- a/src/Tasks/Resources/xlf/Strings.tr.xlf +++ b/src/Tasks/Resources/xlf/Strings.tr.xlf @@ -496,7 +496,7 @@ MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3077: "{0}" komutu 0 dönüş değeriyle tamamlandı ancak yürütme sırasında hatalar algılandı. ExitCode -1 olarak ayarlandı. + MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3077: "} @@ -1185,7 +1185,7 @@ MSB3825: Resource "{0}" will 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 - MSB3825: "{0}" kaynağı çalışma zamanında BinaryFormatter aracılığıyla seri durumdan çıkarılacak. BinaryFormatter, bilinen güvenlik riskleri nedeniyle kullanım dışı bırakıldı ve .NET 9+'dan kaldırdı. Kullanmaya devam etmek istiyorsanız "GenerateResourceWarnOnBinaryFormatterUse" özelliğini false olarak ayarlayın. + MSB3825: "{0}" kaynağı çalışma zamanında BinaryFormatter aracılığıyla seri durumdan çıkarılacak. BinaryFormatter, bilinen güvenlik riskleri nedeniyle kullanım dışıdır ve .NET 9+'dan kaldırılır. Kullanmaya devam etmek istiyorsanız "GenerateResourceWarnOnBinaryFormatterUse" özelliğini false olarak ayarlayın. Daha fazla bilgi için bkz. https://aka.ms/binaryformatter-migration-guide {StrBegin="MSB3825: "} @@ -1271,22 +1271,22 @@ MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. - MSB3828: "{0}" kaynağı için kesin türde kaynak özelliği oluşturma atlanıyor: ad geçerli bir tanımlayıcıya dönüştürülemiyor. + MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. {StrBegin="MSB3828: "} MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. - MSB3829: "{0}" kaynağı için kesin türde kaynak özelliği oluşturma atlanıyor: tanımlayıcı normalleştirmeden sonra "{1}" kaynağı ile ad çakışması var. + MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. {StrBegin="MSB3829: "} MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. - MSB3827: "{0}" kaynağı için kesin türde kaynak özelliği oluşturma atlanıyor: ad ayrılmış bir adla çakışıyor. Ayrılmış adlar: {1}. + MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. {StrBegin="MSB3827: "} MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. - MSB3830: "{0}" kaynağı için kesin türde kaynak özelliği oluşturma atlanıyor: kaynak değeri türü hükümsüz ve özellik türü olarak kullanılamaz. + MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. {StrBegin="MSB3830: "} @@ -2924,7 +2924,7 @@ MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3725: "{0}" komutu 0 dönüş değeriyle tamamlandı ancak yürütme sırasında hatalar algılandı. ExitCode -1 olarak ayarlandı. + MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3725: "} diff --git a/src/Tasks/Resources/xlf/Strings.zh-Hans.xlf b/src/Tasks/Resources/xlf/Strings.zh-Hans.xlf index 85c481533a7..721956f389f 100644 --- a/src/Tasks/Resources/xlf/Strings.zh-Hans.xlf +++ b/src/Tasks/Resources/xlf/Strings.zh-Hans.xlf @@ -496,7 +496,7 @@ MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3077: 命令“{0}”已退出，返回值为 0，但执行过程中检测到错误。ExitCode 被设置为 -1。 + MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3077: "} @@ -1185,8 +1185,8 @@ MSB3825: Resource "{0}" will 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 - MSB3825: 在运行时将通过 BinaryFormatter 反序列化资源“{0}”。由于已知的安全风险，BinaryFormatter 已弃用，并从 .NET 9+ 中删除。如果要继续使用它，请将属性 "GenerateResourceWarnOnBinaryFormatterUse" 设置为 false。 - 有关详细信息，请参阅：https://aka.ms/binaryformatter-migration-guide + MSB3825: 将在运行时通过 BinaryFormatter 反序列化资源“{0}”。由于已知的安全风险，BinaryFormatter 已被弃用，并已从 .NET 9+ 中移除。如果要继续使用它，请将属性 "GenerateResourceWarnOnBinaryFormatterUse" 设置为 false。 + 有关详细信息，请参阅: https://aka.ms/binaryformatter-migration-guide {StrBegin="MSB3825: "} @@ -1271,22 +1271,22 @@ MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. - MSB3828: 正在跳过对资源 "{0}" 的强类型资源属性生成: 无法将名称转换为有效标识符。 + MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. {StrBegin="MSB3828: "} MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. - MSB3829: 正在跳过对资源 "{0}" 的强类型资源属性生成: 标识符规范化后，存在与资源 "{1}" 的名称冲突。 + MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. {StrBegin="MSB3829: "} MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. - MSB3827: 正在跳过对资源 "{0}" 的强类型资源属性生成: 该名称与保留名称冲突。保留名称: {1}。 + MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. {StrBegin="MSB3827: "} MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. - MSB3830: 正在跳过对资源 "{0}" 的强类型资源属性生成: 资源值类型无效，不能用作属性类型。 + MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. {StrBegin="MSB3830: "} @@ -2924,7 +2924,7 @@ MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3725: 命令“{0}”已退出，返回值为 0，但执行过程中检测到错误。ExitCode 被设置为 -1。 + MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3725: "} diff --git a/src/Tasks/Resources/xlf/Strings.zh-Hant.xlf b/src/Tasks/Resources/xlf/Strings.zh-Hant.xlf index f5241dfc562..e945f04452e 100644 --- a/src/Tasks/Resources/xlf/Strings.zh-Hant.xlf +++ b/src/Tasks/Resources/xlf/Strings.zh-Hant.xlf @@ -496,7 +496,7 @@ MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3077: 命令 "{0}" 已結束且傳回值為 0，但在執行期間偵測到錯誤。ExitCode 已設定為 -1。 + MSB3077: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3077: "} @@ -1185,7 +1185,7 @@ MSB3825: Resource "{0}" will 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 - MSB3825: 資源「{0}」會在執行階段透過 BinaryFormatter 進行還原序列化。BinaryFormatter 已因已知的安全性風險而被取代，且已從 .NET 9+ 中移除。如果您想要繼續使用它，請將屬性 "GenerateResourceWarnOnBinaryFormatterUse" 設為 false。 + MSB3825: 資源 "{0}" 會在執行階段透過 BinaryFormatter 進行還原序列化。BinaryFormatter 已因已知的安全性風險遭棄用，且已從 .NET 9+ 中移除。如果您想要繼續使用它，請將屬性 "GenerateResourceWarnOnBinaryFormatterUse" 設為 false。 詳細資訊: https://aka.ms/binaryformatter-migration-guide {StrBegin="MSB3825: "} @@ -1271,22 +1271,22 @@ MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. - MSB3828: 已略過為資源「{0}」產生強型別資源屬性: 該名稱無法轉換為有效識別碼。 + MSB3828: Skipping strongly typed resource property generation for resource "{0}": the name cannot be converted to a valid identifier. {StrBegin="MSB3828: "} MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. - MSB3829: 已略過為資源「{0}」產生強型別資源屬性: 識別碼正規化後與資源「{1}」發生名稱衝突。 + MSB3829: Skipping strongly typed resource property generation for resource "{0}": a name collision exists with resource "{1}" after identifier normalization. {StrBegin="MSB3829: "} MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. - MSB3827: 已略過為資源「{0}」產生強型別資源屬性: 該名稱與保留名稱衝突。保留名稱: {1}。 + MSB3827: Skipping strongly typed resource property generation for resource "{0}": the name conflicts with a reserved name. Reserved names: {1}. {StrBegin="MSB3827: "} MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. - MSB3830: 已略過為資源「{0}」產生強型別資源屬性: 該資源的值型別為 void，無法作為屬性型別使用。 + MSB3830: Skipping strongly typed resource property generation for resource "{0}": the resource value type is void, which cannot be used as a property type. {StrBegin="MSB3830: "} @@ -2924,7 +2924,7 @@ MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - MSB3725: 命令 "{0}" 已結束且傳回值為 0，但在執行期間偵測到錯誤。ExitCode 已設定為 -1。 + MSB3725: The command "{0}" exited with return value 0, but errors were detected during execution. ExitCode was set to -1. {StrBegin="MSB3725: "} diff --git a/src/Utilities/Resources/xlf/Strings.cs.xlf b/src/Utilities/Resources/xlf/Strings.cs.xlf index 01efc804e00..20b1063af24 100644 --- a/src/Utilities/Resources/xlf/Strings.cs.xlf +++ b/src/Utilities/Resources/xlf/Strings.cs.xlf @@ -79,7 +79,7 @@ The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - Příkaz byl ukončen s návratovou hodnotou 0, ale během provádění byly zjištěny chyby. Hodnota ExitCode byla nastavena na hodnotu -1. + The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. diff --git a/src/Utilities/Resources/xlf/Strings.de.xlf b/src/Utilities/Resources/xlf/Strings.de.xlf index f31ae54aa3e..04eef157884 100644 --- a/src/Utilities/Resources/xlf/Strings.de.xlf +++ b/src/Utilities/Resources/xlf/Strings.de.xlf @@ -79,7 +79,7 @@ The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - Der Befehl wurde mit dem Rückgabewert 0 beendet, jedoch wurden während der Ausführung Fehler festgestellt. ExitCode wurde auf -1 festgelegt. + The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. diff --git a/src/Utilities/Resources/xlf/Strings.es.xlf b/src/Utilities/Resources/xlf/Strings.es.xlf index 25a603833f9..fafd8f5c658 100644 --- a/src/Utilities/Resources/xlf/Strings.es.xlf +++ b/src/Utilities/Resources/xlf/Strings.es.xlf @@ -79,7 +79,7 @@ The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - El comando se cerró con el valor devuelto 0, pero se detectaron errores durante la ejecución. ExitCode se estableció en -1. + The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. diff --git a/src/Utilities/Resources/xlf/Strings.fr.xlf b/src/Utilities/Resources/xlf/Strings.fr.xlf index 9f7081d4b93..174dab13f6f 100644 --- a/src/Utilities/Resources/xlf/Strings.fr.xlf +++ b/src/Utilities/Resources/xlf/Strings.fr.xlf @@ -79,7 +79,7 @@ The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - La commande s’est terminée avec une valeur de retour 0, mais des erreurs ont été détectées lors de l’exécution. ExitCode a été défini sur -1. + The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. diff --git a/src/Utilities/Resources/xlf/Strings.it.xlf b/src/Utilities/Resources/xlf/Strings.it.xlf index b8571d61ca5..2b502e91b59 100644 --- a/src/Utilities/Resources/xlf/Strings.it.xlf +++ b/src/Utilities/Resources/xlf/Strings.it.xlf @@ -79,7 +79,7 @@ The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - Il comando è stato chiuso con il valore restituito 0, ma durante l'esecuzione sono stati rilevati errori. ExitCode è stato impostato su -1. + The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. diff --git a/src/Utilities/Resources/xlf/Strings.ja.xlf b/src/Utilities/Resources/xlf/Strings.ja.xlf index 32d07e722b9..8cabe703861 100644 --- a/src/Utilities/Resources/xlf/Strings.ja.xlf +++ b/src/Utilities/Resources/xlf/Strings.ja.xlf @@ -79,7 +79,7 @@ The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - コマンドは戻り値 0 で終了しましたが、実行中にエラーが検出されました。ExitCode は -1 に設定されました。 + The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. diff --git a/src/Utilities/Resources/xlf/Strings.ko.xlf b/src/Utilities/Resources/xlf/Strings.ko.xlf index 92717cf6b5f..24d51233541 100644 --- a/src/Utilities/Resources/xlf/Strings.ko.xlf +++ b/src/Utilities/Resources/xlf/Strings.ko.xlf @@ -79,7 +79,7 @@ The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - 명령이 반환 값 0으로 종료되었지만 실행 중 오류가 감지되었습니다. ExitCode가 -1로 설정되었습니다. + The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. diff --git a/src/Utilities/Resources/xlf/Strings.pl.xlf b/src/Utilities/Resources/xlf/Strings.pl.xlf index a9cd195e78e..606515b0da2 100644 --- a/src/Utilities/Resources/xlf/Strings.pl.xlf +++ b/src/Utilities/Resources/xlf/Strings.pl.xlf @@ -79,7 +79,7 @@ The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - Polecenie zakończyło się z wartością zwracaną 0, ale podczas wykonywania wykryto błędy. Parametr ExitCode został ustawiony na -1. + The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. diff --git a/src/Utilities/Resources/xlf/Strings.pt-BR.xlf b/src/Utilities/Resources/xlf/Strings.pt-BR.xlf index 1ad5f8e64c4..95ed3e538b9 100644 --- a/src/Utilities/Resources/xlf/Strings.pt-BR.xlf +++ b/src/Utilities/Resources/xlf/Strings.pt-BR.xlf @@ -79,7 +79,7 @@ The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - O comando foi encerrado com valor retornado 0, mas erros foram detectados durante a execução. ExitCode foi definido como -1. + The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. diff --git a/src/Utilities/Resources/xlf/Strings.ru.xlf b/src/Utilities/Resources/xlf/Strings.ru.xlf index 76e99c6ee79..3ed458e0e43 100644 --- a/src/Utilities/Resources/xlf/Strings.ru.xlf +++ b/src/Utilities/Resources/xlf/Strings.ru.xlf @@ -79,7 +79,7 @@ The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - Команда завершилась со значением возврата 0, но во время выполнения были обнаружены ошибки. Значение ExitCode задано как -1. + The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. diff --git a/src/Utilities/Resources/xlf/Strings.tr.xlf b/src/Utilities/Resources/xlf/Strings.tr.xlf index ad4d04c0dc3..f4c8275d130 100644 --- a/src/Utilities/Resources/xlf/Strings.tr.xlf +++ b/src/Utilities/Resources/xlf/Strings.tr.xlf @@ -79,7 +79,7 @@ The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - Komut 0 dönüş değeriyle tamamlandı ancak yürütme sırasında hatalar algılandı. ExitCode -1 olarak ayarlandı. + The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. diff --git a/src/Utilities/Resources/xlf/Strings.zh-Hans.xlf b/src/Utilities/Resources/xlf/Strings.zh-Hans.xlf index 1513cad0038..08745406099 100644 --- a/src/Utilities/Resources/xlf/Strings.zh-Hans.xlf +++ b/src/Utilities/Resources/xlf/Strings.zh-Hans.xlf @@ -79,7 +79,7 @@ The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - 命令已退出，返回值为 0，但执行过程中检测到错误。ExitCode 被设置为 -1。 + The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. diff --git a/src/Utilities/Resources/xlf/Strings.zh-Hant.xlf b/src/Utilities/Resources/xlf/Strings.zh-Hant.xlf index 9b40829dcf6..b11d045013b 100644 --- a/src/Utilities/Resources/xlf/Strings.zh-Hant.xlf +++ b/src/Utilities/Resources/xlf/Strings.zh-Hant.xlf @@ -79,7 +79,7 @@ The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1. - 命令已結束且傳回值為 0，但在執行期間偵測到錯誤。ExitCode 已設定為 -1。 + The command exited with return value 0, but errors were detected during execution. ExitCode was set to -1.