The GitHub connector from Locale allows you to select specific content repositories within your GitHub instance, and send them for translation. This aims to help automate content processing by the various entities with which you work, anything from a professional translation agency, a specific person with access to a translation management system (TMS), or even machine translation (MT). Our goal with this connector is to aid in enabling lightening fast translations for your projects with the dedicated resources you trust most.

1. The Login link for Locale.

2. The login link for your GitHub instance.

   1. Note: This is provided to you by your GitHub account manager, support team, or contact person. If you are unsure of this information, please contact your system administrator or your GitHub representative.

3. User login information for both your Locale instance, and your GitHub instance

   1. A trial account of Locale can also be taken for free by going to locale.to and selecting the “Get Started” button.

4. Top Tip 💡No GitHub users need to be created for Locale to access the repositories for translation.

To continue with this process, it’s necessary to have the GitHub connector added and configured between your GitHub and Locale instances. If you have not completed this step yet, please see our article on Locale: Adding the GitHub Connector to your workspace.

1. To create a project in Locale, start by logging into Locale (instructions can be found here: Locale: Accessing your Locale instance) and choosing the "add a project" button.

Open

2. Next select the repository and main branches from the drop down menus where you would like to send and receive content for translation.

   1. Note: If they are not shown, a link to Configure Access can be seen under the Repository dropdown, and the necessary changes can be made here.

Open

3. The next section allows for the configuration of formatting, as well as file path patterns.

4. Next, select the languages you would like to include for your project.

5. Depending on the language processing option you would like for this task, you can choose from the various Language Tool options. (In this case, the example below highlights simple machine translation (MT) but it is possible that different users may see different options.).

6. The final step is allowing Locale to prepare the content to be translated. This step will happen automatically where Locale will do an analysis on the content, and send it for translation via the MT engine of our choice.

7. Selecting the green “Push Content” button in the top right corner will display the analysis result to the user, and allow the content to be sent for machine translation (AI tab), as selected by our language tool settings.

8. Locale will ensure the content is sent for translation (In progress), processed correctly, and sent back to the GitHub instance. After this has been complete, the status for each language will change from “Incomplete” to “Completed” and the GitHub repository will be completely localized into the selected target languages.