Sync Strings #4775
Sync Strings #4775
Conversation
ElementBot
commented
May 26, 2025
ElementBot
commented
- Update Strings from Localazy
github-actions
bot
added
the
Z-Community-PR
| @@ -87,5 +87,6 @@ | |||
| <string name="screen_server_confirmation_message_login_matrix_dot_org">"Matrix est un réseau ouvert pour une communication sécurisée et décentralisée."</string> | |||
| <string name="screen_server_confirmation_message_register">"C’est ici que vos conversations seront enregistrées, comme vous le feriez avec un fournisseur de messagerie pour conserver vos e-mails."</string> | |||
| <string name="screen_server_confirmation_title_login">"Vous êtes sur le point de vous connecter à %1$s"</string> | |||
| <string name="screen_server_confirmation_title_picker_mode">"Choisissez un fournisseur du compte"</string> | |||
There was a problem hiding this comment.
FTR I have fixed a typo here in Localazy (du -> de)
|
@jmartinesp this is not the first time we have issue with plural translations in |
Do you think this is a problem in how Localazy processes the translations or is it coming from the original translations? I can't really make sense of what's its current state in Localazy. EDIT: when looking at the exported JSON files instead of XML this issue is still there and the UI shows no translations for the default values. Maybe these translations were automated using the localazy platform and something broke internally, or they were batch-uploaded somehow with the wrong values 🫤 . |
|
@Meddal sorry to ping you here, but it seems like the most direct way to get you notified about the issue with your submitted Welsh translations for the app. It looks like the tool you're probably using to upload these translations has some issue that send the translation keys as the values and viceversa for the plurals, like: "digits_entered": {
"%1$d nodau wedi eu cynnig": "zero", // Should be "zero": "%1$d nodau wedi eu cynnig" instead, same for the others
"%1$d nod wedi ei gynnig": "one",
"%1$d nod wedi eu cynnig": "other"
},The first translations you submitted were right, so maybe this bug started happening recently? |
