How Can We Help?
< Back
You are here:
Print

Overview

If you want to translate a project online, you may do so by using the Door43 Content Service.  Note that you will need to have a basic knowledge of Markdown or USFM formatting, depending on the project.

Step by Step

The following procedure assumes that you have a Door43 account, if you don’t, create one by going to https://git.door43.org/user/sign_up.

Before continuing, make sure that you are signed in to DCS by going to https://git.door43.org/user/login.

Fork the Project

A “fork” is simply a copy of someone’s project.

The first step is to find the project that you want to translate.  You can search for projects by name on the Explore page, https://git.door43.org/explore/repos.  For this guide, we’ll use the English translationWords project as our example.

  1. Go to the project page, for English Open Bible Stories, go to https://git.door43.org/Door43/en_tw
  2. Click on the “Fork” button in the upper right of the page.
  3. On the “New Repository Fork” page:
    1. Change the language code in the “Repository Name” field to match the language code you are translating into.  For example, if you are translating into Hindi, change the text to “hi_tw”. 
    2. You may update the “Description” field as well.  You can put anything in this box that helps describe your translation project.Click on the green Fork Repository button.
  4. You are now brought to a page that is your own copy of the project.  You can tell that it is a copy because there is a “fork” icon that is next to your username and the project name in the header, like below:

Start Your Translation

Now you are ready to start your translation work.  For example, to start translating the first translationWords article, follow this procedure:

  1. Verify you are on your fork on the project by looking at the username and project name in the header.
  2. Navigate to the first story by clicking on “bible” and then “kt” and then “abomination.md” (in this example, you would end up at https://git.door43.org/jag3773/hi_tw/src/master/bible/kt/abomination.md).
  3. Click the pencil icon that is part way down the screen, on the right.
  4. You are now in edit mode and you can start translating.
    1. Don’t change the formatting of the document.  For example, the hashtag marks (#) should not be modified.
    2. Don’t change the links that are in the parenthesis, but you may change the link titles that are in the brackets.  For example, “[sacrifice](../other/sacrifice.md)” may be translated to “[त्याग](../other/sacrifice.md)”.
    3. Don’t change the file or folder names.
  5. When you are finished editing, scroll to the bottom of the page and find the text boxes below the “Commit Changes” header.
  6. Put a title and description of your changes into the text boxes so that there is a record of your work.
  7. Leave the radio box selected that says “Commit directly to the master branch.” 
  8. Click on the green Commit Changes button.
  9. Repeat steps 2-7 as many times as you need to translate all the content.
Table of Contents