Localization
In UI5 the texts are files the app ships: an i18n.properties per locale, read through a resource bundle or bound in a view as {i18n>KEY}, with the locale coming from the client. The question the door adds is who keeps those files in step with the views that reference them, which is a tooling job rather than a runtime one.
Overview
SAPUI5 ships the resource bundle: .properties files per locale in the app, read through sap/base/i18n/ResourceBundle or bound to control properties through a resource model, so the same app runs in another language without a code change.
Not covered: At the texts the app already carries. Producing the translations is what SAP Translation HubSAP Translation HubSAP's translation service for software texts and documents, drawing on repositories of verified and company translations and on machine translation by SAP's neural MT or large language models.sap official, btp does on BTP, and keeping the bundle files themselves in step with the views that reference them is left to tooling, where @sap-ux/i18n@sap-ux/i18nA library that reads and writes the i18n bundles of a UI5 or CAP project from Node code, the i18n.properties file of a UI5 app and the i18n folder of a CAP project alike.sap official, ui5 sits.
Command-line tools that machine-translate the properties files or round-trip them through a spreadsheet, such as i18n-ai-translator@concircle/i18n-ai-translatorA CLI that translates a UI5 app's i18n.properties with OpenAI and writes the language files back, masking placeholders, applying a glossary and caching what has been translated.independent, ui5 and ui5-i18n-excel-converterui5-i18n-excel-converterA command-line tool that exports a UI5 app's i18n properties files to an Excel sheet of keys and languages for translators and imports the translated sheet back into the files.independent, ui5.
Artifacts
Details
Coverage
For your agent
- Ref
capability:localization- JSON
- /capabilities/localization.json
- MCP
- Connecting an agent