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

also fails in the 6.0 snapshot

ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]

A DESCRIPTION OF THE PROBLEM :
When using a UTF-8 encoded JNLP file containing non-ASCII7 characters in the
<argument> elements, the arguments passed to the program have a ? character
passed in place of the non-ASCII7 character in the JNLP file..

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
 - Generate a UTF-8 encoded JNLP passing non-ASCII7 characters in
   arguments to a program.
 - run the jnlp
 - compare the received argument characters with the expected ones

You can also see the problem just using a JNLP file.

If you create a JNLP file containing UTF-8 encoded non-ASCII7 characters, and
remove the codebase element, then try to run it, it fails. Press the details
button, and select the tab to view the launch file. Looking at the launch file will show the correctly decoded characters.

Then modify the JNLP file so that there is a codebase, but it points to a
non-existent directory, and try to run it. When it fails, press the details button again, select the Launch File tab, and look at the file. At this point, it shows the previously correctly decoded characters as a box glyph.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The arguments received by the program contain the correctly decoded UNICODE
characters
ACTUAL -
Any non-ASCII7 characters in the arguments are replaced by ?

REPRODUCIBILITY :
This bug can be reproduced always.

---------- BEGIN SOURCE ----------
class echo {
    public static void main(String[] args) {
for (int i = 0 ; i < args.length ; i++) {
System.out.println("args[" + i + "]='" + args[i] + "'");
}
    }
}

(in case the two unicode characters are not passed through cleanly, the first
is 0xC3 0x89, the second is 0xC3 0xA9)
---------- END SOURCE ----------

CUSTOMER SUBMITTED WORKAROUND :
Go back to using J2SE 1.4.2

Release Regression From : 1.4.2
The above release value was the last known release where this
bug was known to work. Since then there has been a regression.
###@###.### 2004-12-08 17:25:14 GMT
###@###.### 2004-12-08 17:26:23 GMT