View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009236 | Taler | wallet (all platforms) | public | 2024-09-30 13:33 | 2025-05-10 02:11 |
| Reporter | Emmanuel | Assigned To | Stefan | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.13 | ||||
| Target Version | 1.0 | Fixed in Version | 1.0 | ||
| Summary | 0009236: The field "Objectif" in the creation order in French should be renamed | ||||
| Description | One needs to rename the field "Objectif" in the creation of a new order in the French version (tested in Android app). I would prefer something like "Objet de la transaction". And it should be mentioned in the "Brochure". Yours, Emmanuel | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Thanks, Emmanuel! This is exactly what I really like to see from co-workers in order to optimize strings. Recently, my suggestion to the wallet developers went into the same direction: The key ' send_peer_purpose' should be in English "Subject" instead of "Purpose"; I changed this in German to "Buchungsvermerk" recently. Now you come with "Objet de la transaction" for the same key variable. OK, will be done, also in the merchant brochure. Kind regards, S. | |
| @Emmanuel: You wrote you would prefer "Objet de la transaction". What about "référence de paiement"? Is it this expression you see in France when you make a wire transfer? | |
| @stefan : "référence de paiement" is really good. | |
| Hi Emmanuel, you are translating "Routing" with "Routage" and "Routing number." with "Numero de routage." for the Taler Merchant Backend. My proposition is "Code bancaire" in both cases. Are you consenting to this? | |
| Hi Emmanuel, I still need your reply to my question before this one ^^. Secondly, can we find a good expression in French for the English word "Request" on the main action button in the wallet app? In German, it is "Anfordern" and in French we have now "Demande". I think the French word is too weak for the purpose. The action here is to request e-money from another wallet, the main use case (besides peer-to-peer payments between friends and family members) is in shops where merchants push the button "Request" to generate an invoice with a QR code on the merchant's device that customers have to scan to immediately pay from their wallets. So what is it in French? "Revendication" would be my proposition. WDYT? And thirdly, please look at https://bugs.gnunet.org/view.php?id=9370#c23803 to which extent the French expression "Retrait" for "Withdrawal" is more suitable than "Buy" (e.g. eNetzBon or other tokens). | |
| For routing => routage, or "Code bancaire", it relies on the context. I think routage is clearly out of the scope of our primary users, So I like your proposition. Revendication => non. To my mind this word is now only used for its political sens. I agree that "demande" is too soft, but I can not think to any better word. I asked deepl how to translate "Request for a money transfer" and all the translations used "Demande". So ... | |
| @emmanuel, in case you discovered during the UX/usability tests at E-Seniors that some French wording has to be changed in the apps and/or in the merchant brochure, then please report here in this ticket. I will care for transferring and harmonising the strings across all files and repositories. Thank you in advance. | |
| Please mark this bug as resolved if the strings mentioned have been fixed! | |
| @emmanuel, in case you discovered during the UX/usability tests at E-Seniors that some French wording has to be changed in the apps and/or in the merchant brochure, then please report here in this ticket. I will care for transferring and harmonising the strings across all files and repositories. Thank you in advance. | |
| Stefan, that's not how a bug tracker works. Please resolve this bug if what was reported is addressed. Emmanuel can always open a new bug if there are more strings to be fixed. | |
| Closed. New ticket with similar content is https://bugs.gnunet.org/view.php?id=9616. | |
| This is done. Other strings to change in the French Taler merchant brochure are depending on https://bugs.gnunet.org/view.php?id=9616. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-09-30 13:33 | Emmanuel | New Issue | |
| 2024-09-30 13:33 | Emmanuel | File Added: 1727701672112.jpg | |
| 2024-10-07 07:59 | Christian Grothoff | Assigned To | => Stefan |
| 2024-10-07 07:59 | Christian Grothoff | Status | new => assigned |
| 2024-10-07 07:59 | Christian Grothoff | Target Version | => 1.0 |
| 2024-10-07 14:46 | Stefan | Note Added: 0023467 | |
| 2024-10-08 16:49 | Stefan | Note Added: 0023481 | |
| 2024-10-09 08:38 | Emmanuel | Note Added: 0023487 | |
| 2024-11-04 08:02 | Stefan | Note Added: 0023649 | |
| 2024-12-11 09:10 | Stefan | Note Added: 0023856 | |
| 2024-12-11 09:10 | Stefan | Assigned To | Stefan => Emmanuel |
| 2024-12-11 12:24 | Emmanuel | Note Added: 0023857 | |
| 2024-12-11 12:25 | Emmanuel | Assigned To | Emmanuel => Stefan |
| 2024-12-21 09:17 | Stefan | Note Added: 0023902 | |
| 2025-01-11 10:13 | Christian Grothoff | Note Added: 0023971 | |
| 2025-01-11 10:29 | Stefan | Note Added: 0023972 | |
| 2025-01-11 10:31 | Christian Grothoff | Note Added: 0023973 | |
| 2025-03-12 16:44 | Stefan | Note Added: 0024182 | |
| 2025-03-12 16:45 | Stefan | Status | assigned => informing |
| 2025-03-12 16:45 | Stefan | Resolution | open => fixed |
| 2025-03-12 16:45 | Stefan | Note Added: 0024183 | |
| 2025-03-28 12:11 | Christian Grothoff | Fixed in Version | => 1.0 |
| 2025-05-10 02:11 | Christian Grothoff | Status | informing => closed |