[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#99933: second attempt at more comprehensive unicode policy



On Mon, 2003-01-06 at 16:01, Jochen Voss wrote:

> On Mon, Jan 06, 2003 at 12:21:27AM -0500, Colin Walters wrote:
> > After we have a "sufficient" number of programs supporting UTF-8
> > natively in this way, we change the policy on filenames to a "must",
> > drop support for legacy terminals and encodings, and switch everyone to
> > a UTF-8 terminal, and a UTF-8 locale.
> 
> I think that this would be a really bad idea, because it would be a to
> severe restriction on the set of supported terminal types.  Think of
> remote logins from non-Debian machines: we cannot control the program
> at the other end of the line.  And what about serial (hardware) VT-220
> terminals?  We cannot change the hardware and to loose support for it
> would be not nice.

That's true, but I don't think there is really anything we can do to
solve that problem.

> So in my opinion we cannot drop support for non-UTF8 locales and
> terminals.  We need to do file-name conversion here.

Well, such terminals should be explicitly marked as deprecated inside
Debian.  Actually, probably the best solution is for the terminal to be
able to switch encodings at runtime; the experimental gnome-terminal can
do this.




Reply to: