Follow

Understanding the translation screen

The translation screen is divided in 3 different sections.

  1. Shows the original strings and the search box.
  2. Shows the selected string, translation box and suggested translations for voting.
  3. Shows comments and glossary terms.

See below all three sections explained.

In section 1:

  1. You can double-check the language you’re translating, if you translate more than one. You can click here to switch to another language directly from the translation screen.
  2. You can check if you’re translating from all the files or from a specific file. If you want to change to a certain file, you can click here and select another one.
  3. This is the list of strings to translate. You can follow the order or select a specific string to translate (or change).
  4. You can use the search box to search for a specific string – this is especially useful if you’re looking for an incorrect translation that needs to be corrected on the app. The search finds words in the original strings (in English) and also the ones in the translations (in the selected language).
  5. If you see this icon to the right of a string, that means it has one or more comments on it. You can see comments in section 3.

 

In section 2:

  1. You can double-check the string you’re translating.
  2. You can see the context of the string (where it will be located in the app), and also the file (if you’re translating from all files, this could be useful).
  3. This text box is where you’ll type your translation suggestion. If this is already populated, that means there’s already a suggestion – pay attention to indicator number 7 (duplicate suggestions could lead to your removal from the project). If you like the translation, check number 8; if you don’t like it, you can suggest a different translation.
  4. That button copies the original string, so you can translate it by changing it piece by piece (especially useful when there are variable in the original string, which should not be changed).
  5. This button clears the translation field (deletes whatever is there).
  6. After you’ve typed your suggestion translation, click on the Save button. Saving a suggestion will automatically take you to the next string.
  7. This is where you can see all the already suggested translations. Pay attention to this before suggesting any new translations to avoid duplicates (suggesting the exact same translation could lead to your removal from the project).
  8. This is where votes are given (or approvals, depending on your level of access). If you like a translation, you can use the plus (+) button to vote it up. If there’s something wrong or it’s bad, you can click on the minus (-) button to vote it down. If there’s nothing wrong with a translation but you just don’t like it, be neutral and don’t vote it. You can read more about that here.

 

In section 3:

  1. Under this tab, you can see all comments left on a string. Those could be asking for more context from the Hornet team, or discussions between users to settle on the best translation for their language.
  2. Under this tab you can search Crowdin’s translation memory (TM) for Hornet. The translation memory contains translations that were suggested and approved before for the selected language, so they’re deemed good.
  3. Under this tab, you can search all the translation terms set for the selected language. Those set terms will also appear underlined in the strings on the translation section (you can hover you mouse over them to see the translation). You should always translate those terms as indicated.
  4. You can use this field to add a new comment to a string. You can also tag people using their Crowdin username. Your comment will be visible to all users with access to the project, so it should be written preferably in English. You can check the language of the user who left a comment at the bottom of it, next to the date/time.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk