X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,SARE_SUB_ENC_UTF8,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20100607104043.GG8163@calimero.vinschen.de> References: <20100607092355 DOT GB3028 AT wladimir> <20100607104043 DOT GG8163 AT calimero DOT vinschen DOT de> Date: Mon, 7 Jun 2010 12:14:20 +0100 Message-ID: Subject: Re: Unicode/UTF-8 support (MinTTY) - ncursesw - Mutt, Vim From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 On 7 June 2010 11:40, Corinna Vinschen wrote: > On Jun =C2=A07 11:23, Michael Ludwig wrote: >> The wide-character ncursesw was announced in January: >> >> =C2=A0 This is the first official release of ncurses compiled to support= wide >> =C2=A0 characters, and can be installed simultaineously with the "narrow" >> =C2=A0 ncurses package(s). >> >> http://www.mail-archive.com/cygwin-announce AT cygwin DOT com/msg03179.html >> >> It sounds like Unicode is the preferred way now: >> >> =C2=A0 Actually, I'd prefer if people started using -I/usr/include/ncurs= esw >> =C2=A0 and linking against the wide version of the library instead. >> >> http://sourceware.org/ml/cygwin/2010-05/msg00465.html >> >> People seem to have had success compiling Mutt with ncursesw: >> >> http://code.google.com/p/mintty/issues/detail?id=3D124 >> >> Are ncursesw versions of Vim and Mutt imminent? Or is it not going to >> happen anytime soon? > > Thanks for the heads up. =C2=A0I'll build the next release of vim (there's > a 7.3 release coming soon) against ncursesw. Probably a good idea anyway, but as far as I can see, vim works fine with UTF-8 already. It even handles non-BMP codepoints correctly, which isn't a given due to the UTF-16 wchar_t on Windows and Cygwin. (Emacs and mined get that right too, whereas for example bash and zsh don't.) Michael, what are the issues you're seeing with vim? Are you using Cygwin 1= .7? Mutt and also nano do need rebuilding with ncursesw though. Andy -- 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