Sausalito Developer's Guide - Parent Directory

4—6 Chapter 4: Using i18n and l10n in Sausalito
Beta Draft 11. Copyright ' 2001.Cobalt Networks, Inc. All Rights Reserved.
The i18n Interface
\r -> return
\t -> tab
\v -> vertical newline
\(char) -> literal character
Rule 3. Tags are subject to the following expansion rules:
If the domain equals VAR, then variable expansion occurs. The variable specified in tagname
is looked up in the current hash of variables. Its value is interpolated according to these rules
and its value is substituted here.
If the domain is not equal to VAR, than the domain token is interpreted as the name of a i18n
domain. The tagname token is interpreted as a message identifier, and the appropriate substring
is fetched from the i18n database and interpolated.
Rule 4. The expanded unescaped tokens are reassembled into a single internationalized string.
Application developers use the following interface to fetch properly interpolated and escaped
strings from the i18n database. Generally, the programmer first calls a constructor to create a
new i18n object, perform a number of fetch operations, and then destroy the i18n object.
The i18n object performs its own memory management on strings that it returns. When the
i18n object is destroyed, all memory allocated for various strings is freed automatically.
The i18n library is a C library, but Perl and PHP bindings are provided in addition to the C
interface. These various interfaces to the i18n library are documented below.
The i18n C Language Interface
The function prototypes for the C language interface are in the following include file:
/usr/sausalito/include/cce/i18n.h
The link library for i18n is in these directories:
/usr/sausalito/lib/libi18n.a (library for static linking)
/usr/sausalito/lib/libi18n.so (library for dynamic linking)