Internationalization and Localization (I18n & L10n)

[kevinramharak]

Internationalization and Localization (I18n & L10n)

This is the place to discuss the requested feature to support internationalization and localization.

Tracking Issue

The tracking issue is #144. Use that issue to post possible implementations and to track the technical implementation of the feature.

This discussion is the place to coordinate and brainstorm how to tackle this feature.

Summary

Good news, the #51 has been finished. This opens the road to discussing the implementation of the most requested features, including support for other languages.

Some research about how TS uses locale and maps its own diagnostic messages to the used locale is mentioned in #144.

We would appreciate your input and thoughts on what this feature should do, how it should work for the end user, and possible ways to implement it.

One current roadblock is the heavy reliance on regular expressions to parse the diagnostics that TypeScript provides. The current setup does not make it easy to implement and maintain multiple languages. Ideas on how to overhaul this that would allow for better and easier support of multiple languages would be very welcome.

Some of the issues that requested this feature before:

• Support more languages and locales #27
• After vscode installs the Chinese language pack, the syntax highlighting is incorrect #83
• In Vue and TS file, error no format， after i installed plugin #108
• Not work with Chinese language packs #128

Notable forks:

• https://github.com/ShiGongZhi/pretty-ts-errors (Chinese) [vscode marketplace]https://marketplace.visualstudio.com/items?itemName=SoulFriends.pretty-ts-errors-chinese)

Related PR's that tried to implement it:

• add support for chinese lang #33
• Supporting korean (and boilerplates for i18n) #49
• Partial support for other languages #110

[kevinramharak]

@JUSTIVE, @subframe7536, @sevenc-nanashi, @ShiGongZhi

I'm mentioning you in this discussion as you have previously shown interest in helping with implementing this features. Please feel free to follow or add to this discussion, and help us figure out how to support multiple languages in pretty-vs-errors.