- Home
- Skills
- APIs & Backend
- Fourteen-Language Desktop Localization Kit (English as Key)
Fourteen-Language Desktop Localization Kit (English as Key)
Localizing a shipped desktop app usually means replacing every string with a resource id and losing the ability to read the code.
$39
Works with the AI Agents you already use
Fourteen-Language Desktop Localization Kit (English as Key)
Example session with this skill installed
Run a check on the German and Polish translation files against the source dictionary. The source is at out/lang/app-source.json and translations are in src/Core/Languages.
- Read your context and instructions
- Compiled the fourteen-language desktop localization
The language check for German (de) and Polish (pl) has been completed. The Polish translation is fully synchronized, while the German file requires technical corrections to interpolation and accelerator keys.
Localization Audit Report
| Language | Status | Issues Found | Details |
|---|---|---|---|
| pl | Complete | 0 | All keys match; interpolation holes and whitespace are valid. |
| de | Incomplete | 3 | Mismatched holes, missing underscores, and orphaned keys detected. |
Error Log: de-DE
Interpolation Mismatch: holes differ in "Detected {0}. {1} items" - The German translation is missing the second placeholder.
Accelerator Key Error: underscores differ in "_Refresh now" - The shortcut underscore was omitted in the target string.
Orphaned Key: unknown "Old sentence" - This key exists in the German JSON but has been removed from the C# source code.
Next steps
- Update the
de.jsonfile to include{1}in the "Detected" string to prevent runtime formatting errors. - Re-insert the underscore
_in the German "Refresh" string to restore the keyboard shortcut. - Remove the "Old sentence" key from the German translation file to clean up the dictionary.
Connects securely to your tools. The creator never sees your data.
About this skill
Localizing a shipped desktop app usually means replacing every string with a resource id and losing the ability to read the code. This kit keeps the English sentence in the code as the dictionary key: T("Refresh now"), and T($"Detected {name}. {count} items") whose key is the template with numbered holes. A translation may reorder the holes; a sentence a language lacks shows in English, so the fallback is always real text.
collect-strings.mjs: every XAML text attribute (Text, Content, Header, ToolTip, Window Title, accessibility name and help text; input boxes and bindings skipped) and every T(...) literal in C#, read the way the compiler reads it (escapes, verbatim quotes, interpolation holes with their expressions for context, {{ }} braces), comments skipped, a T(...) that is not one literal reported as a build problem. Output: the translators' source pack with locations and hole meanings. A t('...') mode for scripts.
check-languages.mjs: every language has every sentence with the same holes, the same count of access-key underscores and the same leading and trailing whitespace, and nothing else; per-language summary, exit 1. Store listings: same keys and array lengths as the English, about copied unchanged, Description 9,500, ReleaseNotes 1,450, ShortDescription 400, Features and Captions 190, SearchTerms 30 characters and 3 words, paragraph count preserved.
Lang.cs (reference runtime): an interpolated-string handler that builds the key and formats values in the language's culture, embedded-resource dictionaries, Windows display-language default (Filipino to Tagalog), right-to-left flag, reverse lookup for screens that switch language. i18n-runtime.mjs: the same model for JavaScript with a tagged template. languages.json: fourteen languages with cultures and the Store limits.
Templates: briefs for the translator (the mechanical rules the checker enforces, number formats per language, typed keywords stay English), the localizer engineer, the English help writer (stable section ids and screenshot placeholders as a contract) and the Store listing translator; a PowerShell queue that runs the Windows App Certification Kit over every package in one elevated session.
Reference: the method and the rules that came from doing it. 7 tests. Node 20+, no packages.
XAML collection is regex-based for attributes only. C# collector handles single literals in T() calls; it does not resolve constants or expressions. Node 20+ required.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 18 days ago
Requires