Localized file check-in by OneLocBuild Task: Build definition ID 1218: Build ID 3030501#10184
Localized file check-in by OneLocBuild Task: Build definition ID 1218: Build ID 3030501#10184dotnet-bot wants to merge 7 commits into
Conversation
…: Build ID 3030017
…: Build ID 3030017
…: Build ID 3030017
…: Build ID 3030017
…: Build ID 3030017
…: Build ID 3030017
There was a problem hiding this comment.
Pull request overview
Updates generated localization resources across MSTest and Microsoft Testing Platform components.
Changes:
- Adds translations for new diagnostics and extension descriptions.
- Revises existing localized messages.
- Normalizes BOM encoding in several XLF files.
Reviewed changes
Copilot reviewed 23 out of 24 changed files in this pull request and generated 25 comments.
Show a summary per file
| File | Description |
|---|---|
PlatformResources.ru.xlf |
Localizes FileLogger failure text. |
PlatformResources.ko.xlf |
Localizes log-flush timeout text. |
PlatformResources.it.xlf |
Localizes log-flush timeout text. |
PlatformResources.fr.xlf |
Localizes FileLogger failure text. |
PlatformResources.de.xlf |
Revises named-pipe guidance. |
TerminalResources.tr.xlf |
Revises slow-test option text. |
TerminalResources.pl.xlf |
Revises slow-test option text. |
VSTestBridge/ExtensionResources.ru.xlf |
Localizes browser runsettings guidance. |
VSTestBridge/ExtensionResources.ko.xlf |
Localizes browser runsettings guidance. |
VSTestBridge/ExtensionResources.de.xlf |
Localizes browser runsettings guidance. |
PackagedApp/ExtensionResources.pl.xlf |
Localizes the extension description. |
PackagedApp/ExtensionResources.fr.xlf |
Localizes packaged-app diagnostics. |
PackagedApp/ExtensionResources.es.xlf |
Localizes manifest diagnostics. |
PackagedApp/ExtensionResources.de.xlf |
Localizes activation diagnostics. |
PackagedApp/ExtensionResources.cs.xlf |
Localizes the extension description. |
GitHubActionsResources.ru.xlf |
Revises slow-test reporting text. |
GitHubActionsResources.ko.xlf |
Localizes process-exit text. |
CrashDumpResources.ru.xlf |
Localizes crash-sequence errors. |
CrashDumpResources.fr.xlf |
Localizes crash-sequence errors. |
Resources.ja.xlf |
Localizes analyzer guidance. |
Resources.fr.xlf |
Revises analyzer description formatting. |
Resource.de.xlf |
Localizes cleanup cancellation text. |
PlatformAdapterResources.ko.xlf |
Localizes browser runsettings guidance. |
PlatformAdapterResources.de.xlf |
Localizes browser runsettings guidance. |
Comments suppressed due to low confidence (1)
src/Platform/Microsoft.Testing.Extensions.PackagedApp/Resources/xlf/ExtensionResources.fr.xlf:27
- The final “See” remains untranslated in this French error message.
<target state="translated">Nous ne pouvons pas lancer l’application Windows packagée « {0} » (détectée « {1} »). L’inscription et l’activation d’une application empaquetée (MSIX) nécessitent la version Windows de cette extension, fournie pour net8.0-windows10.0.19041.0 et les versions ultérieures. Ciblez 'net8.0-windows10.0.19041.0' (ou un moniker de framework cible net*-windows ultérieur avec une version de plateforme 10.0.19041.0 ou supérieure) pour que NuGet sélectionne cet élément. La build actuelle lance uniquement des hôtes de test non empaquetés (disposition libre). See https://github.com/microsoft/testfx/issues/9933.</target>
| <source>An unexpected exception occurred in the 'FileLogger' write loop for log file '{0}'. The log file may be incomplete. | ||
| {1}</source> | ||
| <target state="new">An unexpected exception occurred in the 'FileLogger' write loop for log file '{0}'. The log file may be incomplete. | ||
| <target state="translated">В цикле записи файла журнала 'FileLogger' произошла непредвиденная ошибка "{0}". Файл журнала может быть неполным. |
| <trans-unit id="TimeoutFlushingLogsErrorMessage"> | ||
| <source>Failed to flush logs to log file '{0}' before the timeout of '{1}' seconds. The log file may be incomplete.</source> | ||
| <target state="new">Failed to flush logs to log file '{0}' before the timeout of '{1}' seconds. The log file may be incomplete.</target> | ||
| <target state="translated">'{0}'초의 시간 제한이 지나기 전에 로그를 로그 파일 '{1}'에 플러시하지 못했습니다. 로그 파일이 완전하지 않을 수 있습니다.</target> |
| <source>An unexpected exception occurred in the 'FileLogger' write loop for log file '{0}'. The log file may be incomplete. | ||
| {1}</source> | ||
| <target state="new">An unexpected exception occurred in the 'FileLogger' write loop for log file '{0}'. The log file may be incomplete. | ||
| <target state="translated">Une exception inattendue s’est produite dans la boucle d’écriture« FileLogger » du fichier journal « {0} ». Le fichier journal peut être incomplet. |
| <trans-unit id="NamedPipeDirectoryNotWritableErrorMessage"> | ||
| <source>The named pipe directory '{0}' does not exist or is not writable: {1}. Set the '{2}' environment variable to an existing writable directory, or unset it to fall back to the default temporary directory.</source> | ||
| <target state="translated">Das Named Pipe-Verzeichnis „{0}“ ist nicht vorhanden oder kann nicht geschrieben werden: {1}. Legen Sie die Umgebungsvariable „{2}“ auf ein vorhandenes beschreibbares Verzeichnis fest, oder entfernen Sie die Einstellung, um auf das temporäre Standardverzeichnis zurückzugreifen.</target> | ||
| <target state="translated">Das Named Pipe-Verzeichnis „{0}“ ist nicht vorhanden oder kann nicht geschrieben werden: {1}. Legen Sie die Umgebungsvariable „{2}“ auf ein vorhandenes beschreibbares Verzeichnis fest, oder legen Sie sie für das Fallback auf das temporäre Standardverzeichnis fest.</target> |
| <trans-unit id="TerminalShowSlowestTestsOptionDescription"> | ||
| <source>Show the specified number of slowest tests (by reported execution duration) in the run summary. Expects a positive integer.</source> | ||
| <target state="translated">Çalıştırma özetinde belirtilen sayıda en yavaş testi (bildirilen yürütme süresine göre) gösterir. Pozitif bir tamsayı bekliyor.</target> | ||
| <target state="translated">Çalıştırma özetinde belirtilen sayıda en yavaş testi (bildirilen yürütme süresine göre ) gösterir. Pozitif bir tamsayı bekliyor.</target> |
| <trans-unit id="AssemblyFixtureProviderNotSupportedWithNativeAotDescription"> | ||
| <source>'[AssemblyFixtureProvider]' discovery relies on walking the runtime assembly reference graph, which is not supported when the runtime cannot generate dynamic code (for example under Native AOT or Blazor WebAssembly AOT). The attribute is ignored in such builds, so the provided assembly initialize and cleanup methods will not run. Declare the '[AssemblyInitialize]' and '[AssemblyCleanup]' methods directly in the test assembly instead.</source> | ||
| <target state="new">'[AssemblyFixtureProvider]' discovery relies on walking the runtime assembly reference graph, which is not supported when the runtime cannot generate dynamic code (for example under Native AOT or Blazor WebAssembly AOT). The attribute is ignored in such builds, so the provided assembly initialize and cleanup methods will not run. Declare the '[AssemblyInitialize]' and '[AssemblyCleanup]' methods directly in the test assembly instead.</target> | ||
| <target state="translated">[AssemblyFixtureProvider] の検出は、ランタイム アセンブリ参照グラフの走査に依存しています。これは、ランタイムが動的コードを生成できない場合 (例: Native AOT または Blazor WebAssembly AOT の場合) はサポートされません。このようなビルドではこの属性は無視されるため、提供されたアセンブリの初期化メソッドとクリーンアップ メソッドは実行されません。代わりに、'[AssemblyInitialize]' メソッドと '[AssemblyCleanup]' メソッドををテスト アセンブリ内で直接宣言してください。</target> |
| – il doit prendre un paramètre de type « TestContext » | ||
| – le type de retour doit être « void », « Task » ou « ValueTask ». | ||
|
|
||
| {0} |
| <trans-unit id="GlobalTestCleanupWasCancelled"> | ||
| <source>Global test cleanup method '{0}.{1}' was canceled</source> | ||
| <target state="new">Global test cleanup method '{0}.{1}' was canceled</target> | ||
| <target state="translated">Die globae Testbereinigungsmethode „{0}.{1}“ wurde abgebrochen</target> |
| <trans-unit id="RunSettingsEnvironmentVariablesNotSupportedOnBrowser"> | ||
| <source>The runsettings 'EnvironmentVariables' section is not supported on browser/WebAssembly platforms, because applying it requires restarting the test host process. Remove the section to run on browser-wasm.</source> | ||
| <target state="new">The runsettings 'EnvironmentVariables' section is not supported on browser/WebAssembly platforms, because applying it requires restarting the test host process. Remove the section to run on browser-wasm.</target> | ||
| <target state="translated">runsettings 'EnvironmentVariables' 섹션은 브라우저/WebAssembly 플랫폼에서 지원되지 않습니다. 이 섹션을 적용하려면 테스트 호스트 프로세스를 다시 시작해야 하기 때문입니다. browser-wasm에서 실행할 섹션을 제거합니다.</target> |
| <trans-unit id="RunSettingsEnvironmentVariablesNotSupportedOnBrowser"> | ||
| <source>The runsettings 'EnvironmentVariables' section is not supported on browser/WebAssembly platforms, because applying it requires restarting the test host process. Remove the section to run on browser-wasm.</source> | ||
| <target state="new">The runsettings 'EnvironmentVariables' section is not supported on browser/WebAssembly platforms, because applying it requires restarting the test host process. Remove the section to run on browser-wasm.</target> | ||
| <target state="translated">Der runsettings-Abschnitt „EnvironmentVariables“ wird auf Browser-/WebAssembly-Plattformen nicht unterstützt, da für die Anwendung ein Neustart des Testhostprozesses erforderlich ist. Entfernen Sie den Abschnitt, der auf browser-wasm ausgeführt werden soll.</target> |
…: Build ID 3030035
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 31 out of 32 changed files in this pull request and generated 1 comment.
Comments suppressed due to low confidence (17)
src/Analyzers/MSTest.Analyzers/xlf/Resources.fr.xlf:590
- This target introduces
{0}even though the source has no format placeholder. The analyzer description will therefore display a stray{0}to French users. Remove it in the localization source and regenerate the XLF.
{0}
src/Platform/Microsoft.Testing.Platform/Resources/xlf/PlatformResources.ko.xlf:1065
- The placeholders are reversed:
{0}is the log-file path but is rendered as the timeout, while{1}is rendered as the file name. Correct the Korean translation so{1}labels the seconds and{0}labels the log file.
<target state="translated">'{0}'초의 시간 제한이 지나기 전에 로그를 로그 파일 '{1}'에 플러시하지 못했습니다. 로그 파일이 완전하지 않을 수 있습니다.</target>
src/Platform/Microsoft.Testing.Extensions.GitHubActionsReport/Resources/xlf/GitHubActionsResources.ru.xlf:162
- The elapsed-seconds placeholder
{1}was replaced by a second{0}, so the test name will be printed where the duration should appear. Restore{1}for the elapsed seconds via the localization pipeline.
<target state="translated">{0} все еще выполняется через {0} с</target>
src/Platform/Microsoft.Testing.Platform/Resources/xlf/PlatformResources.de.xlf:509
- The source tells users to unset the environment variable to use the default temporary directory, but this translation tells them to set it for the fallback. That reverses the recovery instruction; correct the German translation through OneLoc.
<target state="translated">Das Named Pipe-Verzeichnis „{0}“ ist nicht vorhanden oder kann nicht geschrieben werden: {1}. Legen Sie die Umgebungsvariable „{2}“ auf ein vorhandenes beschreibbares Verzeichnis fest, oder legen Sie sie für das Fallback auf das temporäre Standardverzeichnis fest.</target>
src/Platform/Microsoft.Testing.Platform/Resources/xlf/PlatformResources.ru.xlf:1127
{0}is the log-file path, but this translation presents it as the unexpected error. This makes the diagnostic misleading; retain{0}as the file name and leave{1}as the exception detail.
<target state="translated">В цикле записи файла журнала 'FileLogger' произошла непредвиденная ошибка "{0}". Файл журнала может быть неполным.
{1}</target>
src/Platform/Microsoft.Testing.Extensions.PackagedApp/Resources/xlf/ExtensionResources.es.xlf:32
<Application>is a literal manifest element name, but the translation changes it to the nonexistent<Aplicación>element. It also adds mismatched quotes around{1}. Preserve the XML element name and balanced placeholder quoting in the localized error.
<target state="translated">No se puede activar la aplicación empaquetada de Windows "{0}" (se encontró ''{1}"): su manifiesto no declara ningún <Aplicación>, por lo que no hay ningún identificador de modelo de usuario de aplicación para activar.</target>
src/Platform/Microsoft.Testing.Extensions.PackagedApp/Resources/xlf/ExtensionResources.de.xlf:32
<Application>is a literal manifest element name, but this translation changes it to the nonexistent<Anwendung>element. Preserve<Application>so the error points users to the actual manifest syntax.
<target state="translated">Die verpackte Windows-App "{0}" (gefunden "{1}") kann nicht aktiviert werden: Ihr Manifest deklariert keine <Anwendung>, sodass keine Anwendungsbenutzermodell-ID zum Aktivieren vorhanden ist.</target>
src/Platform/Microsoft.Testing.Extensions.GitHubActionsReport/Resources/xlf/GitHubActionsResources.ko.xlf:47
- The source says a dependent process exited, but
튜닝 프로세스means a tuning process. Correct the Korean term so the exit reason identifies the dependent process.
<target state="translated">튜닝 프로세스가 예기치 않게 종료되었습니다.</target>
src/Platform/Microsoft.Testing.Extensions.PackagedApp/Resources/xlf/ExtensionResources.pl.xlf:17
- The source uses “True” to distinguish genuine UWP/AppContainer hosts, but
o wartości trueturns it into a Boolean-value qualifier. Correct this sentence so the extension limitation is accurately described.
<target state="translated">Wdraża niepakowany (z luźnym układem) host testowy systemu Windows (na przykład rozpakowany winUI) w izolowanym katalogu i uruchamia go z tego miejsca, a w kompilacji systemu Windows rejestruje spakowanego, w pełni zaufanego hosta testów pulpitu MSIX i aktywuje go za pomocą identyfikatora modelu użytkownika aplikacji. Hosty platformy UWP/AppContainer o wartości true nie są obsługiwane. Zobacz stronę https://github.com/microsoft/testfx/issues/9933.</target>
src/Platform/Microsoft.Testing.Extensions.PackagedApp/Resources/xlf/ExtensionResources.fr.xlf:12
- The French sentence repeats
élémentafter the<Identity ... />element, making the localized diagnostic ungrammatical. Remove the duplicate word through the localization pipeline.
<target state="translated">Le manifeste de l’application packagée ne déclare pas d’élément valide <Identity Name="..." Publisher="..." /> élément.</target>
src/Platform/Microsoft.Testing.Extensions.PackagedApp/Resources/xlf/ExtensionResources.cs.xlf:17
UWPis misspelled asUPW, which changes the platform acronym in the localized extension description. Correct the acronym through the localization pipeline.
<target state="translated">Nasadí nezabaleného hostitele testů Windows s volným rozložením souborů (například nezabalené WinUI) do izolovaného adresáře a spustí ho odtud a – v sestavení Windows – zaregistruje zabaleného desktopového hostitele testů MSIX s plnou důvěryhodností a aktivuje ho pomocí Application User Model ID. Skuteční hostitelé UPW/AppContainer nejsou podporováni. Viz https://github.com/microsoft/testfx/issues/9933.</target>
src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.fr.xlf:89
le du fichiercontains two conflicting articles and makes the localized crash-dump error ungrammatical. Correct it tole fichierthrough the localization pipeline.
<target state="translated">Nous n’avons pas pu initialiser le du fichier de séquence d’incidents « {0} » : {1}. Les informations sur la séquence de test ne seront pas disponibles si l’hôte de test se bloque.</target>
src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.ru.xlf:89
- The plural subject
Сведенияdoes not agree withбудет недоступна. Correct the agreement toбудут недоступныin the localization source.
<target state="translated">Не удалось инициализировать файл последовательности сбоя "{0}": {1}. Сведения о последовательности тестирования будет недоступна в случае сбоя тестового узла.</target>
src/Analyzers/MSTest.Analyzers/xlf/Resources.ja.xlf:52
- The particle is duplicated in
メソッドををテスト, making the Japanese analyzer description ungrammatical. Remove oneをthrough the localization pipeline.
<target state="translated">[AssemblyFixtureProvider] の検出は、ランタイム アセンブリ参照グラフの走査に依存しています。これは、ランタイムが動的コードを生成できない場合 (例: Native AOT または Blazor WebAssembly AOT の場合) はサポートされません。このようなビルドではこの属性は無視されるため、提供されたアセンブリの初期化メソッドとクリーンアップ メソッドは実行されません。代わりに、'[AssemblyInitialize]' メソッドと '[AssemblyCleanup]' メソッドををテスト アセンブリ内で直接宣言してください。</target>
src/Adapter/MSTestAdapter.PlatformServices/Resources/xlf/Resource.de.xlf:243
globaeis a typo in the German error message. Correct it toglobalethrough the localization pipeline.
<target state="translated">Die globae Testbereinigungsmethode „{0}.{1}“ wurde abgebrochen</target>
src/Platform/Microsoft.Testing.Platform/Resources/xlf/PlatformResources.fr.xlf:1126
- A space is missing before the opening French quotation mark around
FileLogger, joiningd’écritureand« FileLogger ». Restore the spacing through the localization pipeline.
<target state="translated">Une exception inattendue s’est produite dans la boucle d’écriture« FileLogger » du fichier journal « {0} ». Le fichier journal peut être incomplet.
src/Platform/Microsoft.Testing.Platform/OutputDevice/Terminal/xlf/TerminalResources.pl.xlf:411
- The sentence now starts with lowercase
pokaż. Restore the initial capital in the Polish option description through the localization pipeline.
<target state="translated">pokaż określoną liczbę najwolniejszych testów (według zgłoszonego czasu trwania wykonywania) w podsumowaniu przebiegu. Oczekuje dodatniej liczby całkowitej.</target>
| <trans-unit id="TimeoutFlushingLogsErrorMessage"> | ||
| <source>Failed to flush logs to log file '{0}' before the timeout of '{1}' seconds. The log file may be incomplete.</source> | ||
| <target state="new">Failed to flush logs to log file '{0}' before the timeout of '{1}' seconds. The log file may be incomplete.</target> | ||
| <target state="translated">Non è possibile scaricare il file di log '{0}' prima del timeout di '{1}' secondi. Il file di log potrebbe essere incompleto.</target> |
This is the pull request automatically created by the OneLocBuild task in the build process to check-in localized files generated based upon translation source files (.lcl files) handed-back from the downstream localization pipeline. If there are issues in translations, visit https://aka.ms/icxLocBug and log bugs for fixes. The OneLocBuild wiki is https://aka.ms/onelocbuild and the localization process in general is documented at https://aka.ms/AllAboutLoc.