Smart Construction Internationalization - Intergraph Smart Construction - 2019 (7.0) - Release Bulletin - Hexagon PPM

Intergraph Smart Construction Release Bulletin (2019)

PPMProduct
Intergraph Smart Construction
PPMCategory_custom
Release Bulletin
SPCVersion_custom
2019(7.0)
SPFVersion_custom
2019 (10.0)

Smart Construction supports heterogeneous environments. A heterogeneous environment uses elements from different (or multiple) locales. Examples of heterogeneous environments follow:

  • Entering or viewing Japanese data on a U.S./English operating system and changing input language (keyboard) dynamically, at any point, within one box in the user interface.

  • Using German Regional Settings (where a decimal is a comma) on a U.S./English operating system.

  • Using multiple languages in a project (especially when crossing language-group boundaries).

  • Changing the language of the user interface at any time, regardless of the system locale, by changing the regional settings.

  • Having multiple users access the same client and switch to their preferred language.

String properties, including but not limited to size (in some cases) and thickness, are not localized in Smart Construction.

A heterogeneous environment is flexible because it does not impose limitations on the use of languages or cultural conventions of a user.

The initial release of Smart Construction OnSite supports native language and culture for data with English - United States (en-US) labels, date and number formatting. Future releases will include a full heterogeneous user interface.

Configuration Requirements

You must take great care when configuring international and heterogeneous environments. The following configuration requirements exist for Smart Construction:

Smart Construction Configuration Requirements

  • Close Smart Construction client before changing Regional Options (such as numeric values, date and time formats, and so forth).

  • Close Smart Construction client before changing the user interface language.

Database Creation Configuration Requirements

  • Create Oracle databases using AL32UTF8 for the database character set and AL16UTF16 for the NLS character set.

  • Never modify the NLS_LANG registry entry on an Oracle client. Doing so prevents the character data from converting to Unicode.

  • Create Microsoft SQL Server databases with locale-specific collation settings and ensure that all databases have the same setting.

Questions and Assistance

For questions and assistance, please contact customer support.