Date: Sun, 27 Apr 1997 11:49:36 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: gibbs@plutotech.com (Justin T. Gibbs) Cc: terry@lambert.org, gibbs@plutotech.com, michaelh@cet.co.jp, joa@kuebart.stuttgart.netsurf.de, sysop@mixcom.com, hackers@freebsd.org Subject: Re: VFAT 32 support in msdosfs Message-ID: <199704271849.LAA08885@phaeton.artisoft.com> In-Reply-To: <199704262057.OAA00832@pluto.plutotech.com> from "Justin T. Gibbs" at Apr 26, 97 03:56:18 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> Try almost any foobarW API and it will fail. Don't use the ones which aren't on both platforms. > Win95 will also not > automatically convert between UNICODE and ANSI strings when a message > passes between windows that use different string types. Well, neither will NT. It seems to not have the problem because there's very little ANSI in NT. > 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. That just the stupid "code page" backward compatability crap, may it rot in hell. If they didn't come out with code that could run on win32s on win 3.1, they wouldn't have to jump through the DB/ANSI hoops. > Win95 is the bane of everyone's existance, including the developers > at Microsoft. Backward compatability is just a fact of Microsoft's life. If they were not married to their bane, they wouldn't have to carry it around. There's no accounting for management stupidity in any company. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704271849.LAA08885>