Describes an issue that occurs when you reply to or forward a message in an Exchange Server 2007 SP1, Exchange Server 2010, or Exchange Server 2010 SP1 environment. Japanese DBCS characters in the original message are corrupted. A resolution is provided.

When inputting some characters using the IME Pad in the Microsoft Japanese IME, the wrong characters might be outputted. For example, if you choose “。”, (0xA1) from [Half width Alpha] under [Shift JIS], the character “>” will be outputted.

This issue occurs because the value of the PR_INTERNET_CPID MAPI property of the message is stamped as 50222 by Exchange RPC Client Access service or Outlook Web App. Because of a restriction in Outlook, the code page 50222 characters are corrupted.

Fixes an issue occurs when you set the COLLATE clause to Japanese_XJIS_100_CI_AS in SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014.

Fixes an issue in which Japanese DBCS characters are corrupted. This issue occurs when you send a meeting request or post a reply to a posted item in a public folder by using the OWA in an Exchange Server 2010 environment.

Describes an issue in which an access violation occurs when a database table name contains Japanese characters. Provides a resolution.

Fixes an issue in which Japanese characters are displayed incorrectly when you decompress a compressed (.zip) file that you downloaded from Office 365 Outlook Web Application. This issue occurs in Windows 7 or in Windows Server 2008 R2.

When sending Office 365 Group emails in Plain Text with Hiragana letters (Japanese Characters), the resulting emails may have missing or garbled characters. The email body may show properly in the list view, but it will show blank or garbled in the Reading Pane. STATUS: WORKAROUND.

The raw Japanese characters are written in the "Subject:" header. An affected email client cannot detect the correct character set when the client displays the subject line. This results in unreadable, non-Japanese characters. Resolution. To resolve this issue, follow these steps:

For example, when a character is from the Japanese charset, and the client does not have the Japanese fonts installed, the Japanese character is displayed as a box. Next, I'll talk about how things changed in ASP.NET 1.x, and how those changes affect globalization issues in the context of ASP.NET.