Skip to main content

Internationalization Aspects

The internationalization of the MIMB bridge names, parameters, tooltips and messages is managed by XML files within [MIMB-INSTALL-DIR]\conf\MIRI18n\

The support for transferring internationalized (e.g. multi-byte character sets) through MIMB is achieved via the UTF8 encoding in the MIR neutral metamodel. The MIMB import and export bridges which cannot automatically detect the encodings of the tools, offer a parameter called "Encoding" allowing the user to specify one. There are however a few minor limitations:

  • API based bridges running on Windows, if the tool only works for the LOCALE encoding of the machine. In such case we only support the "English" API while the vendor may offer a different tool and therefore API for other languages. Such API based tools are very limited and include:
  • CA Gen (previously COOL:gen)
  • Java based bridges running on Windows, if the JDK installation path is not expressed in the LOCALE encoding of the machine (due to an outstanding long time bug in most popular JVM implementations). Such Java based bridges include:
  • IBM Cognos ReportNet Repository
  • IBM InfoSphere Data Architect (previously Rational Data Architect)
  • IBM Rational Software Architect
  • IBM WebSphere Metadata Server
  • Oracle Business Intelligence (previously Siebel Analytics) Enterprise Edition
  • Oracle Data Integrator
  • Oracle Warehouse Builder
  • SAP BusinessObjects Crystal Reports
  • SAP BusinessObjects Information Design Tool
  • SAP BusinessObjects Web Intelligence
  • SAP BusinessObjects Repository
  • SAP Business Warehouse
  • SAS Business Intelligence
  • Tableau
  • File based bridges reading or writing Unicode files in 16 bits fixed size encoding which is extremely rare.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!