Appendix A: Language Alternates

Intrado provides the ability to specify descriptions of items in multiple languages. This is accomplished by using the Language Alternates system. Appropriate language strings are automatically selected by the system when returning data to users based on the user’s LocaleID setting.

Multiple field language alternate records can be saved via one parameter. Each record is terminated with the sequence |^|. Fields within each record are delimited with |.|. The record field structure has the following format:

FieldLanguageAlternatesKey|.|Source|.|KeyVal|.|FieldNo|.|LocaleID|.|FieldText|.|Action|^|

Field	Type/Size	Comment
FieldLanguageAlternatesKey	Integer	Pass this value as zero (0).
Source	Integer	Table Source (as identified in the opcode documentation)
KeyVal	Integer	Object Key. Pass zero (0) for this parameter.
FieldNo	Integer	Field number that the text applies to (as identified in the opcode documentation)
LocaleID	Integer	Locale ID indicating the language of this string. (See Locale ID reference in the External User API documentation for a list of values)
FieldText	Varchar 2GB	The actual foreign language text.
Action	Varchar 10	Pass the literal string false for this parameter.

An example string containing Spanish language alternate values for an event grouping description and abstract would be:

0|.|28|.|0|.|1|.|1034|.|Búsqueda|.|false|^|0|.|28|.|0|.|2|.|1034|.|Esto es todo acerca de la búsqueda!|.|false|^|

Certain opcodes provide multiple parameters for specific field language alternates. This is only for convenience purposes. Field language sets can be passed in any of the language alternate parameters for any of the fields and can be intermixed.