|
memoQ is able to import TMX (Translation Memory Exchange) file contents into term bases. Choose a term base to import the TMX file contents into, browse for a TMX file to import: The Term base TMX import settings dialog appears. memoQ attempts to set the values automatically. However, you might need to check them before proceeding with the import.
Note: You can assign the existing languages of the term base to the source and target entries of the TMX file as needed, and you can also process custom metadata fields that exist both in the TMX file and in your translation memory. 
Invoking Navigate to the Term bases pane of the Resource console. Or, in an open project, click the Term bases icon in Project home. In both cases, a list of term bases appears. You will also see a list of term bases in the fourth page of the New memoQ project wizard. Select the term base you want to import the TMX file into, click the Import from CSV/TMX link, then, in the Open dialog, locate and select the TMX file to import.
The Term base TMX import settings dialog automatically appears after you specify the TMX file to import, and memoQ has finished analyzing the TMX file.
Structure The Term base TMX import settings dialog consists of the following areas:
| · | TMX information: Displays information about the TMX file.
|
| · | Languages: Assigns the existing languages of the term base to the source and target entries of the TMX file.
|
| · | Import options: Controls how memoQ should treat available or missing meta-information stored in the TMX file, and allows for limiting the number of importable entries.
|
Use General tab
|
TMX information area:
| · | Name: This field shows the name of the TMX file.
|
| · | Creation tool: This field shows the name of the program where the TMX file was created.
|
| · | Source language: This field shows the source language of the TMX file.
|
Languages area:
Different CAT tools may use different language codes, and export their entries in the TMX format using these language codes. For full compatibility, memoQ first analyzes the TMX file for language codes in the translation units. Then it attempts to match the languages found to the languages of your local term base. In some cases, there is no exact match because there are more than two languages (i.e. more than one target language) in the TMX file, or the sublanguages (locale codes) differ from those in your local term base. For example, your term base can use English (U.K.)-French, while the TMX file contains English (U.S.)-French translation units.
In memoQ, you can manually assign the language codes found in the TMX file to the existing languages of the local term base.
If the languages are not set correctly, use the language drop-down list to adjust the settings.
Note: If your term base is not set for a language that can be found in the TMX file, just select the term base in the Term bases pane of Project home or the Resource console, or in the Term bases dialog of the New memoQ project wizard, click the Properties link, and, in the Languages area, check the check box for the new language to add to the term base. Then click OK.
Import options area:
This area controls how memoQ treats available or missing meta-information stored in the TMX file, and allows for limiting the number of importable entries.
| · | Us
e domain, subject, author and date/time information in the TMX file: This check box is checked by default. Uncheck this check box to import only the source and target segments from the TMX file, without meta-information.
|
| · | Use the following values by default: Check this check box to automatically attribute specified values to the terms if the respective columns are not specified, or the corresponding fields are empty.
|
| · | Subject: Use this box to enter a value that will be automatically attributed to the terms if there is no such column specified, or the corresponding field is empty.
|
| · | Domain: Use this box to enter a value that will be automatically attributed to the terms if there is no such column specified, or the corresponding field is empty.
|
| · | Author: This box shows the value that will be automatically attributed to the terms if there is no such column specified, or the corresponding field is empty.
|
| · | Date: This box shows the value that will be automatically attributed to the terms if there is no such column specified, or the corresponding field is empty.
|
| · | Limit number of imported entries to: This check box is checked by default. Uncheck this check box to import any number of entries. If this check box is checked, memoQ will not import more entries from the TMX file than the number selected in the spin box next to this option. By default, this number is set to 1,000,000 (one million entries).
|
|
Custom field conflicts tab
|
If the TMX file contains custom meta-information fields in the form of <prop type=”name“>value</prop> elements, and your translation memory also contains the same custom fields, memoQ can read the values of these fields from the TMX file. It is possible that the fields in the TMX file and the same fields in the translation memory are not used in a compatible manner. In other words, the TMX fields can be in conflict with the custom fields in your translation memory.
On the Conflicts tab, you can address the following conflicts:
| · | Undefined properties: The TMX file contains a custom field that is not available in the translation memory. You have the following choices:
|
| · | Expand the definition and import as free text: If you click this radio button, memoQ adds the missing fields to the scheme of the translation memory, and imports the translation unit. The type of new custom fields will be Free text because memoQ cannot determine the data type from the values, and Free text is the most permissive option. This is the default setting.
|
| · | Ignore property and import translation unit: If you click this radio button, memoQ imports the translation unit, but it does not import the missing fields. This way you will have the contents of the TMX file, but you will lose some of the metadata.
|
| · | Skip translation unit: If you click this radio button, memoQ does not import translation units with fields that are missing from your translation memory.
|
| · | Undefined pick list values: The TMX file contains a custom field that is defined in the translation memory as a picklist value, but the actual value in the TMX file is not listed among the possible values in the TM. You have the following choices:
|
| · | Expand the definition: If you click this radio button, memoQ adds the value to the possible values of the custom field in the scheme of the translation memory, and imports the translation unit. This is the default setting.
|
| · | Ignore property and import translation unit: If you click this radio button, memoQ imports the translation unit, but it does not import the field with the undefined value. In the translation memory, the corresponding field either will not have a value, or it will have a default value as specified on the Default values tab of the Translation memory TMX import settings dialog. This way you will have the contents of the TMX file, but you will lose some of the metadata.
|
| · | Skip translation unit: If you click this radio button, memoQ does not import translation units where there is a field with an undefined picklist value.
|
| · | Properties of the wrong type: A custom field in the translation memory is a Date/time or a Number value, but the TMX file contains a text value or a malformed value for the same field. In this case, memoQ cannot import the value. You have the following choices:
|
| · | Ignore property and import translation unit: If you click this radio button, memoQ imports the translation unit, but it does not import the fields with the malformed value. This way you will have the contents of the TMX file, but you will lose some of the metadata.
|
| · | Skip translation unit: If you click this radio button, memoQ does not import translation units with fields that have the wrong data type.
|
|
Default values tab
|
The translation memory can contain custom fields that are not present in the TMX file you are importing. You can fill in these custom fields with default values. You can set these default values in the Default values tab of the Translation memory TMX import settings dialog.
| · | To add a default value: Choose a custom field from the Field drop-down list. This list displays all custom fields in your translation memory. Then, type or choose the value in the Value box. For picklist fields, memoQ displays the list of values. If you check the Override value from TMX file check box, memoQ will always use the default value during the import, no matter what values there are in the TMX file. After you choose the field and specify the default value, click Add.
|
| · | To remove a value: Select a custom field in the Custom fields list, and click Remove.
|
|
Navigation Click OK to proceed with importing the TMX file into the term base. Click Cancel to leave the dialog without importing the TMX file.
Term base TMX import settings
|