This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Why cygwin forced convert all input and output to OEM or ANSI ?
- To: Alexander Gotlib <alex at cca dot usart dot ru>
- Subject: Re: Why cygwin forced convert all input and output to OEM or ANSI ?
- From: Kazuhiro Fujieda <fujieda at jaist dot ac dot jp>
- Date: 25 Sep 2001 19:49:16 +0900
- Cc: cygwin at cygwin dot com
- References: <16435422895.20010925011233@cca.usart.ru>
- Reply-To: cygwin at cygwin dot com
>>> On Tue, 25 Sep 2001 01:12:33 +0600
>>> Alexander Gotlib <Alexander.Gotlib@cca.usart.ru> said:
> Now I see only two ways to use nonenglish codepage:
> CYGWIN=codepage:oem and CYGWIN=codepage:ansi. How can I use
> something differing of OEM and ANSI in whith cygwin apps ?
The current Cygwin DLL doesn't support codepages other than
OEM or ANSI in the current system locale, because Win32 APIs
sensitive to the codepage can't handle them.
____
| AIST Kazuhiro Fujieda <fujieda@jaist.ac.jp>
| HOKURIKU Center for Information Science
o_/ 1990 Japan Advanced Institute of Science and Technology
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/