readme

是一个加快Java应用程序国际化和本地化开发的工具集。它将大大减少国际化和本地化开发的所消耗的时间和资源。

                        README
                

    Welcome to Java Internationalization and Localization Toolkit 2.0! 
It consists of the following individual tools:
        - Internationalization Verifier
        - Message Tool
        - Translator
        - Resource Tool

This document has three sections:
- JDK Support
- Changes from version 1.0
- Quick Start


Section I  JDK Support
----------------------
This toolkit release can be run with jdk1.2 or jdk1.1.7 and Swing 1.1 
or later. If you do not have JDK, please see the following URL for
download information:

      http://java.sun.com/products/jdk


Section II  Changes from version 1.0
------------------------------------
1. The toolbox was replaced with a project manager. The project manager can 
define a project to manage all java source files and their resource bunlde 
files. 

2. The GenMessage Tool has been renamed as Resource Tool. There are some new
functionalities which have been added into this tool, such as transforming
the type of resource bundles and encoding conversion. Resource Tool also has 
the functionalities of GenMessage Tool, such as merging and differeniating 
different resource bundles.

3. All the tools can be configured by resetting the properties in the 
properties files.

4. Better GUI than version 1.0. The GUI of version 2.0 is based on Swing. 
A full function editor has been provided in every tool. 

5. Better documents than version 1.0. On-line help is available in this 
version. 

6. Internationalization Verifier can generate verification reports based on
policies which are configurable. It can also be run in command line.

7. MessageTool supports converting string concatenation into MessageFormat, 
and user-defined resource bundles. It also involves all the functionalities
of Internationalization Verifier. The key can be changed when converting a
message item. It also has the functionality to convert all the message
items automatically in command line. 

8. Translator can help you translate the values in the resource bundles
with default dictionaries, reusable resource bundles, and user-defined 
dictionaries. It can also be run in command line.


Section III  Quick Start
------------------------

To run Java Internationalization and Localization Toolkit 2.0:

A. For Solaris:
---------------
1. If you're running on Solaris, set your JAVA_HOME environment variable to
   be the top directory of the JDK release you're using. For example:

   - If you are using jdk1.1
   
    setenv JAVA_HOME /home/me/jdk1.1.7

   - If you plan to use jdk1.2
   
    setenv JAVA_HOME /home/me/jdk1.2 
    
2. Set your SWING_HOME environment variable to be the top directory of 
   the Swing release you're using if your not using jdk1.2.
   
   For example:

    setenv SWING_HOME /home/me/swing-1.1
    
3. Set your CLASSPATH environment variable:
    
    - If you are using jdk1.1 and Swing
    
    setenv CLASSPATH .:${JAVA_HOME}/lib/classes.zip:${SWING_HOME}/swingall.jar

    - If you are using jdk1.2
    
    setenv CLASSPATH .:${JAVA_HOME}/jre/lib/rt.jar

4. Set your PATH environment variable:

    setenv JILKIT_HOME /home/me/JILKIT20
    setenv PATH ${JAVA_HOME}/bin:${JILKIT_HOME}/bin:${PATH}:.

5. Execute the shell script:

    jilkit


B. For Windows NT:
------------------
1. If your operating system is Windows NT, double-click the System icon
   inside the Control Panel. When the System Properties dialog box opens,
   place the following variables in the lower list box, which is labeled
   "User Variables." (Be careful not to change your system 
   environment variables which appear in the upper list box.)

    - If you plan to use jdk1.1.7 and Swing 1.1
    
    JAVA_HOME       C:\jdk1.1.7
    SWING_HOME      C:\swing-1.1
    JILKIT_HOME     C:\JILKIT20
    CLASSPATH       .;%JAVA_HOME%\lib\classes.zip;%SWING_HOME%\swingall.jar;
                    %JILKIT_HOME%;%JILKIT_HOME%\lib\jilkit20.jar
    PATH            %PATH%;%JAVA_HOME%\bin;%JILKIT_HOME%\bin;.

    -If you use jdk1.2
    JAVA_HOME       C:\jdk1.2
    JILKIT_HOME     C:\JILKIT20
    CLASSPATH       .;%JAVA_HOME%\jre\lib\rt.jar;%JILKIT_HOME%;
                    %JILKIT_HOME%\lib\jilkit20.jar
    PATH            %PATH%;%JAVA_HOME%\bin;%JILKIT_HOME%\bin;.

   These settings assume that you have installed the JDK and Swing on drive C. 
   If the JDK has been installed on a different drive, substitute that 
   drive's designator wherever appropriate.
   
2. From the Windows Start menu or from the Control Panel, open a console 
   (MS-DOS-style) window.
   
3. From your console window, execute the batch command:

    jilkit

4. If you run the toolkit in the directory which is not the directory the
toolkit has been installed, you should set an option "-Dtoolkit.home=
<installed directory>" in the command line in jilkit.bat file. For
example,
    java -Dtoolkit.home=%JILKIT_HOME% com.sun.tdc.toolkit.Main


C. For Windows 95 or Windows 98:
--------------------------------
1. Open your favorite text editor and add the following environment-variable
   settings to your system's AUTOEXEC.BAT file:
   
    - If you are using jdk1.1.7 and Swing 1.1
    
    set JAVA_HOME = C:\jdk1.1.7
    set SWING_HOME = C:\swing-1.1
    set JILKIT_HOME = C:\JILKIT20
    set CLASSPATH = .;%JAVA_HOME%\lib\classes.zip;%SWING_HOME%\swingall.jar;
                    %JILKIT_HOME%;%JILKIT_HOME%\lib\jilkit20.jar
    set PATH = %PATH%;%JAVA_HOME%\bin;%JILKIT_HOME%\bin;.

    -If you use jdk1.2
    set JAVA_HOME = C:\jdk1.2
    set JILKIT_HOME = C:\JILKIT20
    set CLASSPATH = .;%JAVA_HOME%\jre\lib\rt.jar;%JILKIT_HOME%;
                    %JILKIT_HOME%\lib\jilkit20.jar
    set PATH = %PATH%;%JAVA_HOME%\bin;%JILKIT_HOME%\bin;.

   These settings assume that you have installed the JDK and Swing on drive C. 
   If the JDK has been installed on a different drive, substitute that 
   drive's designator wherever it is appropriate.

2. From the Windows Start menu or from the Control Panel, open a console 
   (MS-DOS-style) window.
   
3. From your console window, execute the batch command:

    jilkit

4. If you run the toolkit in the directory which is not the directory the
toolkit has been installed, you should set an option "-Dtoolkit.home=
<installed directory>" in the command line in jilkit.bat file. For
example,
    java -Dtoolkit.home=%JILKIT_HOME% com.sun.tdc.toolkit.Main


Note: 
-----
    To make this tool more flexible to use, each compoment of this tool can 
    be run individually.


We look forward to your feedback.

mailto:[e-mail]

Copyright(c) 1997-1999 Sun Microsystems, Inc.
China Technical Development Center.
All Rights Reserved.