From 1a4b3bb165dc7f902c6671e4a2da1c2e0dfac5f6 Mon Sep 17 00:00:00 2001 From: kobergj Date: Mon, 13 Mar 2023 16:12:31 +0100 Subject: [PATCH] Update services/userlog/README.md Co-authored-by: Michael Barz --- services/userlog/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/services/userlog/README.md b/services/userlog/README.md index 0a04dfcd805..a9c3476f3f1 100644 --- a/services/userlog/README.md +++ b/services/userlog/README.md @@ -34,7 +34,7 @@ To delete events for an user, use a `DELETE` request to `ocs/v2.php/apps/notific ## Translations -The `userlog` service has embedded translations sourced via transifex to provide a basic set of translated languages. These embedded translation are available for all deployment scenarios. In addition, the service supports custom translations, though it is currently not possible to just add custom translations to embedded ones. If custom translation are configured, the embedded ones are not used. To configure custom translations, the `USERLOG_TRANSLATION_PATH` environment variable needs to point to a base folder that will further contain the translation files. This path must be available from all instances of the userlog service, a shared storage is recommended. Translation files must be of type [.po](https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html#PO-Files) or [.mo](https://www.gnu.org/software/gettext/manual/html_node/Binaries.html). For each language, the filename needs to be `userlog.po` (or `userlog.mo`) and stored in a folder structure defining the language code. In general the path/name pattern for a translation file needs to be: +The `userlog` service has embedded translations sourced via transifex to provide a basic set of translated languages. These embedded translations are available for all deployment scenarios. In addition, the service supports custom translations, though it is currently not possible to just add custom translations to embedded ones. If custom translations are configured, the embedded ones are not used. To configure custom translations, the `USERLOG_TRANSLATION_PATH` environment variable needs to point to a base folder that will further contain the translation files. This path must be available from all instances of the userlog service, a shared storage is recommended. Translation files must be of type [.po](https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html#PO-Files) or [.mo](https://www.gnu.org/software/gettext/manual/html_node/Binaries.html). For each language, the filename needs to be `userlog.po` (or `userlog.mo`) and stored in a folder structure defining the language code. In general the path/name pattern for a translation file needs to be: ```text {USERLOG_TRANSLATION_PATH}/{language-code}/LC_MESSAGES/userlog.po