On 2008-05-11 21:00:55 -0500, Nicolas Williams wrote: > On Mon, May 12, 2008 at 02:00:56AM +0200, Vincent Lefevre wrote: > > default one at the system level. Perhaps you mean that the SSH client > > should propagate the locale (more precisely, the charmap) to the > > SunSSH 1.1 does (by having the client set per-channel LANG/LC_* > environment variables).
I meant in a way that always works in practice. > It's less than perfect: the client has no idea what a client-side > locale maps to on the server side. Yes, that's the problem: it's not always possible to rebuild a correct LC_CTYPE on the remote side, e.g. if LC_CTYPE is "en_US", one doesn't have information about the charset on the remote side. > Also, it's not just character sets that matter, but language for > localization of messages, date formats, etc... Well, localization of messages and date formats are just a user choice. If they are different on the remote side, this isn't really a problem. Concerning the character set, the remote one must be compatible with the local one, at least when a terminal is used (ditto for the IUTF8 pseudo-terminal mode). Otherwise the user can't view or edit non-ASCII characters correctly. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
