You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing firstname.lastname@example.org.
We are experiencing playback issues from our video hosting provider. Please check back shortly.
4:32Introduction to Project Translation
3:12Import and Export Translations
2:03Session Wide Translation
Take topic challenge
Import and Export Translations
Learn how to use project translation import and export in order to move terms and translations in and out of the system.
Video recorded using: Ignition 7.9
Transcript(open in window)
[00:00] The ability to export and import terms and translations can be a crucial component to the translation of a large project. In this example we will see how that import and export works. Here we have a demo screen that has quite a bit of text on it, first thing we'll do is add all the terms on the screen to the translation manager. We'll do this by opening the translation panel, on the root container, and then selecting all the text and clicking mark for translation. This places all of the terms in the translation manager for translation at a later time. Back in the translation manager, we can see all of our terms. Now we can choose to export the terms to file. We'll click on the Export button and we're presented with the esport screen. This dialogue looks a little bit different than most standard save dialogues because there are several different formats for export and each format usually exports each language to its own file. First we'll select a base folder, and then we'll select a base file name. In this case we'll export both the English alternates and the Spanish translations. Although we don't have many translations to find, what we're really trying to export are the terms so that a translator can fill them in for us. For the format, for this example, we'll choose XML. Properties versus XML are both the standard properties file format of key-verses value but just in different coding mechanisms. XML is a little simpler because it supports BTFA directly. Once we export the terms, we can open the folder and see that the files have been written. Now, once the translator has provided values for our keys, we can come back to the translation manager and choose import. We'll browse to the location where our file is located. And we'll choose the language we want to import. When we select the file, we're presented with the opportunity to accept or reject the translations. So in other words, we don't have to overwrite all of the translations or all of the keys currently in the system. In this case, since we're starting off from a blank slate we will accept them all. But, in general, I could have selected just specific terms to translate. Also I'll want to verify that the language is correct. Once we're satisfied, we can select import all. The existing terms will be overwritten with the provided translations. Now if we come back to our screen and add a language selector, we can check all of the translations that were loaded. Switching to Spanish we see that all of our text has been translated.