Different localization keys are used between Element Android and iOS plus Desktop version #8134
Labels
I18n
O-Frequent
Affects or can be seen by most users regularly or impacts most users' first experience
S-Major
Severely degrades major functionality or product features, with no satisfactory workaround
T-Defect
Something isn't working: bugs, crashes, hangs and other reported problems
X-Needs-ElementX
Issues which will be resolved by ElementX
Steps to reproduce
organize
,use bots
,favorite
, etc.Automatic suggestions
for each caseOutcome
What did you expect?
Automatic suggestions should suggest 100% match for the same sentences, based on British English (for iOS and Desktop).
In general, automatic suggestions greatly help volunteer translators (who mostly work on translation solely and are not organized as a team where you could check each other's work) keep localized strings consistent among the projects, which do not share the same localization database.
What happened instead?
Sometimes automatic suggestions do not return a 100% match suggestion for the same sentences, because suggestions are case sensitive and British English is used as the standard. This increases the chance of inconsistencies if localization keys are long, because translators have to check them carefully, looking for a very tiny difference.
Because of it, volunteers often translate the same keys of the projects in different strings, which should be able to be avoided if the same localization keys were used.
PRs for this issue:
Your phone model
No response
Operating system version
No response
Application version and app store
No response
Homeserver
No response
Will you send logs?
No
Are you willing to provide a PR?
Yes
The text was updated successfully, but these errors were encountered: