summaryrefslogtreecommitdiff
path: root/developers-manual.rst
diff options
context:
space:
mode:
authorbuckE <buckE@disroot.org>2020-05-06 04:52:15 +0000
committerbuckE <buckE@disroot.org>2020-05-06 04:52:15 +0000
commit4b34f9a973bcb382e4dc267fa265521c54b30b44 (patch)
tree744ff20f9291c571683d40ecf8cf38ee2f0ead2c /developers-manual.rst
parent74109cd0682cd4ced092ab6a858b35b65b380317 (diff)
downloaddocs-4b34f9a973bcb382e4dc267fa265521c54b30b44.tar.gz
docs-4b34f9a973bcb382e4dc267fa265521c54b30b44.tar.bz2
docs-4b34f9a973bcb382e4dc267fa265521c54b30b44.zip
adding to Internationalization
Diffstat (limited to 'developers-manual.rst')
-rw-r--r--developers-manual.rst12
1 files changed, 9 insertions, 3 deletions
diff --git a/developers-manual.rst b/developers-manual.rst
index cef2095c..ec25f794 100644
--- a/developers-manual.rst
+++ b/developers-manual.rst
@@ -635,12 +635,17 @@ To create a Component, log into https://weblate.taler.net/ with your *Manager* o
What follows is a sort of Wizard. You can find detailed docs at https://docs.weblate.org/. Here are some important notes about connecting your Component to the Taler Git repository:
+Under *https://weblate.taler.net/create/component/vcs/*:
+
* **Source code repository** - Generally `git+ssh://git@git.taler.net/<reponame>`. Check with `git remote -v`.
* **Repository branch ** - Choose the correct branch to draw from and commit to.
* **Repository push URL** - This is generally `git+ssh://git@git.taler.net/<reponame>` Check with `git remote -v`.
-* **Repository browser** - This is the www URL of the Git repo's file browser. Example `https://git.taler.net/<repo>.git/tree/{{filename}}#L{{line}}`
+* **Repository browser** - This is the www URL of the Git repo's file browser. Example `https://git.taler.net/<repositoryname>.git/tree/{{filename}}?h={{branch}}#n{{line}}`
* **Merge style ** - *Rebase*, in line with GNU Taler development procedures
+* **Translation license** - *GNU General Public License v3.0 or Later*
+* **Adding new translation** - Decide how to handle adding new translations
+
How to Create a Translation
---------------------------
@@ -661,10 +666,11 @@ You may also wish to refer to ``https://docs.weblate.org/``.
Translation Standards and Practices
-----------------------------------
-By default, our Weblate instance is set to accept translations in English, French, German, Italian, Russian, Spanish, and Portuguese.
+By default, our Weblate instance is set to accept translations in English, French, German, Italian, Russian, Spanish, and Portuguese. If you want to contribute a translation in a different language, navigate to the *Component* you want to translate for, and click "Start new translation" to begin. If you require a privilege upgrade, please contact a superuser with your request.
-If you want to contribute a translation in a different language, navigate to the *Component* you want to translate for, and click "Start new translation" to begin. If you require a privilege upgrade, please contact a superuser with your request.
+When asked, set the license to GPLv3 or later.
+Set commit/push to manual only.
GPG Signing of Translations
---------------------------