Verity Locales 6.0 must be installed into an existing installation of Verity K2, Verity Intelligent Classifier, or Verity Developer’s Kit. Installation instructions for Verity Locales are in the Verity Locale Configuration Guide.

For detailed information on product requirements, see the Verity K2 Installation and Setup Guide and the Verity K2 Release Notes.

Installing Multiple Binaries on UNIX

On UNIX platforms, the Locales installer allows the user to specify that binary files for all supported platforms (not just the platform on which the installer is executing) be included in the installation. This capability is of most use when installing Locales on VDK installations that themselves include VDK binaries for all supported platforms. (97282)

Using the GUI-Based Installer on UNIX

To use the graphical (non-console) Locales installer on UNIX, you must set the DISPLAY environment variable correctly. For example:

setenv DISPLAY IP_address:0.0

Where IP_address is the IP address (or host name) of the machine on which the installer will run. (Using the graphical installer also requires the presence of a system windowing environment such as XWindows.)

Disk-Space Requirements

When installed, the Locales package can occupy a large amount of storage. On the Windows platforms, for example, installing Locales requires over 1.5 GB of free disk space.

Memory Requirements for Multilanguage Locale

The amount of memory used by the multilanguage (uni ) locale is dependent on the number of languages it is using. The locale loads language dictionaries as they are needed, into a single process; if all supported languages are loaded, the process requires a total of 380MB of memory for the dictionaries.

Setting a Temporary Directory (UNIX)

If your temporary directory (as defined by the $HOME environment variable) does not have sufficient space, the Locales installer will not allow the installation to proceed. (Approximately 400MB is needed, as noted in the previous section.)

As a workaround, you can specify a temporary directory from the command line like this: -is:tempdir directory

where directory is the pathname of a directory that has sufficient space.

Incompatibility Between uni Locale and Asian Locales

One K2 Server or indexing application cannot load a collection using the multilanguage (uni) locale and a collection using an Asian locale (japanb , koreab , simpcb , tradcb ) into the same process.

If it is important to be able to load uni collections and Asian collections at the same time, you can (if the uni collections are not in Japanese, Korean, or Chinese) disable uni support for them. Use this workaround:

1. Open the multilanguage locale configuration file (uni.cfg ), in the directory productDir/common/uni (where productDir is the Verity product directory, for example, usr/k2_6/k2 ).

2. Locate and comment out the sections for Japanese , Korean , Chinese (Simplified) , and Chinese (Traditional) . For traditional Chinese, for example, change this entry

#Chinese (Traditional)
language: zt
  driver: "unibas -lang zt -nopreload" "unibas"

    cjk_variations: yes

to this:

#Chinese (Traditional)
#language: zt
#  driver: "unibas -lang zt -nopreload" "unibas"

#  post_process:
#  {
#    cjk_variations: yes
#  }

3. Save and close the file.