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.
Activity
assigned to @Jan_Mach
By Jan Mach on 2024-12-26T14:06:40
changed milestone to %2.4
added Done 50% S-In Progress labels and removed Done 0% S-New labels
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.
By Jan Mach on 2019-05-10T09:40:57
added Done 100% S-Closed labels and removed Done 50% S-In Progress labels