Feature #1924
Updated by Alexander Watzinger about 1 year ago
*Update*: Translations are unified and table translation added, see [[Translations]] for details.
Enric, who kindly made Spanish and Catalan translations, noticed that translations for table labels are missing.
I already created the translations string in the *develop* branch and they were added to the translation files:
<pre><code class="python">
_('previous')
_('next')
_('show')
_('entries')
_('showing %(first)s to %(last)s of %(all)s entries', first=1, last=25, all=38)
</code></pre>
It still has to be implemented so that they show up in the UI. At the moment we are using multiple translation system and it can get confusing:
* *.po* files in *openatlas/translations*
** used in the Python and HTML files with the _('string_to_translate') notation
** used for the map and transformed to JavaScript variables in *openatlas/templates/map.html*
** used for general UI translations and transformed to JavaScript variables at top of *openatlas/templates/layout.html*
* JavaScript form error translations in *openatlas/static/js/messages_de.js*
** I noticed it was broken, is fixed in develop and online on demo-dev. I also wrote a test for it to prevent this in the future.
** It's the only one (I think) that is translated outside of the *.po* files, we may want to change that
** Currently only German translations are available but I want to wait to ask e.g. Enric for translations until we decided, if/how we restructure it.
I hope I didn't missed anything.
Assigning this to our fronted expert Andi. It would be great if we could unify this while adding support for table labels translations . e.g.
* All translations in *.po* files
* Transformation to JavaScript at one place
Please let me know if/how we could solve this so that we can discuss it later.