Lokalise for Translation

Lokalise provides tools to automate, integrate, and better manage the translation process.

Platform content that supports our automated API integration with Lokalise:

• Course session content (resources, menu-items, forms, polls, quizzes)
• Course catalog content and application forms
• Track catalog content and application forms
• Profile forms
• Post-registration forms

The general workflow is:

1. Send the platform content to Lokalise (REQUIRED)
2. Order translation of the content in Lokalise (REQUIRED)
3. QA and mark the final translations as "Verified" in Lokalise (OPTIONAL)
4. Mark the final translations as "Reviewed" in Lokalise (REQUIRED), which automatically triggers importing of the final translations back into the TechChange platform

See below for step-by-step instructions on how to do so. Note that Step 1 will be different depending on the type of platform content to send to Lokalise, but Steps 2-4 will be the same after that.

1a. Send the Course content to Lokalise

1. From the Admin Portal, select the Settings -> Translation menu item
2. Choose a specific course as the Base Source
   1. The Base Language will automatically update for you to match the selected course
3. Choose the Target Languages for translation
4. If needed, choose the advanced options settings
   1. Include previous translations -> If you previously translated this course content on the TechChange platform, enable this setting to also send the pre-existing data in the target languages to Lokalise.
   2. Replace modified content -> If you're re-sending course content that is already present in Lokalise, enable this setting to replace it with the most recent data.
5. Click the Send button to upload the course content to Lokalise
6. Click on the project link to open the Lokalise page for the course content

This includes:

• The course catalog content
• The course application form
• The resources, menu-items, forms, polls, and quizzes for each session of the course

Once the content has been sent to Lokalise, you'll be able to find it under a project named [TITLE]:product:[ID], where TITLE and ID are from the course on the TechChange platform:

1b. Send the Track content to Lokalise

1. From the Admin Portal, select the Settings -> Translation menu item
2. Choose a specific track as the Base Source
   1. The Base Language will automatically update for you to match the selected track
3. Choose the Target Languages for translation
4. If needed, choose the advanced options settings
   1. Include previous translations -> If you previously translated this track content on the TechChange platform, enable this setting to also send the pre-existing data in the target languages to Lokalise.
   2. Replace modified content -> If you're re-sending track content that is already present in Lokalise, enable this setting to replace it with the most recent data.
5. Click the Send button to upload the track content to Lokalise
6. Click on the project link to open the Lokalise page for the track content

This includes:

• The track catalog content
• The track application form

Once the content has been sent to Lokalise, you'll be able to find it under a project named [TITLE]:product:[ID], where TITLE and ID are from the track on the TechChange platform:

1c. Send the Profile Form or Post-Registration Form to Lokalise

1. From the Admin Portal, select the Settings -> Translation menu item.
2. Choose a specific form as the Base Source.
   1. The Base Language will automatically update for you.
3. Choose the Target Languages for translation.
4. If needed, choose the advanced options settings
   1. Include previous translations -> If you previously translated this form content on the TechChange platform, enable this setting to also send the pre-existing data in the target languages to Lokalise.
   2. Replace modified content -> If you're re-sending form content that is already present in Lokalise, enable this setting to replace it with the most recent data.
5. Click the Send button to upload the form content to Lokalise
6. Click on the project link to open the Lokalise page for the form content

Once the content has been sent to Lokalise, you'll be able to find it under a project named [TITLE]:organization:[ID], where TITLE and ID are from the organization on the TechChange platform:

2. Order translation of content inside Lokalise

1. Navigate to the project in Lokalise
2. Select the keys to translate using the Filter dropdown and the checkboxes on the left-side of the page
   1. You should probably filter the keys to only include the Untranslated results
3. A blue popup menu should open in the bottom-left corner of the page, choose the Order translation... action and click the Proceed button
4. A confirmation modal should open, click the Confirm button to continue
5. Fill out the Translation order form
   1. Choose the Translation provider, ranked from most expensive to least expensive:
      1. Lokalise -> Uses native professional human translators. Translations in over 90 languages are available. They offer 4 different services: translation, review, bilingual editing, and proofreading.
      2. Gengo -> Uses a network of over 18,000 human translators, which are based around the world and in every timezone. Translations in over 35 languages are available. They offer 2 different services: native speaker and professional translator.
      3. Google -> Uses machine translation (MT). Translations are available in over 100 languages. Final translations should be checked to ensure that they sound native and fit the required context.
      4. DeepL -> Uses machine translation (MT). Translations are available in 24 languages. The result can sound more native than some other MT options. You may want to regularly go back and forth between DeepL and Google MT to see which option better suits your needs.
   2. Choose the Source language, which most likely will be the base language for the content
   3. Choose the Target languages
   4. Choose the Service and other settings related to the selected Translation provider
      1. If using machine translation (MT), we recommend "marking target translations as unverified"
