X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DATE_IN_PAST_96_XX
X-Spam-Check-By:	sourceware.org
Message-Id:	<200904211025.n3LAPf7a022955@mail.bln1.bf.nsn-intra.net>
From:	Thomas Wolff <mined AT towo DOT net>
To:	cygwin AT cygwin DOT com
Date:	Tue, 14 Apr 2009 19:08:09 +0200
Subject:	Re: [1.7] Updated: cygwin-1.7.0-45
References:	<20090402171059 DOT GE12738 AT calimero DOT vinschen DOT de> <20090331111757 DOT GA22043 AT calimero DOT vinschen DOT de> <200904031037 DOT n33Ab4Ma001073 AT mail DOT bln1 DOT bf DOT nsn-intra DOT net> <20090403145139 DOT GJ12738 AT calimero DOT vinschen DOT de>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On April 14, Corinna Vinschen wrote:

> > ... the setting of the console would depend on the
> > LC_ALL/LC_CTYPE/LANG setting when you start the first Cygwin process of
> > a Cygwin process tree in that console.  It would last for all Cygwin
> > processes within the same process tree.
> 
> This approach is now implemented in 1.7.0-46.  Please give it a try.

UTF-8 after rlogin/telnet works fine now, thank you.

There are still a few issues I'd like to report:


----------------------

I still had some confusing UTF-8 malfunction effects, which however 
occured only since I still have the bin directory of cygwin 1.5 in my 
Windows path; I am mentioning the observations anyway in case it 
matters:

After set LC_CTYPE=en_US.UTF-8
this works fine:
	cat utftest
	rlogin ...
	bash --login
However, the following does NOT work:
	bash	# without --login, but using cygwin 1.7 bash
	mined	# my own application

So, somehow, bash --login finds its proper cygwin1.dll while 
bash without --login does not; also cat and rlogin do find 
their proper cygwin1.dll while my self-compiled application 
does not...


----------------------

Another effect:

With some encodings, bash hangs with sed.exe using 99% CPU time; if I 
interrupt with ^C, however, the codepage is properly set up. This happens 
with the "DOS codepages" CP437...CP866 and CP1125, while the "ANSI codepages" 
CP874 and CP1250...CP1258, the ISO codepages, and the CJK codepages work fine.

By the way, maybe it should be mentioned in the user guide that setting the 
console font to Lucida Console rather than "Raster Fonts" enhances the 
Unicode font support. Even then I don't get any Arabic/Hebrew/Thai or CJK 
font display. Do you have a working test setup for those? (I guess so 
since you support the encodings.)


----------------------

Yet another issue:
When I hit Backspace on the command line in UTF-8 or CJK modes, the 
whole line including the prompt is blanked.


----------------------
Thomas

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -