officeimo-studio-translations
Skill713 starsChanged 2 days agoMITView on GitHub
Use when adding OfficeIMO Studio interface languages, completing or correcting translations, or adding interface text to the desktop Studio (Avalonia, Windows and Linux) or the native Apple apps (Mac, iPad, iPhone). Covers the shared export, translate, import and check workflow for both apps.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- officeimo-build-releaseSkill
- officeimo-conversion-operatorSkill
- officeimo-website-wasmSkill
- pswritepdf-retirementSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 1 is distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Run from the repository root.
- Very specific: line 37
Delete Artefacts/Translations when done.
- Very specific: line 39
Use culture names .NET and Apple share: it, es, pt-BR, nb, zh-Hans, zh-Hant.
- Very specific: line 44
Keep every placeholder: {0}, {1:N0}, {page}, %@, %lld, %1$@, ${applicationName}.
- Very specific: line 47
Keep product and format names: OfficeIMO, Studio, PDF, PDF/A, PDF/UA, Word, Excel, PowerPoint, Markdown, JSON, Bates.
- Distinctive: line 48
Use the operating system's own terms for standard commands (Undo, Save, Share, Print) in that language, and stay close to the English …
- Very specific: line 62
Desktop: add the English string to StudioStrings.resx under a feature-scoped key and the same key to every shipped language's .resx in the …
- Very specific: line 67
Apple: write the text in SwiftUI or String(localized:), run Sync-StudioAppleStrings.ps1, and translate the new catalog entries into every …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
OfficeIMO Studio translations
Studio's interface text lives in two places, one per app family, and one workflow translates both:
- Desktop (Avalonia):
OfficeIMO.Studio/Localization/StudioStrings.resxholds English;StudioStrings.<language>.resxholds each language. Code and XAML read stable, feature-scoped keys throughIStudioLocalizer(UiText,UiFormat,{loc:Loc Key}). The picker offers the languages inStudioCultureCatalog.ShippedCultures. - Apple (Mac, iPad, iPhone):
Apple/OfficeIMOStudio/Shared/Localizable.xcstringsholds the interface,AppShortcuts.xcstringsthe Shortcuts phrases andInfoPlist.xcstringsthe app name and permission prompts. SwiftUI text andString(localized:)are keyed by their English text. The Xcode project'sknownRegionslists the languages.
The document engines stay culture-neutral: they don't translate document content or vary behaviour by language.
Add languages
Run from the repository root. Build/Studio holds the scripts; each takes several languages at once.
- On a Mac, sync the Apple strings first:
./Build/Studio/Sync-StudioAppleStrings.ps1. It builds the iOS app, extracts the Swift strings and adds new ones toLocalizable.xcstrings;xcodebuildalone doesn't. Without a Mac, skip it and say the Apple catalog may lack strings added since its last sync. - Export:
./Build/Studio/Export-StudioTranslations.ps1 -Language it,es,pt-BR,ja -OutputDirectory Artefacts/Translationswrites<language>.jsonwith every string that language lacks in both apps (about 2,600 for a new language), its Englishsource, acontextand an emptytranslation.-Allexports translated strings too, to review a language. - Translate each file: fill every
translation, following therulesin the file. Work in batches; a file can be imported partly translated and exported again for the rest. - Import:
./Build/Studio/Import-StudioTranslations.ps1 -Path Artefacts/Translations/it.json,Artefacts/Translations/es.jsonwrites the desktop.resxand the Apple catalogs and registers each language inShippedCulturesandknownRegions. It refuses a file whose translation changes a placeholder, naming each one; nothing from that file is written.-NoRegisterwrites strings without offering the language. - Check:
./Build/Studio/Test-StudioTranslations.ps1must pass (CI runs it in the Studio job). Then run the desktop tests (StudioTranslationResourceTests,StudioInfrastructureTests) and build the Mac and iOS apps. - Delete
Artefacts/Translationswhen done; the translation files aren't kept in the repository.
Use culture names .NET and Apple share: it, es, pt-BR, nb, zh-Hans, zh-Hant. ReservedCultures lists names
already accepted in preferences.
Translating well
- Keep every placeholder:
{0},{1:N0},{page},%@,%lld,%1$@,${applicationName}. Positional forms such as%2$@ … %1$@may reorder Apple values. Header and footer fields ({page},{pages},{date},{file},{title}) stay in English because Studio replaces them. - Keep product and format names: OfficeIMO, Studio, PDF, PDF/A, PDF/UA, Word, Excel, PowerPoint, Markdown, JSON, Bates.
- Use the operating system's own terms for standard commands (Undo, Save, Share, Print) in that language, and stay close to the English length: menus, toolbars and sheets have limited room.
- Translate whole sentences naturally; counts such as "(%lld)" may move within the sentence.
- Right-to-left languages (
ar,he,fa,ur) mirror both apps: desktop windows, menus and dialogs follow the culture (App.ApplyFlowDirection), and the Apple apps follow the system language. PDF pages, scans, signatures, images and file locations keep their own direction. After importing one, runStudioRightToLeftLayoutTestswithOFFICEIMO_STUDIO_VISUAL_OUTPUTset and look at the screenshots; on a Mac, launch the app with-AppleTextDirection YES -NSForceRightToLeftWritingDirection YESto see the mirrored Apple layout. - Languages are translated and reviewed by AI agents; no human translation is required. A pack ships when the check
passes and a second agent pass has reviewed the whole language in the export file (
-All) for meaning, consistent terminology, the platform's standard terms and length, with its corrections imported.
Adding interface text
- Desktop: add the English string to
StudioStrings.resxunder a feature-scoped key and the same key to every shipped language's.resxin the same change. Never put user-facing text in code or XAML. A fallback passed toGetOrDefault/FormatOrDefaultis a safety net, not the English string: the check fails when a key used with one, directly or through a view model'sT(key, fallback)helper, is missing fromStudioStrings.resx, andStudioTranslationResourceTestscovers keys built from enum names. Add a family's keys when you add an enum value. - Apple: write the text in SwiftUI or
String(localized:), runSync-StudioAppleStrings.ps1, and translate the new catalog entries into every known region. Mark strings with no words, such as%@ – %@,shouldTranslate: false. - For a few new strings, export with the languages concerned, translate and import, as above.
- Engine messages (exceptions from Studio.Core and the native engine) are English; the roadmap records making them translatable. Don't translate them in the apps by matching message text.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

