locked
PDF export: characters above 127 not displaying for Wingdings RRS feed

  • Question

  • Hello,
    I have 2008 SP1 CTP and using Report Builder 2.  If I put a text box with Wingdings font on the report, all Wingdings symbols with character values below 127 will display correctly when that report is exported to PDF.  All those above 127 (like the arrows starting at 223) do not (an empty box appears instead.)

    When I look at the PDF properties inside Acrobat Reader 8, and I go to the "Fonts" tab, I can see that Wingdings is "embedded subset" with encoding "ANSI".

    Is there anything I can do to get the characters above 127 to display correctly?

    Thank you,
    Bill
    Thursday, March 12, 2009 1:24 PM

Answers

  • Hi Bill,

    This looks like a bug in our PDF Renderer. I tried it without font embedding as well and the characters are still not displayed correctly in Acrobat Reader. 

    I also tried the Word PDF Exporter and the resulting PDF document displays the characters above 127 just fine. They actually wrote them out using Glyph IDs (CID font) even though the characters are in the ANSI range. We will have to do the same for the PDF Renderer.

    If you can file thus bug using https://connect.microsoft.com/SQLServer then we will keep you updated on when it will be fixed. Thanks for reporting this issue and sorry for the inconvenience it caused.

    Best regards,
    Andre
    • Marked as answer by BillVienna Tuesday, April 7, 2009 11:59 AM
    Monday, April 6, 2009 5:43 PM
    Answerer

All replies

  • Just a little note to "bump" this.  I'm wondering if anybody has successfully shown Wingdings above chr(127) in PDFs of reports.
    Tuesday, March 17, 2009 3:09 PM
  • Well, I guess the answer is that it doesn't work.

    I note that if I put these Wingding characters in to an OpenOffice Writer document and use their export to pdf feature, it works and, when viewing File-Properties from inside Acrobat, the "Fonts" tab shows that the "encoding" for the embedded Wingdings font is "Built-in".  Those pdfs exported from SSRS show "Ansi" in PDF as the encoding used for the embedded Wingdings font.

    Anything I can do to get the encoding for the embedded fonts working like it does with OpenOffice Writer?
    Tuesday, March 24, 2009 4:19 PM
  • One last try...  I guess it's not possible? 
    Monday, April 6, 2009 1:31 PM
  • Okie, make sure that the Font Is present Both at the server and the client Side.
    ~~ Mark it as Answer if you find it correct~~
    Monday, April 6, 2009 4:21 PM
  • Hi Bill,

    This looks like a bug in our PDF Renderer. I tried it without font embedding as well and the characters are still not displayed correctly in Acrobat Reader. 

    I also tried the Word PDF Exporter and the resulting PDF document displays the characters above 127 just fine. They actually wrote them out using Glyph IDs (CID font) even though the characters are in the ANSI range. We will have to do the same for the PDF Renderer.

    If you can file thus bug using https://connect.microsoft.com/SQLServer then we will keep you updated on when it will be fixed. Thanks for reporting this issue and sorry for the inconvenience it caused.

    Best regards,
    Andre
    • Marked as answer by BillVienna Tuesday, April 7, 2009 11:59 AM
    Monday, April 6, 2009 5:43 PM
    Answerer
  • Thank you, Andre.  For all of you who might come across this in the future: I filed it as feedback id 431057
    Tuesday, April 7, 2009 12:23 PM
  • I believe I have encountered the same problem in a wpf application using the winforms reportviewer. This report shows a pass / fail status and I am using wingdings font with  chr(0252) to display a tick and chr(0251) to display a cross. This works really well in the report and for sending to a printer, but when exported to pdf both the characters turn info small dots - not really acceptable for our users.

    Has there been any update or resolution to this issue? I notice the connect.microsoft.com article marks it as closed, fixed - how do I obtain the fix for winforms reportviewer?

    Thanks for any help.

    Tim

    Monday, October 11, 2010 10:35 AM
  • Hi,

    I faced the samilar issue with Chinese locale. Then i fixed that issue by installing Chinese language on server (where SQL reporting services are running).

    Also same issue fixed by installing SQL CU6 update (without installing language pack). Here is the link for that update http://support.microsoft.com/kb/2489376

    Thanks, Rahul Techie.
    • Proposed as answer by Rahul Techie Thursday, April 7, 2011 9:15 AM
    Wednesday, March 30, 2011 5:18 AM