Name: mc57594			Date: 05/31/99

Bug observed on Win 95 and NT, but not Solaris.

I generated a class which just prints the default file Encoding 
classes used by the sun.io ByteToCharConverter and CharToByteConverter classes.

package com.gil.test;
import sun.io.*;
public class Encoding
{
   /**
    * Encoding constructor comment.
    */
   public Encoding() {
   }
   /**
    * This method was created in VisualAge.
    * @param args java.lang.String[]
    */
   public static void main(String args[])
   {
   	System.out.println("Default ByteToChar Class >>'" + sun.io.ByteToCharConverter.getDefault().getClass().getName() + "'");
   	System.out.println("Default CharToByte Class >>'" + sun.io.CharToByteConverter.getDefault().getClass().getName() + "'");
   }
}

if I execute the above class and set the file encoding on the command line:

java -Dfile.encoding=8859_1 -cp . com.gil.test.Encoding

I get the following output:

Default ByteToChar Class >>'sun.io.ByteToCharCp1252'
Default CharToByte Class >>'sun.io.CharToByteCp1252'

If I use the -classic option, to not use Hotspot I get:

Default ByteToChar Class >>'sun.io.ByteToCharISO8859_1'
Default CharToByte Class >>'sun.io.CharToByteISO8859_1'

So it appears that the file encoding does not get set when 
using hotspot.
(Review ID: 83242) 
======================================================================