COmanage Registry can be localized (configured with the deployment-specific text) in two ways: by creating language translation files, or by creating dynamic localizations.
Note that while most texts can be localized as described here, a few stragglers are not yet handled by the common mechanism (CO-117).
1. Language Translation Files
Language strings are rendered via lookup in a language translation file, which can be found in the file
app/Lib/lang.php. This is the best option to change the language of Registry. Note that the language in use is currently a platform wide setting, it cannot yet be adjusted on a CO-specific basis (CO-424).
Registry currently uses a custom localization format, which is scheduled to be replaced in a future release (CO-351).
2. Dynamic Localizations
Specific text strings can be dynamically changed on a per-CO basis, via Collaborations > CO > Configuration > Localizations. It is necessary to know the text key, which unfortunately is best found at the moment either by looking through the source code or by guessing. Changes take effect immediately, but only within the selected CO. This is the best option to change a small number of text strings.
As of Registry v4.0.0, dynamic localizations made in the COmanage CO will apply to the entire platform. However, if the same key is localized in a CO, the CO-specific localization will take precedence over the platform localization.