Sample Script Files: WorkingWithLanguages.mrs, JapaneseTables.mrs

These example scripts are based on the Museum sample data set. See Running the sample table scripts for information on running the example scripts.

If the metadata has been translated, you can choose to create the tables in any of the languages that are available. For example, the metadata in the Museum XML sample (museum.mdd) has been translated into Spanish and Japanese, so you can easily create tables in either of these languages.

You select the language to be used by setting the Document.Language property to the three-character code of the language you want to use. For example, to set the language to Spanish:

Element list syntax provides examples of setting up custom element labels for use in the current language and in more than one language. The following script creates two tables: the first uses the default labels defined in the metadata and the second uses custom element labels that are defined in two languages (English and Spanish):

You can also define custom labels for the variables. For example, the following defines a custom label in Spanish for the interest variable in the second table:

This example makes use of the dynamic property expansion feature of mrScriptBasic, which enables you to access the Interest item as if it were a property of the Side axis. You cannot use this feature with variables that have a period (.) in their name (for example, variables that are inside a grid or loop). For these variables you would specify the custom label like this:

If you do not specify the language code, the custom label applies to only to the currently selected language.

When you are working with foreign languages, make sure that you save your script file using the Unicode or UTF-8 text format option and not the ANSI option.

Here is the table that uses the default Spanish texts:

Here is the table that uses the Spanish texts defined in the script:

The default label (Base) that UNICOM Intelligence Reporter creates for the autobase element is suitable for use in Spanish. However, in some languages you might want to specify a translation. The following example sets the language to Japanese, sets up some tables and changes the text on the autobase elements:

Here is the second table: