Database Scanner
Overview. Database scanner options allow user to specify how Multilizer 2007 localizes database contents, such as tables in a SQL Server database for example. Connection to database is defined as a connection string, so the basic use is the same Microsoft Access and SQL Server for example.
Multilizer needs to connect to the database only when scanning, building, or specifying localization options. All other work can be done offline. So the localization work can be organized in a way that translator doesn't need connection to the database.
The most important settings are the following:
- Database; the connectionstring to the database.
- Destination of localization (Output tab); choose how to localize the database content.
- Import existing translations... (Input tab); allows importing of translations (if any) from the database.
Tabs
Tables and Fields
When there's a correct connectionstring, this tab shows the tables and fields of the database.
- Left pane shows all tables and fields containing text data of the database.
- Right pane shows the tables and fields that will be localized.
Encodings
Native language field lets you specify what's the language of the software being localized.
Default language is a fallback language; if there's no translation in target language, the text of default language is used instead.
Native encoding allows the user to specify, what's the encoding of the native strings. This field can be left empty.
Encodings list allows the user to specify the encoding of texts for localized applications. Here you can also define the resource id offset, which is used if output is multilingual application.
Input
This tab cotains only one checkbox; Import existing translations from database to project.
This option should be checked when creating a new localization project with Multilizer, so that any existing translations are added to Multilizer project. After this it is recommended that this checkbox is not checked, because Multilizer takes care of producing translations to the database.
Output
On this tab you define how to localize the database.
Destination of localization
- Replace original fields will overwrite existing content in database with the localized.
- Set in fields of localization. Translations will be written to fields that are specific for the target language. The fields must be created by the database administrator.
- Set in table of localization. Translations will be written to tables that are specific for the target language. The result will be a table that contains all the same data as orginal table, but texts are localized.
- Database cloning allows user to create a completely new database file for the localized information. The result will be a new database file with localized texts.