Clients and Unicode characters

If you create object names that use characters outside the 7-bit-ASCII character range, the nzsql command, the ODBC, JDBC, and OLE-DB drivers support the entering and display of those characters. On Windows systems, users must ensure that they have appropriate fonts that are loaded to support their character sets of choice.

Netezza Performance Server commands that display object names such as nzload, nzbackup, and nzsession can also display non-ASCII characters, but they must operate on a UTF-8 terminal or DOS window to display characters correctly.

For UNIX clients, make sure that the terminal window in which you run these nz commands uses a UTF-8 locale. The output in the terminal window might not align correctly.

Typically, Windows clients require two setup steps.

This procedure is a general recommendation that is based on common practices. If you encounter any difficulty with Windows client setup, see Microsoft Support to obtain the setup steps for your specific platform and fonts.

  1. Set the command prompt to use an appropriate True Type font that contains the required glyphs. To select a font:
    1. Select Start > Programs > Accessories.
    2. Right-click Command Prompt and then select Properties from the menu.
    3. Select the Font tab. In the Font list, the True Type fixed width font or fonts are controlled by the registry setting 
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Console\TrueTypeFont

      On a standard US system, the font is Lucida Console (which does not contain UTF-8 mapped glyphs for Kanji). On a Japanese system, the font is MS Gothic, which contains those glyphs.

  2. In a DOS command prompt window, change the code page to UTF-8 by entering the chcp 65001 command:

As an alternative to these DOS setup steps, the input/output from the DOS clients can be piped from/to nzconvert and converted to a local code page, such as 932 for Japanese.

On a Windows system, the fonts that you use for your display must meet the Microsoft requirements as outlined on the Support site at http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q247815.