Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2962801

[dotnet-bot]

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.

[github-actions]

🤖 Copilot Code Review — PR #127475

Holistic Assessment

Motivation: This is an automated localization check-in by OneLocBuild (Build ID 2961630), providing actual translations for 4 previously untranslated strings in the System.Text.Json source generator's .xlf resource files. The strings had state="new" (English source text used as placeholder targets) and needed proper translations — this is routine and justified.

Approach: Standard OneLocBuild workflow — replaces English placeholder targets with actual localized translations across all 13 supported languages and updates the state attribute from "new" to "translated". This is the expected process for localization in dotnet/runtime.

Summary: ✅ LGTM. Mechanical localization update with zero code or behavioral changes. All format string placeholders ({0}, {1}) are correctly preserved in all 52 translated strings. The change is perfectly balanced (52 insertions, 52 deletions = 4 strings × 13 languages).

---

Detailed Findings

✅ Translation Completeness — All 4 strings translated consistently across all 13 languages

The same 4 trans-units are updated in every .xlf file (cs, de, es, fr, it, ja, ko, pl, pt-BR, ru, tr, zh-Hans, zh-Hant):

• InaccessibleJsonIncludePropertiesNotSupportedFormat (format string with {0}.{1})
• InaccessibleJsonIncludePropertiesNotSupportedTitle
• JsonIgnoreConditionAlwaysInvalidOnTypeFormat (format string with {0})
• JsonIgnoreConditionAlwaysInvalidOnTypeTitle

Each file changes exactly 8 lines (4 removed, 4 added). No language is missing updates.

✅ Format Placeholder Integrity — All placeholders preserved

Verified that {0} and {1} format placeholders are correctly retained in all translations that require them:

• All 13 InaccessibleJsonIncludePropertiesNotSupportedFormat translations contain both {0} and {1} ✓
• All 13 JsonIgnoreConditionAlwaysInvalidOnTypeFormat translations contain {0} ✓
• The two Title strings have no placeholders (matching the source) ✓

✅ State Attribute Correctness — Proper XLF lifecycle transitions

All entries correctly transition from state="new" to state="translated", which is the standard XLIFF lifecycle for completed translations.

✅ No Code or API Changes — Localization-only PR

No .cs, .csproj, ref assembly, or other source files are modified. No new public API surface detected. This PR has zero risk of behavioral regression.

Generated by Code Review for issue #127475 · ◷