View Issue Details

IDProjectCategoryView StatusLast Update
0008159Talerwallet-corepublic2024-07-01 14:20
ReporterStefan Assigned ToStefan  
PrioritynormalSeveritytextReproducibilityalways
Status assignedResolutionopen 
Product Version0.9.4 
Target Version1.0 
Summary0008159: Wallet UI: review of message texts [July]
DescriptionThis is an ongoing job to verify and harmonise strings between wallets (Android vs. iOS) and to get rid of duplications and bad translations, mainly by using .rst files, Weblate and wallet-core.
Involves MS, SK, CG verifies.
Pre-launch work task #25.
TagsNo tags attached.

Relationships

child of 0008160 assignedStefan Wallet UI: translation of UIs to DE/FR/IT 

Activities

Stefan

2024-06-11 18:51

developer   ~0022579

Communication with Javier and Sebastian after a couple of issues with Weblate. My recommmendations sent them via email:

In case #1 that the future translation is done within an XLIFF file itself (enriched by new translation strings through manual manipulation or through a script) we can manage internationalisation even without Weblate but use it as an external translation platform as well. In the other case (#2), if we want to use Weblate (which is preferable) we have to test out the XLIFF 1.2 file in Weblate with correct configs in the settings.

What I propose for case #2:

- set 'File format' to XLIFF 1.2 translation file
- change 'Source code repository' from https://git.taler.net/taler-ios.git/ to git+ssh://git@git.taler.net/taler-ios.git/
- set 'Repository Push URL' to git+ssh://git@git.taler.net/taler-ios.git/
- empty field 'Push branch' (was dev/sebasjm/testing_weblate)
- deactivate 'Push on commit' (this was activated for testing purposes I assume)
- change 'File mask' from TalerWallet1/Settings.bundle/en.lproj/Root.strings to TalerWallet1/Localizable.xcstrings
- empty field 'Monolingual base language file'
- deactivate 'Edit base file' (as this decides whether any users will be able to edit the base file for monolingual translations [which is a bad idea when others than Sebastian, Javier or Marc and me fill in or change strings directly in Weblate]).
- set translation license to GPL v3 on https://weblate.taler.net/settings/gnu-taler/taler-wallet-ios/ (which was empty before)
- change 'Adding new translation' from "Create new language file" to "Contact maintainers"

In case we deviate Weblate and work with a source file from taler-ios.git (case #1):
- disable "Manage strings" on https://weblate.taler.net/settings/gnu-taler/main-web-site/#translation (disables adding and removing strings straight from Weblate. If your strings are extracted from the source code or managed externally you probably want to keep it disabled)

Currently I am playing around a bit with the component's settings in Weblate. There are multiple issues with the settings up to now and I would dare to care about the correct configuration once Marc has set up his XLIFF translation file.

Issue History

Date Modified Username Field Change
2024-01-21 14:37 Stefan New Issue
2024-01-21 14:37 Stefan Status new => assigned
2024-01-21 14:37 Stefan Assigned To => Stefan
2024-01-21 15:41 Christian Grothoff Relationship added child of 0008160
2024-01-21 15:42 Christian Grothoff Severity minor => text
2024-02-11 12:53 Stefan Summary Wallet UI: review of message texts => Wallet UI: review of message texts [first half of May]
2024-02-11 12:53 Stefan Description Updated
2024-06-11 18:51 Stefan Note Added: 0022579
2024-06-11 19:02 Stefan Summary Wallet UI: review of message texts [first half of May] => Wallet UI: review of message texts [June]
2024-06-11 19:02 Stefan Description Updated
2024-07-01 14:20 Stefan Summary Wallet UI: review of message texts [June] => Wallet UI: review of message texts [July]