Scopes is a big topic and continues here with an emphasis on scope locales. As stated previously, the locale provides context-sensitive formatting and parsing of numbers and currencies and is a feature of every scope.

Locale Attributes

The "locale" attribute is a string representation of the locale and will consist of from 2 to 4 components each of which is also an attribute as applicable. The 4 locale components attributes are

1. language
2. region
3. script
4. variant

The first two of the above attributes are normally sufficient to fully specify a locale. To assign a particular locale to a scope, use properties in the scope declaration following the name to represent the locale. For example, (language="de", region="DE") specifies the standard German locale.

All the attributes of the current scope are available using a scope attribute expression which is a 2-part name with "scope" as the first part and the attribute name as the second part. For example, the current locale is scope.locale.

Note that a "country" attribute is provided as an alternative attribute expression to "region" as usually the two are synonymous.

show-locale.taq demonstrates scope attributes 'name', 'language', 'region' and "locale" for a scope named "luxemberg". The scope has nothing other than two locale properties. A second query is included which executes in the global scope. In this case, the locale will default according to system settings.

The result for query "locale_query1" is:

Scope Attributes

Note that script and variant are likely to be blank.

euro-total.taq shows two scope attributes used to customize an invoice for 3 different European locales so that the text and percentage tax charged are correct for the location where the query is being executed. Here is the body of the "charge_plus_tax" flow. Look for scope.region and scope.locale