locked
PDF export with chinese character not recognised RRS feed

  • Question

  • We have "SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)" and SSRS server "Microsoft SQL Server Reporting Services Version 10.50.4000.0(Standard)".

    We created a report with chinese characters. While exporting to PDF/ Tiff image(Adobe tools), the chinese characters are not recognised, they are shown as squares. For other microsoft tools say Word, Excel the export works with chinese characters.

    We tried:

    1. Changing the fonts to MingLiu, Arial Unicode MS, MS Mincho etc etc all kinds of fonts

    2. We tried another PDF reader called "Foxit reader" as well as asian language pack

    3. Changed regional settings to Hong Kong as well as tried on separate machines(Win 7).

    4. We tried Report Builder 3.0 to generate the report also.

    5. Installed Chinese/ Korean language pack for Adobe Reader 9

    Not sure, what to be done next. Any other suggestions are highly welcomed. 

    regards

    joon




    • Edited by Joon84 Tuesday, May 21, 2013 10:29 AM
    Tuesday, May 21, 2013 9:23 AM

Answers

  • Thanks for your information.

    And we found the cause, our SQL team forgot to install something called "Microsoft SQL Server 2008 R2 Transsact-SQL Language Service" in the SQL server(so only SQL server 2008 R2 was installed).

    regards

    joon



    • Edited by Joon84 Thursday, May 23, 2013 2:25 PM
    • Proposed as answer by Charlie Liao Friday, May 24, 2013 1:10 AM
    • Marked as answer by Charlie Liao Tuesday, May 28, 2013 1:31 AM
    Thursday, May 23, 2013 12:58 PM

All replies

  • Hi Joon,

    I have tested it on my local environment, the PDF display Chinese characters correctly. For PDF the font must be present on your Operating System, so please ensure that you have installed the fonts. You can refer to the link below to see how to install fonts.
    http://www.microsoft.com/typography/truetypeinstall.mspx

    Hope this helps.

    Regards,
    Charlie Liao

    If you have any feedback on our support, please click here.


    Charlie Liao
    TechNet Community Support

    Wednesday, May 22, 2013 2:22 AM
  • Thanks for your information.

    And we found the cause, our SQL team forgot to install something called "Microsoft SQL Server 2008 R2 Transsact-SQL Language Service" in the SQL server(so only SQL server 2008 R2 was installed).

    regards

    joon



    • Edited by Joon84 Thursday, May 23, 2013 2:25 PM
    • Proposed as answer by Charlie Liao Friday, May 24, 2013 1:10 AM
    • Marked as answer by Charlie Liao Tuesday, May 28, 2013 1:31 AM
    Thursday, May 23, 2013 12:58 PM