Tracking: Internationalization and localization

[kevinramharak]

This issue serves as a central hub for tracking all requests and discussions about support for internationalization and localization (I18n & L10n).

Goals

• Track progress on implementing internationalization and localization.

Reported issues

• 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

Related PR's

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

Notable Fork's

• https://github.com/ShiGongZhi/pretty-ts-errors (Chinese)

Resources

• VSCode API on Localization
• VSCode example repo on Localization
• TypeScript all diagnostic messages in JSON format
• TypeScript localization files for those diagnostic messages
• VSCode Language Packs Repo

[kevinramharak]

After some digging it seems TypeScript uses these scripts to use the diagnostics.json and the locale files to generate two big files, one typescript file and one json file:

• https://github.com/microsoft/TypeScript/blob/d3be7e171bf3149fe93c3ce5a85280f1eba3ef8d/scripts/generateLocalizedDiagnosticMessages.mjs
• https://github.com/microsoft/TypeScript/blob/d3be7e171bf3149fe93c3ce5a85280f1eba3ef8d/src/compiler/utilitiesPublic.ts#L687-L704
• https://github.com/microsoft/TypeScript/blob/d3be7e171bf3149fe93c3ce5a85280f1eba3ef8d/scripts/processDiagnosticMessages.mjs

Those are then used in the code to support diagnostics for each language.
I think we can safely use those files as a reference for how to map our own transforms correctly.
Maybe some (semi) automation to pull those files, and use error codes as indexes will keep it clean and prevent us from duplicating all of their diagnostics.

More reading material if you really like l10n:

• https://datatracker.ietf.org/doc/html/rfc4646
• https://learn.microsoft.com/en-us/windows/win32/intl/locale-names?redirectedfrom=MSDN