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

Improve language pack authoring docs #1535

Open
okineadev opened this issue Jan 1, 2024 · 4 comments
Open

Improve language pack authoring docs #1535

okineadev opened this issue Jan 1, 2024 · 4 comments
Assignees
Labels
engineering feature-request Request for new features or functionality
Milestone

Comments

@okineadev
Copy link

  • VS Code Version: 1.86.0-insider
  • OS Version: Windows 11 (22H2)

I want to create a localization for vscode, I followed this guide - https://github.com/Microsoft/vscode-loc/wiki/How-to-create-language-pack-extension

Until I got to the section "Importing a translation to a language pack"

The following commands were written there:

npm run update-localization-extension {path_to_lang_pack_ext}
For example: npm run update-localization-extension -- --location ../vscodeloc/localization de

And at this point I got confused because I couldn't figure out how to specify the location correctly

Here is my file structure (in Codespaces):
Screenshot

@TylerLeonhardt
Copy link
Member

These steps are really old. I need to update them, sorry. I don't think it's very easy to make your own language pack extension right now without also creating a bunch of automation to ensure that you are keeping up-to-date

@TylerLeonhardt TylerLeonhardt transferred this issue from microsoft/vscode Jan 3, 2024
@TylerLeonhardt TylerLeonhardt changed the title Creating your own localization for vscode Improve language pack authoring docs Jan 3, 2024
@TylerLeonhardt TylerLeonhardt added engineering feature-request Request for new features or functionality labels Jan 3, 2024
@TylerLeonhardt TylerLeonhardt added this to the Backlog milestone Jan 3, 2024
@csigs
Copy link
Member

csigs commented Jan 3, 2024

Thank you for your feedback. We are currently reviewing it (reference 935153).

@okineadev
Copy link
Author

@TylerLeonhardt Ok, I'll wait until you fix the documentation. Good luck!

@okineadev
Copy link
Author

okineadev commented Jan 4, 2024

If anything, here I have described the output of the command - microsoft/vscode#201711

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engineering feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

4 participants