|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Yeah, I just checked it again, and it seems java.io.File always operates on the basis of a java.lang.String, ie. with an internal representation-independent form and it always uses the environment settings when choosing the actual filename repesentation when interacting with the filesystem layer. That is nuts because it seemingly cannot handle files with bad name encodings, ie. one could think of falling back to a generic charset like iso8859-1 to handle such cases, at least when the filename's correct encoding is not an issue.....