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: Kazuhiro Fujieda <cygwin at cygwin dot com>
- Subject: Re: Why cygwin forced convert all input and output to OEM or ANSI ?
- From: egor duda <deo at logos-m dot ru>
- Date: Tue, 25 Sep 2001 16:35:33 +0400
- CC: Alexander Gotlib <alex at cca dot usart dot ru>
- Organization: deo
- References: <16435422895.20010925011233@cca.usart.ru><s1sn13jr1eb.fsf@jaist.ac.jp>
- Reply-To: egor duda <cygwin at cygwin dot com>
Hi!
Tuesday, 25 September, 2001 Kazuhiro Fujieda fujieda@jaist.ac.jp wrote:
>> 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 ?
KF> The current Cygwin DLL doesn't support codepages other than
KF> OEM or ANSI in the current system locale, because Win32 APIs
KF> sensitive to the codepage can't handle them.
it's possible, i believe, to add something like CYGWIN=codepage:asis
all codepage-specific functions do allow supplying any valid codepage
to them with one exception: /dev/clipboard handling code.
Unfortunately, windows clipboard api really doesn't allow codepages other
than oem and ansi.
Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
--
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/