ZaclysIndustries/searxngRebrandZaclys
2
0
Fork 0
forked from zaclys/searxng
Code Issues Pull Requests Activity
647e6187d7
searxngRebrandZaclys/docs/dev/translation.rst
Markus Heiser b9cf3c82a1 [mod] add i18n infrastructure for SearXNG message files (searxng.msg) 
With this patch ``searxng.msg`` files can be added to SearXNG.  In
``searxng.msg`` files messages can be defined which are not captured by babel's
gettext, like the generic names of the categories or messages that are stored in
constants.

Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2022-03-16 09:55:53 +01:00

3.0 KiB
Raw Blame History

Translation

translated

Translation takes place on weblate.bubu1.eu.

Translations which has been added by translators on the weblate.bubu1.eu UI are committed to Weblate's counterpart of the SearXNG origin repository which is located at https://weblate.bubu1.eu/git/searxng/searxng.

There is no need to clone this repository, SearXNG Weblate workflow take care of the synchronization with the origin. To avoid merging commits from the counterpart directly on the master branch of SearXNG origin, a pull request (PR) is created by this workflow.

Weblate monitors the translations branch, not the master branch. This branch is an orphan branch, decoupled from the master branch (we already know orphan branches from the gh-pages). The translations branch contains only the

  • translation/messages.pot and the
  • translation/*/messages.po files, nothing else.
SearXNG's PR workflow to be in sync with Weblate
Sync from origin to weblate: using make weblate.push.translations

For each commit on the master branch of SearXNG origin the GitHub job babel / Update translations branch <.github/workflows/integration.yml> checks for updated translations.

Sync from weblate to origin: using make weblate.translations.commit

Every Friday, the GitHub workflow babel / create PR for additons from weblate <.github/workflows/translations-update.yml> creates a PR with the updated translation files:

  • translation/messages.pot,
  • translation/*/messages.po and
  • translation/*/messages.mo

wlc

All weblate integration is done by GitHub workflows, but if you want to use wlc, copy this content into wlc configuration in your HOME ~/.config/weblate

[keys]
https://weblate.bubu1.eu/api/ = APIKEY

Replace APIKEY by your API key.