Skip to content

Conversation

@cassiano
Copy link
Contributor

Fixes #3711

Changes:

I have verified that this pull request:

  • has no linting errors (npm run lint)
  • has no test errors (npm run test)
  • is from a uniquely-named feature branch and is up to date with the develop branch.
  • is descriptively named and links to an issue number, i.e. Fixes #123
  • meets the standards outlined in the accessibility guidelines

@cassiano
Copy link
Contributor Author

cassiano commented Oct 29, 2025

@raclim, this is exactly the kind ot situation discussed in #3666, where a new feature (or bug fix) in introduced into the editor, bringing along with it new localization keys, which remain untranslated for all locales besides the default en-US until some user notices and manually translates it. My previous suggestion to use AI for this kind of situation, collecting eventual translation suggestions by end users afterwards (in the editor itself), would fully solve this problem.

@cassiano
Copy link
Contributor Author

BTW, I couldn't find a way to use the "rename variable" shortcut in my Macbook Pro. I have tried all kinds of Fn, Ctrl, Option and Command combinations with F2. Nothing worked.

…rtcuts-code-editing-rename-variable-locale-key
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add translation in pt-BR for KeyboardShortcuts.CodeEditing.RenameVariable locale key

1 participant