Home

Angular 2 will be in continuous development and its documents will also be constantly updated to reflect the changes for the years to come. Therefore, unlike translating published articles where we can get the job done and leave it alone, we need to keep the localised documents up to date at all times. Obsolete documents can be misleading and the community deserves better.

We have used Git to solve the problem described above. Git is not only good for team collaborations, but also ideal to track changes even between two separate repositories. We forked a copy of angular.io and appended the translations right next to each of the corresponding paragraphs. We added the original repository as an additional remote/upstream path to our local repository/working directory. We then fetch and merge its master branch to our master branch regularly.

The above workflow has not only solved the sync problem, but also made the translation and review job much easier because the translation and original text are side by side. It has also enabled us to add a feature allowing readers to toggle between the translation and the original text, which has encouraged the community to join in and help us improving the quality of our localisation.

If you are familiar with Git, you can skip the “SourceTree workflow” section which are intended for beginners. You can also skip the “Fetch and merge updates from angular.io” section if someone else is handling it or you know how to do it. The following methods are by no means the best practices.