commit 9a264afb085d0cdc5842b2f3058e98562e4b8c70
parent 91a49139d3139c67547ee213fcf7531c889f155d
Author: Sebastian <sebasjm@taler-systems.com>
Date: Wed, 22 Apr 2026 11:29:42 -0300
remove links reference to weblate.taler.net
Diffstat:
4 files changed, 1 insertion(+), 159 deletions(-)
diff --git a/README b/README
@@ -167,139 +167,3 @@ If the page finally builds well, proceed with the following steps:
11. Review the results before deploying the new web site, then publish it on the internet
-D. Internationalization:
-Weblate is used as Web-based platform for internationalization. Before registering new projects on Weblate,
-please read the development docs at https://docs.taler.net/developers-manual.html#internationalization
-for information on how to create projects, components, translations, and general settings.
-
-The original source text for translation stems from the *.html.j2 files in /template/ and from *.j2 files in /common/
-wherever text is in between the mark-up tags {% trans %} and {% endtrans %}.
-The command 'make' gathers all these strings from all HTML files and merges them into the file messages.pot in /locale/.
-The base language is English in our case.
-
-Weblate has to be set up as follows:
-
-1. Fill in the variables for the Weblate project in 'Settings' on https://weblate.taler.net/settings/gnu-taler/#basic
-
-At 'Basic'
-- Project name [the name of the project on the Weblate platform; here: GNU Taler]
-- Project website [here: https://taler.net/]
-- Mailing list [email address of the responsible for the translators' mailing list]
-- Translation instructions [here: Mailing list for translators: languages@taler.net]
-
-At 'Access'
-- Public
-
-At 'Workflow' activate:
-- Set "Language-Team" header
-- Use shared translation memory
-- Contribute to shared translation memory
-- Enable hooks: activated
-- Language aliases [left empty]
-Leave deactivated:
-- Enable reviews
-- Enable source reviews
-
-Go to https://weblate.taler.net/manage/ssh/
-scroll down to 'Add host key' and let Weblate integrate the SSH host key
-by entering into the form the domain name for the project's website (here: taler.net, 'Port' left empty).
-
-2. Add components on https://weblate.taler.net/settings/gnu-taler/#components
-'Components' is a synonym for the software project Weblate shall offer for collaborative translation,
- e.g. for the component 'Main web site' at https://weblate.taler.net/settings/gnu-taler/main-web-site/:
-
-At 'Basic'
-- Component name [e.g. 'Main web site']
-- Translation license - GNU General Public License v3.0 or Later
-- Contributor license agreement [left empty]
-- Source string bug reporting address [email address of the Weblate admin/"Superuser"]
-- Priority: Medium
-- Leave deactivated:
- - Restricted component
- - Share in projects
- - Use as a glossary
-
-At 'Translation'
-- Turn on suggestions
-- Allow translation propagation
-
-At 'Version control'
-- Version control system: Git
-- Repository branch: master
-- Repository push URL: git+ssh://git@git.taler.net/taler-www.git
-- Repository browser [left empty]
-- Push on commit: deactivated
-- Age of changes to commit: 24
-- Merge style: Rebase
-- Lock on error: activated
-
-At 'Commit messages'
-- Commit message when translating:
-Translated using Weblate ({{ language_name }})
-Currently translated at {{ stats.translated_percent }}% ({{ stats.translated }} of {{ stats.all }} strings)
-Translation: {{ project_name }}/{{ component_name }}
-Translate-URL: {{ url }}
-
-At 'Files'
-- File format: gettext PO file
-- Language filter: locale/*/LC_MESSAGES/messages.po
-- Language filter: ^[^.]+$
-- Source language: English
-- Monolingual translations / Monolingual base language file [left empty]
-- Edit base file: deactivated
-- Intermediate language file [left empty]
-- Template for new translations: locale/messages.pot
-- Adding new translation: Create new language file
-- Language code style: Default based on the file format
-
-3. For all components 'Edit base file' in the settings (in the tab 'Files') has to be turned off,
- because it is never a good idea to allow (anonymous) users to edit the base language file...
-4. In 'Settings', 'Repository push URL' should never be left empty.
-5. The messages.pot file in the local working tree /locale/ has to be pushed to Git.
- Then, click in Weblate the 'Manage' link, search for the tab 'Repository maintenance',
- then click on 'Update' or 'Pull'. Weblate pulls the base language strings.
-6. Create new components in Weblate (languages to translate to).
- Edit the strings in those components, preferably using the 'Zen' mode on Weblate (look for the pencil symbol to click!).
- Don't forget to save after every edit. Finish with clicking 'Commit'.
- Weblate automatically pushes to Git at a set time, e.g. every 24 hours. Manual pushes are allowed, too.
-7. For building the web pages on a local machine, pull the messages.po files for all languages via Git (# git pull) and type 'make'.
- Review the rendered pages.
-8. Changes in the base language (English) have to be done in the *.html.j2 files in /template/.
- After every update of these files, the messages.pot AND the respective messages.po files
- for any other language MUST be pushed to Git.
-9. Changes in any other language than the base language have to be edited with Weblate,
- then committed/pushed from Weblate to Git, and 'git pull'ed to a local machine where 'make' builds the web pages for reviewing.
-10. If the base language (English) did not need any changes, consequently
- NO message.po file in /locale/*/LC_MESSAGES/ needs to be pushed to Git,
- because Weblate serves already as the preferred tool for manipulating all the different message.po files.
-
-
-NB: As an alternative to Weblate, language strings still may be manually edited in the .po-files
- - using plain text editors or the poedit program if preferred.
- This requires a manual update in Weblate, though.
-
-If Weblate sends a message like "Missing commits in the Weblate repository"
- it needs a manual update of files from the Git repository.
- Weblate's own local repository obviously does not get your *.po files automatically.
- To solve this, click in Weblate the 'Manage' link, search for the tab 'Repository maintenance' and then click on 'Update'.
-
-Workaround for the 'lock' issue:
- Weblate locks translations automatically after two Weblate administrators pushed one after the other.
- To solve this issue, the successor admin has to unlock translations on Weblate and
- synchronize Weblate's repository and local repositories with the corresponding Git repository.
- This means downloading the language files from Weblate's local repository to the admin's machine:
- # git clone https://weblate.taler.net/git/gnu-taler/main-web-site/
- then copying the *.po files to the Git folder on the local machine, t.i.
- #: ~/taler-www
- pushing these files again to Git,
- finally clicking on 'Update' in Weblate so that it syncs all language files in Weblate's own repository.
-
-Translations components that are bound to a Git repository which is master branch (with ssh-based r/w access) have to denote
- the repository push URL with git+ssh://git@git.taler.net/taler-www.git
- which is the normal case while other components that share strings with other components like the Taler apps denote
- 'Source code repository' with weblate://project/component (e.g. weblate://gnu-taler/wallet-android)
- and 'Repository push URL' left blank.
- For every linked component, the path to 'Monolingual base language file' has to point to the respective file, e.g.
- Wallet Android: wallet/src/main/res/values/strings.xml
- Point-of-Sale Android: merchant-terminal/src/main/res/values/strings.xml
- Cashier Android: cashier/src/main/res/values/strings.xml
diff --git a/template/comingsoon.html.j2 b/template/comingsoon.html.j2
@@ -38,16 +38,6 @@
</p>
</div>
<div class="col-lg-4">
- <h3>Translate to French!</h3>
- <p>Help with French translations on <a href="https://weblate.taler.net/projects/gnu-taler/-/fr/" target="_blank" rel="noopener noreferrer">Taler's translation platform Weblate</a>.
- </p>
- </div>
- <div class="col-lg-4">
- <h3>Translate to Italian!</h3>
- <p>Help with Italian translations on <a href="https://weblate.taler.net/projects/gnu-taler/-/it/" target="_blank" rel="noopener noreferrer">Taler's translation platform Weblate</a>.
- </p>
- </div>
- <div class="col-lg-4">
<h3>Try Taler!</h3>
<p>Try it yourself with the <a href="https://demo.taler.net" target="_blank" rel="noopener noreferrer">interactive demo</a>!
</p>
diff --git a/template/development.html.j2 b/template/development.html.j2
@@ -44,18 +44,6 @@
</div>
<div class="col-lg-4 mb-4">
- <a href="https://weblate.taler.net/" target="_blank" rel="noopener noreferrer">
- <img src="{{ url('icons/noun-translate-5177522.svg') }}" height=60>
- <h3>{{ _("Internationalization")}}</h3>
- </a>
- {% trans %}
- By using <a href="https://weblate.taler.net/" target="_blank" rel="noopener noreferrer">Weblate</a>
- everyone in the community can contribute with translations to the web pages and the GNU Taler applications.
- Please register on the platform and wait for an invitation email to log in.
- {% endtrans %}
- </div>
-
- <div class="col-lg-4 mb-4">
<a href="https://git-www.taler.net/twister.git/" target="_blank" rel="noopener noreferrer">
<img src="{{ url('icons/noun-twister-2280690.svg') }}" height=60>
<h3>{{ _("Twister") }}</h3>
diff --git a/template/funding.html.j2 b/template/funding.html.j2
@@ -52,7 +52,7 @@
<br>
{% trans %}
We are grateful for translation support offered by the following organizations
- (and <a href="https://weblate.taler.net/stats/">all the volunteers</a>
+ (and all the volunteers
that are helping with the translation effort):
{% endtrans %}
<ul>
