Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nls: certain localizations are not always applied #12517

Closed
vince-fugnitto opened this issue May 10, 2023 · 1 comment · Fixed by #12555
Closed

nls: certain localizations are not always applied #12517

vince-fugnitto opened this issue May 10, 2023 · 1 comment · Fixed by #12555
Labels
localization issues related to localization/internalization/nls vscode issues related to VSCode compatibility

Comments

@vince-fugnitto
Copy link
Member

Bug Description:

There seems to be a regression where certain localizations are not applied.
I've noticed the following but there might be others:

export const CANCEL = nls.localizeByDefault('Cancel');

label: nls.localizeByDefault('New Terminal'),

Steps to Reproduce:

  1. start the application
  2. use configure language display to change language besides english (ex: french)
  3. confirm that the two user-facing strings are not localized
@vince-fugnitto vince-fugnitto added vscode issues related to VSCode compatibility localization issues related to localization/internalization/nls labels May 10, 2023
@msujew
Copy link
Member

msujew commented May 11, 2023

@vince-fugnitto It's likely due to the fact that the vscode version was bumped without me updating our nls.metadata.json file. VSCode language packs and this json files need to stay in sync to actually work as expected.

I'm currently on a longer vacation. But I'll be back on the 22nd and could take care of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
localization issues related to localization/internalization/nls vscode issues related to VSCode compatibility
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants