Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Tue, 24 Oct 2000 22:33:38 -0400 From: Christopher Faylor To: cygwin AT sources DOT redhat DOT com Subject: Re: non latin file names? Message-ID: <20001024223338.A2738@redhat.com> Reply-To: cygwin AT sources DOT redhat DOT com Mail-Followup-To: cygwin AT sources DOT redhat DOT com References: <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001024200555 DOT 00d015a0 AT pop DOT bresnanlink DOT net> <000c01c03d82$ce879a10$21c9ca95 AT mow DOT siemens DOT ru> <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001023204853 DOT 00cfe100 AT pop DOT bresnanlink DOT net> <000c01c03d82$ce879a10$21c9ca95 AT mow DOT siemens DOT ru> <20001024110637 DOT A26191 AT redhat DOT com> <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001024200555 DOT 00d015a0 AT pop DOT bresnanlink DOT net> <20001024212112 DOT F1027 AT redhat DOT com> <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001024204212 DOT 00d02b90 AT pop DOT bresnanlink DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.3.6i In-Reply-To: <4.3.2.7.0.20001024204212.00d02b90@pop.bresnanlink.net>; from cabbey@chartermi.net on Tue, Oct 24, 2000 at 09:26:05PM -0500 On Tue, Oct 24, 2000 at 09:26:05PM -0500, Chris Abbey wrote: >>I'm not going to do it because I have no experience in doing it >>and little interest in learning how to do it. > >interest in i18n/l17n aren't really needed... that code, >at least the conversion tables that are iconv/gconv are >there... what's needed is to make them available to programs >in cygwin (jikes could make use of it today, hence my interest) >then as the general i18n/l17n work takes place in the GNU World >(groan, bad pun) it can be readily absorbed by cygwin (ie. to >tie this back to the start of the thread, ls will someday learn >how to display ó in the general gnu-fileutils; when it does, >cygwin will be ready. That second part btw is a massive effort, >and one that a handfull of big companies (IBM) are looking at >very hard.) If no changes to cygwin1.dll are required then this is a possibility. Otherwise, due to licensing considerations we can't just take GPL'ed code that is owned by another entity into Cygwin or newlib. So, it is not necessarily this simple, unfortunately. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com