-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
[Bug]: The built-in language plug-in is invalid #6688
Comments
dingzhouL
added
bug
Something isn't working
triage
This issue needs to be triaged by a maintainer
labels
Feb 26, 2024
I think this is a duplicate of #4735 Basically, when a language pack is installed, VS Code generates a language bundle, but unfortunately there is a bug and this only happens when you install from the UI. We do patch language stuff here in code-server, so I am not sure if this is our bug or something upstream. More investigation will be required. |
Thank you very much for answering my question. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
OS/Web Information
code-server --version
: V4.19.1Steps to Reproduce
docker run -d name code-server -e PASSWORD=111111 [image-id]
command;3.Access the browser.
Expected
I packed the plugin
Language pack extension for Chinese (Simplified)
into it, but did not get thezh-cn
option throughConfigure Display Language
.This seems strange, but when I installed other language packs in the plugin market, the
zh-cn
option appeared.Actual
How do I change the default language option to
zh-cn
with the built-in plugin?In addition, when I switch the language to
zh-cn
, the current language in the configuration is stillen
, which is just a display problem and does not affect the user's use.Logs
No response
Screenshot/Video
No response
Does this issue happen in VS Code or GitHub Codespaces?
Are you accessing code-server over a secure context?
Notes
This problem does not occur by manually installing the language pack.
The text was updated successfully, but these errors were encountered: