On 07/24/09 11:36, Jay Anderson wrote:
I believe my problems with snv_114 were caused by filenames
> with the degree symbol in them (hex 176). Directory listings
in Windows Explorer for directories containing some of these filenames would be incomplete, ending without error at the
> first occurrence, and the "dir" command would end at the > first occurrence with "File not found." Evidently, these > directory listings were also causing problems with the > smb/server service. >
With snv_117 Windows Explorer cannot open the directory, and
> returns "not accessible" and "An unexpected network error > occurred." The "dir" command does not return any results now
for the directory, and returns "File not found."
We'll try to reproduce this here.
Is there a way to support filenames with other character sets than UTF-8 in CIFS Server? Is there a plan to provide this support?
Assuming you mean, is there support for different client locales? Yes, that should work. UTF-8 is just the internal transformation format used within the OS to provide a common frame of reference for all services that have to exchange file names. Windows OEM charsets (sometimes called code pages) should work. The OEM to/from UTF-8 conversions are handled internally by the CIFS Service. What locale or code pages are you using? If you're not sure, what is the Windows version (including SP/SR level) and what is the local language setting? Thanks, Alan _______________________________________________ cifs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
