Share this page

# Known issues for non-English languages

This section describes troubleshooting and known issues when working with non-English languages.

In this topic:

## Script and scenario names

The following known issues apply to script and scenario names:

- When recording COM, FTP, IMAP, SMTP, or POP3 protocols, the length of the script name is limited to 10 multi-byte characters (21 bytes).

- Non-English symbols in script names, and in paths to scripts, scenarios, results, or analysis sessions are not supported.

- The name and path of a scenario cannot contain multi-byte characters. It is also recommended to use English characters for argument and parameter names.
- The GWT DFE extension does not support non-English characters in its classpath.

Back to top

## Browser configuration

If, during recording, non-English characters in the script are displayed as escaped hexadecimal numbers (For example, the string becomes %DC%26), you can correct this by configuring your browser not to send URLs in UTF-8 encoding. In Internet Explorer, select Tools > Internet Options and click the Advanced tab. Clear the Always Send URLs as a UTF-8 option in the Browsing section.
For more information, use the web_sjis_to_euc_param function described in the Function Reference.

Back to top

## Jenkins reports

After running an OpenText Professional Performance Engineering job in Jenkins, the links to several reports, such as the Performance Report and Transaction Summary, may not be translated.

Back to top

## Protocol limitations

SMTP: If you work with the SMTP protocol through MS Outlook or Outlook Express, the Japanese text recorded in a Vuser script is not displayed correctly. However, the script records and replays correctly.

Back to top

## Content check in multilingual environments

Note the following when using content check in multilingual environments:

- This version supports content check rules in French, German, Spanish, and Italian. The correct language file should be installed according to the system locale.
- The suitable language file can also be copied from the installation disk here: ..\lrunner\MSI\setup\international\<lang>\dat\LrwiAedInstallation.xml to the product's dat directory.

Back to top

## Language packs

Note the following when working with language packs:

- While installing the language pack, a warning message may be displayed that the Launcher Process is in use.
  Workaround: Click Continue to resume the installation.
- If you are working with a language pack, it is recommended that you install it before running the product for the first time.
- Match Windows locale. Install the language pack that is appropriate for the Windows locale. For example, if you are installing the Russian language pack, the Windows locale must also be Russian.
- Framework Language Pack. The language pack of .NET Framework needs to be installed to show the localized strings.
- License Utility warnings. A License Utility dialog box may open when installing a language pack. It will not affect the installation. Close it, and continue installing the language pack.
- Recording functions. VuGen cannot record a Vuser script for certain protocols if the installation is on a Chinese operating system, and the installation path contains Chinese characters.
- Tutorial scripts. After the language pack installation, all sessions and scripts for the tutorial remain in English.
- Menus and toolbars. If you install a language pack after running OpenText Professional Performance Engineeringfor the first time, the menus and toolbars may not get translated.
  Workaround: Close the application and delete the HKEY_CURRENT_USER\Software\<Folder Name> folder from the registry, where <Folder Name> is the drive on which you installed the product.
  For example, if the product is installed on the C drive, the registry folder name would be HKEY_CURRENT_USER\Software\C. Restart the application.
- Report Templates in Analysis. If you install a language pack after running OpenText Professional Performance Engineering for the first time, the Report Templates in Analysis (Reports > Report Templates) may not get translated.
  Workaround: Close the application and copy the files from your installation package's \Reporting folder to the <installdir>\bin\dat\Reporting folder. Restart the application.
- OpenText Professional Performance Engineering fails to uninstall on a Chinese operating system if the installation path contains Chinese characters.

Back to top

## Non-localized installations on non-English language systems

Note the following when working with non-localized installations on non-English language operating systems:

- Language support. OpenText Professional Performance Engineering supports English and the native language of the machine's operating system. For example, if you are using Japanese Windows OS, you can work with the application in Japanese and in English.
- Installation path. The paths to the installation files, and for the product installation, can contain English characters only.
- .NET Framework 3.5 failure. Installing OpenText Professional Performance Engineering on a localized machine may result in a failure in the .NET Framework 3.5 installation process, and you will be asked to terminate the installation. This happens because the .NET 3.5 Framework installation attempts to download the Framework Language Pack but fails.
  Workaround: Terminate the installation according to the Installation wizard's instructions and invoke the installation again.
- Online Help. The search functionality may not function as expected for strings that contain Chinese/Japanese characters (except Japanese full-width Katakana).
  Workaround: Add a half-width space after each character in the search string.
- Japanese characters in Web - HTTP/HTML scripts. If you set the advanced recording option to specify the encoding of an application, and the application uses different character encoding for different pages, then the recording log or script may display invalid Japanese characters. This does not cause any errors in the script replay.
- Non-breaking spaces in web protocols for Far Eastern languages. A non-breaking space (such as &nbsp; &#160; &#xA0; `\xA0') cannot be represented in some Far Eastern locale character sets (in which it is considered a lead byte). Instead, non-breaking spaces are converted to regular spaces (such as ` `, `\x20'), both during script code generation and replay. This may cause replay problems, such as mismatches in length due to eliminating multiple regular spaces.
  Workaround: Remove/add space(s) from/to the script so the comparison succeeds or specify regular expressions to avoid the issue.
- Standalone installations. The installation interface of the VuGen and Analysis standalone versions are in English and not localized.
- rdp_type. The rdp_type function does not support native language characters for both record and replay.

- Word Completion. Word completion does not work when Windows is configured to use the Ctrl+Space combination. This is common when using a Chinese keyboard.
  Workaround: Select Complete word from the Edit menu. Advanced users can disable Ctrl+Space for Chinese keyboards, by setting the following registry keys:

  - `[HKEY_CURRENT_USER\Control Panel\Input Method\Hot Keys\00000010]
    "Key Modifiers"=hex:00,c0,00,00
    "Target IME"=hex:00,00,00,00
    "Virtual Key"=hex:ff,00,00,00`
  - `[HKEY_CURRENT_USER\Control Panel\Input Method\Hot Keys\00000070]
    "Key Modifiers"=hex:00,c0,00,00
    "Target IME"=hex:00,00,00,00
    "Virtual Key"=hex:ff,00,00,00`
- ODBC and Oracle-2 Tier protocols. When recording a script in VuGen using the ODBC or Oracle-2 Tier protocols, if you stop the recording while the AUT is still open, VuGen may crash.
  Workaround: Close VuGen and open the file <installdir>\dat\protocols\options\script\general.opt in a text editor.
  Comment out the following line by adding a semicolon at the beginning of the line: `Option=DumpProcesses` so it looks like this: `;Option=DumpProcesses`

- PDF reports. In Analysis, a PDF report may be generated with unreadable characters if it contains non-English characters.
  Workaround: Before you generate the PDF file, change the font in the Report Template that you are using:

  1. Select Reports > Report Templates.
  2. Select the template that you want to use.
  3. In the Detailed Report section, select the Format tab.
  4. For each UI element in the list, change the font to a font that supports the language in which the report is written.

Back to top

https://admhelp.microfocus.com Professional Performance Engineering,VuGen 8942
Tips to improve your search results... OpenText™ Professional Performance Engineering Help Center OpenText™ Professional Performance Engineering Help 25.1-25.3 All View Local Help Center View Online Help Center Version: