[
https://issues.apache.org/jira/browse/LUCENE-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616331#comment-14616331
]
Dawid Weiss commented on LUCENE-6563:
-------------------------------------
bq. In MacOSX, right up to the FS understands it as UTF-8.
I doubt it does anything special. Try forming an incorrect UTF-8 sequence in a
C application and creating a file on disk. If it fails, it means it is
interpreted as such (but I don't think it will).
Or mount a FAT-32 filesystem and create some UTF-8 files in there, then
re-mount it under Windows. Good luck.
As for Java, yes, the fact that the API uses UTF-16 has been a problem (or a
blessing, depends how you look at it). Till this day I see ways to "fix"
codepage conversion problems with horrible things like {{new
String(bytesFromNetwork, "ISO-8859-1")}}...
> MockFileSystemTestCase.testURI should be improved to handle cases where
> OS/JVM cannot create non-ASCII filenames
> ----------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-6563
> URL: https://issues.apache.org/jira/browse/LUCENE-6563
> Project: Lucene - Core
> Issue Type: Wish
> Reporter: Christine Poerschke
> Assignee: Dawid Weiss
> Priority: Minor
>
> {{ant test -Dtestcase=TestVerboseFS -Dtests.method=testURI
> -Dtests.file.encoding=UTF-8}} fails (for example) with 'Oracle Corporation
> 1.8.0_45 (64-bit)' when the default {{sun.jnu.encoding}} system property is
> (for example) {{ANSI_X3.4-1968}}
> [details to follow]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
