Details
-
Bug
-
Status: Code Review (Post-Commit)
-
Should
-
Resolution: Unresolved
-
None
-
None
-
None
-
Low
Description
At some point recently, Transifex changed to a new configuration format that is incompatible with the existing configuration in our refapp modules. This ticket aims to fix this in each of the modules that have translations managed in transifex.
This task has already been undertaken for coreapps, and the ticket under which that was done can be found here for reference:
https://issues.openmrs.org/browse/RA-2019
This is dependent upon upgrading Bamboo to use the latest Transifex client. There is a PR for this outstanding here: https://github.com/openmrs/openmrs-contrib-itsmresources/pull/48
Fixing this issue involves changeing the .tx/config file within each codebase to match the following:
[main]
host = https://www.transifex.com/
[o:openmrs:p:OpenMRS:r:xxxxxxx]
source_file = api/src/main/resources/messages.properties
source_lang = en
file_filter = api/src/main/resources/messages_<lang>.properties
type = UNICODEPROPERTIES
Where "xxxxxxx" would be replaced with the name of the resource slug in Transifex. These are as follows:
- htmlformentry-module
- allergyapi-module
- allergyui-module
- appointmentschedulingui-module
- coreapps-module
- dispensing-module
- haiti-core-module
- htmlformentryui-module
- labworkflow-owa
- mdr-tb-module
- openmrs-module-operationtheater
- orderentry-owa
- printer-module
- radiology-app-module
- radiology-module
- react-components
- referenceapplication-module
- registrationapp-module
- reporting-ui-module
- uicommons-module
- uiframework-module
As a part of this ticket, we should also identify how the openmrs-core resource in Transifex is being used (if at all) and ensure the process for pulling in core translations is fixed.
dkayiwa / ibacher / mogoodrich FYI