Skip to content

Translations for built-in extensions are missing in remote mode #250579

@hyrious

Description

@hyrious
Contributor

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.100.3
  • OS Version: Darwin arm64 24.5.0

Steps to Reproduce:

  1. Switch the UI language to non-English, e.g. Chinese
  2. Connect to a remote server.
  3. Notice almost all UI elements are translated, except for those contributed by built-in extensions, e.g. The source control view.
vscode-remote-i18n-issue.mp4

(This reproduction video is captured by @BlackHole1.)

We have submitted a fix #249430.

Activity

lszomoru

lszomoru commented on Jun 4, 2025

@lszomoru
Member

@TylerLeonhardt, could you please take a look at this! Thanks!

added this to the Backlog milestone on Jun 11, 2025
added
bugIssue identified by VS Code Team member as probable bug
l10n-platformLocalization platform issues (not wrong translations)
on Jun 11, 2025

3 remaining items

added this to the June 2025 milestone on Jun 27, 2025
added
insiders-releasedPatch has been released in VS Code Insiders
and removed
unreleasedPatch has not yet been released in VS Code Insiders
on Jun 30, 2025
alexr00

alexr00 commented on Jul 2, 2025

@alexr00
Member

Looks like this is still happening:

Image

reopened this on Jul 2, 2025
hyrious

hyrious commented on Jul 3, 2025

@hyrious
ContributorAuthor

@alexr00 Try restart the code server because the clp folder must (will explain below) be generated on the second start of a fresh install.

The clp generation needs both nls.*.json (in the out folder) and languagepacks.json (in the user data folder) having correct content BEFORE server-main.js starting. We can see that languagepacks.json is only generated when you're switching languages from the front-end.

So here's the detailed steps to enable language packs in remote server:

  1. You have connected to a remote server and the UI language is switched to non-English. The 2 steps' order doesn't matter.
  2. Wait until languagepacks.json being generated. It should be quite fast since the progress happens on scanning extensions. For correctness you can check for some path like ~/.vscode-server-insiders/data/languagepacks.json depending on your remote type.
  3. Restart the server progress, use commands like killall code-server-insiders node. Then you can simply do reload window.
  4. Now the clp folder should be generated. For correctness you can check for paths like ~/.vscode-server-insiders/data/clp/{hash}.{lang}/ depending on your remote type.
BlackHole1

BlackHole1 commented on Jul 3, 2025

@BlackHole1
Contributor
Area.mp4
alexr00

alexr00 commented on Jul 3, 2025

@alexr00
Member

This does work after restarting the remote server. @TylerLeonhardt in case you want to consider this verified.

TylerLeonhardt

TylerLeonhardt commented on Jul 9, 2025

@TylerLeonhardt
Member

No I think we should handle this better. We should show a notification when we were unable to fetch the translations and offer a restart to apply the extension that was just installed.

It was suppose to work this way even before the most recent PR, but perhaps something else broke along the way

hyrious

hyrious commented on Jul 9, 2025

@hyrious
ContributorAuthor

In case it helps, the remote code server's setup & start is managed by the remote extensions (Remote SSH, Dev Containers, etc). Remote SSH does provide a command Kill VS Code Server on Host while Dev Containers do not have a way to kill the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugIssue identified by VS Code Team member as probable bugl10n-platformLocalization platform issues (not wrong translations)

Type

No type

Projects

No projects

Relationships

None yet

    Participants

    @TylerLeonhardt@lszomoru@hyrious@BlackHole1@alexr00

    Issue actions

      Translations for built-in extensions are missing in remote mode · Issue #250579 · microsoft/vscode