Mail Archives: cygwin-developers/2002/07/03/13:16:16

Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
To: cygwin-developers AT cygwin DOT com
Subject: Re: UTF8 support in cygwin
References: <008401c22279$68759a00$0100a8c0 AT advent02>
<s1ssn31nf4y DOT fsf AT jaist DOT ac DOT jp>
<01d501c22294$44a874b0$0100a8c0 AT advent02>
<20020703154355 DOT GE24177 AT redhat DOT com>
Mime-Version: 1.0 (generated by tm-edit 7.106)
From: Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>
Date: 04 Jul 2002 02:13:44 +0900
In-Reply-To: Christopher Faylor's message of Wed, 3 Jul 2002 11:43:55 -0400
Message-ID: <>
Lines: 22

>>> On Wed, 3 Jul 2002 11:43:55 -0400
>>> Christopher Faylor <cgf AT redhat DOT com> said:

> I'm wondering if we need to augment newlib's existing but meager wide
> character support, though?  Or isn't that necessary?

I recognize it isn't necessary for nor unrelated to the 
translation in the system side. It is necessary when we develop
or port applications sensitive to wide characters.

BTW, I'm trying to add APIs related with i18n to Cygwin API for
these applications. Please see the following URL.  My approach,
however, only supports ANSI codepages in various locales.

The package distributed through this page has some troubles,
so I will release another package in the near future.
  | AIST      Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>
  | HOKURIKU  Center for Information Science
o_/ 1990      Japan Advanced Institute of Science and Technology

- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019