We should consider adding localization (l10n) support to our VS Code extension to make it easier to translate into multiple languages and provide a better experience for non-English users.
Reference Implementation
Microsoft provides an official example demonstrating how to implement localization in a VS Code extension:
🔗 https://github.com/microsoft/vscode-extension-samples/tree/main/l10n-sample
Notes
- We plan to display data from the compatibility tables, which currently include only English descriptions. This limitation should be taken into account when implementing localization — or we should consider adding localization support to the compatibility tables as well.
- The error messages provided by the linter are also available only in English.
- We could also consider using Crowdin to manage translations and streamline the localization workflow.
We should consider adding localization (l10n) support to our VS Code extension to make it easier to translate into multiple languages and provide a better experience for non-English users.
Reference Implementation
Microsoft provides an official example demonstrating how to implement localization in a VS Code extension:
🔗 https://github.com/microsoft/vscode-extension-samples/tree/main/l10n-sample
Notes