Japanese Character Is Not Displayed Correctly When You Use MAPIReadMail

Article translations Article translations
Article ID: 317011 - View products that this article applies to.
This article was previously published under Q317011
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

When the MAPIReadMail function is called, Japanese (double-byte) characters are not displayed correctly. As a result, you cannot read strings by using the MAPIReadMail function.

This problem occurs in the following scenario:
  1. Create a program that uses the MAPIReadMail function, which can output Japanese strings in the message body (to do so, use lpszNoteText in the MAPIMessage structure).
  2. Make sure that your default MAPI client is Microsoft Outlook Express.
  3. Use Japanese Industry Standards (JIS), which is the code set for Japanese characters, to create a message that contains Japanese characters in the message body, and then send this message to your Inbox.
  4. Use a sample program to call the MAPIReadMail function, and then read the message that you received in step 3.
  5. Review the string that appears, specifically the string in lpMessage->lpszNoteText in the MAPIMessage structure.
The string is not displayed correctly. This string appears as a raw JIS-encoded string. The string is not displayed correctly in the message body only. This problem does not occur in the To box, the From box, or the Subject box.

RESOLUTION

To resolve this problem, obtain the latest service pack for Internet Explorer 6. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
328548 How to Obtain the Latest Internet Explorer 6 Service Pack
The English-language version of the fix should have the following file attributes or later:
   Date         Time   Version        Size      File name
   --------------------------------------------------------
   25-Jan-2002  09:09  6.00.2713.2400  1,175,040  Msoe.dll
				

STATUS

Microsoft has confirmed that this is a problem in Internet Explorer 6. This problem was first corrected in Internet Explorer 6 Service Pack 1.

Properties

Article ID: 317011 - Last Review: February 27, 2014 - Revision: 3.5
APPLIES TO
  • Microsoft Internet Explorer 6.0, when used with:
    • Microsoft Windows XP Home Edition
    • Microsoft Windows XP Professional
    • Microsoft Windows XP Media Center Edition
    • Microsoft Windows XP Tablet PC Edition
    • Microsoft Windows 2000 Advanced Server
    • Microsoft Windows 2000 Datacenter Server
    • Microsoft Windows 2000 Professional Edition
    • Microsoft Windows 2000 Server
    • Microsoft Windows NT Server 4.0 Standard Edition
    • Microsoft Windows NT Server 4.0, Terminal Server Edition
    • Microsoft Windows NT Workstation 4.0 Developer Edition
    • Microsoft Windows 98 Second Edition
    • Microsoft Windows 98 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix kbqfe kbie600presp1fix kbhotfixserver KB317011

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com