X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Thu, 2 Apr 2009 15:39:14 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [1.7] Updated: vim-7.2.148-1
Message-ID: <20090402133914.GD18152@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20090331200950.GH12738@calimero.vinschen.de> <2bf229d30904020600x7a47be6bsf5bc46bf7220574f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <2bf229d30904020600x7a47be6bsf5bc46bf7220574f@mail.gmail.com>
User-Agent: Mutt/1.5.19 (2009-02-20)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Apr  2 09:00, Chris Sutcliffe wrote:
> > This is an update to the latest upstream patchlevel 148.  Cygwin Vim
> > builds from the vanilla sources.  This is the first vim release for
> > Cygwin with extended character set support.
> 
> Are there particular configuration options you have to use to enable
> the extended character support?  My current configure line is:
> 
> ./configure \
>       --prefix=/usr \
>       --sysconfdir=/etc \
>       --libexecdir='$(sbindir)' \
>       --localstatedir=/var \
>       --datadir='$(prefix)/share' \
>       --mandir='$(prefix)/share/man' \
>       --enable-multibyte \
>       --without-x \
>       --enable-gui=no \
>       --with-features=huge

That's fine.  It's exactly what I used to build vim.

Maybe the term "extended character set support" was a bit clumsy.
What I meant was this:  The previous vim was built before all the
widechar and multibyte functionality was available in Cygwin 1.7.
The result was that vim was not able to convert files from one
charset to another, for instance, from iso-8859-1 to utf-8.  The new
vim can do that on the fly at load time now.


Corinna

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

--
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/

