Import Localized Content

After editing the exported localization file to include translated text, you use the Localization import command to add the translated content to your Library. This process overwrites the text in the set of duplicate documents that you exported for localization with the translations contained in the imported file.

When importing for localization, you can select a single Microsoft Word or XLIFF localization file. The Developer reads the selected import file and identifies the documents to be replaced according to the Document IDs recorded during export. The replacement of source text by translated text within a document is then based on the translation unit IDs contained in the localization file. If no translation is provided for a particular translation unit, the source text is left unchanged.

In addition to adding the translated text to the imported documents, the import process also updates the Language property of each document to the target language selected during export. If the language of a document has changed since it was exported, you will not be prevented from continuing with the import process, but an informational message will be added to the activity log.

Tip: If the imported content includes topics for which role assignments were translated, you should update the master role list for the target language to include these roles. If no master role list exists for the target language, you should create a new master role list before importing the translated content.

A summary message appears if some of the documents you selected could not be processed. Clicking the View activity log link in the message displays a list of the results for each document.

Selecting Cancel during import stops processing after completion of the current document and displays a message with a link to a list of the documents that have already been imported. Click the View activity log link in the message to display a list of the results for each document.

Multi-user Considerations

For a document to be overwritten during import, it must be checked out. Therefore, before initiating the import process, you should ensure that any documents that must be overwritten are either checked out to you or checked in to the server. If you plan to import a localization file while offline, you must check out all such documents before going offline.

However, if a document that needs to be overwritten is not checked out and you are online, the Developer automatically checks the document out to you and replaces it with the corresponding document from the localization file. If the document cannot be checked out, for example, if it is open in another editor or checked out to another user, it is skipped. At the end of the process, a summary message appears with a link to an activity log. Clicking the View activity log link in the message displays a list of the documents that were checked out to you during the process and those that could not be checked out.

After you complete the import process, you should check in all affected documents to make them available to other authors and add the changes to the Developer's version control system. When you check in a translated document, its version number is incremented, reflecting the fact that its contents have changed.

It is recommended that you always manually check out all documents to be overwritten during import, to ensure that all documents are processed during import of localized content.

To import content for localization:

1. On the Tools menu, point to Import and choose Localization.
2. Click Browse and navigate to the translated file you want to import.
3. Click OK.

   The Developer processes the selected file, replacing the text in the original documents with the translated copy.

   If any errors occur, they are written to an activity log, and a Partial Import message box appears. You can click the View activity log link to view the results of the import or click OK to close the message box.