The Metaview Applet supports Java 1.02, which is good in that it runs in most browsers. Unfortunately, Java 1.02 does not support the use of resource files and fonts, which would enable the automated use of translated text and localized formats as supported by Java 1.2. To overcome this limitation, the Metaview Applet enables you to name a resource file and a resource font by specifying applet parameters. In this resource file you can hard-code translated versions of the text that the Metaview Applet uses.
Follow these steps to manually translate the text in the Metaview Applet:
Specify the LOGRESOURCES parameter in your SAS job, generate the HTML, and view it in a browser. (See Metaview Applet Parameters on page 475.) The Metaview Applet will then write its tag/value pairs to the Java console.
Copy the tag/value pairs that you want to translate out of the Java console and paste them into your resources file. Then translate those values to your language. You do not need to translate all of the tag/value pairs. The defaults will be used where translations are not provided.
Store your resources file in a location that can be accessed by your Web audience.
In the SAS program, remove the LOGRESOURCES parameter specification. Then specify the RESOURCES parameter. The value of that parameter is the URL of your resources file.
Note that you do not have to specify the RESOURCES parameter if you name the resource file MVAResources.properties and store that file in the same location as the HTML output file.
If your resources file requires a non-English text font, then specify that font as the value of the parameter RESOURCESFONTNAME. To display this font, your Web audience must have this font installed.
Run your program and test your Web output.
For information on specifying applet parameters, see Specifying Applet Parameters Using the ODS PARAMETERS= Statement on page 477. For reference information on the Metaview Applet parameters, see Metaview Applet Parameters on page 475.