Known issues - Multilingual applications

Relevant for: GUI tests and components

This topic includes general limitations about multilingual issues in OpenText Functional Testing.

VMware

OpenText Functional Testing may behave unexpectedly when using multi-byte string inputs if it is installed on a VMware operating system.

Workaround: Set the hardware acceleration of the display driver to None. If this does not work, uninstall the VMware display adapter.

When using Chinese IME to record multiline objects:

Some mouse operations on the IME are recorded and are not executed during the run session.

Workaround: Avoid performing mouse operations on the IME window while recording.
Selecting a character from the IME Candidate window is not supported.

There may be cases during a run session when OpenText Functional Testing loses the focus of the application you are testing when working in a Korean, Chinese, or Japanese operating system. This may result in a loss of data during the run session.

Workaround: Run an Activate method on the application's window to ensure focus on the window before performing the next step. For example:
```
Window("Notepad").Activate
```
Running the Type method on computers with Japanese, Korean, or Chinese operating systems may not work as expected.

Workaround: Add an English input locale to the computer (using the Regional Options or Regional and Language Options in your Control Panel).
The Silent Test Runner does not support tests where file paths include non-English characters.

When using the Baidu Cloud OCR engine

Letter casing (upper case and lower case) is sometimes identified incorrectly, if the Language type configured in the text recognition options is Chinese and English.
Image size for text recognition:

The shortest side should be at least 15 pixels and the longest side should be at most 4096 pixels.

When using the Google Cloud OCR engine

Text from hieroglyphic languages, such as Chinese, Japanese, or Korean, is not recognized when it is on the same line as another language.
Image size for text recognition:

Should not exceed 20M pixels (length x width). Recommended size is 1024 x 768.

The image displayed when selecting View Sample Snapshot in the OpenText Functional Testing Asset Comparison tool is not localized.

Additionally, some user interface items are not localized.

Workaround: Install the relevant user interface language .NET Framework Language Pack. You can download it from the Microsoft download center.

Examples of interface items that are not localized include:

Tooltips in the Properties Pane
Tooltips and context menu in the editor of the File Content Checkpoint dialog box
Compilation information in the Output pane for an API Test
Context menu for the search box in the toolbar of the File Content Checkpoint Properties dialog box
Error messages when importing a WSDL Web service
The default value string for a Date parameter in the Add Input Parameter dialog box for an API test
Warning or error messages in the Test Batch Runner, for example, when saving files using the Save As command
Strings displayed when adding a date-type input parameter in the Properties pane of an API test
Some of the OpenText Functional Testing user interface related to XML operations
XML Validation results in the Run Results Viewer