On UNIX, iPlanet 6.0 Web Server decodes the EURO currency symbol (€) incorrectly when using the Internet Explorer escape function. As a result, the € symbol appears as a question mark (?) in various areas of the product.

On Windows, you may not create a procedure name with the micro sign (µ) character.

The following are known NLS issues on MVS:

• In Chart Titles, Chart Subtitles, and Chart Footnote, the \n created by a carriage return is not respected. Instead, the characters are wrapped on the same line.
• You cannot create a new Data Server application with NLS characters in its name.
• When an MVS WebFOCUS Reporting Server is configured for CP 1026 and is processing Turkish data that contains double quotation marks, it fails when comparing the value of HEX FC to 7F. This limitation is a result of the following:
  • The IBM MVS system uses HEX FC for the value of double quotation marks, and HEX 7F for the 'ü' character for a Turkish code page.
  • All other EBCDIC code pages except Turkish use HEX 7F for double quotation marks.
  • All EBCDIC WebFOCUS Reporting Servers expect HEX 7F for double quotation marks when processing data, regardless of the EBCDIC server code page.

  As an alternative, you must use an ASCII Hub Server that resides on the Windows or UNIX platform. This server cannot be an EBCDIC Hub Server.

• When the WebFOCUS Client is configured for the WFServlet on MVS, drilling down on an EXL2K report and passing an NLS parameter value yields a NO OUTPUT message. HTML and PDF outputs work correctly.

The following are known NLS issues on all platforms:

• There are problems with the WebFOCUS interfaces and tools listing application directory names and files that contain the BETA character. Information Builders recommends not using the BETA character in WebFOCUS Reporting Server application directory names and Master File names.
• Some NLS characters cannot be typed into WebFOCUS Reporting Server procedure names using international keyboards. This is a limitation of Sun Java VM.
• WebFOCUS uses extended Japanese double-byte characters by default. To take advantage of this feature, the end user browser encoding method must be set to use Shift JIS.

  If Auto-Select is used instead, extended DBCS will not display correctly within WebFOCUS and the parameter NLS_MS932 must be switched to OFF through the WebFOCUS Administration Console.

• If your browser is configured to use Sun JVM and you are using a German keyboard, when you attempt to type a Euro symbol using the Right-Alt + e combination, the Euro symbol will not display as expected. This is a limitation due to Sun JVM. To avoid this issue, use Microsoft VM.
• The following characters cannot be used in a field name or alias name on OS/400, MVS, and USS WebFOCUS Reporting Servers. They appear as a terminator $ sign (0x5B) in Master Files, Access Files, and StyleSheet files and cause unexpected results.

  Server Code Page	Character	Countries
  277	Å (Capital A with a ring above)	Denmark/Norway
  278	Å (Capital A with a ring above)	Finland/Sweden
  285	£ (Pound sign)	United Kingdom
  1026	Í (Capital I with a dot above)	Norway

The following are known Java limitations when using NLS:

• The Beta character (ß) and the Eszett German character (U+00DF) are not supported in synonym names.
• The Beta character (ß) is not supported in directory names.

While configuring the WebFOCUS Server for National Language Support using the WebFOCUS Reporting Server Console, you may see incorrect characters if the language configured is Baltic, Czech, Greek, Hebrew, Polish, Russian, or Turkish.

To correct this:

1. Copy wceng.lng to wclang.lng.

   where:

   lang

   Is a 3-character string for the language you select:

   • BAL – Baltic
   • CZE – Czech
   • GRE – Greek
   • HEB – Hebrew
   • POL – Polish
   • RUS – Russian
   • TUR – Turkish

2. Edit the following line in the wclang.lng file to the charset value for the language you want to use:

   1 = Windows-1252

   • If {LANG} is "BAL", set this line to "1 = Windows-1257" or "1 = iso-8859-4".
   • If {LANG} is "CZE", set this line to "1 = Windows-1250" or "1 = iso-8859-2".
   • If {LANG} is "GRE", set this line to "1 = Windows-1253" or "1 = iso-8859-7".
   • If {LANG} is "HEB", set this line to "1 = Windows-1255" or "1 = iso-8859-8".
   • If {LANG} is "POL", set this line to "1 = Windows-1250" or "1 = iso-8859-2".
   • If {LANG} is "RUS", set this line to "1 = Windows-1250" or "1 = iso-8859-2".
   • If {LANG} is "RUS", set this line to "1 = Windows-1251" or "1 = iso-8859-5".
3. Restart the server.

The following are known NLS issues related to WebFOCUS and ReportCaster installation and configuration:

• Support for Baltic code pages requires manual configuration of the WebFOCUS Reporting Server and WebFOCUS Client.
• The French Canadian WebFOCUS setup program calls an English version of the WebFOCUS Client program. However, this behavior does not affect the files installed.
• On a simplified Chinese version of Windows, the English ReportCaster Distribution Server installation freezes. As an alternative, select Regional Options in the Control Panel. Change your locale to something other than S-Chinese before running the installation.

The following are known NLS issues related to Managed Reporting:

• As of Version 7 Release 7.02, NLS characters in passwords cause Managed Reporting login failures after migrating to a Unicode configured environment. This is due to the passwords having been encrypted with the application server encoding of the environment being migrated from and then being decrypted with an application server encoding of UTF-8. A workaround is to change passwords without using NLS characters prior to the migration process. For post migration, change the application server encoding from UTF-8 to the original encoding of the migrated environment and change passwords using no NLS characters.

  Note: Users can login successfully when NLS characters in passwords are created post migration.

• In Domain Builder, Korean characters that start with 0xA0 become question marks after the browser is refreshed in domain name, report name, folder name, and so on. In order to view these characters correctly, you must use Sun j2re-1_4_1_06 or higher.
• Managed Reporting uses an encrypting method when saving procedures that contain NLS characters. However, the Import utility does not have a decoding method. As a result, the imported procedure retains the same name as when it was stored.
• You cannot use the beta NLS character (ß) in Domains and Standard Report names.
• NLS characters should be avoided when creating a profile and Help file for a Domain. Although there are no errors when using NLS characters, they will be converted to an alphabetical character to create the file name, and no NLS character will appear in Managed Reporting.

When the WebFOCUS Reporting Server is configured for code page 278 (Finnish/Swedish) and you edit and save a Master File using the Data Server component in Managed Reporting on z/OS, the terminator character ($) appears as an Angstrom character (Å).

The following are known NLS issues related to synonyms:

• When using the Create Synonym feature for remote server configuration through the WebFOCUS Reporting Server Console, do not begin a synonym name with a tilde (~) or hyphen (-). Use another character at the beginning of the name.

When customers use Japanese DBCS characters in certain input boxes, such as the Field name box in the WebFOCUS Field Creator dialog, the Parameter name box in the Selection Criteria tab, the Condition name box in the WebFOCUS Edit Condition dialog, or the Chart Title/Chart Subtitle/Chart Footnote boxes in the Graph Titles tab, the corresponding OK buttons, Add button, or Style Title/Subtitle/Footnote buttons may not be activated in Report Assistant on Japanese Windows XP platforms. This is due to limitations with JavaScript functions and Windows XP. As an alternative, input name values before expressions, or use the Left and Right arrow keys to move the cursor inside these input boxes.

The following are known NLS issues related to graphs:

