taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 705eeeafa67b47b8a73d9cedf032aefdd7a2fb01
parent 9f12faa11c8d356a90139c0ed7046223dd8cb6eb
Author: Christian Grothoff <christian@grothoff.org>
Date:   Fri,  1 May 2020 12:43:10 +0200

Merge branch 'master' of git+ssh://git.taler.net/docs

Diffstat:
Mdevelopers-manual.rst | 64++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 64 insertions(+), 0 deletions(-)

diff --git a/developers-manual.rst b/developers-manual.rst @@ -590,6 +590,70 @@ for that. There is also the possibility to trigger builds manually, but this is only reserved to "admin" users. + +Internationalization +==================== + +Internationalization (a.k.a "Translation") is handled with Weblate (https://weblate.org) via our instance at ``https://weblate.taler.net/``. + +At this time, this system is still very new for Taler.net and this documentation may be incorrect and is certainly incomplete. + +Who can Register +---------------- + +At this time, anyone can register an account at ``https://weblate.taler.net/`` to create translations. Registered users default to the **Users** and **Viewers** privilege level. + +About Privilege Levels +---------------------- + +This is the breakdown of privilege levels in Weblate: + +* **Users**/**Viewers** = Can log in, view Translations (*applies to new users*) + +* **Reviewers** = Can contribute Translations to existing *Components* + +* **Managers** = Can create new *Components* of existing *Projects* + +* **Superusers** = Can create new *Projects* + +Upgrading Privileges +-------------------- + +To upgrade from **Users**/**Viewers**, a superuser must manually augment your privileges. At this time, superusers are Christian, Florian, and Buck. + +How to Create a Translation +--------------------------- + +1 - Log into ``https://weblate.taler.net`` + +2 - Navigate to *Projects* > *Browse all projects* + +3 - Choose the *project* you wish to contribute to. + +4 - Choose the *component* you wish to contribute to. + +5 - Find the language you want to translate into. Click "Translate" on that line. + +6 - Find a phrase and translate it. + +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. + +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. + + +GPG Signing of Translations +--------------------------- + +weblate.taler.net signs GPG commits with the GPG key CD33CE35801462FA5EB0B695F2664BF474BFE502, and the corresponding public key can be found at https://weblate.taler.net/keys/. + +This means that contributions made through weblate will not be signed with the individual contributor's key when they are checked into the Git repository, but with the weblate key. + + Android Apps ============