From owner-freebsd-hackers Sun Apr 27 11:57:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA23358 for hackers-outgoing; Sun, 27 Apr 1997 11:57:38 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA23351 for ; Sun, 27 Apr 1997 11:57:35 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA08899; Sun, 27 Apr 1997 11:51:29 -0700 From: Terry Lambert Message-Id: <199704271851.LAA08899@phaeton.artisoft.com> Subject: Re: VFAT 32 support in msdosfs To: jfieber@indiana.edu (John Fieber) Date: Sun, 27 Apr 1997 11:51:29 -0700 (MST) Cc: gibbs@plutotech.com, terry@lambert.org, michaelh@cet.co.jp, joa@kuebart.stuttgart.netsurf.de, sysop@mixcom.com, hackers@freebsd.org In-Reply-To: from "John Fieber" at Apr 26, 97 07:07:26 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Try almost any foobarW API and it will fail. Win95 will also not > > automatically convert between UNICODE and ANSI strings when a message > > passes between windows that use different string types. > > Over on the unicode mailing list, there was a lot of discussion > (grumbling) about this, and the general conclusion was that > writing Unicode applications to work on Win95 sure fire way to > programmer insanity, if not suicide. Alternately, live in the subset, and write your own 'W' functions, as necessary, for where a function is absolutely required. One thing these non-working 'W' functions are probably telling you is that you should pick some other method of solving the problem. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.