MULTILIZER - The Software Globalization Company
PRODUCTSCOMPANYPARTNERSSTOREFree TrialsSupportContact Us
Developer Zone

Databases

2. Table Localization

The basic principle of table localization is to isolate all of the localizable columns and create a new localizable table for each language. Localizable table can be either a clone or subset of the native table.

Clones of the native table
Each localized table will contain All of the data contained in the native with localized data instead of native.

Subsets of the native table
each localized table will contain ONLY the localized columns data plus as many extra columns as those contained in the primary index of the native table.

In both cases the localizable table MUST contain the localizable columns. The choice is dependent on the data your database contains.


Picture 1: Native "Dialogs" table with sample data.
 

Picture 2: Japanese "Dialogs_JA" table, subset of the native table with sample data.

If there is a large amount of data that need not be localized and maybe requiring large amount of storage (like blobs) then the obvious choice is to subset the translatable tables; in this way there is no unnecessary data cloning. If these are no issues to be concerned with then cloning the tables will work just the same.

Example SQL script to get dialog information in Japanese:

SELECT Dialogs.Dialog, Dialogs.Control,
  Dialogs.Property, Dialogs_JA.Value
FROM
Dialogs, Dialogs_JA
WHERE
Dialogs.Id = Dialogs_JA.Id;

<< Back | Index | Next >>

Localization Techniques
Field Localization
Table Localization
Row Localization
Database Cloning
Comparison Matrix