Database Localization

Before localizing a database the data structure has to be designed to support localization. Database structure can follow one of these four different methods:

  1. Field Localization
  2. Table Localization
  3. Row Localization (also known as "Single Table Localization")
  4. Replace localization

For a single-file databases such as Microsoft Access or InterBase the fifth option is 5. database cloning.

See also the comparison matrix of different database localization techniques and the Database localization architecture document.

Localization Workflow with Multilizer

In all four database localization techniques the workflow is the same:

  1. Database administrator prepares the database structure to match the selected localization technique.  
  2. Multilizer project is created by connecting to the database, defining the used localization technique and selecting the localizable columns.  
  3. Multilizer scan the database and fetches the native values and optionally the translations that are already available in the database.  
  4. The translations are entered to Multilizer project by using standard procedures (using Translation Memory, importing glossaries, exchanging data with translators, entering translations manually, etc.).  
  5. By selecting from main menu [Project | Build Localized Items] Multilizer writes the translations straight to the database in correct places.

Multilizer Products that Support Database Localization

For localizing databases you need Database Scanner plug-in

Database Versions Tested with Multilizer

Database localization was tested in Multilizer with the following database versions.

  • Oracle 9i Enterprise
  • Oracle 8i Enterprise
  • IBM DB2
  • MySQL 5.1
  • MySQL 4.1 (with Connector/ODBC 3.51)
  • MySQL 4.0 (with Connector/ODBC 3.51)
  • MySQL 3.23 (with Connector/ODBC 3.51)
  • Microsoft SQL Server 7
  • Microsoft SQL Server 2000
  • Microsoft Access 2000
  • Microsoft Access 2002
  • InterBase 6.0
  • InterBase 6.5
  • InterBase 7.0