Export Wizard - Options

Use this sheet to specify how and what part of the project data is exported to the export file.

Export scope

Specifies what part of project is exported. Possible options are:

Translation status

This group lets you include and exclude items based on their translation status. Strings having a status belonging to those statuses that have been checked will be exported to the file. All other will not be exported.

Row status

This group lets you include and exclude items based on their row status. Strings having a row status belonging to those statuses that have been checked will be exported to the file. All other will not be exported.

Data types

This group lets you include and exclude items based on their data types. Check those data types that you want to export.

Other

This group lets you include and exclude items based on other properties.

Do not Translate

You can filter items based on their Do not translate state. Possible values are:

Invalidated

You can filter items based on their Invalidated state. Possible values are:

Marked

You can filter items based on their Marked state. Possible values are:

Comments

Check Row comments if you want to include only those rows that have Row comment.

Check Translation comments if you want to include only those rows that has at least one translation comment.

Special

Specifies if duplicated strings are exported. Possible options are:

Languages

Select those languages that you want to be included to the exported file.

By default each item in the language list correspond to the language of the project. For example if you have English, German and Japanese in the project the language list contains these items. When exporting to TMX Sisulizer writes the language codes to the TMX file. Normally it is all right to use the language codes matching to the project languages. In our example it would be

<tuv xml:lang="en">
  <seg>Hello</seg>
</tuv>

Unfortunately some tools can not cope that well with country netural language codes (e.g. "en" vs. "en-US"). If the other tool that you use requires country part you can change the language code to be used by right clicking the Language list box and choosing Edit. The dialog lets you to define a language that is used when writing tuv elements of the TMX file. For example if you select English in our sample, right click and change the language to English (United States), Sisulizer will write your previous tuv element as

<tuv xml:lang="en-US">
  <seg>Hello</seg>
</tuv>

How new line and other special characters are escaped

Specifies the escape method how line feed, carriage return and other special characters are encoded.

Sort data

If checked the exported data is sorted by original string value.

Use alternative original values

If checked the alternative orginal values are used instead of actual original values whne exporting data. This is enabled only if you have set alternative original.