• The Edit Graph option in Graph Assistant may not work when the Developer Studio language does not match the language of the Windows regional settings. There are three alternatives you can use to resolve this issue:
  1. Change the Regional Options Location to United States and restart the machine.
  2. Add or revise IBIJAVAPATH in your registry. Notice that language and country now appears in the first string, as shown in the following example.

     C:\j2sdk1.6.0_06\jre\bin\javaw -Duser.language=en -Duser.country=US
     -classpath
     C:\j2sdk1.6.0_06\jre\lib\rt.jar;
     C:\ibi\DevStudio77\ibi_html\javaassist

  3. Copy the language folder that corresponds to the regional settings from:

     \ibi\WebFOCUS77\ibi_html\javaassist\intl

     to:

     \ibi\DevStudio77\ibi_html\javaassist\intl

• In Graph Assistant, clicking Graph Titles under the Headings tab and then typing a single NLS character with the ALT+0+nnn combination in the Chart Title, Chart Subtitle, or Chart Footnote boxes, causes the buttons for Style Title, Style Subtitle, and Style Footnote to become grayed out. However, you can still click the buttons to apply styling to the charts.
• When customers use Japanese DBCS characters in certain input boxes, such as the Field name box in the WebFOCUS Field Creator dialog, the Parameter name box in the Selection Criteria tab, the Condition name box in the WebFOCUS Edit Condition Dialog, or the Chart Title/Chart Subtitle/Chart Footnote boxes in the Graph Titles tab, the corresponding OK buttons, Add button, or Style Title/Subtitle/Footnote buttons may not be activated in Graph Assistant on Japanese Windows XP platforms. This is due to limitations with JavaScript functions and Windows XP. As an alternative, input name values before expressions, or use the Left and Right arrow keys to move the cursor inside these input boxes.
• On a Unicode configuration, ACROSS field names with NLS characters are displayed as squares in SVG graphs. As a workaround, specify the following line at GRAPHSTYLE:

  setDefaultFontName("ArialUnicodeMS");

• When reentering Advanced Graph Assistant in Developer Studio, NLS fields are not displayed in X and Y buckets. Executing or viewing the procedure in an editor produces the correct results.

The following are known NLS issues related to Dashboard:

• Baltic characters do not display correctly in Content Block names. Use non-NLS characters for block names instead.
• On localized versions of Business Intelligence Dashboard, you may notice truncation in the left side of View Builder or Domain Trees in Public Views. You can correct this by moving the frame separator to view all links.

The following are known NLS issues related to Developer Studio:

• As of Version 7 Release 7, the Developer Studio Managed Reporting context menu has been fixed to not show the Run option to MR Administrators when the selected report (FEX) has the Run only as a Deferred report property selected. The context menu will continue to display the Run Deferred option so that users authorized to run reports can submit the report to be run deferred.
• The Euro symbol (€) appears as a question mark (?) in the display value of an Execute Tool Wizard parameter.
• When using OEM data, you can create a procedure and run it from Report Painter but not from the Window component. If you run the procedure from the Window component, you will receive the following message:

  FOC003: THE FIELDNAME IS NOT RECOGNIZED

The following are known NLS issues related to ReportCaster:

• Japanese double-byte tilde (~) and dash (-) characters appear as question marks (???) in the Subject, From, and Report Name fields in e-mails received from ReportCaster.
• The EURO currency symbol (€) appears as a question mark (?) in the following areas of ReportCaster:
  • Distribution List burst values
  • Task tab
  • ReportCaster User Migration
• If you are using ReportCaster with NLS, the bursted FTP file names created on disk do not match those in the index file. As a result, the distributed report is not viewable. As an alternative, create standard sequence file names with standard characters (such as, FILE01 and FILE02). These file names are referenced to a virtual field that is equal to a sequence number, which you must make the primary BY field of the report.
• NLS characters appear corrupt on report names when distributing reports to a zip file. However, the report output appears correctly.
• Symbols do not appear correctly in a log report. As an alternative, set the encoding method of the browser to Unicode.

The EURO currency symbol (€) appears as a question mark (?) in the e-mail message of a Two-Way Email template.

When using the Japanese user interface with browser encoding set to Unicode or EUC, JavaScript error messages may appear. As an alternative, set the browser encoding to Japanese Shift-JIS.