This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: New setup.exe snapshot 2.249.2.2
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- To: Robert Collins <robert dot collins at syncretize dot net>
- Cc: 'Earnie Boyd' <Cygwin-Apps at Cygwin dot Com>
- Date: Mon, 10 Jun 2002 09:37:03 -0400
- Subject: Re: New setup.exe snapshot 2.249.2.2
- References: <007d01c21083$1b512c60$0200a8c0@lifelesswks>
- Reply-to: Earnie Boyd <Cygwin-Apps at Cygwin dot Com>
Robert Collins wrote:
>
> > -----Original Message-----
> > From: Earnie Boyd [mailto:earnie_boyd@yahoo.com]
> > Sent: Monday, 10 June 2002 11:20 PM
> > To: Robert Collins
> > Cc: cygwin-apps@cygwin.com
> > Subject: Re: New setup.exe snapshot 2.249.2.2
> >
> >
> > Robert Collins wrote:
> > >
> > > Hmm, well it's definitely a bug, but how to fix? The workaround will
> > > (setting non-UNICODE programs to English) will have to do for now.
> > >
> >
> > Perhaps a #define UNICODE before #include <windows.h> would help?
>
> We can't rely on the MS layer for unicode on win9x. Doesn't the above
> require that? I hesitate to look at multiple binaries either :[.
>
If you wish to continue supporting W9x, and I suppose you do, perhaps an
alternative binary would suffice, I.E.: A binary with UNICODE and a
binary without UNICODE?
Earnie.