Implement better mechanism for web interface translations
The new mechanism should be versatile enough to support local translations on remote system installations. Currently the only reasonably easy way for translations is to do them in development. There is a Makefile target ready for this task. However when the Mentat system is installed in production environment there is no way to create additional local translations or change/tweak the distribution translations.
Updated by Jan Mach over 3 years ago
- Status changed from In Progress to Closed
- % Done changed from 50 to 100
Attached pathes greatly improve the ability to customize reporting templates and message catalog translations on target host.
The current solution however removes the information about the location of translated message. This was necessary to prevent from unnecessary changes in target files due to the possibility of message catalogs being updated by two different commands (makefile and hawat-cli). There is a new version of mentat-reporter.py behind the horizon, which merges message catalogs for Mentat and Hawat into single instance and brings in additional changes to localization workflow, so I have not bothered with coming up with better solution that this one.