Microsoft KB Archive/122290

= DOC: Errors In "Implementing Localization Support" =

Article ID: 122290

Article Last Modified on 8/16/2005

-

APPLIES TO


 * Microsoft OLE Control Developer's Kit (CDK)

-



This article was previously published under Q122290



SUMMARY
The Programmer's Guide from the Microsoft OLE Control Development Kit, version 1.0, contains some errors in the "Implementing Localization Support" section. The section contains information about implementing support for international versions of OLE controls.



MORE INFORMATION
Please make the following corrections to the "Implementing Localization Support" section:

 The second paragraph mentions three strategies for loading resources but fails to point out that the LOCALIZE sample uses the first strategy (loading resources on demand). In addition, it fails to mention that the second strategy is used for the rest of the topic. The part that explains how to create localized type libraries mentions these three scenarios:

Developing 16-bit controls under Windows 3.1 or later

Developing 16-bit controls under Windows NT

Developing 32-bit controls

Please change this to the following more precise description:

Developing 16-bit controls under Windows 3.1 or 3.11

Developing 16-bit controls under Windows NT or Windows 95

Developing 32-bit controls

 The following phrase in the first section titled "To add a new type library command to the tools menu", step 5, is incorrect:

... and the CDK was installed in C:\MSVC

It should read:

... and the CDK was installed in C:\MSVC\CDK16

 The following phrase in the second section titled "To add a new type library command to the tools menu", step 5, is incorrect:

... and the CDK was installed in C:\CDK16

It should read:

... and the CDK was installed in C:\MSVC\CDK16

 The following sentence should be deleted:

Because projects built under NT or Chicago store 16-bit type

libraries in the TLB16 subdirectory you must move any .ODL.

  The code sample for CSampleCtrl::GetLocalizedResourceHandle makes the following declaration: LANGID lang = LANGFROMLCID(lcid);  The lang variable is never used, so it can be safely deleted.</li></ul>

Additional query words: 1.00 docerr

Keywords: KB122290

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.