New Translation Memory

Use this dialog to create a new translation memory on a local or server database.

Name

Specifies the name of the translation memory. If you have multiple translation memories each one has to have a unique name.

Database

Specifies the database where translation memory exists. If the database does not yet contains the translation memory tables Soluling will add them. Supported databases are:

Database	Description
SQLite	This is the recommended database for translation memories if you are the only user of the translation memory.
SQL Server	Use this if you want that two or more users can access the same translation memory.
MySQL	As SQL Server but uses MySQL database.

Options

Specifies the creation options of the translation memory. Possible values are

Value	Description
Use segmentation	If checked (default), all strings that are added to the translation memory are segmented using the current segmentation rules. If unchecked strings, even very long ones containing multiple sentences, are stored as one item. For example, "I have a car. It is red." becomes two segments: "I have a car." and "It is red.". Both segments are stored in translation memory as individual items.
Reduce strings	If checked (default), leading and trailing white spaces, certain punctuation marks, and special characters are removed from the string. For example, " It is red. " becomes to "It is red". Learn more about reduced strings.

When processing strings, segmentation is done first, and string reduction is performed after that. Once translation memory is created, these options cannot be changed. If you want to maximize the usability of your translation memory, keep everything checked (default value).

String length

Specifies the maximum string length of the translation memory. Possible values are

Value	Description
Default	Translation memory uses the default string length that is the same as the maximum string length. This value depends on the database that is used to store the translation memory.
Custom	You can specify the string length. Use this if you want to optimize the database size of your translation memory. Note that SQLite uses dynamic string fields, so even if you use a long string field length, only the memory needed to store the actual string is allocated. So no memory is wasted.

If you use segmentation, the maximum string length is almost always enough to store all your strings.