add a context note to AppShortcuts.strings explaining intentional phrasing variations #21252
Closed
fateh-bouyahiaoui
started this conversation in
Password Manager
Replies: 3 comments 1 reply
|
✨ Thank you for your code contribution proposal! While the Bitwarden team reviews your submission, we encourage you to check out our contribution guidelines. Please ensure that your code contribution includes a detailed description of what you would like to contribute, along with any relevant screenshots and links to existing feature requests. This information helps us gather feedback from the community and Bitwarden team members before you start writing code. To keep discussions focused, posts that do not include a proposal for a code contribution will be removed.
Thank you for contributing to Bitwarden! |
0 replies
|
Thank you @fateh-bouyahiaoui, I have passed the feedback on to the responsible team. |
1 reply
|
Closing this one out as it has been passed to the team. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Select Topic Area
✅ Code Contribution Proposal
Code Contribution Proposal
While localizing AppShortcuts.strings to Arabic, we noticed several different English phrasings used for what appears to be the same underlying action, for example:
"Open password generator", "Launch ... password creator", "Show the ... generator", "Access password maker", "Start ... password builder", "Load the password creator" — all seemingly pointing to the same Generator feature.
"Lock all ... accounts", "Secure every ... account", "Freeze every ... account", "Lock up all accounts in ...", "Activate full lock for ..." — multiple phrasings for what seems like the same lock action.
We initially assumed these were inconsistencies worth standardizing in the source — but suspect they're actually intentional, designed to widen Siri voice-command matching (so users can trigger the same shortcut using different natural phrasings).
If that's correct, would it be possible to add a short context note (e.g., as a Crowdin string context, or a code comment) along the lines of "Intentional phrasing variation for voice command matching — do not standardize across languages"?
This would save other language teams (across the 65+ supported languages) from the same investigation, and clarify whether per-language phrasing variation is expected/desired too, or whether it only matters for the English source.
Happy to help if useful!
All reactions