The Jmix framework subsystems come with
messages.properties files containing messages in English. It means that even if you set a different locale in your project and translate your own message files, your users will still see parts of the UI in English because they are implemented in the framework. This includes standard actions and data management components like filter and pagination, as well as the entire UI views of the security and other subsystems.
We provide translations of the framework messages to some languages in the form of translation modules. A translation module is a set of message files packed together in a JAR that can be added to your project as a dependency. You can find the translation modules created by the Jmix team and community members on the Jmix marketplace: open Jmix tool window → Settings → Marketplace in Studio and filter by the Localization tag.
If you need to translate the framework messages to a different language, you can do it right in your project. Below is a recommended way to do it:
Clone https://github.com/jmix-framework/jmix repository and checkout a branch corresponding to the Jmix version used in your project.
Depending on the set of add-ons used in your project, copy all or some of the
messages.propertiesfiles from the
jmix-translations/contentfolder to the same paths under your project’s
messages_<your_language>.propertiesand translate the messages.
|If you like to contribute to the framework translations project, feel free to send us pull requests with new languages or changes in existing translations!|