translations in transifex

[pvgenuchten]

How are we managing translation in microservices? I noticed the .properties format for translations.
Idea is to set up new project in transifex or add to the existing project?
I have added a single microservices-file in https://www.transifex.com/geonetwork/core-geonetwork/translate/#nl/api_enproperties/308707898

• set up transifex
• hooks and scripts to synchronise with github

[fxprunayre]

How are we managing translation in microservices?

I think it could make sense to have something (at least core set of strings) that we can share between GN-UI and microservice to avoid duplication. So we can have a file in both repo created from transifex (we have to define a master file probably?).

Then each project can have separate files for their specific translations eg. errors in microservice, components or custom apps in GN-UI.

It would be good to also have a more precise scheme for translation keys to avoid terms to be used in a context it was not expected to eg. "y" could have been yes or true or public ... as it is used in facet for isTemplate, isPublic, isHarvested ... in GN3.

The number of strings shared between the 2 projects should be probably quite limited and are more about the "theme" and strings which appears in a common header (eg. sign in) and footer.

@fgravin any ideas/suggestions?

• microservice will use properties https://github.com/geonetwork/geonetwork-microservices/blob/ogcapirecords/modules/services/ogc-api-records/service/src/main/resources/messages/api.properties
• GN-UI JSON https://github.com/geonetwork/geonetwork-ui/blob/master/apps/search/src/assets/i18n/en.json

[pvgenuchten]

Note that we can also export any transifex source as .properties file, but still it would be more optimal if spring is able to ingest the json files (in case people want to customise a translation file). Would be good it is the same file used in both projects, or at least it has a similar format.

Does this help? https://www.baeldung.com/spring-boot-json-properties