Exporting Texts for Translation

Start TranslationTool.exe.

(The Manual button opens this book if present in the .. \manuals folder.)

Select Export texts for translation.

Select the desired database type: MS SQL or ORACLE.

Click Next.

Select the texts you want to export by activating the corresponding check boxes:

Designer Texts: Exports texts from the CRM.designer database, see Texts in the Aurea CRM web Administrator Guide.
Text Table: Exports texts from the Text info area (04), see Text Info Area.
Catalogs: Exports variable catalog values, see Catalogs.

Select the Output Format: CSV (Excel) or XML (Passolo), see Contents of the Export File.

Enter the path and file name in the Target File field or browse to the desired location.

Click Next.

Enter the Connection String(s) for the Aurea CRM and/or CRM.designer database(s) using the following syntax:

for MS SQL databases: Server=[name];Database=[name];UID=[login];PWD=[password]
for Oracle databases: Data Source=[name];user id=[login];password=[password]

Enter the Table Prefix for the Aurea CRM database if applicable.

Click Check Connection(s).

Check Save settings to save the connection settings for later use.

Click Next.

Depending on the specified database connection(s) the following languages are listed in the language selection fields:

languages defined in the Aurea CRM win database (Language info area (00))
languages defined in the CRM.designer database with a CRM Sub-Language, see Languages in the Aurea CRM web Administrator Guide.

If both Aurea CRM and CRM.designer texts are to be translated, only languages defined in both databases are listed. (Text Table Base Language always lists all languages as defined in Aurea CRM win.) The language number in the Aurea CRM database (Language No. field in the Language info area) must be entered as the CRM Sub-Language in CRM.designer.

Specify the desired Languages settings:

Note: The source and target languages may not be the same.

Catalog translations: The catalog base language cannot be selected as the target language.

Target Language: Select the target language.
When exporting to CSV, you can select multiple target languages. For each language a separate row is output to the CSV. Thus you can create translations to multiple languages in a single export and import.
Text Table Base Language: This language is used to determine the number of untranslated records in the Text info area (04). By default, the catalog base language is selected.
In addition to the languages defined in the Aurea CRM win database, the list contains a "Language-independent" entry with Language No. '0' (for counting the Language-independent entries in the Text info area), see Displaying and Editing Texts.
Additional Languages (CSV): When exporting to CSV, select the source language here. You can select additional languages to be exported, e g. if you are using an extra "language" to document texts and catalog values.

The following options only apply when exporting to XML:

Text Table Add. Lang. (XML): When exporting the text table to XML, select an additional language here. This language's text is written to the AdditionalInfo attribute. It can give translators more information about the usage of the text.
Source Language (XML): When exporting to XML, select the source language here.
Passolo Source/Target Language (XML): Select the matching SDL Passolo languages.
Generate glossary file for Passolo (XML): Enable this check box to create a Passolo-compliant glossary file in addition to the export file. The glossary file allows you to reuse translated strings. It contains all existing translations as "language pairs" in the source and target languages.

If you chose to export CRM.designer texts, specify the desired Designer settings:

Designer texts per verticals: Select the desired vertical(s).
Configurations to Export: Select the configurations from which texts are to be exported.
All available CRM.designer configurations are displayed with their names and IDs. The UPDATE* configurations are listed as well. Although texts from these default configurations may be exported (e. g. to create a glossary), they cannot be imported.
Truncate Texts/Meaning at Character: Use these options to truncate the strings to be exported (default=250 characters).
By default, all text fields and the Meaning field have a length of 1024 characters. Exporting the Default Text plus one additional language plus Meaning would result in a row width of 6K. The Truncate options enable you to set a row width below the 8K database limit.

The Truncate Texts option affects the following fields: Default Text, Text and texts in additional languages.

The Truncate Meaning option affects the Meaning field.

Specify Further Options:

Database-independent: Enable this check box if you plan to import the translated texts into another database. This option affects the match-up method used when importing, see Match-up.
In addition, the XML output is created with database-independent IDs, see ID Creation (XML).

Note: If you use the Database-independent option when exporting you have to enable this option when importing the file as well, see Importing Translated Texts.

Only export texts with translations: Enable this check box to export translated texts only (e.g. to change texts in a sub-language that are already translated in a parent language). If this check box is enabled
- Only export texts without translations is disabled automatically
- Text Table Base Language is disabled automatically
Only export texts with translations works as follows:
- If text table items are exported, only texts containing a text table entry for the target language are exported. The "DefaultText" column contains the language-independent text. If no language-independent text exists, it contains the same text as the Text column, see Contents of the Export File.
- If catalog values or texts from CRM.designer are exported, only texts where a translation exists for the target language are exported.
If Only export texts with translations is disabled all texts are exported.
Only export texts without translations: Enable this check box to export untranslated texts only. If this check box is disabled all texts are exported.
Only export used text table entries: Enable this check box to export only text table entries that are used in the current installation and are therefore referenced in one of the following files: mm_dbstr.txt and mm_fixcatno_custom.txt, see mmba.exe Parameters. If you use the --CheckRights parameter you can create these files for only those items for which the current user has access rights.
The texts exported to the glossary are not affected by this option.
Exclude text table entries used for online field help: Enable this check box to exclude text table entries that are linked to field help records (FH) from the export.
Export field help in Usage column: This option is only available when exporting text table records. Enable this check box to export field help for texts used by a field in the data model. The field help is written to the "Usage" column. If multiple field help records are found, the first one is output.
This option requires an mm_dbstr.txt file in the .. \system\db folder.

The field help is exported in the Text Table Base Language. If no field help exists for this language, the Target Language is used. If no field help exists for this language, the Additional Languages are searched and the first one containing field help is used.
Exclude locked catalog entries: This option is only available when exporting catalog values. Enable this check box to exclude locked catalog values from the export. If this option is enabled, values with Lock set for the catalog value in the language to export and/or the catalog base language are not exported.

Click Next.

Click Start Export.

The texts are exported to a file according to the specified settings.

CRM.designer texts flagged as "Sealed" are not exported, see Editing Texts in the Aurea CRM web Administrator Guide.

Click Close to exit the application, or click Back to export texts for another target language. Make sure to specify a different name for the output file.