Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com To: cygwin-developers AT cygwin DOT com Subject: Re: OemToAnsi patch from 2000-07-04 References: <1091101003 DOT 20001115120228 AT logos-m DOT ru> <20001115105258 DOT A7529 AT redhat DOT com> <3038577491 DOT 20001115222705 AT logos-m DOT ru> <20001117003721 DOT A16135 AT redhat DOT com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Kazuhiro Fujieda Date: 17 Nov 2000 16:43:59 +0900 In-Reply-To: Christopher Faylor's message of Fri, 17 Nov 2000 00:37:21 -0500 Message-ID: Lines: 18 X-Mailer: Gnus v5.3/Emacs 19.34 >>> On Fri, 17 Nov 2000 00:37:21 -0500 >>> Christopher Faylor said: > I don't suppose there are already any UNIX methods for accomplishing this > already, are there? In the i18n framework of UNIX, the character set (codepage in the Windows terminology) used by an application is controlled via environemnt variables, such as LC_CTYPE or LANG. But the character set used by the system side (console devices or file systems) is generally controlled by a way specific to the implementation. That will be the CYGWIN environment variable in Cygwin. ____ | AIST Kazuhiro Fujieda | HOKURIKU School of Information Science o_/ 1990 Japan Advanced Institute of Science and Technology