CVS update: samba/source/param

[Tim Potter]

On Tue, Mar 05, 2002 at 09:42:19PM -0800, Andrew Tridgell wrote:

> > This (silently) breaks international characters on command lines 
> 
> it does? How can it be worse than the previous default, which was
> "ascii"

By silently I mean it mysteriously fails to work.  (-:

Previously it was working with codepage and "fake" unicode magic
so at least this is configurable.  I haven't done any of this
testing for about 6 months so I guess a lot has gone on in HEAD
since then.

> > if you are mucking around with i18n domain and usernames you need 
> > 'unix charset = ISO_8859-1', assuming your environment is set to 
> > 8859-1.
> 
> surely you needed to do that before for international chars?

Before it required "character set = iso8859-1".

> > I'm just wondering what setting the default unix charset to utf8 actually
> > does?
> 
> it means that when a client sends us a unicode char we can store it
> and fetch it back accurately from the filesystem. That means for
> clients that do unicode (all Microsoft clients) Samba will "out of the
> box" support all chars in many applications.

OK - that makes sense.  I've got a feeling that a iso8859-1 environment
and utf8 filesystem will fight with each other.  Perhaps the client
routines need to convert their input in to utf8 before passing it on
to the rpc marshalling routines?


Tim.