Re: CYGWIN=codepage? Or LC_CTYPE=foo?

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Apr  8 00:10, Brian Dessent wrote:
> Kazuhiro Fujieda wrote:
> 
> > You don't need to worry about a UTF-8 capable terminal. Windows
> > console can handle UTF-8 through Unicode.  Cygwin DLL will
> > convert UTF-8 messages to Unicode and feed them to WriteConsoleW,
> > if the codeset part of LANG or LC_CTYPE is UTF-8.
> 
> That's good news, but it only helps those that use a Windows Console.  I
> can't speak for anyone else but I detest the Windows Console with its
> awful cut+paste and inability to resize, so I avoid it at all costs. 
> We'd essentially be rendering rxvt and xterm broken out-of-the-box if we
> turned on UTF-8 output by default.  Of course in an ideal world we would
> release updated versions of xterm and (u)rxvt with UTF-8 support
> enabled, but at least in the case of rxvt that means losing the W11 port
> and in the case of xterm it means we'd need to find an X11 maintainer.

At least that's a solvable problem now that the DLL itself understands
UTF-8 paths.  We just need a maintainer :)

However, I'm not trying to enforce UTF-8, I'm merily asking.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat