WARNING! Protect yourself from data loss by making regular backups of your work.

## 3. Using the Kit

Once your copy of the Windows Installer Localization Kit is correctly installed, you may begin your localization work by following the instructions in the remainder of this document. The next section discusses the contents of the localization notes provided with this kit. It is important that you work properly with the instructions contained in these files or the localized product you create may not function.

### Understanding the Localization Notes

Each localized module to be installed has an associated initialization (.INI) file. The localization notes for these files, and for the localizable dynamic link libraries used by the InstallShield installer, are provided as HTML documentation. (There are no localization databases in this kit). Additionally, a section detailing the required Windows registry settings is also provided in HTML format.

The next section presents the basic localization process as a checklist.

### Localization Checklist

This checklist applies to the "modifying an existing Communicator installer" method. If you are creating your own installer, you will need to adapt this checklist accordingly. A reference is provided to help you implement the correct Windows registry settings.

1. Download an existing installer
You will need a matching installer for the product you are localizing. In other words, if you are localizing Netscape Communicator version 4.03, you need an installer for the Export version of Netscape Communicator 4.03. If you are localizing Mozilla Navigator version 5.0, you need an installer for the Export version (if any) of Mozilla Navigator version 5.0. Latest versions of Netscape products can be downloaded from the Netscape homepage. Older versions of Netscape installers, matching the versions used to generate the localization kits, can be found on the mozilla.org ftp site.

Current Netscape installers come in two forms: base and complete. Complete installers include plugins and other components besides the basic Communicator software. You may use either installer as the foundation for your work, but note that there may not be localization kits for the additional components. Even if you choose to distribute the English version of these components, however, you must modify the associated initialization files, listed in the Localize These Files page in order for the additional components to be installed properly.

2. Uncompress the Installer files

- Run the installer you downloaded in step 1. This will bring up the following dialog (or something very similar):
- Click yes. InstallShield will extract all the installation files to your temporary directory. (Usually, this will be C:\temp or something similar). Once this process is complete, the blue InstallShield background will display.
- Without exiting the installer, locate the unpacked installer files in your temp directory and copy them to a new directory. Call this directory "install" (or something similar).
- Exit the installer.

3. Uncompress the Deinstaller files

- Change directories to your "install" directory. Locate the file cd32*.exe (where * equals the version number you are working on. For example, version 4.03 would be represented as cd32403.exe).
- Execute cd32*.exe. This will bring up a dialog similar to the one shown is step 2. Click yes and wait until InstallShield has finished unpacking the deinstaller files (the blue InstallShield background will display).
- Without exiting the installer, locate the unpacked deinstaller files in your temp directory and copy them to a new directory. Call this directory "deinstall" (or something similar).
- Exit the installer.

4. Extract localizable installer .DLLs
Change directories to your "install" directory. Use the InstallShield tool ICOMP.EXE to extract RSUTIL.DLL and _ISUSER.DLL from _SETUP.LIB:

`Example: icomp _setup.lib -d`

4. Localize files
Consult the Localize These Files page to learn which files contain localizable resources.

For each file to be localized, locate the associated Localization Notes for that file and follow them carefully.

5. Replace original product files contained in nav40.z with localized product files
Use the ICOMP tool to replace the original (English language) Communicator or Navigator files with the ones you have localized using the Windows Front End Localization Kit.

- Make sure your localized product directory structure matches the structure inside the compressed file nav40.z. (If necessary, uncompress nav40.z (including subdirectories), and replace all the localizable files (as identified by the Windows Front End Localization Kit) with your localized versions).
- Update nav40.z with your localized files:

`Example: icomp \kitRoot\products\client\windows\platform\locale\*.* nav40.z -i`

6. Rebuild the self-extracting deinstaller program
Use the InstallShield tool EXE Builder to reassemble the self-extracting deinstaller archive.

- Specify your "deinstall" directory as the source directory.
- Set compression on.
- Specify Setup.exe as the command line program to run when self-extraction is complete. (No optional parameters are required.)
- Specify your "install" directory as the target directory.
- Enter the name of your localized product as the application name.
- Do not specify a password.
- Once creation of your localized self-extracting deinstaller is complete, locate the file Setupex.exe in your "install" directory and rename it to match the original name of the deinstaller self-extracting program (e.g., cd32403.exe).

7. Rebuild the self-extracting installer program
Use the InstallShield tool EXE Builder to reassemble the self-extracting installer archive.

- Specify your "install" directory as the source directory.
- Set compression on.
- Specify Setup.exe as the command line program to run when self-extraction is complete. (No optional parameters are required.)
- Specify any directory you want as the target directory.
- Enter the name of your localized product as the application name.
- Do not specify a password.
- Once creation of your localized self-extracting installer is complete, locate the file Setupex.exe in your target directory and rename it to something meaningful.

8. Complete post-translation processing
After translation is complete, you need to test your work and deal with any problems:

- Test the localized installer.
- Fix translation bugs using your localization tools or a resource editor.
- Fix dialog size bugs using your localization tools or a resource editor.
- Report core bugs to Netscape.

9. Publish your localized product to the Internet
As the terms of the universal localization program license agreement state, your localized product

`"must be made publicly available in executable code form,`
`free of charge, for electronic delivery via a mechanism`
`generally accepted in the software development`
`community."`

In plain English, this means you should post your localized product on a publicly accessible http: or ftp: server. You may also want to send an announcement of your product's availability to mozilla.org (though you are not required to do so).

## Product Branding Issues

If you are using this kit under the auspices of the universal localization program, you must remove or replace Netscape trademarked strings, images and icons in your localized version. Click here for instructions.

## How to Localize Different Resource Types

This section provides you with general information about localizing the various resource types and files found with this kit.

### Localizing .INI Files

Most of the work for the Windows installers is localizing initialization (.INI) files. You may use the text editor of your choice to do this work. Be sure the localized files are saved as plain text only.

#### Localization Notes

Individual localization notes for the installer .INI files are contained in the individual HTML documents linked from the Localize These Files page.

### Localizing URLs

You will not likely encounter any URLs (Universal Resource Locators) in the installers, but if you do, how they are localized depends on whether you are creating a branded Netscape version or not. The rules for how to handle URLs are found here.

### Localizing String Tables

Use the resource editor of your choice to localize STRINGTABLE resources. These are the most sensitive, potentially problematic resource type you will be working with. Therefore, you must pay close attention to the instructions provided in the localization notes.

#### Localization Notes

Individual localization notes for the installer resource .DLLs are contained in the individual HTML documents linked from the Localize These Files page. This section gives you some additional general guidelines to follow when localizing the installer binary files.

- Some strings may contain C++ print format strings, such as %s, %ld, %lu, etc. Do not modify these while translating the rest of the string.
- Some strings may contain new line characters: \n. In general, you should try leave these as you find them.

### Localizing Menus

There are no menu resources in the Windows installer

### Localizing Dialogs

Use the resource editor of your choice to localize and resize DIALOG resources. Dialog translation is usually not as tricky as localizing string tables; however, you should take care to assign unique pickletters to dialog controls.

#### Localization Notes

Individual localization notes for the installer resource .DLLs are contained in the individual HTML documents linked from the Localize These Files page.

[BACK] | [NEXT] | [CONTENTS]

1998, Copyright Netscape Communications Corp. All Rights Reserved