On Wed, Jan 08, 2003 at 01:10:36AM -0500, Colin Walters wrote: > On Tue, 2003-01-07 at 18:50, David Starner wrote: > > If you're using a terminal that can't support UTF-8, you always have the > > option of running > > something like GNU screen to translate the system charset to the terminal > > charset. > > It seems more important to get a systemwide encoding working, then worry > > about the > > minority who use physical terminals. > > That is interesting advice. I am not sure I understand exactly how it > would work though. Would you just tell screen that all input is in
Forget about screen and use filterm (from konwert package). I am using it from time to time on legacy terminals with a great success filterm - UTF8-iso1 is all you need to use your unicode setup to work on legacy iso-8859-1 terminal. It even converts characters to their most appropriate iso1 equvalents (strips diacritics, transliterates cyrillic etc.). This is not some hypothetical option like most of what is proposed, but I was really using it to read Russian and Slovak etc on broken|old terminals -- ----------------------------------------------------------- | Radovan Garabík http://melkor.dnp.fmph.uniba.sk/~garabik/ | | __..--^^^--..__ garabik @ melkor.dnp.fmph.uniba.sk | ----------------------------------------------------------- Antivirus alert: file .signature infected by signature virus. Hi! I'm a signature virus! Copy me into your signature file to help me spread!
