Database Localization

Localtransformer provides three different database localization types. Field Localization , Table Localization and Single Table Localization. Many databases are supported Microsoft Sql Server 2005 , Oracle , MySql , Microsoft Access etc..

Field Localization

In this database localization type for each field that is localized a different field is created ,one for each language. If for example the field that is localized is "Description" and we localize the database to German (de) and Spanish (es) then two new fields will be created in the table named "Description_de" and "Description_es". In order to get the localized data we could execute the following query :

SELECT 
Product_ID,Product_Name,Description_de as "Description"

FROM Products

Table Localization

In this database localization type for each language a new table is created that holds the localized data. If for example the field that is localized is "Description" of the table "Products" and we localize to German (de)and Spanish (es) then two new tables will be created. The tables "Products_de" and "Products_es" each containing the localized data. In order to get the localized data we could execute the following query :

SELECT 
Products.Product_ID,Products.Product_Name,Products_de.Description

FROM Products, Products_de

WHERE Products.Product_ID=Products_de.Product_ID

Single Table Localization

In this database localization type only one table is created for all languages together. Also another column called "Language" is created in the new table in order to identify the language of the row. If for example the field that is localized is "Description" of the table "Products" and we localize to German (de)and Spanish (es) then only one table will be created. The table "Products_localized" that contains the localized data. In order to get the localized data for the German (de) language we could execute the following query :

SELECT 
Description

FROM Products_localized

WHERE Language='de'

Localtransformer can localize ODBC Databases. If ,for example, we wanted to localize a Microsoft Access Database we would have to make the following steps.
At first, we would have to setup a DSN for our database. In Windows "Control Panel" we select "Administrative Tools" and then "Data Sources (ODBC)".

There we select the "System DSN" tab and we press the "Add" button. In the new screen that opens, we select the proper database driver. In this case "Microsoft Access Driver".

Afterwards, we type the "Data Source Name" and "Description". Then, we press the "Select" button and select the Microsoft Access database file. Finally, we press the "OK" button.

After having setup the driver we either create a new Localtransformer project or select "Add / Remove Target" in an existing Localtransformer project. There we press the "Add Database" button.

In the new screen we type the data source name ("StudentsDB") and the connection string of the database (in this case "dsn=STUDENTSDB"). Moreover, we press the "Test Connection" button. If everything is correct we will get a message "Connection Successful". If not, we would have to correct the connection properties.

Additionally, after we press the "Next" button, we would have to specify the database tables that should be localized.

Then, we will have to specify for each table that will get localized the table columns whose values should get localized.

Afterwards, we specify the primary key columns of the tables i.e. the columns that make the key of the table.

Then, we specify the database localization type. We can select between "Field Localization","Table Localization" and "Single Table Localization".

Then, after pressing the "Next" button the final screen is being shown with the summary for the database localization properties. In the end we press the "Finish" button and Localtransformer will then scan the database.