Manually Translating Openspace Application Resource Bundles

You can manually translate the Openspace application resource bundles.

The location of the resource bundles are:
  • Openspace - There are several Openspace application plugins that contain resource bundles.
    • \CONFIG_HOME\tibcohost\adminenvironment-bpmenvironment-adminservername\data_n\host\plugins\com.tibco.openspace.login_n\resources\locale.
    • \CONFIG_HOME\tibcohost\adminenvironment-bpmenvironment-adminservername\data_n\host\plugins\com.tibco.openspace.login_n\resources\CalendarGadget\locale.
    • \CONFIG_HOME\tibcohost\adminenvironment-bpmenvironment-adminservername\data_n\host\plugins\com.tibco.openspace.login_n\resources\openform\locale
    • \CONFIG_HOME\tibcohost\adminenvironment-bpmenvironment-adminservername\data_n\host\plugins\com.tibco.os.data_n\resources\data\locale.
    • \CONFIG_HOME\tibcohost\adminenvironment-bpmenvironment-adminservername\data_n\host\plugins\com.tibco.bpm.casemanagement_n\resources\dataview\locale.
    • \CONFIG_HOME\tibcohost\adminenvironment-bpmenvironment-adminservername\data_n\host\plugins\com.tibco.os.org_n\resources\org\locale.
    • \CONFIG_HOME\tibcohost\adminenvironment-bpmenvironment-adminservername\data_n\host\plugins\com.tibco.openspace.adhoc.app_n\resources\adhoc\locale.
    • \CONFIG_HOME\tibcohost\adminenvironment-bpmenvironment-adminservername\data_n\host\plugins\com.tibco.os.businessservice.app_n\resources\bizapp\locale
  • Accessible Openspace - These are available in
    • \CONFIG_HOME\tibcohost\adminenvironment-bpmenvironment-adminservername\data_n\host\plugins\com.tibco.os.a11y.app_n\accessibility\locale.
    • \CONFIG_HOME\tibcohost\adminenvironment-bpmenvironment-adminservername\data_n\host\plugins\com.tibco.os.a11y.app_n\accessibility\webcomponent\locale.
  • MobileSpace - These are available in \CONFIG_HOME\tibcohost\adminenvironment-bpmenvironment-adminservername\data_n\host\plugins\com.tibco.openspace.login_n\resources\mobile\advanced\locale.

See Openspace Configuration Overview for information.

Procedure

  1. For each Openspace application, copy the base properties files. The base properties files are the files that do not have locale key already specified in the filename.
  2. Once you have translated them, you must:
    • Rename the files so that the file names now include the new locale key, see Locales Overview. For example, if you are translating from American English to Spanish, then LoggerMessages.properties must now be called LoggerMessages_es.properties. Properties files should be saved in UTF-8 encoding.
    • Copy the files back to their original location.
      Note:
      • All forms that you are using in your process must also be translated. For information on how to translate forms, see TIBCO Business Studio Forms User's Guide.
      • You cannot translate a default TIBCO form. You must create a custom form for all your steps and manually translate these. Once you have translated the TIBCO Forms, you must redeploy your application to BPM for the new language to take effect.
      • Openspace cannot translate any third party OpenSocial gadgets. If these gadgets are not available from the third party in the new language, they display in Openspace in their original language.
      • The Logger gadget enables you to quickly identify any words that are not translated in a locale pack. Specify the level of logging in the Logger gadget at INFO level, and an error displays if there are any words that are not translated. Words that are not translated default to American English. See "Adding gadgets to a Tab" in TIBCO Openspase User's Guide.
      • You can configure your Openspace Login page to use a different language using the ?locale query parameter. See "Adding a locale code" in TIBCO Openspace User's Guide.
      • See "Logging into Openspace" in the TIBCO Openspace User's Guide for information on selecting another language from the Openspace Login page.