Guide to Globalizing Windows Applications

JimCricket writes "Does your application need to be usable in multiple countries? Art & Logic has posted a handbook for developers who want to globalize their applications. The handbook gives design and implementation tips, plus code samples for globalization on Windows applications."

Comments

Why bother with Win32/MFC now ?

[Bazouel]

I mean, that's the whole point of .NET !

MFC is a f*cking mess : no respect of standard, need to discover "hidden" interfaces, break of OO concepts, overuse of macros, bloated, etc. etc. etc. And if you add COM/ATL to that ... well, welcome to hell :)

And don't even get me started on Win32 API ! That might be fine for some cases where optimization is a top priority (and even then ...), but do you really want to spend at least 50 % of programming time digging for some informations about an obscure function call or simply reinventing the wheel all over again ?

So while this guide can really be useful for what it's meant for (mostly C++ with MFC), I say, just take a look at C# and .NET and I can guarantee you will not want to go back to those "good old days" where you needed to hand code unicode conversions !

________________

Re:"Globalize?"

[Twylite]

Where's my moderator points when I need them sigh. One of the reasons good information is becoming hard to find on the 'Net is that everyone wants to invent their own name for something, often because they haven't bothered to research the topic first.

Internationalization, i18n, and occasionally localization are the accepted terms. Globalization is used in economics, not CS. Mod this guy up!