Installation guide

By default, setlocale expects the locale-specific data to be in the
language support databases contained in the /usr/lib/nls/loc directory
(the /usr/lib/intln directory on ULTRIX systems).
On ULTRIX systems, you can store the locale-specific data in a directory
that is not in the default search path. You specify where the locale-specific
data is by defining the INTLINFO variable. On DIGITAL UNIX systems you
specify where the locale-specific data is by defining the LOCPATH variable.
Except for these differences, the setlocale routine is the same on
DIGITAL UNIX and ULTRIX systems.
6.10.3 Creating Locale-Specific Information
On DIGITAL UNIX systems, you can create your own locale-specific
information. Use the localedef command to process locale and character
map files and produce a locale database. This command replaces the
ULTRIX ic command. For information about using the localedef
command, see localedef
(1).
6.10.4 The iconv Command
Like the ULTRIX iconv command, the DIGITAL UNIX iconv command
converts the encoding of characters in one codeset to another codeset. On
DIGITAL UNIX systems, you can use iconv to convert between a number
of character sets. The system provides conversion tables in the
/usr/lib/nls/loc/iconv directory. For information about using iconv
to convert codesets, see iconv
(1).
6.11 Event-Logging Software
On DIGITAL UNIX systems, system events are recorded using two
facilities:
• A systemwide event-logging facility, which logs events in ASCII format.
• A binary event-logging facility, which logs hardware and software
events in the kernel in binary format records.
The binary event logging is like the binary error logging provided on
ULTRIX systems. There are differences between the system logging
facilities on ULTRIX and DIGITAL UNIX systems. Both the ULTRIX and
DIGITAL UNIX systems provide a set of application interfaces for syslog.
See Section B.16 for more information.
Overview of the DIGITAL UNIX Programming Environment 6–23