dotnet-cpp-localizer_skill

Overview

This skill provides end-to-end internationalization (i18n) and localization (l10n) tooling for .NET and C++ projects. It automates resource generation, string extraction, translation file management, and runtime locale wiring to deliver robust multi-language applications. The skill supports .resx, gettext (.po/.mo), ICU, and common frameworks like ASP.NET Core, WPF, MAUI, and Boost.Locale.

How this skill works

It scans code to extract hard-coded strings and generates appropriate resource templates (.resx, .pot) or binding code (gettext/ICU). It manages translation files, runs quality checks (missing translations, duplicates, format errors), and compiles runtime artifacts (.mo, merged .resx). It also produces integration snippets and middleware configuration for ASP.NET Core, WPF, MAUI, and C++ build systems (CMake).

When to use it

• Adding multi-language support to new or existing .NET web, desktop, or mobile apps
• Localizing C++ CLI tools, desktop apps, or games with gettext or ICU
• Automating translation file lifecycle and syncing with code changes
• Enforcing localization QA before release (missing keys, plural and format checks)
• Preparing translation-ready deliverables for external translators

Best practices

• Keep all UI strings out of code and in resource files from project start
• Use culture-aware formatting for dates, numbers, and currencies via locale APIs
• Extract strings regularly and run msgmerge or resx updates after code changes
• Define a clear resources folder and naming convention per framework
• Test plural forms and parameterized strings in each target locale

Example use cases

• Generate Resources/ controllers and views .resx files and configure RequestLocalization for ASP.NET Core
• Extract strings with xgettext, create .po templates, and compile .mo files for a C++ app
• Add runtime language switch to a WPF or MAUI app and persist user preference
• Integrate ICU for advanced locale formatting, collation, and plural rules in C++
• Automate translation pipeline in CI: extract → update .po/.resx → quality checks → compile artifacts