-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/2007 09:59 PM, Christian Pernegger escreveu:
>> > Thanks for trying, but that won't help - all (user) files on the
>> > server have UTF-8 names already.
>>
>> That was also my impression before I use convmv. :-)
>
> :-)
>
> Unfortunately, ch
> Thanks for trying, but that won't help - all (user) files on the
> server have UTF-8 names already.
That was also my impression before I use convmv. :-)
:-)
Unfortunately, charset conversion can't fix the fact that names of
_newly_created_ files and folders are interpreted slightly different
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/09/2007 02:23 PM, Christian Pernegger escreveu:
>> I solve that using convmv, Samba3 uses UTF-8 and tries to figure out
>> by itself the best way
>> to handle the charset stuff between server and clients, after
>> converting a couple of files
>
I solve that using convmv, Samba3 uses UTF-8 and tries to figure out by itself
the best way
to handle the charset stuff between server and clients, after converting a
couple of files
Thanks for trying, but that won't help - all (user) files on the
server have UTF-8 names already.
C.
--
To uns
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/09/2007 09:05 AM, Christian Pernegger escreveu:
> Hi list!
Hi Christian!
> I've been using Samba (as packaged in Debian) for years without any
> charset conversion issus, but now one bit me:
>
> Server:
> Samba 3.0.23d-2 (Debian testi
Hi list!
I've been using Samba (as packaged in Debian) for years without any
charset conversion issus, but now one bit me:
Server:
Samba 3.0.23d-2 (Debian testing),
system locale en_US.UTF-8, no charset options in smb.conf specified
Client-DE: MS Windows XP Pro SP2 German, locale for non-Unicod