diff --git a/src/Build/Resources/xlf/Strings.cs.xlf b/src/Build/Resources/xlf/Strings.cs.xlf index a04e8adbf9a..9a8c025d6f5 100644 --- a/src/Build/Resources/xlf/Strings.cs.xlf +++ b/src/Build/Resources/xlf/Strings.cs.xlf @@ -731,7 +731,7 @@ Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. - Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. + Při vytváření objektu Project není podporované částečné vyhodnocení (fáze vyhodnocení „{0}“). K částečnému vyhodnocení použijte ProjectInstance. Případně vytvořte Project ve fázi vyhodnocení Full. UE: This message is shown when a partial (non-Full) ProjectEvaluationStage is passed to a Project factory method such as Project.FromFile. {0} is the requested ProjectEvaluationStage. @@ -3319,6 +3319,142 @@ Využití: Průměrné využití {0}: {1:###.0} MSB4247: Překladač sady SDK se nepodařilo načíst. Soubor manifestu existuje, ale cestu k souboru DLL překladače sady SDK se nepodařilo najít. Cesta k souboru manifestu: {0}. Cesta k překladači sady SDK: {1} {StrBegin="MSB4247: "} + + MSB4188: Build was canceled. + MSB4188: Build was canceled. + {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. + + + 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 + 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 + + + + MSB4025: The project file could not be loaded. {0} + MSB4025: The project file could not be loaded. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. + + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}" is not a valid logger verbosity level. + {StrBegin="MSB4103: "} + + + This collection is read-only. + This collection is read-only. + + + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: The project file is malformed: "{0}". {1} + {StrBegin="MSB5019: "} + + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: Could not load the project file: "{0}". {1} + {StrBegin="MSB5020: "} + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5004: The solution file has two projects named "{0}". + MSB5004: The solution file has two projects named "{0}". + {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. + + + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. + + + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. + + + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. + + + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the nested project section in solution file. + MSB5009: Error parsing the nested project section in solution file. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. + + + MSB5010: No file format header found. + MSB5010: No file format header found. + {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. + + + MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: Parent project GUID not found in "{0}" project dependency section. + {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. + + + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. + + + MSB5013: Error parsing a project section. + MSB5013: Error parsing a project section. + {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. + + + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. + + + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. + + + Solution file + Solution file + UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: + "MSBUILD : Solution file error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + + Unrecognized solution version "{0}", attempting to continue. + Unrecognized solution version "{0}", attempting to continue. + + - + \ No newline at end of file diff --git a/src/Build/Resources/xlf/Strings.de.xlf b/src/Build/Resources/xlf/Strings.de.xlf index 593a7f2b7ad..a0b88caca84 100644 --- a/src/Build/Resources/xlf/Strings.de.xlf +++ b/src/Build/Resources/xlf/Strings.de.xlf @@ -731,7 +731,7 @@ Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. - Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. + Die Teilauswertung (die Auswertungsphase „{0}“) wird beim Erstellen eines Projekts nicht unterstützt. Verwenden Sie ProjectInstance, um eine Teilauswertung durchzuführen, oder verwenden Sie die vollständige Auswertungsphase, um ein Projekt zu erstellen. UE: This message is shown when a partial (non-Full) ProjectEvaluationStage is passed to a Project factory method such as Project.FromFile. {0} is the requested ProjectEvaluationStage. @@ -3319,6 +3319,142 @@ Auslastung: {0} Durchschnittliche Auslastung: {1:###.0} MSB4247: Der SDK-Resolver konnte nicht geladen werden. Eine Manifestdatei ist vorhanden, aber der Pfad zur SDK-Resolver-DLL-Datei wurde nicht gefunden. Manifestdateipfad: {0}. SDK-Resolverpfad: {1} {StrBegin="MSB4247: "} + + MSB4188: Build was canceled. + MSB4188: Build was canceled. + {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. + + + 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 + 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 + + + + MSB4025: The project file could not be loaded. {0} + MSB4025: The project file could not be loaded. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. + + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}" is not a valid logger verbosity level. + {StrBegin="MSB4103: "} + + + This collection is read-only. + This collection is read-only. + + + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: The project file is malformed: "{0}". {1} + {StrBegin="MSB5019: "} + + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: Could not load the project file: "{0}". {1} + {StrBegin="MSB5020: "} + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5004: The solution file has two projects named "{0}". + MSB5004: The solution file has two projects named "{0}". + {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. + + + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. + + + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. + + + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. + + + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the nested project section in solution file. + MSB5009: Error parsing the nested project section in solution file. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. + + + MSB5010: No file format header found. + MSB5010: No file format header found. + {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. + + + MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: Parent project GUID not found in "{0}" project dependency section. + {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. + + + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. + + + MSB5013: Error parsing a project section. + MSB5013: Error parsing a project section. + {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. + + + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. + + + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. + + + Solution file + Solution file + UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: + "MSBUILD : Solution file error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + + Unrecognized solution version "{0}", attempting to continue. + Unrecognized solution version "{0}", attempting to continue. + + - + \ No newline at end of file diff --git a/src/Build/Resources/xlf/Strings.es.xlf b/src/Build/Resources/xlf/Strings.es.xlf index 6ceebabcb6e..384b533e01a 100644 --- a/src/Build/Resources/xlf/Strings.es.xlf +++ b/src/Build/Resources/xlf/Strings.es.xlf @@ -731,7 +731,7 @@ Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. - Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. + No se admite la evaluación parcial (la fase de evaluación "{0}") al crear un proyecto. Use ProjectInstance para realizar una evaluación parcial o use la fase de evaluación completa para crear un proyecto. UE: This message is shown when a partial (non-Full) ProjectEvaluationStage is passed to a Project factory method such as Project.FromFile. {0} is the requested ProjectEvaluationStage. @@ -3319,6 +3319,142 @@ Utilización: Utilización media de {0}: {1:###.0} MSB4247: No se pudo cargar la resolución de SDK. Existe un archivo de manifiesto, pero no se encuentra la ruta de acceso al archivo DLL de la resolución del SDK. Ruta de acceso del archivo de manifiesto: {0}. Ruta de acceso de resolución de SDK: {1} {StrBegin="MSB4247: "} + + MSB4188: Build was canceled. + MSB4188: Build was canceled. + {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. + + + 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 + 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 + + + + MSB4025: The project file could not be loaded. {0} + MSB4025: The project file could not be loaded. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. + + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}" is not a valid logger verbosity level. + {StrBegin="MSB4103: "} + + + This collection is read-only. + This collection is read-only. + + + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: The project file is malformed: "{0}". {1} + {StrBegin="MSB5019: "} + + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: Could not load the project file: "{0}". {1} + {StrBegin="MSB5020: "} + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5004: The solution file has two projects named "{0}". + MSB5004: The solution file has two projects named "{0}". + {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. + + + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. + + + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. + + + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. + + + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the nested project section in solution file. + MSB5009: Error parsing the nested project section in solution file. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. + + + MSB5010: No file format header found. + MSB5010: No file format header found. + {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. + + + MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: Parent project GUID not found in "{0}" project dependency section. + {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. + + + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. + + + MSB5013: Error parsing a project section. + MSB5013: Error parsing a project section. + {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. + + + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. + + + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. + + + Solution file + Solution file + UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: + "MSBUILD : Solution file error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + + Unrecognized solution version "{0}", attempting to continue. + Unrecognized solution version "{0}", attempting to continue. + + - + \ No newline at end of file diff --git a/src/Build/Resources/xlf/Strings.fr.xlf b/src/Build/Resources/xlf/Strings.fr.xlf index 5f4af27800d..7d1dfb1dd41 100644 --- a/src/Build/Resources/xlf/Strings.fr.xlf +++ b/src/Build/Resources/xlf/Strings.fr.xlf @@ -731,7 +731,7 @@ Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. - Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. + L’évaluation partielle (l’étape d’évaluation « {0} ») n’est pas prise en charge lors de la création d’un Project. Utilisez ProjectInstance pour effectuer une évaluation partielle ou utilisez l’étape d’évaluation complète pour créer un Project. UE: This message is shown when a partial (non-Full) ProjectEvaluationStage is passed to a Project factory method such as Project.FromFile. {0} is the requested ProjectEvaluationStage. @@ -3319,6 +3319,142 @@ Utilisation : {0} Utilisation moyenne : {1:###.0} MSB4247: Impossible de charger le programme de résolution de SDK. Un fichier manifeste existe, mais le chemin au fichier DLL du programme de résolution de SDK est introuvable. Chemin du fichier manifeste : '{0}'. Chemin du programme de résolution de SDK : {1} {StrBegin="MSB4247: "} + + MSB4188: Build was canceled. + MSB4188: Build was canceled. + {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. + + + 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 + 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 + + + + MSB4025: The project file could not be loaded. {0} + MSB4025: The project file could not be loaded. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. + + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}" is not a valid logger verbosity level. + {StrBegin="MSB4103: "} + + + This collection is read-only. + This collection is read-only. + + + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: The project file is malformed: "{0}". {1} + {StrBegin="MSB5019: "} + + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: Could not load the project file: "{0}". {1} + {StrBegin="MSB5020: "} + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5004: The solution file has two projects named "{0}". + MSB5004: The solution file has two projects named "{0}". + {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. + + + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. + + + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. + + + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. + + + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the nested project section in solution file. + MSB5009: Error parsing the nested project section in solution file. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. + + + MSB5010: No file format header found. + MSB5010: No file format header found. + {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. + + + MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: Parent project GUID not found in "{0}" project dependency section. + {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. + + + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. + + + MSB5013: Error parsing a project section. + MSB5013: Error parsing a project section. + {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. + + + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. + + + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. + + + Solution file + Solution file + UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: + "MSBUILD : Solution file error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + + Unrecognized solution version "{0}", attempting to continue. + Unrecognized solution version "{0}", attempting to continue. + + - + \ No newline at end of file diff --git a/src/Build/Resources/xlf/Strings.it.xlf b/src/Build/Resources/xlf/Strings.it.xlf index b37d83458e6..7ab3fbbfd19 100644 --- a/src/Build/Resources/xlf/Strings.it.xlf +++ b/src/Build/Resources/xlf/Strings.it.xlf @@ -731,7 +731,7 @@ Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. - Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. + La valutazione parziale (fase di valutazione "{0}") non è supportata durante la creazione di un'istanza di Project. Usare ProjectInstance per eseguire una valutazione parziale oppure usare la fase Valutazione completa per creare un'istanza di Project. UE: This message is shown when a partial (non-Full) ProjectEvaluationStage is passed to a Project factory method such as Project.FromFile. {0} is the requested ProjectEvaluationStage. @@ -3319,6 +3319,142 @@ Utilizzo: {0} Utilizzo medio: {1:###.0} MSB4247: non è stato possibile caricare il resolver di SDK. Il file manifesto è presente, ma non è stato possibile trovare il percorso del file DLL del resolver. Percorso del file manifesto: '{0}'. Percorso del resolver di SDK: {1} {StrBegin="MSB4247: "} + + MSB4188: Build was canceled. + MSB4188: Build was canceled. + {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. + + + 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 + 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 + + + + MSB4025: The project file could not be loaded. {0} + MSB4025: The project file could not be loaded. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. + + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}" is not a valid logger verbosity level. + {StrBegin="MSB4103: "} + + + This collection is read-only. + This collection is read-only. + + + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: The project file is malformed: "{0}". {1} + {StrBegin="MSB5019: "} + + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: Could not load the project file: "{0}". {1} + {StrBegin="MSB5020: "} + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5004: The solution file has two projects named "{0}". + MSB5004: The solution file has two projects named "{0}". + {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. + + + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. + + + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. + + + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. + + + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the nested project section in solution file. + MSB5009: Error parsing the nested project section in solution file. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. + + + MSB5010: No file format header found. + MSB5010: No file format header found. + {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. + + + MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: Parent project GUID not found in "{0}" project dependency section. + {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. + + + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. + + + MSB5013: Error parsing a project section. + MSB5013: Error parsing a project section. + {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. + + + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. + + + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. + + + Solution file + Solution file + UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: + "MSBUILD : Solution file error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + + Unrecognized solution version "{0}", attempting to continue. + Unrecognized solution version "{0}", attempting to continue. + + - + \ No newline at end of file diff --git a/src/Build/Resources/xlf/Strings.ja.xlf b/src/Build/Resources/xlf/Strings.ja.xlf index bd701fae979..04b9d0538ac 100644 --- a/src/Build/Resources/xlf/Strings.ja.xlf +++ b/src/Build/Resources/xlf/Strings.ja.xlf @@ -731,7 +731,7 @@ Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. - Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. + Project の作成時に、部分評価 ("{0}" 評価ステージ) はサポートされていません。部分評価を実行するには ProjectInstance を使用するか、Project を作成するには Full 評価ステージを使用してください。 UE: This message is shown when a partial (non-Full) ProjectEvaluationStage is passed to a Project factory method such as Project.FromFile. {0} is the requested ProjectEvaluationStage. @@ -3319,6 +3319,142 @@ Utilization: {0} Average Utilization: {1:###.0} MSB4247: SDK 競合回避モジュールを読み込めませんでした。マニフェスト ファイルは存在しますが、SDK 競合回避モジュール DLL ファイルへのパスが見つかりませんでした。マニフェスト ファイル パス '{0}'。SDK 競合回避モジュール パス: {1} {StrBegin="MSB4247: "} + + MSB4188: Build was canceled. + MSB4188: Build was canceled. + {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. + + + 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 + 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 + + + + MSB4025: The project file could not be loaded. {0} + MSB4025: The project file could not be loaded. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. + + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}" is not a valid logger verbosity level. + {StrBegin="MSB4103: "} + + + This collection is read-only. + This collection is read-only. + + + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: The project file is malformed: "{0}". {1} + {StrBegin="MSB5019: "} + + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: Could not load the project file: "{0}". {1} + {StrBegin="MSB5020: "} + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5004: The solution file has two projects named "{0}". + MSB5004: The solution file has two projects named "{0}". + {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. + + + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. + + + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. + + + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. + + + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the nested project section in solution file. + MSB5009: Error parsing the nested project section in solution file. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. + + + MSB5010: No file format header found. + MSB5010: No file format header found. + {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. + + + MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: Parent project GUID not found in "{0}" project dependency section. + {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. + + + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. + + + MSB5013: Error parsing a project section. + MSB5013: Error parsing a project section. + {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. + + + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. + + + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. + + + Solution file + Solution file + UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: + "MSBUILD : Solution file error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + + Unrecognized solution version "{0}", attempting to continue. + Unrecognized solution version "{0}", attempting to continue. + + - + \ No newline at end of file diff --git a/src/Build/Resources/xlf/Strings.ko.xlf b/src/Build/Resources/xlf/Strings.ko.xlf index 51e8204c5dc..cd4de490bab 100644 --- a/src/Build/Resources/xlf/Strings.ko.xlf +++ b/src/Build/Resources/xlf/Strings.ko.xlf @@ -731,7 +731,7 @@ Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. - Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. + 프로젝트를 만들 때는 부분 평가("{0}" 평가 단계)를 지원하지 않습니다. 부분 평가를 수행하려면 ProjectInstance를 사용하세요. 프로젝트를 만들려면 전체 평가 단계(Full evaluation stage)를 사용하세요. UE: This message is shown when a partial (non-Full) ProjectEvaluationStage is passed to a Project factory method such as Project.FromFile. {0} is the requested ProjectEvaluationStage. @@ -3319,6 +3319,142 @@ Utilization: {0} Average Utilization: {1:###.0} MSB4247: SDK 확인자를 로드할 수 없습니다. 매니페스트 파일이 있지만 SDK 확인자 DLL 파일에 대한 경로를 찾을 수 없습니다. 매니페스트 파일 경로 '{0}'. SDK 확인자 경로: {1} {StrBegin="MSB4247: "} + + MSB4188: Build was canceled. + MSB4188: Build was canceled. + {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. + + + 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 + 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 + + + + MSB4025: The project file could not be loaded. {0} + MSB4025: The project file could not be loaded. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. + + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}" is not a valid logger verbosity level. + {StrBegin="MSB4103: "} + + + This collection is read-only. + This collection is read-only. + + + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: The project file is malformed: "{0}". {1} + {StrBegin="MSB5019: "} + + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: Could not load the project file: "{0}". {1} + {StrBegin="MSB5020: "} + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5004: The solution file has two projects named "{0}". + MSB5004: The solution file has two projects named "{0}". + {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. + + + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. + + + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. + + + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. + + + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the nested project section in solution file. + MSB5009: Error parsing the nested project section in solution file. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. + + + MSB5010: No file format header found. + MSB5010: No file format header found. + {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. + + + MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: Parent project GUID not found in "{0}" project dependency section. + {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. + + + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. + + + MSB5013: Error parsing a project section. + MSB5013: Error parsing a project section. + {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. + + + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. + + + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. + + + Solution file + Solution file + UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: + "MSBUILD : Solution file error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + + Unrecognized solution version "{0}", attempting to continue. + Unrecognized solution version "{0}", attempting to continue. + + - + \ No newline at end of file diff --git a/src/Build/Resources/xlf/Strings.pl.xlf b/src/Build/Resources/xlf/Strings.pl.xlf index 594884c4764..4b0ee9a2754 100644 --- a/src/Build/Resources/xlf/Strings.pl.xlf +++ b/src/Build/Resources/xlf/Strings.pl.xlf @@ -731,7 +731,7 @@ Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. - Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. + Ocena częściowa (etap oceny „{0}”) nie jest obsługiwana podczas tworzenia projektu. Użyj klasy ProjectInstance, aby przeprowadzić ocenę częściową, lub użyj pełnego etapu oceny, aby utworzyć projekt. UE: This message is shown when a partial (non-Full) ProjectEvaluationStage is passed to a Project factory method such as Project.FromFile. {0} is the requested ProjectEvaluationStage. @@ -3319,6 +3319,142 @@ Wykorzystanie: Średnie wykorzystanie {0}: {1:###.0} MSB4247: Nie można załadować mechanizmu rozpoznawania zestawów SDK. Plik manifestu istnieje, ale nie można odnaleźć ścieżki do biblioteki DLL mechanizmu rozpoznawania zestawów SDK. Ścieżka do pliku manifestu: „{0}”. Ścieżka do mechanizmu rozpoznawania zestawów SDK: {1} {StrBegin="MSB4247: "} + + MSB4188: Build was canceled. + MSB4188: Build was canceled. + {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. + + + 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 + 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 + + + + MSB4025: The project file could not be loaded. {0} + MSB4025: The project file could not be loaded. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. + + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}" is not a valid logger verbosity level. + {StrBegin="MSB4103: "} + + + This collection is read-only. + This collection is read-only. + + + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: The project file is malformed: "{0}". {1} + {StrBegin="MSB5019: "} + + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: Could not load the project file: "{0}". {1} + {StrBegin="MSB5020: "} + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5004: The solution file has two projects named "{0}". + MSB5004: The solution file has two projects named "{0}". + {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. + + + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. + + + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. + + + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. + + + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the nested project section in solution file. + MSB5009: Error parsing the nested project section in solution file. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. + + + MSB5010: No file format header found. + MSB5010: No file format header found. + {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. + + + MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: Parent project GUID not found in "{0}" project dependency section. + {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. + + + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. + + + MSB5013: Error parsing a project section. + MSB5013: Error parsing a project section. + {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. + + + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. + + + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. + + + Solution file + Solution file + UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: + "MSBUILD : Solution file error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + + Unrecognized solution version "{0}", attempting to continue. + Unrecognized solution version "{0}", attempting to continue. + + - + \ No newline at end of file diff --git a/src/Build/Resources/xlf/Strings.pt-BR.xlf b/src/Build/Resources/xlf/Strings.pt-BR.xlf index 22748c660d2..565657b74fe 100644 --- a/src/Build/Resources/xlf/Strings.pt-BR.xlf +++ b/src/Build/Resources/xlf/Strings.pt-BR.xlf @@ -731,7 +731,7 @@ Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. - Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. + A avaliação parcial (o estágio de avaliação "{0}") não tem suporte ao criar um projeto. Use ProjectInstance para realizar uma avaliação parcial ou use o estágio de avaliação Completa para criar um projeto. UE: This message is shown when a partial (non-Full) ProjectEvaluationStage is passed to a Project factory method such as Project.FromFile. {0} is the requested ProjectEvaluationStage. @@ -3319,6 +3319,142 @@ Utilização: {0} Utilização Média: {1:###.0} MSB4247: Não foi possível carregar o Resolvedor do SDK. Existe um arquivo de manifesto, mas o caminho para o arquivo DLL do Resolvedor do SDK não pôde ser encontrado. Caminho do arquivo de manifesto '{0}'. Caminho do resolvedor do SDK: {1} {StrBegin="MSB4247: "} + + MSB4188: Build was canceled. + MSB4188: Build was canceled. + {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. + + + 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 + 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 + + + + MSB4025: The project file could not be loaded. {0} + MSB4025: The project file could not be loaded. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. + + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}" is not a valid logger verbosity level. + {StrBegin="MSB4103: "} + + + This collection is read-only. + This collection is read-only. + + + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: The project file is malformed: "{0}". {1} + {StrBegin="MSB5019: "} + + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: Could not load the project file: "{0}". {1} + {StrBegin="MSB5020: "} + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5004: The solution file has two projects named "{0}". + MSB5004: The solution file has two projects named "{0}". + {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. + + + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. + + + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. + + + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. + + + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the nested project section in solution file. + MSB5009: Error parsing the nested project section in solution file. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. + + + MSB5010: No file format header found. + MSB5010: No file format header found. + {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. + + + MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: Parent project GUID not found in "{0}" project dependency section. + {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. + + + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. + + + MSB5013: Error parsing a project section. + MSB5013: Error parsing a project section. + {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. + + + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. + + + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. + + + Solution file + Solution file + UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: + "MSBUILD : Solution file error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + + Unrecognized solution version "{0}", attempting to continue. + Unrecognized solution version "{0}", attempting to continue. + + - + \ No newline at end of file diff --git a/src/Build/Resources/xlf/Strings.ru.xlf b/src/Build/Resources/xlf/Strings.ru.xlf index 897c55012aa..b08d11f7b8c 100644 --- a/src/Build/Resources/xlf/Strings.ru.xlf +++ b/src/Build/Resources/xlf/Strings.ru.xlf @@ -731,7 +731,7 @@ Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. - Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. + Частичное вычисление (этап вычисления "{0}") не поддерживается при создании проекта. Используйте ProjectInstance для выполнения частичной оценки или этап полной оценки для создания проекта. UE: This message is shown when a partial (non-Full) ProjectEvaluationStage is passed to a Project factory method such as Project.FromFile. {0} is the requested ProjectEvaluationStage. @@ -3319,6 +3319,142 @@ Utilization: {0} Average Utilization: {1:###.0} MSB4247: не удалось загрузить сопоставитель SDK. Файл манифеста существует, но не удается найти файл библиотеки DLL сопоставителя SDK по указанному пути. Путь к файлу манифеста: "{0}". Путь к сопоставителю SDK: {1} {StrBegin="MSB4247: "} + + MSB4188: Build was canceled. + MSB4188: Build was canceled. + {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. + + + 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 + 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 + + + + MSB4025: The project file could not be loaded. {0} + MSB4025: The project file could not be loaded. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. + + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}" is not a valid logger verbosity level. + {StrBegin="MSB4103: "} + + + This collection is read-only. + This collection is read-only. + + + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: The project file is malformed: "{0}". {1} + {StrBegin="MSB5019: "} + + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: Could not load the project file: "{0}". {1} + {StrBegin="MSB5020: "} + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5004: The solution file has two projects named "{0}". + MSB5004: The solution file has two projects named "{0}". + {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. + + + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. + + + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. + + + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. + + + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the nested project section in solution file. + MSB5009: Error parsing the nested project section in solution file. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. + + + MSB5010: No file format header found. + MSB5010: No file format header found. + {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. + + + MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: Parent project GUID not found in "{0}" project dependency section. + {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. + + + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. + + + MSB5013: Error parsing a project section. + MSB5013: Error parsing a project section. + {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. + + + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. + + + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. + + + Solution file + Solution file + UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: + "MSBUILD : Solution file error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + + Unrecognized solution version "{0}", attempting to continue. + Unrecognized solution version "{0}", attempting to continue. + + - + \ No newline at end of file diff --git a/src/Build/Resources/xlf/Strings.tr.xlf b/src/Build/Resources/xlf/Strings.tr.xlf index 32545a1248d..4f236c5ffa6 100644 --- a/src/Build/Resources/xlf/Strings.tr.xlf +++ b/src/Build/Resources/xlf/Strings.tr.xlf @@ -731,7 +731,7 @@ Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. - Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. + Proje oluştururken kısmi değerlendirme ("{0}" değerlendirme aşaması) desteklenmez. Kısmi değerlendirme gerçekleştirmek için ProjectInstance kullanın veya Tam değerlendirme aşaması'nı kullanarak bir Proje oluşturun. UE: This message is shown when a partial (non-Full) ProjectEvaluationStage is passed to a Project factory method such as Project.FromFile. {0} is the requested ProjectEvaluationStage. @@ -3319,6 +3319,142 @@ Kullanım: {0} Ortalama Kullanım: {1:###.0} MSB4247: SDK Çözümleyicisi yüklenemedi. Bir bildirim dosyası var, ancak SDK Çözümleyicisi DLL dosyasının yolu bulunamadı. Bildirim dosyasının yolu: '{0}'. SDK çözümleyicisinin yolu: {1} {StrBegin="MSB4247: "} + + MSB4188: Build was canceled. + MSB4188: Build was canceled. + {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. + + + 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 + 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 + + + + MSB4025: The project file could not be loaded. {0} + MSB4025: The project file could not be loaded. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. + + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}" is not a valid logger verbosity level. + {StrBegin="MSB4103: "} + + + This collection is read-only. + This collection is read-only. + + + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: The project file is malformed: "{0}". {1} + {StrBegin="MSB5019: "} + + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: Could not load the project file: "{0}". {1} + {StrBegin="MSB5020: "} + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5004: The solution file has two projects named "{0}". + MSB5004: The solution file has two projects named "{0}". + {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. + + + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. + + + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. + + + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. + + + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the nested project section in solution file. + MSB5009: Error parsing the nested project section in solution file. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. + + + MSB5010: No file format header found. + MSB5010: No file format header found. + {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. + + + MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: Parent project GUID not found in "{0}" project dependency section. + {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. + + + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. + + + MSB5013: Error parsing a project section. + MSB5013: Error parsing a project section. + {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. + + + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. + + + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. + + + Solution file + Solution file + UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: + "MSBUILD : Solution file error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + + Unrecognized solution version "{0}", attempting to continue. + Unrecognized solution version "{0}", attempting to continue. + + - + \ No newline at end of file diff --git a/src/Build/Resources/xlf/Strings.zh-Hans.xlf b/src/Build/Resources/xlf/Strings.zh-Hans.xlf index 34d0c1070fa..f4391e13a79 100644 --- a/src/Build/Resources/xlf/Strings.zh-Hans.xlf +++ b/src/Build/Resources/xlf/Strings.zh-Hans.xlf @@ -731,7 +731,7 @@ Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. - Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. + 创建项目时不支持部分评估(“{0}”评估阶段)。使用 ProjectInstance 执行部分评估，或使用“完全评估”阶段创建项目。 UE: This message is shown when a partial (non-Full) ProjectEvaluationStage is passed to a Project factory method such as Project.FromFile. {0} is the requested ProjectEvaluationStage. @@ -3319,6 +3319,142 @@ Utilization: {0} Average Utilization: {1:###.0} MSB4247: 无法加载 SDK 解析程序。清单文件存在，但无法找到 SDK 解析程序 DLL 文件的路径。清单文件路径“{0}”。 SDK 解析程序路径: {1} {StrBegin="MSB4247: "} + + MSB4188: Build was canceled. + MSB4188: Build was canceled. + {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. + + + 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 + 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 + + + + MSB4025: The project file could not be loaded. {0} + MSB4025: The project file could not be loaded. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. + + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}" is not a valid logger verbosity level. + {StrBegin="MSB4103: "} + + + This collection is read-only. + This collection is read-only. + + + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: The project file is malformed: "{0}". {1} + {StrBegin="MSB5019: "} + + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: Could not load the project file: "{0}". {1} + {StrBegin="MSB5020: "} + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5004: The solution file has two projects named "{0}". + MSB5004: The solution file has two projects named "{0}". + {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. + + + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. + + + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. + + + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. + + + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the nested project section in solution file. + MSB5009: Error parsing the nested project section in solution file. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. + + + MSB5010: No file format header found. + MSB5010: No file format header found. + {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. + + + MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: Parent project GUID not found in "{0}" project dependency section. + {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. + + + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. + + + MSB5013: Error parsing a project section. + MSB5013: Error parsing a project section. + {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. + + + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. + + + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. + + + Solution file + Solution file + UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: + "MSBUILD : Solution file error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + + Unrecognized solution version "{0}", attempting to continue. + Unrecognized solution version "{0}", attempting to continue. + + - + \ No newline at end of file diff --git a/src/Build/Resources/xlf/Strings.zh-Hant.xlf b/src/Build/Resources/xlf/Strings.zh-Hant.xlf index 65e084f73f5..b6aefe0a0ea 100644 --- a/src/Build/Resources/xlf/Strings.zh-Hant.xlf +++ b/src/Build/Resources/xlf/Strings.zh-Hant.xlf @@ -731,7 +731,7 @@ Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. - Partial evaluation (the "{0}" evaluation stage) is not supported when creating a Project. Use ProjectInstance to perform a partial evaluation, or use the Full evaluation stage to create a Project. + 建立專案時不支援部分評估 ("{0}" 評估階段)。使用 ProjectInstance 來執行部分評估，或使用完整評估階段來建立專案。 UE: This message is shown when a partial (non-Full) ProjectEvaluationStage is passed to a Project factory method such as Project.FromFile. {0} is the requested ProjectEvaluationStage. @@ -3319,6 +3319,142 @@ Utilization: {0} Average Utilization: {1:###.0} MSB4247: 無法載入 SDK 解析程式。資訊清單檔案存在，但找不到 SDK 解析程式 DLL 檔案的路徑。資訊清單檔案路徑 '{0}'。SDK 解析程式路徑: {1} {StrBegin="MSB4247: "} + + MSB4188: Build was canceled. + MSB4188: Build was canceled. + {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. + + + 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 + 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 + + + + MSB4025: The project file could not be loaded. {0} + MSB4025: The project file could not be loaded. {0} + {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is + invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is + provided separately to loggers. + LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. + + + MSB4103: "{0}" is not a valid logger verbosity level. + MSB4103: "{0}" is not a valid logger verbosity level. + {StrBegin="MSB4103: "} + + + This collection is read-only. + This collection is read-only. + + + + MSB5019: The project file is malformed: "{0}". {1} + MSB5019: The project file is malformed: "{0}". {1} + {StrBegin="MSB5019: "} + + + MSB5020: Could not load the project file: "{0}". {1} + MSB5020: Could not load the project file: "{0}". {1} + {StrBegin="MSB5020: "} + + + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". + {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. + + + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + MSB5025: Json in solution filter file "{0}" is incorrectly formatted. + {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. + + + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. + {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. + + + MSB5004: The solution file has two projects named "{0}". + MSB5004: The solution file has two projects named "{0}". + {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. + + + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. + {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. + + + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + MSB5006: Error parsing project section for project "{0}". The project file name is empty. + {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. + + + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. + + + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. + {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the nested project section in solution file. + MSB5009: Error parsing the nested project section in solution file. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. + {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. + + + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. + {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. + + + MSB5010: No file format header found. + MSB5010: No file format header found. + {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. + + + MSB5011: Parent project GUID not found in "{0}" project dependency section. + MSB5011: Parent project GUID not found in "{0}" project dependency section. + {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. + + + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + MSB5012: Unexpected end-of-file reached inside "{0}" project section. + {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. + + + MSB5013: Error parsing a project section. + MSB5013: Error parsing a project section. + {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. + + + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. + {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. + + + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. + {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. + + + Solution file + Solution file + UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: + "MSBUILD : Solution file error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + + Unrecognized solution version "{0}", attempting to continue. + Unrecognized solution version "{0}", attempting to continue. + + - + \ No newline at end of file diff --git a/src/Framework/Resources/xlf/SR.cs.xlf b/src/Framework/Resources/xlf/SR.cs.xlf index 47fbe2defb5..68b691bb333 100644 --- a/src/Framework/Resources/xlf/SR.cs.xlf +++ b/src/Framework/Resources/xlf/SR.cs.xlf @@ -147,6 +147,77 @@ {0} neobsahuje odpovídající element. + + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + + + + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{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. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + + + + MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: Task attempted to log before it was initialized. Message was: {0} + {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. + + + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + {StrBegin="MSB3511: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. + The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown + LOCALIZATION: "Importance" should not be localized. + High should not be localized. + Normal should not be localized. + Low should not be localized. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: The name "{0}" contains an invalid character "{1}". + {StrBegin="MSB5016: "} + + + "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{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. + + + 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: 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. + + + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + + + + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. + + + 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: 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. + {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. + \ No newline at end of file diff --git a/src/Framework/Resources/xlf/SR.de.xlf b/src/Framework/Resources/xlf/SR.de.xlf index cfed4304fa7..b30de58063f 100644 --- a/src/Framework/Resources/xlf/SR.de.xlf +++ b/src/Framework/Resources/xlf/SR.de.xlf @@ -147,6 +147,77 @@ „{0}“ enthält kein übereinstimmendes Element. + + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + + + + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{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. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + + + + MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: Task attempted to log before it was initialized. Message was: {0} + {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. + + + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + {StrBegin="MSB3511: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. + The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown + LOCALIZATION: "Importance" should not be localized. + High should not be localized. + Normal should not be localized. + Low should not be localized. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: The name "{0}" contains an invalid character "{1}". + {StrBegin="MSB5016: "} + + + "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{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. + + + 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: 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. + + + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + + + + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. + + + 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: 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. + {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. + \ No newline at end of file diff --git a/src/Framework/Resources/xlf/SR.es.xlf b/src/Framework/Resources/xlf/SR.es.xlf index e6de02f69d4..fa4d6126126 100644 --- a/src/Framework/Resources/xlf/SR.es.xlf +++ b/src/Framework/Resources/xlf/SR.es.xlf @@ -147,6 +147,77 @@ "{0}" no contiene un elemento coincidente. + + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + + + + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{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. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + + + + MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: Task attempted to log before it was initialized. Message was: {0} + {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. + + + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + {StrBegin="MSB3511: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. + The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown + LOCALIZATION: "Importance" should not be localized. + High should not be localized. + Normal should not be localized. + Low should not be localized. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: The name "{0}" contains an invalid character "{1}". + {StrBegin="MSB5016: "} + + + "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{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. + + + 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: 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. + + + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + + + + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. + + + 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: 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. + {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. + \ No newline at end of file diff --git a/src/Framework/Resources/xlf/SR.fr.xlf b/src/Framework/Resources/xlf/SR.fr.xlf index 9274922e8e7..1be92d8a550 100644 --- a/src/Framework/Resources/xlf/SR.fr.xlf +++ b/src/Framework/Resources/xlf/SR.fr.xlf @@ -147,6 +147,77 @@ « {0} » ne contient pas d’élément correspondant. + + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + + + + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{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. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + + + + MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: Task attempted to log before it was initialized. Message was: {0} + {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. + + + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + {StrBegin="MSB3511: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. + The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown + LOCALIZATION: "Importance" should not be localized. + High should not be localized. + Normal should not be localized. + Low should not be localized. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: The name "{0}" contains an invalid character "{1}". + {StrBegin="MSB5016: "} + + + "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{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. + + + 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: 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. + + + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + + + + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. + + + 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: 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. + {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. + \ No newline at end of file diff --git a/src/Framework/Resources/xlf/SR.it.xlf b/src/Framework/Resources/xlf/SR.it.xlf index 62ac52e0625..19015895b22 100644 --- a/src/Framework/Resources/xlf/SR.it.xlf +++ b/src/Framework/Resources/xlf/SR.it.xlf @@ -147,6 +147,77 @@ '{0}' non contiene un elemento corrispondente. + + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + + + + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{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. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + + + + MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: Task attempted to log before it was initialized. Message was: {0} + {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. + + + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + {StrBegin="MSB3511: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. + The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown + LOCALIZATION: "Importance" should not be localized. + High should not be localized. + Normal should not be localized. + Low should not be localized. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: The name "{0}" contains an invalid character "{1}". + {StrBegin="MSB5016: "} + + + "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{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. + + + 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: 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. + + + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + + + + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. + + + 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: 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. + {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. + \ No newline at end of file diff --git a/src/Framework/Resources/xlf/SR.ja.xlf b/src/Framework/Resources/xlf/SR.ja.xlf index a5b691a8338..8400c0b1707 100644 --- a/src/Framework/Resources/xlf/SR.ja.xlf +++ b/src/Framework/Resources/xlf/SR.ja.xlf @@ -147,6 +147,77 @@ '{0}' には、一致する要素が含まれていません。 + + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + + + + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{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. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + + + + MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: Task attempted to log before it was initialized. Message was: {0} + {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. + + + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + {StrBegin="MSB3511: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. + The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown + LOCALIZATION: "Importance" should not be localized. + High should not be localized. + Normal should not be localized. + Low should not be localized. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: The name "{0}" contains an invalid character "{1}". + {StrBegin="MSB5016: "} + + + "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{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. + + + 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: 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. + + + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + + + + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. + + + 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: 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. + {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. + \ No newline at end of file diff --git a/src/Framework/Resources/xlf/SR.ko.xlf b/src/Framework/Resources/xlf/SR.ko.xlf index 2dbab3ea610..391cc52b35f 100644 --- a/src/Framework/Resources/xlf/SR.ko.xlf +++ b/src/Framework/Resources/xlf/SR.ko.xlf @@ -147,6 +147,77 @@ '{0}'에 일치하는 요소가 없습니다. + + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + + + + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{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. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + + + + MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: Task attempted to log before it was initialized. Message was: {0} + {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. + + + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + {StrBegin="MSB3511: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. + The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown + LOCALIZATION: "Importance" should not be localized. + High should not be localized. + Normal should not be localized. + Low should not be localized. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: The name "{0}" contains an invalid character "{1}". + {StrBegin="MSB5016: "} + + + "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{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. + + + 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: 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. + + + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + + + + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. + + + 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: 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. + {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. + \ No newline at end of file diff --git a/src/Framework/Resources/xlf/SR.pl.xlf b/src/Framework/Resources/xlf/SR.pl.xlf index 673026bfdcf..eaa12ba21c0 100644 --- a/src/Framework/Resources/xlf/SR.pl.xlf +++ b/src/Framework/Resources/xlf/SR.pl.xlf @@ -147,6 +147,77 @@ Wtyczka „{0}” nie zawiera pasującego elementu. + + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + + + + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{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. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + + + + MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: Task attempted to log before it was initialized. Message was: {0} + {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. + + + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + {StrBegin="MSB3511: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. + The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown + LOCALIZATION: "Importance" should not be localized. + High should not be localized. + Normal should not be localized. + Low should not be localized. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: The name "{0}" contains an invalid character "{1}". + {StrBegin="MSB5016: "} + + + "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{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. + + + 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: 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. + + + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + + + + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. + + + 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: 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. + {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. + \ No newline at end of file diff --git a/src/Framework/Resources/xlf/SR.pt-BR.xlf b/src/Framework/Resources/xlf/SR.pt-BR.xlf index a7e4f1788af..cb10c65adc3 100644 --- a/src/Framework/Resources/xlf/SR.pt-BR.xlf +++ b/src/Framework/Resources/xlf/SR.pt-BR.xlf @@ -147,6 +147,77 @@ "{0}" não contém elemento correspondente. + + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + + + + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{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. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + + + + MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: Task attempted to log before it was initialized. Message was: {0} + {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. + + + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + {StrBegin="MSB3511: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. + The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown + LOCALIZATION: "Importance" should not be localized. + High should not be localized. + Normal should not be localized. + Low should not be localized. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: The name "{0}" contains an invalid character "{1}". + {StrBegin="MSB5016: "} + + + "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{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. + + + 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: 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. + + + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + + + + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. + + + 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: 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. + {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. + \ No newline at end of file diff --git a/src/Framework/Resources/xlf/SR.ru.xlf b/src/Framework/Resources/xlf/SR.ru.xlf index 034220b21ce..c9f6f455fa1 100644 --- a/src/Framework/Resources/xlf/SR.ru.xlf +++ b/src/Framework/Resources/xlf/SR.ru.xlf @@ -147,6 +147,77 @@ "{0}" не содержит соответствующего элемента. + + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + + + + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{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. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + + + + MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: Task attempted to log before it was initialized. Message was: {0} + {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. + + + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + {StrBegin="MSB3511: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. + The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown + LOCALIZATION: "Importance" should not be localized. + High should not be localized. + Normal should not be localized. + Low should not be localized. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: The name "{0}" contains an invalid character "{1}". + {StrBegin="MSB5016: "} + + + "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{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. + + + 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: 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. + + + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + + + + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. + + + 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: 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. + {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. + \ No newline at end of file diff --git a/src/Framework/Resources/xlf/SR.tr.xlf b/src/Framework/Resources/xlf/SR.tr.xlf index f6a3720043a..15faffdf655 100644 --- a/src/Framework/Resources/xlf/SR.tr.xlf +++ b/src/Framework/Resources/xlf/SR.tr.xlf @@ -147,6 +147,77 @@ '{0}' eşleşen öğe içermiyor. + + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + + + + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{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. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + + + + MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: Task attempted to log before it was initialized. Message was: {0} + {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. + + + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + {StrBegin="MSB3511: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. + The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown + LOCALIZATION: "Importance" should not be localized. + High should not be localized. + Normal should not be localized. + Low should not be localized. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: The name "{0}" contains an invalid character "{1}". + {StrBegin="MSB5016: "} + + + "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{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. + + + 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: 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. + + + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + + + + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. + + + 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: 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. + {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. + \ No newline at end of file diff --git a/src/Framework/Resources/xlf/SR.zh-Hans.xlf b/src/Framework/Resources/xlf/SR.zh-Hans.xlf index 9108de2761b..f4dfad0017b 100644 --- a/src/Framework/Resources/xlf/SR.zh-Hans.xlf +++ b/src/Framework/Resources/xlf/SR.zh-Hans.xlf @@ -147,6 +147,77 @@ “{0}”不包含匹配元素。 + + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + + + + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{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. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + + + + MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: Task attempted to log before it was initialized. Message was: {0} + {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. + + + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + {StrBegin="MSB3511: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. + The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown + LOCALIZATION: "Importance" should not be localized. + High should not be localized. + Normal should not be localized. + Low should not be localized. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: The name "{0}" contains an invalid character "{1}". + {StrBegin="MSB5016: "} + + + "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{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. + + + 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: 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. + + + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + + + + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. + + + 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: 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. + {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. + \ No newline at end of file diff --git a/src/Framework/Resources/xlf/SR.zh-Hant.xlf b/src/Framework/Resources/xlf/SR.zh-Hant.xlf index 1b2b1f067e3..d9edf6acb80 100644 --- a/src/Framework/Resources/xlf/SR.zh-Hant.xlf +++ b/src/Framework/Resources/xlf/SR.zh-Hant.xlf @@ -147,6 +147,77 @@ '{0}' 未包含相符的元素。 + + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + The number of elements in the collection is greater than the available space in the destination array (when starting at the specified index). + + + + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. + + + + MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{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. + Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. + + + + MSB6005: Task attempted to log before it was initialized. Message was: {0} + MSB6005: Task attempted to log before it was initialized. Message was: {0} + {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. + + + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. + {StrBegin="MSB3511: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. + The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown + LOCALIZATION: "Importance" should not be localized. + High should not be localized. + Normal should not be localized. + Low should not be localized. + + + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. + {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. + + + MSB5016: The name "{0}" contains an invalid character "{1}". + MSB5016: The name "{0}" contains an invalid character "{1}". + {StrBegin="MSB5016: "} + + + "{0}" is a reserved item metadata, and cannot be modified or deleted. + "{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. + + + 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: 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. + + + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. + + + + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. + LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. + + + 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: 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. + {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. + \ No newline at end of file diff --git a/src/MSBuild/Resources/xlf/Strings.cs.xlf b/src/MSBuild/Resources/xlf/Strings.cs.xlf index 3ac1cdc57b9..818e63f4aee 100644 --- a/src/MSBuild/Resources/xlf/Strings.cs.xlf +++ b/src/MSBuild/Resources/xlf/Strings.cs.xlf @@ -382,62 +382,62 @@ could not connect to the server within the timeout window; the server may have failed to start - v časovém limitu se nepovedlo připojit k serveru; server se možná nepodařilo spustit + v časovém limitu se nepovedlo připojit k serveru; server se možná nepodařilo spustit LOCALIZATION: No format arguments. Used for any connect failure when the server's exit code is not known — covers both pipe-connect timeouts and non-timeout I/O errors during the connect attempt. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process exited with code {0} immediately after launch - Proces serveru byl ukončen s kódem {0} ihned po spuštění + Proces serveru byl ukončen s kódem {0} ihned po spuštění LOCALIZATION: {0} is the integer process exit code; rendered with InvariantCulture as a decimal integer, do not localize the digits. This message is concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process could not be launched - proces serveru se nepovedlo spustit + proces serveru se nepovedlo spustit LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). Reusing the running MSBuild Server node for this build (process ID {0}). - Reusing the running MSBuild Server node for this build (process ID {0}). + Pro toto sestavení se znovu používá spuštěný uzel serveru MSBuild (ID procesu {0}). MSBuild Server node started for this build (process ID {0}). - MSBuild Server node started for this build (process ID {0}). + Uzel serveru MSBuild byl spuštěn pro toto sestavení (ID procesu {0}). MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). - MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). + Uzel serveru MSBuild byl spuštěn jen pro toto sestavení. Po jeho dokončení se vypne (ID procesu {0}). MSBuild Server was requested but not used for this build: {0}. - MSBuild Server was requested but not used for this build: {0}. + Server MSBuild byl vyžádán, ale pro toto sestavení se nepoužil: {0}. the server was busy with another build - the server was busy with another build + server byl zaneprázdněný jiným sestavením this invocation is not compatible with MSBuild Server - this invocation is not compatible with MSBuild Server + toto vyvolání není kompatibilní se serverem MSBuild node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) - node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) + opakované použití uzlu je zakázané (-nodeReuse:false nebo MSBUILDDISABLENODEREUSE=1) the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled - the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled + je povolený nouzový přepínač MSBUILDENSURESTDOUTFORTASKPROCESSES the current server state could not be determined - aktuální stav serveru nelze určit + aktuální stav serveru nelze určit LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). @@ -2373,6 +2373,36 @@ Když se nastaví na MessageUponIsolationViolation (nebo jeho krátký MSBUILD : error MSB4192: Soubor projektu {0} je ve formátu .vcproj nebo .dsp, který nástroj MSBuild nemůže přímo sestavit. Proveďte převod projektu – otevřete projekt v prostředí IDE sady Visual Studio nebo spusťte nástroj pro převod. V případě souboru .vcproj můžete místo toho sestavit soubor řešení obsahující projekt pomocí nástroje MSBuild. {StrBegin="MSBUILD : error MSB4192: "} LOC: ".vcproj" and ".dsp" should not be localized + + 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: 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. + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: There was an exception while reading the log file: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + 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}'. + 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 + + + Schema validation + Schema validation + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + \ No newline at end of file diff --git a/src/MSBuild/Resources/xlf/Strings.de.xlf b/src/MSBuild/Resources/xlf/Strings.de.xlf index bda76b89b51..d61dc042f49 100644 --- a/src/MSBuild/Resources/xlf/Strings.de.xlf +++ b/src/MSBuild/Resources/xlf/Strings.de.xlf @@ -382,62 +382,62 @@ could not connect to the server within the timeout window; the server may have failed to start - innerhalb des Zeitfensters konnte keine Verbindung zum Server hergestellt werden. Der Server konnte möglicherweise nicht gestartet werden. + innerhalb des Zeitfensters konnte keine Verbindung zum Server hergestellt werden. Der Server konnte möglicherweise nicht gestartet werden. LOCALIZATION: No format arguments. Used for any connect failure when the server's exit code is not known — covers both pipe-connect timeouts and non-timeout I/O errors during the connect attempt. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process exited with code {0} immediately after launch - der Serverprozess wurde unmittelbar nach dem Start mit Code {0} beendet. + der Serverprozess wurde unmittelbar nach dem Start mit Code {0} beendet. LOCALIZATION: {0} is the integer process exit code; rendered with InvariantCulture as a decimal integer, do not localize the digits. This message is concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process could not be launched - der Serverprozess konnte nicht gestartet werden + der Serverprozess konnte nicht gestartet werden LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). Reusing the running MSBuild Server node for this build (process ID {0}). - Reusing the running MSBuild Server node for this build (process ID {0}). + Der laufende MSBuild-Serverknoten wird für diesen Build wiederverwendet (Prozess-ID {0}). MSBuild Server node started for this build (process ID {0}). - MSBuild Server node started for this build (process ID {0}). + MSBuild-Serverknoten wurde für diesen Build gestartet (Prozess-ID {0}). MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). - MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). + MSBuild-Serverknoten wurde nur für diesen Build gestartet und wird danach heruntergefahren (Prozess-ID {0}). MSBuild Server was requested but not used for this build: {0}. - MSBuild Server was requested but not used for this build: {0}. + MSBuild Server wurde angefordert, aber für diesen Build nicht verwendet: {0}. the server was busy with another build - the server was busy with another build + Der Server war mit einem anderen Build beschäftigt. this invocation is not compatible with MSBuild Server - this invocation is not compatible with MSBuild Server + Dieser Aufruf ist nicht mit MSBuild Server kompatibel. node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) - node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) + Die Knotenwiederverwendung ist deaktiviert (-nodeReuse:false oder MSBUILDDISABLENODEREUSE=1) the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled - the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled + Die Ausnahmeregel MSBUILDENSURESTDOUTFORTASKPROCESSES ist aktiviert. the current server state could not be determined - der aktuelle Serverstatus konnte nicht ermittelt werden + der aktuelle Serverstatus konnte nicht ermittelt werden LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). @@ -2361,6 +2361,36 @@ Hinweis: Ausführlichkeit der Dateiprotokollierungen MSBUILD : error MSB4192: Die Projektdatei "{0}" weist das Dateiformat ".vcproj" oder ".dsp" auf, das von MSBuild nicht direkt erstellt werden kann. Konvertieren Sie das Projekt, indem Sie es in der Visual Studio IDE öffnen oder das Konvertierungstool ausführen. Für ".vcproj" verwenden Sie zum Erstellen der Projektmappendatei, die stattdessen das Projekt enthält, MSBuild. {StrBegin="MSBUILD : error MSB4192: "} LOC: ".vcproj" and ".dsp" should not be localized + + 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: 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. + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: There was an exception while reading the log file: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + 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}'. + 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 + + + Schema validation + Schema validation + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + \ No newline at end of file diff --git a/src/MSBuild/Resources/xlf/Strings.es.xlf b/src/MSBuild/Resources/xlf/Strings.es.xlf index 7fb50cc4506..0da50879a74 100644 --- a/src/MSBuild/Resources/xlf/Strings.es.xlf +++ b/src/MSBuild/Resources/xlf/Strings.es.xlf @@ -381,62 +381,62 @@ Esta marca es experimental y puede que no funcione según lo previsto. could not connect to the server within the timeout window; the server may have failed to start - no se pudo conectar con el servidor dentro de la ventana de tiempo de espera; es posible que el servidor no se haya iniciado + no se pudo conectar con el servidor dentro de la ventana de tiempo de espera; es posible que el servidor no se haya iniciado LOCALIZATION: No format arguments. Used for any connect failure when the server's exit code is not known — covers both pipe-connect timeouts and non-timeout I/O errors during the connect attempt. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process exited with code {0} immediately after launch - el proceso de servidor se cerró con código {0} inmediatamente después del inicio + el proceso de servidor se cerró con código {0} inmediatamente después del inicio LOCALIZATION: {0} is the integer process exit code; rendered with InvariantCulture as a decimal integer, do not localize the digits. This message is concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process could not be launched - no se pudo iniciar el proceso del servidor + no se pudo iniciar el proceso del servidor LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). Reusing the running MSBuild Server node for this build (process ID {0}). - Reusing the running MSBuild Server node for this build (process ID {0}). + Reutilizando el nodo de clúster de MSBuild en ejecución para esta compilación (id. de proceso {0}). MSBuild Server node started for this build (process ID {0}). - MSBuild Server node started for this build (process ID {0}). + Se ha iniciado el nodo de clúster de MSBuild para esta compilación (id. de proceso {0}). MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). - MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). + Se ha iniciado el nodo de clúster de MSBuild solo para esta compilación; se apagará después (id. de proceso {0}). MSBuild Server was requested but not used for this build: {0}. - MSBuild Server was requested but not used for this build: {0}. + Se ha solicitado el servidor de MSBuild, pero no se ha usado para esta compilación: {0}. the server was busy with another build - the server was busy with another build + el servidor estaba ocupado con otra compilación this invocation is not compatible with MSBuild Server - this invocation is not compatible with MSBuild Server + esta invocación no es compatible con el servidor de MSBuild node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) - node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) + la reutilización del nodo está deshabilitada (-nodeReuse:false o MSBUILDDISABLENODEREUSE=1) the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled - the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled + la vía de escape MSBUILDENSURESTDOUTFORTASKPROCESSES está habilitada the current server state could not be determined - no se pudo determinar el estado actual del servidor + no se pudo determinar el estado actual del servidor LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). @@ -2365,6 +2365,36 @@ Esta marca es experimental y puede que no funcione según lo previsto. MSBUILD : error MSB4192: El formato de archivo del proyecto "{0}" es ".vcproj" o ".dsp", que MSBuild no puede compilar directamente. Convierta el proyecto abriéndolo en el IDE de Visual Studio o ejecutando la herramienta de conversión; o bien, para ".vcproj", use MSBuild para compilar el archivo de solución que contiene el proyecto. {StrBegin="MSBUILD : error MSB4192: "} LOC: ".vcproj" and ".dsp" should not be localized + + 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: 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. + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: There was an exception while reading the log file: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + 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}'. + 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 + + + Schema validation + Schema validation + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + \ No newline at end of file diff --git a/src/MSBuild/Resources/xlf/Strings.fr.xlf b/src/MSBuild/Resources/xlf/Strings.fr.xlf index 1f979fbe14d..5a4920706d3 100644 --- a/src/MSBuild/Resources/xlf/Strings.fr.xlf +++ b/src/MSBuild/Resources/xlf/Strings.fr.xlf @@ -382,62 +382,62 @@ futures could not connect to the server within the timeout window; the server may have failed to start - nous n’avons pas pu vous connecter au serveur dans le délai imparti; le serveur a peut-être échoué au démarrage + nous n’avons pas pu vous connecter au serveur dans le délai imparti; le serveur a peut-être échoué au démarrage LOCALIZATION: No format arguments. Used for any connect failure when the server's exit code is not known — covers both pipe-connect timeouts and non-timeout I/O errors during the connect attempt. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process exited with code {0} immediately after launch - le processus serveur s’est terminé avec le code {0} immédiatement après le lancement + le processus serveur s’est terminé avec le code {0} immédiatement après le lancement LOCALIZATION: {0} is the integer process exit code; rendered with InvariantCulture as a decimal integer, do not localize the digits. This message is concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process could not be launched - le processus serveur n’a pas pu être démarré + le processus serveur n’a pas pu être démarré LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). Reusing the running MSBuild Server node for this build (process ID {0}). - Reusing the running MSBuild Server node for this build (process ID {0}). + Réutilisation du nœud du Serveur MSBuild en cours d’exécution pour cette build (ID de processus {0}). MSBuild Server node started for this build (process ID {0}). - MSBuild Server node started for this build (process ID {0}). + Nœud du Serveur MSBuild lancé pour cette build (ID de processus {0}). MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). - MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). + Nœud du Serveur MSBuild lancé pour cette build uniquement. Il s’arrêtera ensuite (ID de processus {0}). MSBuild Server was requested but not used for this build: {0}. - MSBuild Server was requested but not used for this build: {0}. + Le Serveur MSBuild a été demandé, mais n’a pas été utilisé pour cette build : {0}. the server was busy with another build - the server was busy with another build + le serveur était occupé par une autre build this invocation is not compatible with MSBuild Server - this invocation is not compatible with MSBuild Server + cet appel n’est pas compatible avec le Serveur MSBuild node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) - node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) + la réutilisation des nœuds est désactivée (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled - the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled + la trappe de secours MSBUILDENSURESTDOUTFORTASKPROCESSES est activée the current server state could not be determined - l’état actuel du serveur n’a pas pu être déterminé + l’état actuel du serveur n’a pas pu être déterminé LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). @@ -2362,6 +2362,36 @@ Remarque : verbosité des enregistreurs d’événements de fichiers MSBUILD : error MSB4192: Le fichier projet "{0}" utilise le format de fichier ".vcproj" ou ".dsp", que MSBuild ne peut pas générer directement. Convertissez le projet en l'ouvrant dans l'IDE de Visual Studio ou en exécutant l'outil de conversion. Pour ".vcproj", utilisez à la place MSBuild pour générer le fichier solution contenant le projet. {StrBegin="MSBUILD : error MSB4192: "} LOC: ".vcproj" and ".dsp" should not be localized + + 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: 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. + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: There was an exception while reading the log file: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + 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}'. + 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 + + + Schema validation + Schema validation + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + \ No newline at end of file diff --git a/src/MSBuild/Resources/xlf/Strings.it.xlf b/src/MSBuild/Resources/xlf/Strings.it.xlf index 6946a96a218..699445893ce 100644 --- a/src/MSBuild/Resources/xlf/Strings.it.xlf +++ b/src/MSBuild/Resources/xlf/Strings.it.xlf @@ -382,62 +382,62 @@ Questo flag è sperimentale e potrebbe non funzionare come previsto. could not connect to the server within the timeout window; the server may have failed to start - non è stato possibile connettersi al server entro il timeout; il server potrebbe non essersi avviato + non è stato possibile connettersi al server entro il timeout; il server potrebbe non essersi avviato LOCALIZATION: No format arguments. Used for any connect failure when the server's exit code is not known — covers both pipe-connect timeouts and non-timeout I/O errors during the connect attempt. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process exited with code {0} immediately after launch - il processo del server è terminato con il codice {0} immediatamente dopo l'avvio + il processo del server è terminato con il codice {0} immediatamente dopo l'avvio LOCALIZATION: {0} is the integer process exit code; rendered with InvariantCulture as a decimal integer, do not localize the digits. This message is concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process could not be launched - non è stato possibile avviare il processo server + non è stato possibile avviare il processo server LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). Reusing the running MSBuild Server node for this build (process ID {0}). - Reusing the running MSBuild Server node for this build (process ID {0}). + Riutilizzo del nodo del server MSBuild in esecuzione per questa compilazione (ID del processo {0}). MSBuild Server node started for this build (process ID {0}). - MSBuild Server node started for this build (process ID {0}). + Nodo del server MSBuild avviato per questa compilazione (ID del processo {0}). MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). - MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). + Nodo del server MSBuild avviato solo per questa compilazione; verrà arrestato in seguito (ID del processo {0}). MSBuild Server was requested but not used for this build: {0}. - MSBuild Server was requested but not used for this build: {0}. + Il server MSBuild è stato richiesto ma non è stato usato per questa compilazione: {0}. the server was busy with another build - the server was busy with another build + il server era impegnato con un'altra compilazione this invocation is not compatible with MSBuild Server - this invocation is not compatible with MSBuild Server + questa chiamata non è compatibile con MSBuild Server node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) - node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) + Il riutilizzo dei nodi è disabilitato (-nodeReuse:false o MSBUILDDISABLENODEREUSE=1) the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled - the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled + l'opzione di emergenza MSBUILDENSURESTDOUTFORTASKPROCESSES è abilitata the current server state could not be determined - impossibile determinare lo stato corrente del server + impossibile determinare lo stato corrente del server LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). @@ -2377,6 +2377,36 @@ Esegue la profilatura della valutazione di MSBuild e scrive MSBUILD : error MSB4192: il file di progetto "{0}" è in formato ".vcproj" o ".dsp", che non è possibile compilare direttamente con MSBuild. Per convertire il progetto, aprirlo in Visual Studio IDE o eseguire lo strumento di conversione oppure, per ".vcproj", usare MSBuild per compilare il file della soluzione contenente il progetto. {StrBegin="MSBUILD : error MSB4192: "} LOC: ".vcproj" and ".dsp" should not be localized + + 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: 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. + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: There was an exception while reading the log file: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + 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}'. + 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 + + + Schema validation + Schema validation + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + \ No newline at end of file diff --git a/src/MSBuild/Resources/xlf/Strings.ja.xlf b/src/MSBuild/Resources/xlf/Strings.ja.xlf index 1c00e9cda01..a7ff966fffd 100644 --- a/src/MSBuild/Resources/xlf/Strings.ja.xlf +++ b/src/MSBuild/Resources/xlf/Strings.ja.xlf @@ -382,62 +382,62 @@ could not connect to the server within the timeout window; the server may have failed to start - タイムアウト時間内にサーバーに接続できませんでした。サーバーの起動に失敗した可能性があります + タイムアウト時間内にサーバーに接続できませんでした。サーバーの起動に失敗した可能性があります LOCALIZATION: No format arguments. Used for any connect failure when the server's exit code is not known — covers both pipe-connect timeouts and non-timeout I/O errors during the connect attempt. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process exited with code {0} immediately after launch - 起動直後にサーバー プロセスがコード {0} で終了しました + 起動直後にサーバー プロセスがコード {0} で終了しました LOCALIZATION: {0} is the integer process exit code; rendered with InvariantCulture as a decimal integer, do not localize the digits. This message is concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process could not be launched - サーバー プロセスを起動できませんでした + サーバー プロセスを起動できませんでした LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). Reusing the running MSBuild Server node for this build (process ID {0}). - Reusing the running MSBuild Server node for this build (process ID {0}). + 実行中の MSBuild Server ノードをこのビルドに再利用しています (プロセス ID {0})。 MSBuild Server node started for this build (process ID {0}). - MSBuild Server node started for this build (process ID {0}). + このビルドの MSBuild Server ノードが開始されました (プロセス ID {0})。 MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). - MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). + MSBuild Server ノードがこのビルド専用で開始されました。後でシャットダウンされます (プロセス ID {0})。 MSBuild Server was requested but not used for this build: {0}. - MSBuild Server was requested but not used for this build: {0}. + MSBuild Server が要求されましたが、このビルドには使用されませんでした: {0}。 the server was busy with another build - the server was busy with another build + サーバーは別のビルドで使用中でした this invocation is not compatible with MSBuild Server - this invocation is not compatible with MSBuild Server + この呼び出しは MSBuild Server と互換性がありません node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) - node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) + ノードの再利用が無効になっています (-nodeReuse:false または MSBUILDDISABLENODEREUSE=1) the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled - the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled + MSBUILDENSURESTDOUTFORTASKPROCESSES エスケープ ハッチが有効になっています the current server state could not be determined - 現在のサーバーの状態を判断できませんでした + 現在のサーバーの状態を判断できませんでした LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). @@ -2361,6 +2361,36 @@ MSBUILD : error MSB4192: プロジェクト ファイル "{0}" は ".vcproj" または ".dsp" ファイル形式であり、MSBuild では直接ビルドできません。Visual Studio IDE でファイルを開くか、変換ツールを実行して、プロジェクトを変換してください。または、".vcproj" の場合は、MSBuild を使用して、このプロジェクトを含むソリューション ファイルを代わりにビルドできます。 {StrBegin="MSBUILD : error MSB4192: "} LOC: ".vcproj" and ".dsp" should not be localized + + 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: 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. + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: There was an exception while reading the log file: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + 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}'. + 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 + + + Schema validation + Schema validation + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + \ No newline at end of file diff --git a/src/MSBuild/Resources/xlf/Strings.ko.xlf b/src/MSBuild/Resources/xlf/Strings.ko.xlf index 9f5d79df556..ced52eabed5 100644 --- a/src/MSBuild/Resources/xlf/Strings.ko.xlf +++ b/src/MSBuild/Resources/xlf/Strings.ko.xlf @@ -383,62 +383,62 @@ could not connect to the server within the timeout window; the server may have failed to start - 제한 시간 내에 서버에 연결할 수 없었습니다. 서버가 시작되지 못했을 수 있습니다 + 제한 시간 내에 서버에 연결할 수 없었습니다. 서버가 시작되지 못했을 수 있습니다 LOCALIZATION: No format arguments. Used for any connect failure when the server's exit code is not known — covers both pipe-connect timeouts and non-timeout I/O errors during the connect attempt. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process exited with code {0} immediately after launch - 서버 프로세스가 시작 직후 코드 {0}(으)로 종료되었습니다 + 서버 프로세스가 시작 직후 코드 {0}(으)로 종료되었습니다 LOCALIZATION: {0} is the integer process exit code; rendered with InvariantCulture as a decimal integer, do not localize the digits. This message is concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process could not be launched - 서버 프로세스를 시작할 수 없습니다 + 서버 프로세스를 시작할 수 없습니다 LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). Reusing the running MSBuild Server node for this build (process ID {0}). - Reusing the running MSBuild Server node for this build (process ID {0}). + 이 빌드에 대해 실행 중인 MSBuild Server 노드를 다시 사용합니다(프로세스 ID {0}). MSBuild Server node started for this build (process ID {0}). - MSBuild Server node started for this build (process ID {0}). + 이 빌드에서 MSBuild Server 노드가 시작되었습니다(프로세스 ID {0}). MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). - MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). + 이 빌드에서만 MSBuild Server 노드가 시작되었습니다. 이후에는 종료됩니다(프로세스 ID {0}). MSBuild Server was requested but not used for this build: {0}. - MSBuild Server was requested but not used for this build: {0}. + MSBuild Server가 요청되었지만 이 빌드에는 사용되지 않았습니다: {0}. the server was busy with another build - the server was busy with another build + 서버가 다른 빌드를 처리하느라 바빴습니다. this invocation is not compatible with MSBuild Server - this invocation is not compatible with MSBuild Server + 이 호출은 MSBuild Server와 호환되지 않습니다. node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) - node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) + 노드 재사용이 사용하지 않도록 설정되어 있습니다(-nodeReuse:false 또는 MSBUILDDISABLENODEREUSE=1). the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled - the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled + MSBUILDENSURESTDOUTFORTASKPROCESSES 이스케이프 해치가 사용하도록 설정되어 있습니다. the current server state could not be determined - 현재 서버 상태를 확인할 수 없습니다 + 현재 서버 상태를 확인할 수 없습니다 LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). @@ -2362,6 +2362,36 @@ MSBUILD : error MSB4192: 프로젝트 파일 "{0}"이(가) MSBuild에서 직접 빌드할 수 없는 ".vcproj" 또는 ".dsp" 파일 형식입니다. 프로젝트를 Visual Studio IDE에서 열거나 변환 도구를 실행하여 프로젝트를 변환하거나, ".vcproj"의 경우 MSBuild를 사용하여 해당 프로젝트가 포함된 솔루션 파일을 대신 빌드하세요. {StrBegin="MSBUILD : error MSB4192: "} LOC: ".vcproj" and ".dsp" should not be localized + + 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: 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. + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: There was an exception while reading the log file: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + 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}'. + 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 + + + Schema validation + Schema validation + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + \ No newline at end of file diff --git a/src/MSBuild/Resources/xlf/Strings.pl.xlf b/src/MSBuild/Resources/xlf/Strings.pl.xlf index d36cd902804..dcd9d05cded 100644 --- a/src/MSBuild/Resources/xlf/Strings.pl.xlf +++ b/src/MSBuild/Resources/xlf/Strings.pl.xlf @@ -381,62 +381,62 @@ Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami. could not connect to the server within the timeout window; the server may have failed to start - nie można było połączyć się z serwerem w oknie limitu czasu; serwer mógł się nie uruchomić + nie można było połączyć się z serwerem w oknie limitu czasu; serwer mógł się nie uruchomić LOCALIZATION: No format arguments. Used for any connect failure when the server's exit code is not known — covers both pipe-connect timeouts and non-timeout I/O errors during the connect attempt. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process exited with code {0} immediately after launch - proces serwera zakończył działanie z kodem {0} zaraz po uruchomieniu + proces serwera zakończył działanie z kodem {0} zaraz po uruchomieniu LOCALIZATION: {0} is the integer process exit code; rendered with InvariantCulture as a decimal integer, do not localize the digits. This message is concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process could not be launched - nie można uruchomić procesu serwera + nie można uruchomić procesu serwera LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). Reusing the running MSBuild Server node for this build (process ID {0}). - Reusing the running MSBuild Server node for this build (process ID {0}). + Ponowne użycie uruchomionego węzła serwera MSBuild dla tej kompilacji (identyfikator procesu {0}). MSBuild Server node started for this build (process ID {0}). - MSBuild Server node started for this build (process ID {0}). + Węzeł serwera MSBuild został uruchomiony dla tej kompilacji (identyfikator procesu {0}). MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). - MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). + Węzeł serwera MSBuild został uruchomiony tylko dla tej kompilacji; zostanie ona później zamknięta (identyfikator procesu {0}). MSBuild Server was requested but not used for this build: {0}. - MSBuild Server was requested but not used for this build: {0}. + Zażądano serwera MSBuild Server, ale nie użyto go dla tej kompilacji: {0}. the server was busy with another build - the server was busy with another build + serwer był zajęty inną kompilacją this invocation is not compatible with MSBuild Server - this invocation is not compatible with MSBuild Server + to wywołanie nie jest zgodne z serwerem MSBuild node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) - node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) + ponowne użycie węzła jest wyłączone (-nodeReuse:false lub MSBUILDDISABLENODEREUSE=1) the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled - the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled + kreskowanie ucieczki MSBUILDENSURESTDOUTFORTASKPROCESSES jest włączone the current server state could not be determined - nie można określić bieżącego stanu serwera + nie można określić bieżącego stanu serwera LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). @@ -2370,6 +2370,36 @@ Ta flaga jest eksperymentalna i może nie działać zgodnie z oczekiwaniami. MSBUILD : error MSB4192: Plik projektu „{0}” ma format „.vcproj” lub „.dsp”, którego program MSBuild nie może skompilować bezpośrednio. Przekonwertuj projekt, otwierając go w programie Visual Studio IDE lub uruchamiając narzędzie konwersji, albo (w przypadku pliku „.vcproj”) użyj programu MSBuild, aby utworzyć plik rozwiązania zawierający ten projekt. {StrBegin="MSBUILD : error MSB4192: "} LOC: ".vcproj" and ".dsp" should not be localized + + 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: 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. + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: There was an exception while reading the log file: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + 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}'. + 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 + + + Schema validation + Schema validation + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + \ No newline at end of file diff --git a/src/MSBuild/Resources/xlf/Strings.pt-BR.xlf b/src/MSBuild/Resources/xlf/Strings.pt-BR.xlf index 384c1226268..dadccd69094 100644 --- a/src/MSBuild/Resources/xlf/Strings.pt-BR.xlf +++ b/src/MSBuild/Resources/xlf/Strings.pt-BR.xlf @@ -381,62 +381,62 @@ could not connect to the server within the timeout window; the server may have failed to start - não foi possível se conectar ao servidor dentro do período de tempo limite; o servidor pode ter falhado ao iniciar + não foi possível se conectar ao servidor dentro do período de tempo limite; o servidor pode ter falhado ao iniciar LOCALIZATION: No format arguments. Used for any connect failure when the server's exit code is not known — covers both pipe-connect timeouts and non-timeout I/O errors during the connect attempt. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process exited with code {0} immediately after launch - o processo do servidor foi encerrado com o código {0} imediatamente após o início + o processo do servidor foi encerrado com o código {0} imediatamente após o início LOCALIZATION: {0} is the integer process exit code; rendered with InvariantCulture as a decimal integer, do not localize the digits. This message is concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process could not be launched - o processo do servidor não pôde ser iniciado + o processo do servidor não pôde ser iniciado LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). Reusing the running MSBuild Server node for this build (process ID {0}). - Reusing the running MSBuild Server node for this build (process ID {0}). + Reutilizando o nó do Servidor do MSBuild em execução para esta compilação (ID do processo {0}). MSBuild Server node started for this build (process ID {0}). - MSBuild Server node started for this build (process ID {0}). + Nó do Servidor do MSBuild iniciado para esta compilação (ID do processo {0}). MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). - MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). + Nó do Servidor do MSBuild iniciado somente para esta compilação; ele será encerrado depois (ID do processo {0}). MSBuild Server was requested but not used for this build: {0}. - MSBuild Server was requested but not used for this build: {0}. + O Servidor do MSBuild foi solicitado, mas não usado para esta compilação: {0}. the server was busy with another build - the server was busy with another build + o servidor estava ocupado com outra compilação this invocation is not compatible with MSBuild Server - this invocation is not compatible with MSBuild Server + esta invocação não é compatível com o Servidor do MSBuild node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) - node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) + a reutilização do nó está desabilitada (-nodeReuse:false ou MSBUILDDISABLENODEREUSE=1) the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled - the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled + A hachura de escape MSBUILDENSURESTDOUTFORTASKPROCESSES está habilitada the current server state could not be determined - o estado atual do servidor não pode ser determinado + o estado atual do servidor não pode ser determinado LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). @@ -2361,6 +2361,36 @@ arquivo de resposta. MSBUILD : error MSB4192: O arquivo de projeto "{0}" está no formato de arquivo ".vcproj" ou ".dsp", o qual não pode ser compilado diretamente pelo MSBuild. Converta o projeto abrindo-o no IDE do Visual Studio ou executando uma ferramenta de conversão ou, para ".vcproj", use o MSBuild para compilar o arquivo de solução que contém o projeto. {StrBegin="MSBUILD : error MSB4192: "} LOC: ".vcproj" and ".dsp" should not be localized + + 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: 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. + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: There was an exception while reading the log file: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + 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}'. + 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 + + + Schema validation + Schema validation + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + \ No newline at end of file diff --git a/src/MSBuild/Resources/xlf/Strings.ru.xlf b/src/MSBuild/Resources/xlf/Strings.ru.xlf index 2932ad45ad9..ba3241dce3f 100644 --- a/src/MSBuild/Resources/xlf/Strings.ru.xlf +++ b/src/MSBuild/Resources/xlf/Strings.ru.xlf @@ -381,62 +381,62 @@ could not connect to the server within the timeout window; the server may have failed to start - не удалось установить связь с сервером в течение времени ожидания; возможно, сервер не запустился + не удалось установить связь с сервером в течение времени ожидания; возможно, сервер не запустился LOCALIZATION: No format arguments. Used for any connect failure when the server's exit code is not known — covers both pipe-connect timeouts and non-timeout I/O errors during the connect attempt. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process exited with code {0} immediately after launch - серверный процесс завершил работу с кодом {0} сразу после запуска + серверный процесс завершил работу с кодом {0} сразу после запуска LOCALIZATION: {0} is the integer process exit code; rendered with InvariantCulture as a decimal integer, do not localize the digits. This message is concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process could not be launched - не удалось запустить серверный процесс + не удалось запустить серверный процесс LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). Reusing the running MSBuild Server node for this build (process ID {0}). - Reusing the running MSBuild Server node for this build (process ID {0}). + Повторно используется запущенный узел сервера MSBuild для этой сборки (идентификатор процесса {0}). MSBuild Server node started for this build (process ID {0}). - MSBuild Server node started for this build (process ID {0}). + Узел сервера MSBuild запущен для этой сборки (идентификатор процесса {0}). MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). - MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). + Узел сервера MSBuild запущен только для этой сборки; после этого он завершит работу (идентификатор процесса {0}). MSBuild Server was requested but not used for this build: {0}. - MSBuild Server was requested but not used for this build: {0}. + Сервер MSBuild был запрошен, но не использовался для этой сборки: {0}. the server was busy with another build - the server was busy with another build + сервер был занят другой сборкой this invocation is not compatible with MSBuild Server - this invocation is not compatible with MSBuild Server + этот вызов несовместим с MSBuild Server node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) - node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) + повторное использование узла отключено (-nodeReuse:false или MSBUILDDISABLENODEREUSE=1) the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled - the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled + Включен аварийный обход MSBUILDENSURESTDOUTFORTASKPROCESSES the current server state could not be determined - не удалось определить текущее состояние сервера + не удалось определить текущее состояние сервера LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). @@ -2361,6 +2361,36 @@ MSBUILD : error MSB4192: файл проекта "{0}" указан в формате "VCPROJ" или "DSP", непосредственная сборка которого с помощью MSBuild невозможна. Преобразуйте проект, открыв его в Visual Studio IDE или запустив инструмент преобразования, либо (в случае с "VCPROJ") используйте MSBuild для сборки файла решения, содержащего данный проект. {StrBegin="MSBUILD : error MSB4192: "} LOC: ".vcproj" and ".dsp" should not be localized + + 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: 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. + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: There was an exception while reading the log file: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + 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}'. + 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 + + + Schema validation + Schema validation + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + \ No newline at end of file diff --git a/src/MSBuild/Resources/xlf/Strings.tr.xlf b/src/MSBuild/Resources/xlf/Strings.tr.xlf index 35c280003f7..2795a9217da 100644 --- a/src/MSBuild/Resources/xlf/Strings.tr.xlf +++ b/src/MSBuild/Resources/xlf/Strings.tr.xlf @@ -381,62 +381,62 @@ could not connect to the server within the timeout window; the server may have failed to start - zaman aşımı süresi içinde sunucuya bağlanılamadı; sunucu başlatılamamış olabilir + zaman aşımı süresi içinde sunucuya bağlanılamadı; sunucu başlatılamamış olabilir LOCALIZATION: No format arguments. Used for any connect failure when the server's exit code is not known — covers both pipe-connect timeouts and non-timeout I/O errors during the connect attempt. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process exited with code {0} immediately after launch - sunucu işlemi başlatıldıktan hemen sonra {0} koduyla çıktı + sunucu işlemi başlatıldıktan hemen sonra {0} koduyla çıktı LOCALIZATION: {0} is the integer process exit code; rendered with InvariantCulture as a decimal integer, do not localize the digits. This message is concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process could not be launched - sunucu işlemi başlatılamadı + sunucu işlemi başlatılamadı LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). Reusing the running MSBuild Server node for this build (process ID {0}). - Reusing the running MSBuild Server node for this build (process ID {0}). + Bu derleme için çalışan MSBuild Sunucu düğümü yeniden kullanılıyor (işlem kimliği {0}). MSBuild Server node started for this build (process ID {0}). - MSBuild Server node started for this build (process ID {0}). + Bu derleme için MSBuild Sunucu düğümü başlatıldı (işlem kimliği {0}). MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). - MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). + MSBuild Sunucu düğümü yalnızca bu derleme için başlatıldı, ardından kapatılacak (işlem kimliği {0}). MSBuild Server was requested but not used for this build: {0}. - MSBuild Server was requested but not used for this build: {0}. + MSBuild Sunucusu istendi ancak bu derleme için kullanılmadı: {0}. the server was busy with another build - the server was busy with another build + sunucu başka bir derlemeyle meşguldü this invocation is not compatible with MSBuild Server - this invocation is not compatible with MSBuild Server + bu çağrı MSBuild Sunucu ile uyumlu değil node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) - node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) + düğüm yeniden kullanımı devre dışı (-nodeReuse:false veya MSBUILDDISABLENODEREUSE=1) the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled - the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled + MSBUILDENSURESTDOUTFORTASKPROCESSES kaçış mekanizması etkin the current server state could not be determined - geçerli sunucu durumu belirlenemedi + geçerli sunucu durumu belirlenemedi LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). @@ -2364,6 +2364,36 @@ MSBUILD : error MSB4192: "{0}" proje dosyası, MSBuild’in doğrudan derleyemeyeceği ".vcproj" veya ".dsp" dosya biçiminde. Lütfen projeyi Visual Studio IDE içinde açarak veya dönüştürme aracını kullanarak dönüştürün ya da “.vcproj” için MSBuild kullanarak projeyi içeren çözüm dosyasını derleyin. {StrBegin="MSBUILD : error MSB4192: "} LOC: ".vcproj" and ".dsp" should not be localized + + 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: 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. + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: There was an exception while reading the log file: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + 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}'. + 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 + + + Schema validation + Schema validation + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + \ No newline at end of file diff --git a/src/MSBuild/Resources/xlf/Strings.zh-Hans.xlf b/src/MSBuild/Resources/xlf/Strings.zh-Hans.xlf index f455ffd8681..264d95fc4eb 100644 --- a/src/MSBuild/Resources/xlf/Strings.zh-Hans.xlf +++ b/src/MSBuild/Resources/xlf/Strings.zh-Hans.xlf @@ -382,62 +382,62 @@ could not connect to the server within the timeout window; the server may have failed to start - 在超时时间内无法连接到服务器；服务器可能启动失败 + 在超时时间内无法连接到服务器；服务器可能启动失败 LOCALIZATION: No format arguments. Used for any connect failure when the server's exit code is not known — covers both pipe-connect timeouts and non-timeout I/O errors during the connect attempt. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process exited with code {0} immediately after launch - 服务器进程启动后立即退出，显示代码: {0} + 服务器进程启动后立即退出，显示代码: {0} LOCALIZATION: {0} is the integer process exit code; rendered with InvariantCulture as a decimal integer, do not localize the digits. This message is concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process could not be launched - 无法启动服务器进程 + 无法启动服务器进程 LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). Reusing the running MSBuild Server node for this build (process ID {0}). - Reusing the running MSBuild Server node for this build (process ID {0}). + 为此生成重用了正在运行的 MSBuild Server 节点(进程 ID {0})。 MSBuild Server node started for this build (process ID {0}). - MSBuild Server node started for this build (process ID {0}). + 为此生成启动了 MSBuild Server 节点(进程 ID {0})。 MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). - MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). + 仅为此生成启动了 MSBuild Server 节点；它将在之后关闭(进程 ID {0})。 MSBuild Server was requested but not used for this build: {0}. - MSBuild Server was requested but not used for this build: {0}. + 已请求 MSBuild Server，但未用于此生成: {0}。 the server was busy with another build - the server was busy with another build + 服务器正在处理另一个生成 this invocation is not compatible with MSBuild Server - this invocation is not compatible with MSBuild Server + 此调用与 MSBuild Server 不兼容 node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) - node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) + 已禁用节点重用(-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled - the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled + 已启用 MSBUILDENSURESTDOUTFORTASKPROCESSES 安全门 the current server state could not be determined - 无法确定当前服务器状态 + 无法确定当前服务器状态 LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). @@ -2364,6 +2364,36 @@ MSBUILD : error MSB4192: 项目文件“{0}”为“.vcproj”或“.dsp”文件格式，而 MSBuild 无法直接生成这些文件格式。请通过在 Visual Studio IDE 中打开该项目或运行转换工具来转换该项目；对于“.vcproj”格式，还可以使用 MSBuild 来生成包含该项目的解决方案文件。 {StrBegin="MSBUILD : error MSB4192: "} LOC: ".vcproj" and ".dsp" should not be localized + + 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: 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. + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: There was an exception while reading the log file: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + 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}'. + 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 + + + Schema validation + Schema validation + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + \ No newline at end of file diff --git a/src/MSBuild/Resources/xlf/Strings.zh-Hant.xlf b/src/MSBuild/Resources/xlf/Strings.zh-Hant.xlf index 3a0b421af38..4e75766743c 100644 --- a/src/MSBuild/Resources/xlf/Strings.zh-Hant.xlf +++ b/src/MSBuild/Resources/xlf/Strings.zh-Hant.xlf @@ -382,62 +382,62 @@ could not connect to the server within the timeout window; the server may have failed to start - 在逾時時段內無法連線至伺服器; 伺服器可能無法啟動 + 在逾時時段內無法連線至伺服器; 伺服器可能無法啟動 LOCALIZATION: No format arguments. Used for any connect failure when the server's exit code is not known — covers both pipe-connect timeouts and non-timeout I/O errors during the connect attempt. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process exited with code {0} immediately after launch - 伺服器處理序在啟動後立即以代碼 {0} 結束 + 伺服器處理序在啟動後立即以代碼 {0} 結束 LOCALIZATION: {0} is the integer process exit code; rendered with InvariantCulture as a decimal integer, do not localize the digits. This message is concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). the server process could not be launched - 無法啟動伺服器處理序 + 無法啟動伺服器處理序 LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). Reusing the running MSBuild Server node for this build (process ID {0}). - Reusing the running MSBuild Server node for this build (process ID {0}). + 正在針對此組建重複使用執行中的 MSBuild 伺服器節點 (處理序識別碼 {0})。 MSBuild Server node started for this build (process ID {0}). - MSBuild Server node started for this build (process ID {0}). + MSBuild 伺服器節點已針對此組建啟動 (處理序識別碼 {0})。 MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). - MSBuild Server node started for this build only; it will shut down afterward (process ID {0}). + MSBuild 伺服器節點已僅針對此組建啟動; 之後會將其關閉 (處理序識別碼 {0})。 MSBuild Server was requested but not used for this build: {0}. - MSBuild Server was requested but not used for this build: {0}. + 已要求 MSBuild 伺服器，但未用於此組建: {0}。 the server was busy with another build - the server was busy with another build + 伺服器正在忙碌於另一個組建 this invocation is not compatible with MSBuild Server - this invocation is not compatible with MSBuild Server + 此叫用與 MSBuild 伺服器不相容 node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) - node reuse is disabled (-nodeReuse:false or MSBUILDDISABLENODEREUSE=1) + 節點重複使用已停用 (-nodeReuse:false 或 MSBUILDDISABLENODEREUSE=1) the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled - the MSBUILDENSURESTDOUTFORTASKPROCESSES escape hatch is enabled + MSBUILDENSURESTDOUTFORTASKPROCESSES 逸出交錯線已啟用 the current server state could not be determined - 無法判斷目前的伺服器狀態 + 無法判斷目前的伺服器狀態 LOCALIZATION: No format arguments. Concatenated mid-sentence after a colon in MSBuildServerUnavailable: lower-case start in English is intentional and the message must NOT end with a period (the outer template adds it). @@ -2361,6 +2361,36 @@ MSBUILD : error MSB4192: 專案檔 "{0}" 的檔案格式為 ".vcproj" 或 ".dsp"，MSBuild 無法直接加以建置。請在 Visual Studio IDE 中開啟此專案或執行轉換工具加以轉換，若是 ".vcproj"，則改為使用 MSBuild 建置包含專案的方案檔。 {StrBegin="MSBUILD : error MSB4192: "} LOC: ".vcproj" and ".dsp" should not be localized + + 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: 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. + + + MSB4233: There was an exception while reading the log file: {0} + MSB4233: There was an exception while reading the log file: {0} + {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. + + + 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}'. + 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 + + + Schema validation + Schema validation + + UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is + displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: + "MSBUILD : Schema validation error MSB0000: This is an error." + LOCALIZATION: This fragment needs to be localized. + + \ No newline at end of file diff --git a/src/Utilities/Resources/xlf/Strings.cs.xlf b/src/Utilities/Resources/xlf/Strings.cs.xlf index f1dc84cee6e..b440e81e4f4 100644 --- a/src/Utilities/Resources/xlf/Strings.cs.xlf +++ b/src/Utilities/Resources/xlf/Strings.cs.xlf @@ -302,6 +302,21 @@ Vytváření sestavení bylo úspěšně dokončeno. + + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + {StrBegin="MSB5002: "} + + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + {StrBegin="MSB5021: "} + + + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + {StrBegin="MSB5018: "} + \ No newline at end of file diff --git a/src/Utilities/Resources/xlf/Strings.de.xlf b/src/Utilities/Resources/xlf/Strings.de.xlf index 9b1a407ba48..a4445a5014a 100644 --- a/src/Utilities/Resources/xlf/Strings.de.xlf +++ b/src/Utilities/Resources/xlf/Strings.de.xlf @@ -302,6 +302,21 @@ Der Buildvorgang wurde erfolgreich ausgeführt. + + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + {StrBegin="MSB5002: "} + + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + {StrBegin="MSB5021: "} + + + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + {StrBegin="MSB5018: "} + \ No newline at end of file diff --git a/src/Utilities/Resources/xlf/Strings.es.xlf b/src/Utilities/Resources/xlf/Strings.es.xlf index 769ed548530..3b18bff3422 100644 --- a/src/Utilities/Resources/xlf/Strings.es.xlf +++ b/src/Utilities/Resources/xlf/Strings.es.xlf @@ -302,6 +302,21 @@ Compilación correcta. + + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + {StrBegin="MSB5002: "} + + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + {StrBegin="MSB5021: "} + + + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + {StrBegin="MSB5018: "} + \ No newline at end of file diff --git a/src/Utilities/Resources/xlf/Strings.fr.xlf b/src/Utilities/Resources/xlf/Strings.fr.xlf index 68457df7602..875bfdee3aa 100644 --- a/src/Utilities/Resources/xlf/Strings.fr.xlf +++ b/src/Utilities/Resources/xlf/Strings.fr.xlf @@ -302,6 +302,21 @@ La génération a réussi. + + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + {StrBegin="MSB5002: "} + + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + {StrBegin="MSB5021: "} + + + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + {StrBegin="MSB5018: "} + \ No newline at end of file diff --git a/src/Utilities/Resources/xlf/Strings.it.xlf b/src/Utilities/Resources/xlf/Strings.it.xlf index bf6ce90796d..f284b46b5a9 100644 --- a/src/Utilities/Resources/xlf/Strings.it.xlf +++ b/src/Utilities/Resources/xlf/Strings.it.xlf @@ -302,6 +302,21 @@ Compilazione completata. + + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + {StrBegin="MSB5002: "} + + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + {StrBegin="MSB5021: "} + + + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + {StrBegin="MSB5018: "} + \ No newline at end of file diff --git a/src/Utilities/Resources/xlf/Strings.ja.xlf b/src/Utilities/Resources/xlf/Strings.ja.xlf index f91d83d9fd9..5af019db14f 100644 --- a/src/Utilities/Resources/xlf/Strings.ja.xlf +++ b/src/Utilities/Resources/xlf/Strings.ja.xlf @@ -302,6 +302,21 @@ ビルドに成功しました。 + + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + {StrBegin="MSB5002: "} + + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + {StrBegin="MSB5021: "} + + + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + {StrBegin="MSB5018: "} + \ No newline at end of file diff --git a/src/Utilities/Resources/xlf/Strings.ko.xlf b/src/Utilities/Resources/xlf/Strings.ko.xlf index f39256ce839..1408197c179 100644 --- a/src/Utilities/Resources/xlf/Strings.ko.xlf +++ b/src/Utilities/Resources/xlf/Strings.ko.xlf @@ -302,6 +302,21 @@ 빌드했습니다. + + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + {StrBegin="MSB5002: "} + + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + {StrBegin="MSB5021: "} + + + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + {StrBegin="MSB5018: "} + \ No newline at end of file diff --git a/src/Utilities/Resources/xlf/Strings.pl.xlf b/src/Utilities/Resources/xlf/Strings.pl.xlf index b97dfc21013..b56e5161133 100644 --- a/src/Utilities/Resources/xlf/Strings.pl.xlf +++ b/src/Utilities/Resources/xlf/Strings.pl.xlf @@ -302,6 +302,21 @@ Kompilacja powiodła się. + + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + {StrBegin="MSB5002: "} + + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + {StrBegin="MSB5021: "} + + + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + {StrBegin="MSB5018: "} + \ No newline at end of file diff --git a/src/Utilities/Resources/xlf/Strings.pt-BR.xlf b/src/Utilities/Resources/xlf/Strings.pt-BR.xlf index 858b50ef32a..4341bb596e4 100644 --- a/src/Utilities/Resources/xlf/Strings.pt-BR.xlf +++ b/src/Utilities/Resources/xlf/Strings.pt-BR.xlf @@ -302,6 +302,21 @@ Compilação com êxito. + + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + {StrBegin="MSB5002: "} + + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + {StrBegin="MSB5021: "} + + + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + {StrBegin="MSB5018: "} + \ No newline at end of file diff --git a/src/Utilities/Resources/xlf/Strings.ru.xlf b/src/Utilities/Resources/xlf/Strings.ru.xlf index c77e149ed89..b7290500fc8 100644 --- a/src/Utilities/Resources/xlf/Strings.ru.xlf +++ b/src/Utilities/Resources/xlf/Strings.ru.xlf @@ -302,6 +302,21 @@ Сборка успешно завершена. + + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + {StrBegin="MSB5002: "} + + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + {StrBegin="MSB5021: "} + + + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + {StrBegin="MSB5018: "} + \ No newline at end of file diff --git a/src/Utilities/Resources/xlf/Strings.tr.xlf b/src/Utilities/Resources/xlf/Strings.tr.xlf index 83ae273f27f..b507e6f86fa 100644 --- a/src/Utilities/Resources/xlf/Strings.tr.xlf +++ b/src/Utilities/Resources/xlf/Strings.tr.xlf @@ -302,6 +302,21 @@ Oluşturma başarılı oldu. + + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + {StrBegin="MSB5002: "} + + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + {StrBegin="MSB5021: "} + + + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + {StrBegin="MSB5018: "} + \ No newline at end of file diff --git a/src/Utilities/Resources/xlf/Strings.zh-Hans.xlf b/src/Utilities/Resources/xlf/Strings.zh-Hans.xlf index 44eb460d3fc..b32a071e8b4 100644 --- a/src/Utilities/Resources/xlf/Strings.zh-Hans.xlf +++ b/src/Utilities/Resources/xlf/Strings.zh-Hans.xlf @@ -302,6 +302,21 @@ 已成功生成。 + + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + {StrBegin="MSB5002: "} + + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + {StrBegin="MSB5021: "} + + + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + {StrBegin="MSB5018: "} + \ No newline at end of file diff --git a/src/Utilities/Resources/xlf/Strings.zh-Hant.xlf b/src/Utilities/Resources/xlf/Strings.zh-Hant.xlf index 27049a59e01..48043a2d7b0 100644 --- a/src/Utilities/Resources/xlf/Strings.zh-Hant.xlf +++ b/src/Utilities/Resources/xlf/Strings.zh-Hant.xlf @@ -302,6 +302,21 @@ 建置成功。 + + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. + {StrBegin="MSB5002: "} + + + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. + {StrBegin="MSB5021: "} + + + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + MSB5018: Failed to delete the temporary file "{0}". {1} {2} + {StrBegin="MSB5018: "} + \ No newline at end of file