Soluling home Document home
Use this sheet to set options for the database. This sheet is part of the source dialog and Project Wizard.
A database source contains one database table node for each table of the database that has been selected to be localized. This value specifies how data of database table nodes are shown on the project tree. Possible values are:
|Flat||The table node contains all items. There are no sub-nodes except the table contains structural data such as XML or HTML.|
|By fields||The table node contains one field node for each field that has been selected to be localized. The field node contains all items of that field. Select this if you want to view data mostly by fields.|
|By rows||The table node contains a one-row node for each row of the table. The row node contains all the items of that row. Select this if you want to view data mostly by rows.|
|By groups||The table node contains one group node for each group of composite id (.i.e. id that contains two or more fields). The group node contains all the items of that grow. Select this if you want to view data mostly by groups. If the table does not contain composite id, then this behaves like By rows.|
Changing the value will make the application to restructure the project file. This may take some time if the project file is large. Read more about database structure.
Specifies other database options.
Check Use case sensitive context if the database uses case insensitive collation.
Specifies if and how translations from the original file are imported to the project. Possible values are:
|Never||Do not import any value from the file to the project *)|
|Import a translation if there is no current value and the translation is not the same as original
||Import value only if the current value in the project is empty, and the import value is not the same as the original value.|
|Import a translation if there is no current value||Import value only if the current value in the project is empty.|
|Import a translation and overwrite the possible existing value in the project
||Import value always even if the current value is not empty, and even if it is different than the imported value.
Note! This might overwrite the current values in the project with the values in the original file or database.
*) When you initially create a project, existing translations (if any) will be imported no matter what is the value of the above setting. These settings are only used when performing the second or later scan. This is visible only if the original file or database is multilingual.
Specifies how to format language ids used in xml:lang attributes. Possible values are:
|Standard: la[-Ssss][-CC]||Standard language id that contains an ISO 639-1 language id (la) and optional script id (Ssss) and/or ISO-3166 country id (CC).|
|Legacy: la[-CC]||Legacy language id that contains an ISO 639-1 language id (la) and an optional ISO-3166 country id (CC). If the id uses the secondary script of the language (e.g., Traditional Chinese), then the country id is required.|
|Underline: ll[_CC]||As above, but separator character is underline, "_", instead of the hyphen, "-".|
It is recommended to use the default language ids (either Use the same format as in the original file or Standard). Use other formats only if your files are consumed by a system that requires legacy ids.
Specifies the case of the language attributes that are used in the file. Possible values are:
|Standard (la-CC)||The language part is written in lower case. The optional country part is written in the upper case. For example, en-US is for English in the United States. This is the default value.|
|Lower (la-cc)||Both language and country parts are written in lower case. For example en-us|
|Upper (LL-CC)||Both language and country parts are written in upper case. For example EN-US|
Specifies when the script part is included in the language id. This is visible when language id format is set to Standard. Possible values are:
|Standard||Script id is included if it is absolutely needed to make id unambiguous. For example, English is
|On multiple scripts||Script id is included if the language can use more than one script. For example, English is
|Always||Script id is always included. For example, English is
Specifies when the script part is included in the language id. This is visible when language id format is set to Legacy or Underline. Possible values are:
|No||A country id is not added if not implicational given. For example, English is
|Yes||A country id is included if the language has more than one possible script. For example, English is