The information in this article applies to:
- Microsoft OLE Control Development Kit (CDK), version 1.0
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.
|