Date: Sat, 26 Apr 1997 15:56:18 -0600 From: "Justin T. Gibbs" <gibbs@plutotech.com> To: Terry Lambert <terry@lambert.org> Cc: gibbs@plutotech.com (Justin T. Gibbs), michaelh@cet.co.jp, joa@kuebart.stuttgart.netsurf.de, sysop@mixcom.com, hackers@freebsd.org Subject: Re: VFAT 32 support in msdosfs Message-ID: <199704262057.OAA00832@pluto.plutotech.com> In-Reply-To: Your message of "Sat, 26 Apr 1997 13:46:18 PDT." <199704262046.NAA07616@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>Not the ActiveX string marshalling interfaces I've been using. Are you >referring to the ones implemented by CTL3D32.DLL? We've already been >over all that... they don't count, because smart programmers will use >the subset common to both platforms. Even dumb programmers will, if >they want to get their "Designed For Windows 95" logo certification, >which requires that the progam also run on NT. 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. 95% of Office97 uses UNICODE internally, but serious hoops were jumped through in order to convert strings to DB or ANSI so that it could run without too many features "losing" after internationalization under Win95. Why do I know this? Because I had to implement some of these hoops while working on the PowerPoint97 project. Win95 is the bane of everyone's existance, including the developers at Microsoft. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704262057.OAA00832>