Importing the translated strings

step8.png

After you send out the XLIFF file to translators, they will return a translated file to you. The next step in the process is to import this file so that you can create new localized views or update previously translated views in your application.

When you import items, the status for items in the dictionary automatically changes from Ready to Translate to Ready for Review. For more information, see Reviewing-the-translations.

To import using the command-line interface, see Using-the-CLI-to-localize-your-application. When you import strings from the .xlf file, if the item ID does not exist in the l10n.db file, then the item is skipped. Additionally, new items found in the .xlf file are not added to the l10n.db. Therefore, you should use the same .xlf file that was exported from l10n.db file when importing the strings.

Related topics

Reviewing-the-translations

Using-the-CLI-to-localize-your-application

Extracting-the-strings-for-localization

To import the translated strings

  1. In Developer Studio, open the localization package definition.
  2. In the Localize section, click Import Strings.
  3. In the Localization Item Import dialog box, enter the path to the translated .xlf file.
  4. Select the state of the strings that you want to import.
  5. Click OK.

  6. If you have attachments that were translated, copy the translated files into the appropriate l10n folders.

    Warning

    Make sure that the file names match the file names in the folders; otherwise, those translations will not work.

    For more information, see Extracting-the-strings-for-localization.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*