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

Include localized message files in the typescript npm package #13703

Closed
mhegazy opened this issue Jan 26, 2017 · 2 comments
Closed

Include localized message files in the typescript npm package #13703

mhegazy opened this issue Jan 26, 2017 · 2 comments
Assignees
Labels
Fixed A PR has been merged for this issue Infrastructure Issue relates to TypeScript team infrastructure Suggestion An idea for TypeScript VS Code Tracked There is a VS Code equivalent to this issue

Comments

@mhegazy
Copy link
Contributor

mhegazy commented Jan 26, 2017

In order to support microsoft/vscode#18634 (comment), we need to publish localized messages with the TS package.

@mhegazy mhegazy added Suggestion An idea for TypeScript Infrastructure Issue relates to TypeScript team infrastructure VS Code Tracked There is a VS Code equivalent to this issue labels Jan 26, 2017
@gcnew
Copy link
Contributor

gcnew commented Jan 27, 2017

What will the process be for contributing changes that add or touch existing messages? Who will translate them?

@mhegazy
Copy link
Contributor Author

mhegazy commented Jan 27, 2017

We already have translated messages that are shipped as part of VS. I will need to figure out the process of getting these into the main TS npm package..

@mhegazy mhegazy added this to the TypeScript 2.6 milestone Sep 22, 2017
@mhegazy mhegazy self-assigned this Sep 22, 2017
@mhegazy mhegazy added the Fixed A PR has been merged for this issue label Oct 3, 2017
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Fixed A PR has been merged for this issue Infrastructure Issue relates to TypeScript team infrastructure Suggestion An idea for TypeScript VS Code Tracked There is a VS Code equivalent to this issue
Projects
None yet
Development

No branches or pull requests

2 participants