6. Verify the languages, total cost, and estimated delivery time in the Order summary section
7. Confirm billing and credit card information in the Checkout modal, click the Pay $x.xx button

3. Verify the final translations inside Lokalise

Lokalise offers a number of features related to quality assurance (QA) and verification.

If you're not doing the QA and verification yourself, then you'll need to invite others to contribute to the project.

1. Navigate to the project in Lokalise
2. Click on the Contributors tab in the navigation menu
3. Click the Add contributor button at the top of the Contributors list
4. Fill out the Invite new user form
   1. Enter their email addresses in the Add via e-mail input
   2. Choose their Role
      1. We recommend selecting the Translator option, as this will give them the ability to modify the final translations and then mark it as "verified" when they're done
   3. Choose their Editable languages, i.e. what final translations they can modify
   4. Choose their Readable languages
      1. We recommend including all of the editable languages, as well as the base language
5. Click the Add project contributor button to invite them to the Lokalise project
6. Verify the details for the new contributor in the Contributors list

The new contributor should receive an email inviting them to join the Lokalise project.

Once they accept the email invite and create a new Lokalise account, they'll be able to navigate to the Lokalise project, and start QA of the final translations.

There are 2 different ways to mark the final translations for the keys as "verified", either one-at-a-time or in bulk.

1. To mark a single key as "verified", click the Mark as Verified icon button.

1. To mark multiple keys as "verified" in bulk, select the keys using the Filter dropdown and the checkboxes on the left-side of the page
2. A blue popup menu should open in the bottom-left corner of the page, choose the Unverified: set/unset... action and click the Unset button
3. A confirmation modal for "Mark X keys as verified?" should open, click the Confirm button to continue
4. A green success alert should popup saying "X translations were set as verified"

4. Review the final translations inside Lokalise

In order to import the final translations back into the TechChange platform, you'll need to mark them as "reviewed".

As soon as you mark the final translations as "reviewed" inside Lokalise, it'll automatically be imported back into the TechChange platform. Depending on the size of the final translations, the import can take up to a few minutes to process.

There are 2 different ways to mark the final translations for the keys as "reviewed", either one-at-a-time or in bulk.

1. To mark a single key as "reviewed", click the Mark as Reviewed icon button.

1. To mark multiple keys as "reviewed" in bulk, select the keys using the Filter dropdown and the checkboxes on the left-side of the page
2. A blue popup menu should open in the bottom-left corner of the page, choose the Review: set/unset... action and click the Set button
3. A confirmation modal for "Mark X keys as reviewed?" should open, click the Confirm button to continue
4. A green success alert should popup saying "X keys reviewed"

Learn More

• Lokalise offers a free suite of on-demand courses at Lokalise Academy related to how to plan, manage, and deliver localization projects
• Lokalise offers a playlist of YouTube videos at Lokalise Tutorials related to their various features

Translation Memory (TM)

• https://docs.lokalise.com/en/articles/1409589-translation-memory

Lokalise offers a powerful built-in translation memory that's shared across all team projects and members. Anything entered in the editor or uploaded by you or your team is automatically saved to the translation memory for future use.

For instance, once a translator completes translating a key from English to French, Lokalise automatically saves this translation to the TM.

By default, each project within a team shares the same translation memory, but this can be adjusted as needed. Admins have the flexibility to create and assign as many memory storages as necessary.

When sending TechChange platform content to Lokalise, we'll automatically pre-translate the data using the TM. For each piece of content, Lokalise searches for a matching entry in the TM. If a 100% match is found, the corresponding translation will be automatically populated for the piece of content, as long as it doesn’t already have a translation.

If you remove a piece of content, the TM will be unaffected. All entries will remain intact. It is only updated when translations are created or edited.

Translation Glossary

• https://lokalise.com/blog/localization-glossary/
• https://docs.lokalise.com/en/articles/1400629-glossary

The Lokalise glossary helps maintain consistency across project translations. Any contributor can add terms to the project glossary. When a term from the glossary is used in the source language translation, it will automatically appear in the editor's inline suggestion box.

Machine translation engines (i.e. Google-Translate or DeepL) do not take the glossary into account. However, Lokalise AI translations will use your glossary entries when applicable.

If you’re creating a professional, human translation order, glossary entries won’t be shared with translators if you choose Gengo as the provider. To ensure translators see glossary entries or translation memory suggestions, please choose Lokalise as the provider.

The glossary is meant for reference, and there’s no option to automatically apply it to translations, without using the Lokalise AI.

You can share the glossary to make it available for other projects within the same Lokalise team.