Mercurial > gemma
changeset 4375:6ebd2d7756d5
client: docs: add hints for translations
| author | Fadi Abbud <fadi.abbud@intevation.de> |
|---|---|
| date | Wed, 11 Sep 2019 16:02:41 +0200 |
| parents | ad2bf9580696 |
| children | 8949b4d714ee |
| files | client/docs/dev-translations.md |
| diffstat | 1 files changed, 5 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/client/docs/dev-translations.md Wed Sep 11 15:51:15 2019 +0200 +++ b/client/docs/dev-translations.md Wed Sep 11 16:02:41 2019 +0200 @@ -26,7 +26,11 @@ - `gettext` must be called only in javascript part. For html part we use `<translate>` and `<v-translate>` to make sure that `makemessages` marks the strings correctly - passing a value with \`\` to `gettext` leads to break up the translation process (e.g. gettext(\` text to translate ${value} \`)) - passing html element (e.g. `<div>`) to gettext is interpreted as string. -- The strings to translate have to be included in the source code and not directly in `.po` files. +- The strings to translate have to be included in the source code and not directly in `.po` files. +- Check if the development work does not ruin the translation process: + Call `make makemessages` ---> if `.po` files were generated ---> everything is ok. + **Notice**: To avoid merge conflicts we push `.po` files into the repository after we synchronize it with the new translations on `weblate`. + We do this one time weekly, so you don not have to do this yourself. If it is required to merge the new strings instantly please contact one of the translation managers. ## Why was gettext chosen?