Date: Thu, 19 Dec 1996 21:04:34 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: 8-bit characters in gecos field Message-ID: <199612192004.VAA00894@uriah.heep.sax.de> In-Reply-To: <Pine.BSF.3.95.961219074741.763A-100000@nagual.ru> from "[?KOI8-R?]" at "Dec 19, 96 07:58:24 am"
next in thread | previous in thread | raw e-mail | index | archive | help
As [?KOI8-R?] wrote: [Charset KOI8-R unsupported, skipping...] :-) Perhaps mutt handles this situation better than elm? ;) Anyway: > > Finger, however, is easy to fix, by sending quoted printable > > with =?char-set rather than 8-bit characrters. The character > > set indicator should reflect the default language applicable > > for the user class. > > In this case you need to parse QP into finger client and > yet one passwd field to store default charset. > It will be nice to set MM_CHARSET environment variable to this > value at login stage. > > To continue thinking in this direction: > nice thing will be default locale name stored into passwd instead. > Since locale > charset, we can automatically set both LANG and MM_CHARSET > environment variables at login stage. Yep, that's basically what David was suggesting (but you've probably been missing). He wrote that he's got a working login class implementation, and that the login charset could be stored there. This way, Andrey Chernov, Satoshi Asami, and Joerg Wunsch could, for example, store their GECOS names in their native charactersets on freefall. People fingering the respective entries with an appropriate finger client, and with an agreeing local charset will then be able to see it in the right language. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612192004.VAA00894>