Maybe the translations have not made it in yet?

It is translated.
In fact, changing localize = nls.loadMessageBundle(__filename); to localize = nls.config(process.env.VSCODE_NLS_CONFIG)(__filename); in Microsoft VS Code\resources\app\extensions\git\out\commands.js will work.

I do not know secondary modules defined by vscode-nls, but I think it is the cause of the issue.
The issue is happening not only in the git extension but also in other built-in extensions.

Strangely this works for TS and other extensions. I don't know what Git does different here. Could be a problem with the tool that extracts the strings.

As far as I confirmed, the following is also no translated.(It's already in i18n folder)
Would you debug it?

• php (a portion)
• markdown (a portion)
• merge-confilict (insiders)

Also, if you don’t mind, could you tell me how to debug the Code-OSS including the display language function?

@EbXpJ6bp you can't since nls is a build time step to make dev time expierence easy. You can only debug this in a build version which you can produce using the gulp script vscode-win32-x64

@dbaeumer Thanks!

Apparently the issue was that message bundles were loaded before nls configuration was happening, thus defaulting to English locale.

https://github.com/Microsoft/vscode-nls indicates that

The config call configures the nls module and should only be called once in the applications entry point.

I fixed it for git, php, markdown and merge-conflict extensions.

FYI @joaomoreno @chrmarti @mjbvz

@Microsoft/vscode if you own any extension that is localized, please ensure that nls.config() is called before any other code in your extension, otherwise localization won't be working for you.

See ab3c945 for reference 🙂

@michelkaporin We're lucky extensions are built to CommonJS... AMD wouldn't make this easy.

@joaomoreno yeah, we would have to redesign all our localization logic...

@michelkaporin Should we replicate that change across all extensions or only for specific cases?

@chrmarti across all that use nls, but only for extension entrypoints.

@michelkaporin Thanks for looking into this.

Verified: