# HG changeset patch
# User Fadi Abbud <fadi.abbud@intevation.de>
# Date 1568362103 -7200
# Node ID 3184210f50e9a31588f7d8afa9f35434f3fbd0ad
# Parent  def4b06cd0a4012d51ff361eb5b7f400806e6146
client: docs: add hint for translation about whitespace

diff -r def4b06cd0a4 -r 3184210f50e9 client/docs/dev-translations.md
--- a/client/docs/dev-translations.md	Fri Sep 13 09:19:35 2019 +0200
+++ b/client/docs/dev-translations.md	Fri Sep 13 10:08:23 2019 +0200
@@ -27,6 +27,7 @@
 - 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.
+- Use the central defined class `<span class="fix-trans-space"> text<span>` to fix leading and trailing whitespace problem.see:[https://github.com/Polyconseil/vue-gettext/issues/80](https://github.com/Polyconseil/vue-gettext/issues/80).
 - 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`.