JDK-4808414 : file.encoding should be made changeable
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.io
  • Affected Version: 1.4.1
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2003-01-27
  • Updated: 2005-02-25
  • Resolved: 2005-02-25
Related Reports
Duplicate :  
Description

Name: rmT116609			Date: 01/26/2003


FULL PRODUCT VERSION :
java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)

A DESCRIPTION OF THE PROBLEM :
file.encoding is a key property in testing g11n related java programs, but changing it in command line has different effect from platform to platform.  there are many ppl have requested this property be made changeable.  why
doesn't sun refuse to do this?

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
run java as follows on w2k: java -Dfile.encoding=UTF-8 myClass

EXPECTED VERSUS ACTUAL BEHAVIOR :
expected: result should be utf-8 byte array using string.getByteArray().

actual: w2k's locale encoding byte array.

REPRODUCIBILITY :
This bug can be reproduced always.
(Review ID: 179778) 
======================================================================

Comments
EVALUATION Duplicate. 4163515: -Dfile.encoding option doesn't affect default ByteToChar converter ###@###.### 2005-2-25 22:19:26 GMT
2005-02-25