Hi,

Christian Perrier, le Wed 01 Feb 2006 07:38:45 +0100, a écrit :
> Quoting Samuel Thibault ([EMAIL PROTECTED]):
> > I don't understand why display charset currently defaults to ASCII
> > and unix charset defaults to UTF8.  Can't they just both default to
> > the current locale ? (particularly display charset). This would make
> > accented letters work in hardly every usual case, and possibly fix some
> > of the charset bugs that were reported against samba.
> 
> Well, *which* locale?

The current locale when running smbclient/smbget, for instance.

Locales in logs are yet another issue, which doesn't seem to have been
really solved in debian.

> You're certainly aware that while the system locale can be, say
> fr_FR.UTF-8, users are still able to use another locale such as, say
> fr_FR for those who still live in stone age....

Yes, that's why when running smbclient, the display charset should get
set to the _current_ locale's charset.

> So, *which* of those three locales should be used for "display
> charset"?

As I said, the _current_ one, just like any other localized program.

> Not mentioning that SWAT itself, which uses this "display charset"
> parameters, has no reason to depend on whatever charset of the Unix
> system.

Yet, swat should probably just use UTF-8 (and advertise this in the http
headers of course).

> Finally, we're talking about locales....while these parameters are
> about character sets....these are quite different beasts.

No. Locales tells the charset too: nl_langinfo(CHARSET) returns what I
call the "current" locale's charset.

BTW, it's still not clear to me the difference between unix charset
and display charset. I thought that unix charset was used for local
filesystem names, while display charset was used for displaying names on
ttys, but it doesn't seem to be so (and I don't see why in such case
there should be such distinction: "ls" doesn't make such distinction).

Regards,
Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to