This topic describes the limitations of device application localization.
- The screen title and menu of the Push Logs screen cannot change language (for example, Chinese) after selecting a new device language even though the value in the localization file itself has been changed.
- Some properties are not included in the localization file, so some characters that should be localized on a BlackBerry application, are not. For example:
- Mobile Application Object (MBO) package name in the Synchronize screen
- Synchronization Group name in the Synchronize screen
- Continue and No buttons in the Push Request screen
- Table header text (Time, Status) in Push Logs screen
- Save message in Logs setting screen
- Some client log menus in the Logs screen
- Some error messages are not localized
- In the Push Logs screen, when you delete the push logs, the pop-up message confirming the deletion is not localized.
- On BlackBerry device applications, you cannot change the language for the HTTP MDS server name in the Push Settings screen after selecting the device language, for example Chinese, even though the MDS server name property value (SettingsScreen.12.StockProperties.com.sybase.uep.bob.rim.PUSH_SETTINGS_SCREEN_HTTP_MDS_SERVER_NAME.value=localhost) has been changed in the localization properties file.
- On BlackBerry devices, for the date/time/datetime picker screen, there are no properties for the message in the pick screen in the localization properties file.
- Using the PIM action to perform a write event on , the localized value cannot be written correctly. Using the PIM action to perform a read event on , the localized value can be read only as English.