Consider the following scenario:
You have applied Cumulative Update 1 for SQL Server 2008 R2 Service Pack 1 (SP1) or a later updates installed on a computer whose locale is set to Japanese.
The Windows code page (ANSI code page) has half-width characters on the computer.
You export a report to PDF, and the selected font has a full-width version of the ± (plus-minus) character.
In this scenario, you may find one or more of following issues in the PDF file that is generated:
There are extra spaces after apostrophes.
Text before dollar signs overlaps the dollar signs.
Some special characters seem to cause spacing problems.
Note The issue also occurs in SQL Server 2012 and SQL Server 2014.
The issue occurs because of an incorrect Unicode change made since SQL Server 2008 R2 SP2 CU1.
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 4 for SQL Server 2014 /en-us/help/2999197
Cumulative Update 2 for SQL Server 2012 SP2 /en-us/help/2983175
Cumulative Update 11 for SQL Server 2008 R2 SP2 /en-us/help/2926028
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Note After you apply this cumulative update, you may experience the following issue: if the report server is on a system whose locale set to Japanese, and the ± (plus-minus character) is in a report being exported to PDF, some characters may overlap. To work around this issue, use one of the following methods:
Change to a font that uses a half-width "±" character.
Change the locale of the server that is running SQL Server 2008 R2 Reporting Services or SQL Server 2012 Reporting Services to English.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.