Fwd: 7050570: (fs) FileSysteProvider fails to initializes if run with file.encoding set to Cp037 (original) (raw)
Alan Bateman Alan.Bateman at oracle.com
Mon Aug 27 05:43:41 PDT 2012
- Previous message: Fwd: 7050570: (fs) FileSysteProvider fails to initializes if run with file.encoding set to Cp037
- Next message: Fwd: 7050570: (fs) FileSysteProvider fails to initializes if run with file.encoding set to Cp037
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 27/08/2012 12:57, Ulf Zibis wrote:
:
I still do not see any reasonable why this UnixFileSystem-API is partly processing chars vs. bytes. E.G compare UnixPath.normalize(...) vs. UnixPath.initOffsets(). This is the initialization of the file system and so is somewhat special, it basically needs the default directory so that it can compare it it to the working directory of the process. The syscall for the later give it to us in bytes. You are right that the absolute path check could be done with chars but I don't think it makes any difference unless there are wider changes to support multi-byte encodings.
-Alan. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/nio-dev/attachments/20120827/93ba3e7d/attachment.html
- Previous message: Fwd: 7050570: (fs) FileSysteProvider fails to initializes if run with file.encoding set to Cp037
- Next message: Fwd: 7050570: (fs) FileSysteProvider fails to initializes if run with file.encoding set to Cp037
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]