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.

Describes an issue that occurs when you reply to or forward a message in an Exchange 2013, Exchange 2010, or Exchange Online environment. When this issue occurs, Japanese DBCS characters in the message are corrupted.

Office installed from the Windows store has garbled or incorrect characters in the ribbon and other places in the application. This issue is specific to the Japanese user interface. STATUS: FIXED. This issue is now fixed in Version 1708 (8431.2094).

Symptoms. Assume that you execute a statement that contains a LIKE operator with the collation Japanese_XJIS_100_CI_AS in Microsoft SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014. There is a Japanese repeat character 'ー' (Cho-On) in the LIKE pattern.

Fixes an issue that garbles an email message body when Simplified Chinese characters are included in the BCC field in an Exchange Server 2013 or Exchange Server 2016 environment.

Symptoms. When you input Japanese characters on a contentEditable element by using Japanese Input Method Editor (IME), the caret may jump to an incorrect place, or a composition string may disappear.

When you receive a Skype for Business online meeting invitation that's created by Japanese version of Skype for Business 2016, you may find the email is garbled, and many Japanese characters can't be recognized. Resolution. To fix this issue, install the July 10, 2018, security update for Skype for Business 2016 (KB4022221).

In this scenario, Japanese characters in the subject line of the missed call notification email message are garbled. Cause. This issue occurs because the user notification XML file that is sent by Lync Server is encoded by using US-ASCII instead of UTF8. Resolution

Here is a sample working with full-width Unicode numbers in traditional Chinese, simplified Chinese, Japanese and Korean: dbcs,sizeof(dbcs),conv,sizeof(conv));

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: