Dynamic locale support

The Datacap Recognition Engines use locale variables to validate language and regional settings such as currency, numbers, and date data types. You can use dynamic locale support to set different locale variables on the nodes of your application that use different languages.

The value of the locale variable is inherited by to all of the child nodes of the batch object. Unless a different locale value is assigned to a child node. Then, all of the child nodes of that object inherit the new locale value. For example, if you add a locale value to a Document, that locale value is also assigned to the Pages and fields in that Document. If you then set a different locale value to a Page in the Document, that new value is also assigned to the fields in that Page.

You can set the locale variable for document processing by the application at the system level, the application level, or the node level in the application.

By default, the Windows Regional and Language locale is used system wide for all validations that are done during recognition. Unless the locale variable is set differently elsewhere.

For applications that use different languages, you can set the locale variable at the application level in the Datacap Application Manager. This setting is used on the batch object and is inherited down to of the all child nodes in the batch object. Setting the locale variable on the application level overrides the Windows Regional and Language setting.

If your applications run workflows, documents, pages, or fields that use different languages, you can set the locale variable at any node level in the DCO. Setting the locale variable on these levels overrides the locale value in Datacap Application Manager.

All of the standard actions, including the Recognition Engine, use the Locale property setting for the node to which the action is bound. The action property setting dynamically overrides the locale values that are set at the system, application, or batch object levels. For example, if the rrSet(en-US,@P.hr_locale) action is bound on the Page node. That node and its child nodes use the setting for English US (en-US) locale. Regardless of the locale that is set on the application level or in the Batch or Document level of the DCO.