Localization Tables

The project database has a series of tables that are used to support only localization procedures.

Since the program itself depends only on the values in the translatable tables (see Translatable Tables in the Project Database), these localization tables are always blank in the product's schema databases and sample databases.

The following summarizes the localization tables:

Table Title Purpose Primary Key
lang_lang Languages Validating list of languages supported by the Localization application (for example, French, Spanish). Add your own value if you add a language. Language
lang_files File Strings

List of translatable strings that appear in .axvw, .js, .xml (home page descriptors), or java files.

Each string remembers its file name and its ID, so that the same string can be translated differently in different contexts.

The ID typically includes the class name and the English value. For instance, “Spanish|ab-miniconsole.js|Ab.grid.MiniConsole|Filter” would have the translated value “Filtro”.

 Language, File Name, Constant or ID Value
lang_enum Enumeration Strings

List of enumerated values and translatable values.

This table has one entry for each unique enumeration list, so that if a particular list is repeated many times for different fields (for example, “0;No;1;Yes;”) it needs to be translated only once.

 Language, Enumerated Field Value
lang_strings Navigator and Table Strings List of translatable strings that appear in the translatable tables in the project database. See String Types. Language, English String, String Type
lang_glossary Glossary

Glossary of unique strings used in all tables, combined regardless of context.

This list is used to jump-start the localization of new languages. For instance, if “Building Code” is used in 112 different fields, you can translate them all once using the glossary.

 Language, English String

String Types

The following lists the string types from translatable tables: