Hi!
What is the approach for translations in Capella 7.1.0?
My question is - if I would like to prepare the translation, what is the process?
BR,
Marek Kuciński
Let me check internally how this can be done.
Thanks for offering to contribute. For custom MBSE model property translations, using the Capella Property Extension or custom viewlet properties files is usually the most maintainable path.
Hello,
Translations in Eclipse require some knowledge on how to develop Eclipse plugins. You can lookup articles on Eclipse internationalisation such as How to Internationalize your Eclipse Plug-In or Eclipse Internationalization Part 1/4 - Current Situation by Dirk Fauth - vogella Blog .
The gist of it is that you will need to create localization plugins that will provide translated properties files following a specific naming convention. The Strings in Capella (or any Eclipse project) are spread throughout the codebase in properties files. For Example, you can look at this one, in a plugin named “org.polarsys.capella.common.ui” : capella/common/plugins/org.polarsys.capella.common.ui/src/org/polarsys/capella/common/ui/preferences/messages.properties at master · eclipse-capella/capella · GitHub .
If you want to translate these Strings, you will need to create a fragment plugin that targets org.polarsys.capella.common.ui as its host. This fragment needs to have a file named “message_ja_JP” (for a japanese translation) in the same package hierarchy (so the file would be “org.polarsys.capella.common.ui/src/org/polarsys/capella/common/ui/preferences/messages_ja_JP.properties”). This needs to be repeated for all translatable properties files in the code base.
You would then push a PR against the Capella repository for these translations plugins.
Laurent Goubet
Obeo