You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Part of the translation process entails downloading translated string maps from Transifex locally and generating their respective machine object (.mo) files. A separate file must be downloaded for each translated language. This is currently a manual process.
To make this process faster and less error-prone, we should implement a script to automatically download and compile the translation files for commitment to the code base. The Django project utilizes a script that we can probably borrow.
Justification
Automating this process will greatly simplify it and greatly reduce the likelihood of errors.
The text was updated successfully, but these errors were encountered:
I had passed on the GitHub integration initially because I'm worried about the amount of noise it may generate. We generally need to merge translations only as part of the release process, as opposed to automatically in response to changes or at a set interval. But maybe it's worth experimenting with to see if we can come up with a workable configuration.
Proposed Changes
Part of the translation process entails downloading translated string maps from Transifex locally and generating their respective machine object (.mo) files. A separate file must be downloaded for each translated language. This is currently a manual process.
To make this process faster and less error-prone, we should implement a script to automatically download and compile the translation files for commitment to the code base. The Django project utilizes a script that we can probably borrow.
Justification
Automating this process will greatly simplify it and greatly reduce the likelihood of errors.
The text was updated successfully, but these errors were encountered: