You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Same path, just switched `en` for `id`, `ja` & `pt`.
38
+
39
+
#### This repo
40
+
41
+
This repo contains all of the non-English locale files. It means you can clone and translate without all the infrastructure overhead of the pretty complex TypeScript-Website.
42
+
43
+
For example if you wanted to translate a new handbook page you would:
44
+
45
+
- Clone this repo (see above)
46
+
- Pull in the English files `yarn pull-en` (these will be gitignored)
47
+
- Find your english file: `docs/documentation/en/handbook-v2/Basics.md`
48
+
- Recreate the same folder path in your language: `docs/documentation/it/handbook-v2/Basics.md`
49
+
- Translate the file!
50
+
- Create a pull request to this repo
51
+
- Once merged, the translation will appear on the next website deploy
52
+
53
+
#### Language owners
54
+
55
+
When a new language is created, we ask for a few people to become language owners. These owners are able to merge pull requests to files in their language via [code-owner-self-merge](https://github.com/OSS-Docs-Tools/code-owner-self-merge) in a pull request. They will be pinged on PRs which affect them, you can see the flow in PRs like [this](https://github.com/microsoft/TypeScript-Website/pull/1478) or [this](https://github.com/microsoft/TypeScript-Website/pull/1458).
21
56
57
+
The TypeScript team generally only know English, and can answer clarifying questions if needed! For quick questions, you can use the `ts-website-translation` channel in the [TypeScript Discord](https://discord.gg/typescript).
0 commit comments