This chapter describes how to customize locale data and includes the following topics:
The Oracle Locale Builder offers an easy and efficient way to customize locale data. It provides a graphical user interface through which you can easily view, modify, and define locale-specific data. It extracts data from the text and binary definition files and presents them in a readable format so that you can process the information without worrying about the formats used in these files.
The Oracle Locale Builder manages four types of locale definitions: language, territory, character set, and linguistic sort. It also supports user-defined characters and customized linguistic rules. You can view definitions in existing text and binary definition files and make changes to them, or create your own definitions.
This section contains the following topics:
The Oracle Locale Builder uses Unicode characters in many of its functions. For example, it shows the mapping of local character code points to Unicode code points. Oracle Locale Builder depends on the local fonts that are available on the operating system where the characters are rendered. Therefore, Oracle recommends that you use a Unicode font to fully support the Oracle Locale Builder. If a character cannot be rendered with your local fonts, then it will probably be displayed as an empty box.
There are many Windows
OpenType fonts that support Unicode. Oracle recommends using the Arial Unicode MS font from Microsoft, because it includes over 50,000 glyphs and supports most of the characters in Unicode 5.0.
After installing the Unicode font, add the font to the Java Runtime
font.properties file so it can be used by the Oracle Locale Builder. The
font.properties file is located in the
$JAVAHOME/jre/lib directory. For example, for the Arial Unicode MS font, add the following entries to the
dialog.n=Arial Unicode MS, DEFAULT_CHARSET dialoginput.n=Arial Unicode MS, DEFAULT_CHARSET serif.n=Arial Unicode MS, DEFAULT_CHARSET sansserif.n=Arial Unicode MS, DEFAULT_CHARSET
n is the next available sequence number to assign to the Arial Unicode MS font in the font list. Java Runtime searches the font mapping list for each virtual font and uses the first font available on your system.
After you edit the
font.properties file, restart the Oracle Locale Builder.
See Also:Sun's internationalization Web site for more information about the
There are fewer choices of Unicode fonts for non-Windows platforms than for Windows platforms. If you cannot find a Unicode font with satisfactory character coverage, then use multiple fonts for different languages. Install each font and add the font entries into the
font.properties file using the steps described for the Windows platform.
For example, to display Japanese characters on Sun Solaris using the font
mincho, add entries to the existing
font.properties file in
$JAVAHOME/lib in the
sansserif sections. For example:
serif.plain.3=-ricoh-hg mincho l-medium-r-normal--*-%d-*-*-m-*-jisx0201.1976-0
Note:Depending on the operating system locale, the locale-specific
font.propertiesfile might be used. For example, if the current operating system locale is
ja_JP.eucJPon Sun Solaris, then
font.properties.jamay be used.
See Also:Your operating system documentation for more information about available fonts
Ensure that the
ORACLE_HOME parameter is set before starting Oracle Locale Builder.
In a Windows operating system, start the Oracle Locale Builder from the Start menu as follows: Start > Programs > Oracle-OraHome10 > Configuration and Migration Tools > Locale Builder. You can also start it from the DOS prompt by entering the
%ORACLE_HOME%\nls\lbuilder directory and executing the
When you start the Oracle Locale Builder, the screen shown in Figure 13-1 appears.
Before using Oracle Locale Builder for a specific task, you should become familiar with the following tab pages and dialog boxes:
Note:Oracle Locale Builder includes online help.
When you choose New Language, New Territory, New Character Set, or New Linguistic Sort, the first tab page that you see is labelled General. Click Show Existing Definitions to see the Existing Definitions dialog box.
The Existing Definitions dialog box enables you to open locale objects by name. If you know a specific language, territory, linguistic sort (collation), or character set that you want to start with, then click its displayed name. For example, you can open the
AMERICAN language definition file as shown in Figure 13-2.
Language and territory abbreviations are for reference only and cannot be opened.
> View Log to see the Session Log dialog box. The Session Log dialog box shows what actions have been taken in the current session. Click Save Log to keep a record of all changes. Figure 13-3 shows an example of a session log.
The NLT (National Languare Text) file is an XML file with the file extension
.nlt that stores the settings for a specific language, territory, character set, or linguistic sort. The Preview NLT tab page presents a readable form of the file so that you can see whether the changes you have made are correct. You cannot modify the NLT file from the Preview NLT tab page. You must use the specific tools and procedures available in Oracle Locale Builder to modify the NLT file.
Figure 13-4 shows an example of the Preview NLT tab page for a user-defined language called
You can see the Open File dialog box by choosing File
> By File Name. Then choose the NLB (National Language Binary) file that you want to modify or use as a template. An NLB file is a binary file with the file extension
.nlb that contains the binary equivalent of the information in the NLT file. Figure 13-5 shows the Open File dialog box with the
lx00001.nlb file selected. The Preview pane shows that this NLB file is for the
This section shows how to create a new language based on French. This new language is called
FRENCH. First, open
FRENCH from the Existing Definitions dialog box. Then change the language name to
FRENCH and the Language Abbreviation to
AF in the General tab page. Retain the default values for the other fields. Figure 13-6 shows the resulting General tab page.
Names must contain only ASCII characters
Names must start with a letter
Language, territory, and character set names cannot contain underscores
The valid range for the Language ID field for a user-defined language is 1,000 to 10,000. You can accept the value provided by Oracle Locale Builder or you can specify a value within the range.
Note:Only certain ID ranges are valid values for user-defined
MONOLINGUAL COLLATION, and
COLLATIONdefinitions. The ranges are specified in the sections of this chapter that concern each type of user-defined locale object.
Figure 13-7 shows how to set month names using the Month Names tab page.
All names are shown as they appear in the NLT file. If you choose Yes for capitalization, then the month names are capitalized in your application, but they do not appear capitalized in the Month Names tab page.
Figure 13-8 shows the Day Names tab page.
You can choose day names for your user-defined language. All names are shown as they appear in the NLT file. If you choose Yes for capitalization, then the day names are capitalized in your application, but they do not appear capitalized in the Day Names tab page.
Figure 13-9 shows the Common Info tab page.
You can display the territories, character sets, Windows character sets, and linguistic sorts that have associations with the current language. In general, the most appropriate or the most commonly used items are displayed first. For example, with a language of FRENCH, the common territories are FRANCE, BELGIUM, CANADA, and DJIBOUTI, while the character sets for supporting French are WE8ISO8859P1, WE8MSWIN1252, AL32UTF8, and WE8ISO8859P15. As WE8MSWIN1252 is more common than WE8ISO8859P1 in a Windows environment, it is displayed first.
The basic tasks are as follows:
Assign a territory name
Choose formats for the calendar, numbers, date and time, and currency
Figure 13-10 shows the General tab page with
SHORES specified as the Territory Name,
1001 specified as the Territory ID, and
RS specified as the Territory Abbreviation.
The valid range for Territory ID for a user-defined territory is 1000 to 10000.
Figure 13-11 shows settings for calendar formats in the Calendar tab page.
Monday is set as the first day of the week, and the first week of the calendar year is set as an ISO week. Figure 13-11 displays a sample calendar.
"Calendar Formats" for more information about choosing the first day of the week and the first week of the calendar year
"Customizing Calendars with the NLS Calendar Utility" for information about customizing calendars themselves
Figure 13-12 shows the Date&Time tab page.
When you choose a format from a list, Oracle Locale Builder displays an example of the format. In this case, the Short Date Format is set to
DD-MM-YY. The Short Time Format is set to
HH24:MI:SS. The Oracle Date Format is set to
DD-MM-YY. The Long Date Format is set to
fmDay, Month dd, yyyy. The TimeStamp Timezone Format is not set.
You can also enter your own formats instead of using the selection from the drop-down menus.
Figure 13-13 shows the Number tab page.
A period has been chosen for the Decimal Symbol. The Negative Sign Location is specified to be on the left of the number. The Numeric Group Separator is a comma. The Number Grouping is specified as 3 digits. The List Separator is a comma. The Measurement System is metric. The Rounding Indicator is 4.
You can enter your own values instead of using values in the lists.
When you choose a format from a list, Oracle Locale Builder displays an example of the format.
Figure 13-14 shows settings for currency formats in the Monetary tab page.
The Local Currency Symbol is set to
$. The Alternative Currency Symbol is the euro symbol. The Currency Presentation shows one of several possible sequences of the local currency symbol, the debit symbol, and the number. The Decimal Symbol is the period. The Group Separator is the comma. The Monetary Number Grouping is
3. The Monetary Precision, or number of digits after the decimal symbol, is
3. The Credit Symbol is
+. The Debit Symbol is
-. The International Currency Separator is a blank space, so it is not visible in the field. The International Currency Symbol (ISO currency symbol) is
USD. Oracle Locale Builder displays examples of the currency formats you have selected.
You can enter your own values instead of using the lists.
Figure 13-15 shows the Common Info tab page.
You can display the common languages and time zones for the current territory. For example, with a territory of CANADA, the common languages are ENGLISH, CANADIAN FRENCH, and FRENCH. The common time zones are America/Montreal, America/St_Johns, America/Halifax, America/Winnipeg, America/Regina, America/Edmonton, and America/Vancouver.
The rest of this section contains the following topics:
Offset from Coordinated Universal Time (UTC)
Transition times for daylight savings time
Abbreviations for standard time and daylight savings time. The abbreviations are used with the time zone names.
Two time zone files are included in the Oracle Database home directory. The default file is
oracore/zoneinfo/timezlrg.dat. The commonly used and smaller time zones are included in
See Also:"Choosing a Time Zone File" for more information about the contents of the time zone files and how to install the smaller time zone file
Oracle Database supports several calendars. All of them are defined with data derived from globalization support in Oracle Database, but some of them may require the addition of ruler eras or deviation days in the future. To add this information without waiting for a new release of Oracle Database, you can use an external file that is automatically loaded when the calendar functions are executed.
Calendar data is first defined in a text file. The text definition file must be converted into binary format. You can use the NLS Calendar Utility (
lxegen) to convert the text definition file into binary format.
The name of the text definition file and its location for the
lxegen utility are hard-coded and depend on the platform. On UNIX platforms, the file name is
lxecal.nlt. It is located in the
$ORACLE_HOME/nls directory. A sample text definition file is included in the
lxegen utility produces a binary file from the text definition file. The name of the binary file is also hard-coded and depends on the platform. On UNIX platforms, the name of the binary file is
lxecal.nlb. The binary file is generated in the same directory as the text file and overwrites an existing binary file.
After the binary file has been generated, it is automatically loaded during system initialization. Do not move or rename the file.
Invoke the calendar utility from the command line as follows:
Operating system documentation for the location of the files on your system
You can display and print the code charts of character sets with the Oracle Locale Builder. From the opening screen for Oracle Locale Builder, choose File
> Character Set. Figure 13-16 shows the resulting screen.
Click Show Existing Definitions. Highlight the character set you wish to display. Figure 13-17 shows the Existing Definitions combo box with US7ASCII highlighted.
Click Open to choose the character set. Figure 13-18 shows the General tab page when US7ASCII has been chosen.
Click the Character Data Mapping tab. Figure 13-19 shows the Character Data Mapping tab page for US7ASCII.
Click View CodeChart. Figure 13-20 shows the code chart for US7ASCII.
It shows the encoded value of each character in the local character set, the glyph associated with each character, and the Unicode value of each character in the local character set.
If you want to print the code chart, then click Print Page.
You can customize a character set to meet specific user needs. You can extend an existing encoded character set definition. User-defined characters are often used to encode special characters that represent the following language elements:
Historical Han characters that are not defined in an existing character set standard
New symbols or characters that you define
This section describes how Oracle Database supports user-defined characters. It includes the following topics:
User-defined characters are typically supported within East Asian character sets. These East Asian character sets have at least one range of reserved code points for user-defined characters. For example, Japanese Shift-JIS preserves 1880 code points for user-defined characters. They are shown in Table 13-1.
|Japanese Shift JIS User-Defined Character Range||Number of Code Points|
The Oracle Database character sets listed in Table 13-2 contain predefined ranges that support user-defined characters.
|Character Set Name||Number of Code Points Available for User-Defined Characters|
The code point value that represents a particular character can vary among different character sets. A Japanese kanji character is shown in Figure 13-21.
The following table shows how the character is encoded in different character sets.
|Unicode Encoding||JA16SJIS Encoding||JA16EUC Encoding||JA16DBCS Encoding|
Oracle Database defines all character sets with respect to Unicode 5.0 code points. That is, each character is defined as a Unicode 5.0 code value. Character conversion takes place transparently by using Unicode as the intermediate form. For example, when a JA16SJIS client connects to a JA16EUC database, the character shown in Figure 13-21 has the code point value 889F when it is entered from the JA16SJIS client. It is internally converted to Unicode (with code point value 4E9C), and then converted to JA16EUC (code point value B0A1).
Unicode 5.0 reserves the range E000-F8FF for the Private Use Area (PUA). The PUA is intended for end users' or vendors' private use character definition.
User-defined characters can be converted between two Oracle Database character sets by using Unicode 5.0 PUA as the intermediate form, which is the same as for standard characters.
Cross-references between different character sets are required when registering user-defined characters across operating systems. Cross-references ensure that the user-defined characters can be converted correctly across the different character sets when they are mapped to a Unicode PUA value.
For example, when registering a user-defined character on both a Japanese Shift-JIS operating system and a Japanese IBM Host operating system, you may want to assign the F040 code point on the Shift-JIS operating system and the 6941 code point on the IBM Host operating system for this character. This is so that Oracle Database can map this character correctly between the character sets JA16SJIS and JA16DBCS.
User-defined character cross-reference information can be found by viewing the character set definitions using the Oracle Locale Builder. For example, you can determine that both the Shift-JIS UDC value F040 and the IBM Host UDC value 6941 are mapped to the same Unicode PUA value E000.
By default, the Oracle Locale Builder generates the next available character set ID for you. You can also choose your own character set ID. Use the following format for naming character set definition NLT files:
dddd is the 4-digit character set ID in hex.
When you modify a character set, observe the following guidelines:
Do not remap existing characters.
All character mappings must be unique.
New characters should be mapped into the Unicode private use range e000 to f4ff. (Note that the actual Unicode 5.0 private use range is e000-f8ff. However, Oracle Database reserves f500-f8ff for its own private use.)
No line in the character set definition file can be longer than 80 characters.
Note:When you create a new multibyte character set from an existing character set, use an 8-bit or multibyte character set as the original character set.
If you derive a new character set from an existing Oracle Database character set, then Oracle recommends using the following character set naming convention:
For example, if a company such as Sun Microsystems adds user-defined characters to the JA16EUC character set, then the following character set name is appropriate:
The character set name contains the following parts:
JA16EUC is the character set name defined by Oracle Database
SUNW represents the organization name (company stock trading abbreviation for Sun Microsystems)
EXT specifies that this character set is an extension to the JA16EUC character set
1 specifies the version
This section shows how to create a new character set called
10001 for its Character Set ID. The example uses the WE8ISO8859P1 character set and adds 10 Chinese characters.
Figure 13-22 shows the General tab page for
Click Show Existing Definitions and choose the WE8ISO8859P1 character set from the Existing Definitions dialog box.
The ISO Character Set ID and Base Character Set ID fields are optional. The Base Character Set ID is used for inheriting values so that the properties of the base character set are used as a template. The Character Set ID is automatically generated, but you can override it. The valid range for a user-defined character set ID is 8000 to 8999 or 10000 to 20000.
Note:If you are using Pro*COBOL, then choose a character set ID between 8000 and 8999.
The ISO Character Set ID field remains blank for user-defined character sets.
In this example, the Base Character Set ID field remains blank. However, you can specify a character set to use as a template. The settings in the Type Specification tab page must match the type settings of the base character set that you enter in the Base Character Set ID field. If the type settings do not match, then you will receive an error when you generate your custom character set.
Figure 13-23 shows the Type Specification tab page.
The Character Set Category is
ASCII_BASED. The BYTE_UNIQUE button is checked.
When you have chosen an existing character set, the fields for the Type Specification tab page should already be set to appropriate values. You should keep these values unless you have a specific reason for changing them. If you need to change the settings, then use the following guidelines:
FIXED_WIDTH is used to identify character sets whose characters have a uniform length.
BYTE_UNIQUE means that the single-byte range of code points is distinct from the multibyte range. The code in the first byte indicates whether the character is single-byte or multibyte. An example is JA16EUC.
DISPLAY identifies character sets that are used only for display on clients and not for storage. Some Arabic, Devanagari, and Hebrew character sets are display character sets.
SHIFT is used for character sets that require extra shift characters to distinguish between single-byte characters and multibyte characters.
See Also:"Variable-width multibyte encoding schemes" for more information about shift-in and shift-out character sets
Figure 13-24 shows how to add user-defined characters.
Open the Character Data Mapping tab page. Highlight the character that you want to add characters after in the character set. In this example, the
0xff local character value is highlighted.
You can add one character at a time or use a text file to import a large number of characters. In this example, a text file is imported. The first column is the local character value. The second column is the Unicode value. The file contains the following character values:
88a2 963f 88a3 54c0 88a4 611b 88a5 6328 88a6 59f6 88a7 9022 88a8 8475 88a9 831c 88aa 7a50 88ab 60aa
> User-Defined Characters Data.
Figure 13-25 shows that the imported characters are added after
0xff in the character set.
This section shows how to create a new multilingual linguistic sort called
MY_GENERIC_M with a collation ID of
GENERIC_M linguistic sort is used as the basis for the new linguistic sort. Figure 13-26 shows how to begin.
Settings for the flags are automatically derived. SWAP_WITH_NEXT is relevant for Thai and Lao sorts. REVERSE_SECONDARY is for French sorts. CANONICAL_EQUIVALENCE determines whether canonical rules are used. In this example, CANONICAL_EQUIVALENCE is checked.
The valid range for Collation ID (sort ID) for a user-defined sort is 1000 to 2000 for monolingual collation and 10000 to 11000 for multilingual collation.
Figure 13-30, "Canonical Rules Dialog Box" for more information about canonical rules
Figure 13-27 shows the Unicode Collation Sequence tab page.
This example customizes the linguistic sort by moving digits so that they sort after letters. Complete the following steps:
Highlight the Unicode value that you want to move. In Figure 13-27, the
\x0034 Unicode value is highlighted. Its location in the Unicode Collation Sequence is called a node.
Click Cut. Select the location where you want to move the node.
Click Paste. Clicking Paste opens the Paste Node dialog box, shown in Figure 13-28.
The Paste Node dialog box enables you to choose whether to paste the node after or before the location you have selected. It also enables you to choose the level (Primary, Secondary, or Tertiary) of the node in relation to the node that you want to paste it next to.
Select the position and the level at which you want to paste the node.
In Figure 13-28, the After button and the Primary button are selected.
Click OK to paste the node.
Use similar steps to move other digits to a position after the letters
Figure 13-29 shows the resulting Unicode Collation Sequence tab page after the digits
4 have been moved to a position after the letters
The rest of this section contains the following topics:
This example shows how to change the sort order for characters with diacritics. You can do this by changing the sort for all characters containing a particular diacritic or by changing one character at a time. This example changes the sort of each character with a circumflex (for example,
û) to be after the same character containing a tilde.
Verify the current sort order by choosing Tools
> Canonical Rules. This opens the Canonical Rules dialog box, shown in Figure 13-30.
Figure 13-30 shows how characters are decomposed into their canonical equivalents and their current sorting orders. For example,
û is represented as
See Also:Chapter 5, "Linguistic Sorting and String Searching" for more information about canonical rules
In the Oracle Locale Builder collation window (shown in Figure 13-26), click the Non-Spacing Characters tab. If you use the Non-Spacing Characters tab page, then changes for diacritics apply to all characters. Figure 13-31 shows the Non-Spacing Characters tab page.
Select the circumflex and click Cut. Click Yes in the Removal Confirmation dialog box. Select the tilde and click Paste. Choose After and Secondary in the Paste Node dialog box and click OK.
Figure 13-32 illustrates the new sort order.
To change the order of a specific character with a diacritic, insert the character directly into the appropriate position. Characters with diacritics do not appear in the Unicode Collation Sequence tab page, so you cannot cut and paste them into the new location.
This example changes the sort order for
ä so that it sorts after
Select the Unicode Collation tab. Highlight the character,
Z, that you want to put
ä next to. Click Add. The Insert New Node dialog box appears, as shown in Figure 13-33.
Choose After and Primary in the Insert New Node dialog box. Enter the Unicode code point value of
ä. The code point value is
\x00e4. Click OK.
Figure 13-34 shows the resulting sort order.
After you have defined a new language, territory, character set, or linguistic sort, generate new NLB files from the NLT files as follows.
As the user who owns the files (typically user
oracle), back up the NLS installation boot file (
lx0boot.nlb) and the NLS system boot file (
lx1boot.nlb) in the
ORA_NLS10 directory. On a UNIX platform, enter commands similar to the following example:
% setenv ORA_NLS10 $ORACLE_HOME/nls/data % cd $ORA_NLS10 % cp -p lx0boot.nlb lx0boot.nlb.orig % cp -p lx1boot.nlb lx1boot.nlb.orig
Note that the
-p option preserves the timestamp of the original file.
In Oracle Locale Builder, choose Tools
> Generate NLB or click the Generate NLB icon in the left side bar.
Click Browse to find the directory where the NLT file is located. The location dialog box is shown in Figure 13-35.
Do not try to specify an NLT file. Oracle Locale Builder generates an NLB file for each NLT file.
Click OK to generate the NLB files.
Figure 13-36 illustrates the final notification that you have successfully generated NLB files for all NLT files in the directory.
lx1boot.nlb file into the path that is specified by the
ORA_NLS10 environment variable. For example, on a UNIX platform, enter a command similar to the following example:
% cp /directory_name/lx1boot.nlb $ORA_NLS10/lx1boot.nlb
Copy the new NLB files into the
ORA_NLS10 directory. For example, on a UNIX platform, enter commands similar to the following example:
% cp /directory_name/lx22710.nlb $ORA_NLS10 % cp /directory_name/lx52710.nlb $ORA_NLS10
Note:Oracle Locale Builder generates NLB files in the directory where the NLT files reside, which is typically ../nlsrtl3/admin/data.
Restart the database to use the newly created locale data.
To use the new locale data on the client side, exit the client and re-invoke the client after installing the NLB files.
See Also:"Locale Data on Demand" for more information about the
When deploying your locale customization files on other Oracle Database installations, running with the same Oracle Database release, and under the same operating system platform, you will need to copy all the custom NLB files together with the
lx1boot.nlb file over to the target machine. In order to deploy the custom NLB files on a different platform, you will need to copy over the custom
.NLT files to your new platform, and then repeat the NLB generation and installation steps as described in the section "Generating and Installing NLB Files".
Locale definition files are database release-dependent. For example, NLB files from Oracle Database 9i and Oracle Database 10g are not directly supported in an Oracle Database 11g Release 1 installation, and so forth. In order to migrate your locale customization files from a previous release of the database to your current release, you first need to convert the files into the latest NLT format. This is achieved by loading the locale customization files (either NLB or NLT), and saving them individually into NLT files using the current version of the Oracle Locale Builder. Next, you need to repeat the NLB generation and installation steps as described in the section "Generating and Installing NLB Files".
Please note that Oracle Locale Builder can read and process previous versions of the NLT and NLB files, as well as read and process these files from different platforms. However, Oracle Locale Builder always saves NLT files and generates NLB files in the latest format for the release of Oracle Database that you have installed.
NLB files that are generated on one platform can be transported to another platform by FTP or other copy utilities. The transported NLB files can be used the same way as the NLB files that were generated on the original platform. For example, NLB files that are generated on a Solaris platform can be copied by FTP to a Windows platform and will provide the same functionality there. This is convenient because locale data can be modified on one platform and copied to other platforms. Note that you must copy all of the NLB files from one platform to another, not just the files that have been modified. Also note that "Generating and Installing NLB Files" described is performed the same way as in previous releases.
Different binary formats (such as 32-bit, 64-bit, big-endian, little-endian, ASCII, and EBCDIC) are processed transparently during NLB loading.
ginstall utility adds custom character sets, language, territory, and linguistic sorts to Java components in your applications. You use Locale Builder to define your custom character sets, language, territory, and linguistic sort. Locale Builder generates NLT files, which contain the custom definitions. Then to add the custom definitions to the Java components, you run
ginstall to generate
gdk_custom.jar. The same procedures can be used for Oracle Database release 10.2 and 10.1, as well as release 11.1.
To add custom definitions for character set, language, territory, and linguistic sort:
Generate the NLT file using Oracle Locale Builder.
If you are upgrading custom NLB files from a previous release, follow the procedure described in Upgrading Custom NLB Files from Previous Releases of Oracle Database.
-a option to generate
ginstall –[add | a] lx2dddd.nlt
To generate multiple NLT files:
ginstall -[add | a] lx2dddd.nlt lx2dddd.nlt lx2dddd.nlt
gdk_custom.jar to the same directory as
To remove a custom definition:
ginstall as follows.
ginstall –[remove | r] <path to gdk_custom.jar> <name of NLT file>
To update a custom definition:
ginstall as follows.
ginstall –[update | u] <path to gdk_custom.jar> <name of NLT file>