Bug 994 - Incorrect support of accentuated chars in filenames created by Samba v2
Summary: Incorrect support of accentuated chars in filenames created by Samba v2
Status: CLOSED INVALID
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: Extended Characters (show other bugs)
Version: 3.0.1
Hardware: All OSF/1
: P2 major
Target Milestone: none
Assignee: Alexander Bokovoy
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-22 04:28 UTC by Michel Jouvin
Modified: 2004-08-24 06:51 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Jouvin 2004-01-22 04:28:13 UTC 
I upgraded from 2.2.8 to 3.0.1, keeping the same smb.conf. After that, 
existing file names containing accentuated characters (code >128) are 
incorrectly truncated at the 1st accentuated character when displayed.

There is no problem with filename of files created by Samba 3.0.1. But there 
is a difference : the accentuated character is now encoded on 2 bytes 
(characters).

I looked in the doc but found no parameter related to this.

Thanks in advance.

Michel
Comment 1 Michel Jouvin 2004-01-22 04:41:57 UTC 
I just saw the 'unix charset' parameter. It has some effect on the problem. I 
tried to set it to ASCII. In this case the file name is not truncated but the 
accentuated character is incorrectly displayed and the file cannot opened. May 
be I just need to find the right value for this parameter...

Thanks in advance.

Michel
Comment 2 Michel Jouvin 2004-01-22 05:47:17 UTC 
Looking again at the docs, I found a description of the problem (move to UTF8 
encoding) and a proposed workaround (use convmv). I'll try.

It is still unclear for me why reverting to ASCII encoding using 'unix 
charset' didn't work properly. May be I should have tried ISO8859-1 ?

Michel
Comment 3 Björn Jacke 2004-08-24 06:51:09 UTC 
unix charset needs to be set properly, otherwise these effects are normal.