X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=1.2 required=5.0 tests=AWL,BAYES_05,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SARE_SUB_ENC_UTF8,TW_RX,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Date: Tue, 8 Jun 2010 00:47:30 +0200 From: Michael Ludwig To: cygwin AT cygwin DOT com Subject: Re: Unicode/UTF-8 support (MinTTY) - ncursesw - Mutt, Vim Message-ID: <20100607224655.GB1448@wladimir> Mail-Followup-To: cygwin AT cygwin DOT com References: <20100607092355 DOT GB3028 AT wladimir> <20100607104043 DOT GG8163 AT calimero DOT vinschen DOT de> <20100607124439 DOT GA2808 AT wladimir> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Andy Koppe schrieb am 07.06.2010 um 19:17 (+0100): > On 7 June 2010 13:44, Michael Ludwig wrote: > > As you say, Vim works fine with UTF-8. It's just that until very > > recently, I've been using the rxvt terminal emulator, which lacks > > Unicode support; so Vim being compiled against ncurses (*without* > > wide characters) was a good match. > > > > Now that I'm switching to the MinTTY terminal, which supports > > Unicode/UTF-8, I need a Vim compiled against ncursesw (*with* > > wide characters) if my assessment of the situation is correct. My assessment was incorrect. > If vim works fine with UTF-8 already, what does it matter which > ncurses it's linked against? I don't know vim's internals, but I'd > guess it works without ncursesw because it does its own screen > buffering and displaying, using ncurses only for accessing the > terminfo database. I don't have much of an idea of what ncurses is actually used for, nor how Unicode support works in Vim. I simply "assessed" the two were somehow connected. :-) The truth is rather trivial and refreshing. My ~/.vimrc contained some hard-coded configuration for Latin1 on Cygwin (win32unix): " MiLu: Cygwin/rxvt kann nur Latin1. if has('win32unix') set termencoding=latin1 endif That setting applied on a UTF-8 terminal garbled input, output and display for non-ASCII characters. After eliminating that it all works fine. Thanks for not letting my "assessment" pass! -- Michael Ludwig -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple