Bug#99933: second attempt at more comprehensive unicode policy
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
UTF-8? It seems like this would not be true if the user has legacy
filenames, and they do something simple like 'ls'...
Reply to: