Hi Frank,
Does this work as expected? The method doesn't seem to validate whether
a character is legal as a file name. For example, on Windows, the
original char (e.g. \u0159) used in the test is legal in a file name,
but it didn't pass that decode/encode test by the Windows' default
encoding (Windows-1252). Does that mean this test will no longer run on
Windows?
Thanks,
Joe
On 10/13/16, 2:05 AM, Frank Yuan wrote:
Hi all
Would you like to review
http://cr.openjdk.java.net/~fyuan/8167478/webrev.00/
<http://cr.openjdk.java.net/%7Efyuan/8167478/webrev.00/> ?
Bug: https://bugs.openjdk.java.net/browse/JDK-8167478
This is a test bug, because Bug6341770.java is invalid when the system
environment doesn't support non-ascii characters, the test will exit
immediately in this condition.
Thanks,
Frank