Difference between revisions of "Strings In Database Documentation"

From Nexus Mods Wiki
Jump to: navigation, search
Line 6: Line 6:
  
 
While you work with the ''string'' table, all modifications made to it are automatically propagated to the ''string_localized'' table (by database trigger) with ''language_id = 0'' (''WHS'', another working language which used to be mostly Czech during the development of the main game). This could make it a little bit easier to finalize the texts for export.
 
While you work with the ''string'' table, all modifications made to it are automatically propagated to the ''string_localized'' table (by database trigger) with ''language_id = 0'' (''WHS'', another working language which used to be mostly Czech during the development of the main game). This could make it a little bit easier to finalize the texts for export.
 +
 +
= Working with string in '''DB Addin''' =
 +
 +
Working with strings in database is much more comfortable when using the [[DB_Addin_Documentation|DB Addin]]. Whenever you open a table that has some string property (column containing some ''string_name'' referencing a record in the ''string'' table), the addin automatically displays a column with the associated text (content of the string) next to it.

Revision as of 14:11, 29 January 2020

When some database table contains text that should be visible in the game (in any form), for example description of some item, the table itself stores only the id (string_name) of this string. The content (text) is stored separately in the table string. It is worth noting, that even this text is not the one used in the running game. The final versions of texts appearing in the game are exported from the string_localized table (with various language versions).

Exporting new strings

In order for a string to be exported to the game correctly, it has to have value in the string_localized table for language_id = 1 (PDG, which is sort of a working language) and language_id = 2 (ENG, which is the final English version).

While you work with the string table, all modifications made to it are automatically propagated to the string_localized table (by database trigger) with language_id = 0 (WHS, another working language which used to be mostly Czech during the development of the main game). This could make it a little bit easier to finalize the texts for export.

Working with string in DB Addin

Working with strings in database is much more comfortable when using the DB Addin. Whenever you open a table that has some string property (column containing some string_name referencing a record in the string table), the addin automatically displays a column with the associated text (content of the string) next to it.