Hello, I am having a little problem, with Samba 2.2.5. I have a few users that have Japanese file formats. Once they copy them over to the samba server, they lose there formats and are rendered useless. I need help finding solutions to the problem here. Let me know if anybody has ran into the problem. Thanks, Kevin Morland
On Fri, 2004-01-30 at 09:23, Kevin Morland wrote:> Hello, > > I am having a little problem, with Samba 2.2.5. I have a few users > that have Japanese file formats. Once they copy them over to the samba > server, they lose there formats and are rendered useless. I need help > finding solutions to the problem here. Let me know if anybody has ran > into the problem.Samba will not modify the contents of the file, however Samba 2.2 has very poor support for anything other than ASCII in filenames. Samba 3.0 introduced real support for unicode filenames. Andrew Bartlett -- Andrew Bartlett abartlet@pcug.org.au Manager, Authentication Subsystems, Samba Team abartlet@samba.org Student Network Administrator, Hawker College abartlet@hawkerc.net http://samba.org http://build.samba.org http://hawkerc.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/samba/attachments/20040131/e9b08eac/attachment.bin
On Sat, Jan 31, 2004 at 06:24:08PM +1100, Andrew Bartlett wrote:> On Fri, 2004-01-30 at 09:23, Kevin Morland wrote: > > Hello, > > > > I am having a little problem, with Samba 2.2.5. I have a few users > > that have Japanese file formats. Once they copy them over to the samba > > server, they lose there formats and are rendered useless. I need help > > finding solutions to the problem here. Let me know if anybody has ran > > into the problem. > > Samba will not modify the contents of the file, however Samba 2.2 has > very poor support for anything other than ASCII in filenames. Samba 3.0 > introduced real support for unicode filenames.Weeeeellll - not true. If you set the code page correctly then Samba 2.2 does English + one other language perfectly well. Jeremy.
How would you set the code page correctly, to do both languages? Thanks, Kevin On Monday, February 2, 2004, at 09:25 AM, Jeremy Allison wrote:> On Sat, Jan 31, 2004 at 06:24:08PM +1100, Andrew Bartlett wrote: >> On Fri, 2004-01-30 at 09:23, Kevin Morland wrote: >>> Hello, >>> >>> I am having a little problem, with Samba 2.2.5. I have a few users >>> that have Japanese file formats. Once they copy them over to the >>> samba >>> server, they lose there formats and are rendered useless. I need >>> help >>> finding solutions to the problem here. Let me know if anybody has >>> ran >>> into the problem. >> >> Samba will not modify the contents of the file, however Samba 2.2 has >> very poor support for anything other than ASCII in filenames. Samba >> 3.0 >> introduced real support for unicode filenames. > > Weeeeellll - not true. If you set the code page correctly then Samba > 2.2 > does English + one other language perfectly well. > > Jeremy.
On Mon, Feb 02, 2004 at 10:02:30AM -0800, Kevin Morland wrote:> How would you set the code page correctly, to do both languages?In Samba 2.2 set : client code page = 932 (for Japanese SJIS) and then set "character set" to the encoding used on the Japanese UNIX system and also look at the "coding system" parameter (specifically for Japanese). Jeremy.