You have two choices when deploying Multilizer: Deploy everything in a single JAR file, or deploy classes in multiple JAR files.
The first choice is to deploy all Multilizer classes using the mlall.jar
file. It is all you have to deploy.
The following table contains the description of the Multilizer's JAR files:
| File | Design time |
Run time |
Size in kBytes |
Description |
| multilizer.jar | x | 90 | Contains every Multilizer class. Use it to add Multilizer beans to you IDE. You are not allowed to include the file with your applications. | |
| mlall.jar | x | 62 | Contains every Multilizer class that is needed in run time. Deploy it with your multilingual applications and applets. |
When using applets the download size is the key issue in many cases. If this is true
you can optimize the download size by deploying only these classes that are needed.or you
deploy Multilizer in multiple JAR files. They are mlbase.jar and one
dictionary JAR (mltext.jar, mlbinary.jar, mlresource.jar,
mlserver.jar, and mldatabase.jar). For example, if you
application uses the binary dictionary you have to include the mlbase.jar and
mlbinary.jar with your application. If you application uses the server
dictionary and you have added a bi-directional language (Arabic, Hebrew or Farsi) and you
let the user select the language you have to include the mlbase.jar, mlbidi.jar,
mlselect.jar, and mlserver.jar with your application.
Using the sub packages you can shrink the overhead of Multilizer as low as 30 kBytes.
The following table contains the description of the Multilizer's sub JAR files:
| File | Size in kBytes |
Description |
| mlbase.jar | 25 | Contains the core Multilizer classes. Deploy it with your multilingual applications and applets. |
| mlselect.jar | 5 | Contains the multilingual select dialog classes, such as SelectLanguageDialog, SelectSublanguageDialog and SelectLocaleDialog. Deploy it only if you use multilingual select dialogs. |
| mlbidi.jar | 8 | Contains the bi-directional Multilizer classes. Deploy it if you use the bi-directional translator, BidiTranslator. |
| mlbinary.jar | 5 | Contains the binary dictionary classes. Deploy it if you use the binary dictionary, BinaryDictionary. |
| mltext.jar | 5 | Contains the text dictionary classes. Deploy it if you use the text dictionary, TextDictionary. |
| mlresource.jar | 4 | Contains the resource dictionary classes. Deploy it if you use the resource dictionary, ResourceDictionary. |
| mlserver.jar | 4 | Contains the server dictionary classes. Deploy it if you use the server dictionary, ServerDictionary. |
| mldatabase.jar | 3 | Contains the database dictionary classes. Deploy it if you use the database dictionary, DatabaseDictionary. |
| mltest.jar | 3 | Contains the test dictionary classes. Deploy it if you use the test dictionary, TestDictionary. |
To deploy a multilingual applets you have to place ome or more Multilizer's JAR files to the ARCHIVE tag. Separate multiple files with the comma (,).
The following example applet uses the server dictionary:
<APPLET ARCHIVE = "/ml/mlbase.jar,/ml/mlselect.jar,/ml/mlserver.jar" CODEBASE = "." CODE = "SampleApplet.class" NAME = "SampleApplet" WIDTH = 150 HEIGHT = 100 HSPACE = 0 VSPACE = 0 ALIGN = Middle >
Multilizer requires JDK 1.1 compatible browser. Unfortunately not Internet Explored 4.0 nor Netscape Navigator 4.0 are fully JDK 1.1 compatible. To get Multilizer working on these browser you have to use Sun's Activator technology (www.javasoft.com/products/activator/index.html). Activator is a browser component that makes it possible to replace the default VM of the browser.