This repository contains files to build localized Language Pack extensions for Visual Studio Code. A Language Pack contains the localized string resources for a particular language.
Localized resource files are managed and edited in Microsoft Localization Community. Files will be exported to this repository when prepare the publishing of language pack.
Language pack extensions are published to the Visual Studio Code Marketplace
There are currently 14 "Core" languages for Visual Studio Code.
| Language | Visual Studio Code Language ID | MLCP Language Code |
|---|---|---|
| French | fr | French (fr-fr) |
| Italian | it | Italian (it-it) |
| German | de | German (de-de) |
| Spanish | es | Spanish (es-es) |
| Russian | ru | Russian (ru-ru) |
| Chinese (Simplified) | zh-cn | Chinese Simplified (zh-cn) |
| Chinese (Traditional) | zh-tw | Chinese Traditional (zh-tw) |
| Japanese | ja | Japanese (ja-jp) |
| Korean | ko | Korean (ko-kr) |
| Czech | cs | Czech (cs-CZ) |
| Portuguese (Brazil) | pt-br | Portuguese (Brazil) (pt-br) |
| Turkish | tr | Turkish (tr-tr) |
| Pseudo Language | qps-ploc | Pseudo (qps-ploc) |
If you want to give feedback or report issue, please create a new GitHub issue. Please check if a topic about your issue already exists!. Since translation strings are managed and edited in Microsoft Localization Platform. Change can only be made there. So pull request won't be accepted in vscode-loc repo except language pack readme.md.
Before we can accept your pull request you will need to sign a Contribution License Agreement. All you need to do is to submit a pull request, then the PR will get appropriately labelled (e.g. cla-required, cla-norequired, cla-signed, cla-already-signed). If you already signed the agreement we will continue with reviewing the PR, otherwise system will tell you how you can sign the CLA. Once you sign the CLA all future PR's will be labeled as cla-signed.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.