X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 26 Nov 2007 11:00:13 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: utf-8 and cygwin Message-ID: <20071126100013.GA16782@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200711251046 DOT lAPAkZbO015926 AT cba1 DOT math DOT Berkeley DOT EDU> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200711251046.lAPAkZbO015926@cba1.math.Berkeley.EDU> User-Agent: Mutt/1.5.16 (2007-06-09) 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 Nov 25 02:46, Mariusz Wodzicki wrote: > I would like to reopen the discussion about utf-8 support in cygwin. I'd like to close it again. I'm working on converting Cygwin's path handling to use NT's unicode functions. Given that there's practically no coding help from anybody, this will take much longer than I thought. > SIXTEEN months passed since there were some exchanges about it > on the cygwin mail list. > > The lack of support for filenames with non-Latin1 characters is > currently the MOST SEVERE LIMITATION of cygwin in my opinion. Etc, etc. instead of shouting, roll up your sleeves and help. http://cygwin.com/acronyms/#SHTDI http://cygwin.com/acronyms/#PTC http://cygwin.com/contrib.html 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/