Skip to content
Snippets Groups Projects
Commit 0cb39512 authored by Jan Mach's avatar Jan Mach
Browse files

Updated documentation for administrators regarding in-situ translations.

(Redmine issue: #4789)
parent 8ca4da51
No related branches found
No related tags found
No related merge requests found
...@@ -60,6 +60,34 @@ ramdisk allocation size is technically just an upper limit and overflowing data ...@@ -60,6 +60,34 @@ ramdisk allocation size is technically just an upper limit and overflowing data
will be swapped to hard disk. will be swapped to hard disk.
Local customizations of reporting translations
````````````````````````````````````````````````````````````````````````````````
It is possible to locally customize the reporting templates and translations. All
relevant files reside inside the ``/etc/mentat/templates`` configuration directory.
* ``/etc/mentat/templates/informant`` - Templates and message catalogs for ``mentat-informant.py``
* ``/etc/mentat/templates/reporter`` - Templates and message catalogs for ``mentat-reporter.py``
In each of the directories above you should aim for following files:
* ``*.j2`` - Jinja templates for email reports
* ``translations/cs/LC_MESSAGES/messages.po`` - Message catalog for czech translations
The workflow for customizing the templates is as follows::
# Step 1: Modify the appropriate '.j2' file
# Step 2: Update the message catalogs:
hawat-cli repintl update
# Step 3: Translate newly added strings in appropriate '*.po' file(s)
# Step 4: Compile the message catalogs:
hawat-cli repintl compile
hawat-cli repintl clean
.. _section-administration-monitoring: .. _section-administration-monitoring:
Monitoring Monitoring
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment