App languages
The language picker in the portal's top bar sets your portal language. A new Calculator App starts in that language when it supports it. Otherwise it starts in the default declared by its author. An app's Language picker lists its supported languages. Changing it preserves entered values, scenarios, current pages and the last result, and leaves the portal language unchanged.
Author an app's translations
Open App languages in the editor. The language resource describes a default, the supported language codes, and a dictionary for each language. Save or publish the app to keep those resources with its version. Save as keeps the same resources in the new copy. Older apps without a declaration retain their original text.
{
"languages": { "default": "en", "supported": ["en", "sv"] },
"locales": {
"en": { "name": "Savings plan", "labels": {} },
"sv": {
"name": "Sparplan",
"labels": {
"Savings plan": "Sparplan",
"Annual contribution": "Årlig insättning",
"Balance": "Saldo"
}
}
}
}The dictionary keys are the app's original display text. Missing entries retain that original text. The default must appear in the supported list. Use distinct language codes such as en, sv or en-GB. Each app owns its translations; changing one app does not change another app or the portal.
Domain package files
A domain package can contain additional calculation and language resource files. Select a file tab to edit it, use + to create a file, and use its file actions to rename or delete it. The entry file remains the package's entry point. Relative references stay within the package. Saved apps keep their pinned package files when a newer package version is published.
Language resource files belong to the package that owns their display text. Documentation keeps its existing language independently of the portal language picker.
Use language resource names such as i18n/en.json and i18n/sv.json in a domain package. Each resource has the same labels dictionary as an app resource; add "default": true to the package's fallback resource. The app combines resources from its pinned packages for the selected language, then applies its own dictionary last. This lets an app override a package label without changing the package or copying its entire language file. Package dictionaries remain part of their pinned versions when an app is saved or copied.