At 01:10 AM 1/8/2003 -0500, Colin Walters wrote: >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'...
Well, screen should react in the same way that any UTF-8 terminal should react. (There's a specification that not all of them follow, but all of them I've tried handle it non-catastrophically.) The suggestion was how to handle legacy terminals in a UTF-8 world. As for legacy filenames, I'd think that it would be easiest for each system to declare a flag day, and change over to UTF-8. (zsh be damned -- they've had plenty of time to figure how to properly handle UTF-8.) I've submitted bugs on packages for having filenames not in ASCII, so for the most part Debian's filenames won't be a problem. There is no way for a POSIX filesystem to tag filenames with encodings, so there is no option for this to be a clean changeover, especially as there's no clean state to start from. David Starner - [EMAIL PROTECTED] ([EMAIL PROTECTED] may be disappearing soon - [EMAIL PROTECTED] will work, but is not suitable for high-volume traffic.)
