diff --git a/developer_manual/basics/translations.rst b/developer_manual/basics/translations.rst index 7a745c5a0..de654dfd5 100644 --- a/developer_manual/basics/translations.rst +++ b/developer_manual/basics/translations.rst @@ -119,6 +119,18 @@ They differ a bit in terms of usage compared to php: t('myapp', '{name} is available. Get {linkstart}more information{linkend}', {name: 'Nextcloud 16', linkstart: '', linkend: ''}); n('myapp', 'Import %n calendar into {collection}', 'Import %n calendars into {collection}', selectionLength, {collection: 'Nextcloud'}); + +ExApps (Python) +--------------- + +For ExApps, Python is currently only supported for automated Transifex translations. + +Alongside the usual ``l10n/*.json`` and ``l10n/*.js`` files, translation source files located in ``translationfiles//*.po`` are also included in the Transifex sync. +These ``.po`` files can be compiled into ``.mo`` files, which are typically used by the ExApp backend for runtime translations. + +For more details, see :ref:`ex_app_translations_page`. + + Guidelines ---------- diff --git a/developer_manual/exapp_development/development_overview/ExAppOverview.rst b/developer_manual/exapp_development/development_overview/ExAppOverview.rst index 1ee545e4d..2306b1b2c 100644 --- a/developer_manual/exapp_development/development_overview/ExAppOverview.rst +++ b/developer_manual/exapp_development/development_overview/ExAppOverview.rst @@ -93,7 +93,7 @@ The bootstrap of the Vue app (`UI Example bootstrap ` are supported. To add support of your programming language from translations string extraction using Nextcloud translation tool, you just need to add your file extensions to it `in createPotFile `_ and down below adjust the ``--language`` and ``keyword`` parameters. -Here is an example using translationtool adjusted in the same way: + +Currently only Python is supported as an additional language in translationtool for ExApps. +Here is an example using translationtool adjusted for Python: .. code-block:: @@ -158,7 +159,7 @@ Here is an example using translationtool adjusted in the same way: $keywords = ''; if (substr($entry, -4) === '.php') { $keywords = '--keyword=t --keyword=n:1,2'; - + } else if (substr($entry, -3) === '.py') { + + } elseif (substr($entry, -3) === '.py') { + $keywords = '--keyword=_ --keyword=_n:1,2'; } else { $keywords = '--keyword=t:2 --keyword=n:2,3'; @@ -167,7 +168,7 @@ Here is an example using translationtool adjusted in the same way: $language = '--language='; if (substr($entry, -4) === '.php') { $language .= 'PHP'; - + } else if (substr($entry, -3) === '.py') { + + } elseif (substr($entry, -3) === '.py') { + $language .= 'Python'; } else { $language .= 'Javascript'; @@ -187,46 +188,13 @@ and can be used to translate ExApp strings on the backend or frontend in the sam You might need to convert the translation files to the format that is used in your language. -And this can be done with simple bash script, as `in our example for Python `_: +And this can be done with simple bash scripts, as `in our example for Python `_: +- `scripts/compile_po_to_mo.sh `_: compiles the ``.po`` files to ``.mo`` files. (needed in case of Transifex sync, only ``.po`` and ``l10n/*js|json`` files are provided) +- `scripts/copy_translations.sh `_: for Python example ExApp transforms ``translationfiles//*.(po|mo)`` into the locale folder structure: ``//LC_MESSAGES/*.(po|mo)``. This can be adjusted to your needs, depending on the language you are using. -.. code-block:: - - #!/bin/bash - - # This script is used to transform default translation files folders (translationfiles//*.(po|mo)) - # to the locale folder (locale//LC_MESSAGES/*.(po|mo)) - - cd .. - - # Remove the locale/* if it exists to cleanup the old translations - if [ -d "locale" ]; then - rm -rf locale/* - fi - - # Create the locale folder if it doesn't exist - if [ ! -d "locale" ]; then - mkdir locale - fi - - # Loop through the translation folders and copy the files to the locale folder - # Skip the templates folder - - for lang in translationfiles/*; do - if [ -d "$lang" ]; then - lang=$(basename $lang) - if [ "$lang" != "templates" ]; then - if [ ! -d "locale/$lang/LC_MESSAGES" ]; then - mkdir -p locale/$lang/LC_MESSAGES - fi - # Echo the language being copied - echo "Copying $lang locale" - cp translationfiles/$lang/*.po locale/$lang/LC_MESSAGES/ - cp translationfiles/$lang/*.mo locale/$lang/LC_MESSAGES/ - fi - fi - done - +.. note:: + Your translations conversion should be also included in `Dockerfile `_ build process, so that the ExApp translations are available in the Docker image. Makefile @@ -242,7 +210,8 @@ It is recommended to use the following default set of commands: - ``register``: performs registration of running manually ExApp using the ``manual_install`` Deploy daemon. - ``translation_templates``: execute translationtool.phar to extract translation strings from sources (frontend and backend). - ``convert_translations_nc``: converts translations to Nextcloud format files (json, js). -- ``convert_to_locale``: copies translations to the common locale//LC_MESSAGES/.(po|mo). Depending on the language, you might need to adjust the script. +- ``compile_po_to_mo``: compiles the ``.po`` files to ``.mo`` files using the ``scripts/compile_po_to_mo.sh`` script. +- ``copy_translations``: copies translations to needed location depending on your ExApp backend programming language. .. note:: These Makefiles are typically written to work in the `nextcloud-docker-dev `_ development environment. diff --git a/developer_manual/exapp_development/tech_details/Translations.rst b/developer_manual/exapp_development/tech_details/Translations.rst index ad6ca880f..1d9a2f272 100644 --- a/developer_manual/exapp_development/tech_details/Translations.rst +++ b/developer_manual/exapp_development/tech_details/Translations.rst @@ -1,3 +1,5 @@ +.. _ex_app_translations_page: + Translations ============ @@ -19,9 +21,24 @@ For the front-end part, AppAPI will inject the current user's locale ``l10n/`_. +There are two Python functions used by `translationtool `_ to extract translation string: ``_('singular string')`` and ``_n('singular string', 'plural string', count)``. + + +Manual translations +******************* + +Manual translations instructions can be found :ref:`here `. + + +Transifex sync +-------------- + +For automated Transifex sync there are only ``.po`` files included. +You can then compile them to ``.mo`` files using `ui_example's `_ ``scripts/compile_po_to_mo.sh`` script. + Manual install **************