tracker issue : CF-3127827

select a category, or use search below
(searches all categories and all time range)
Title:

Special Unicode characters not rendered in pdf documentd

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/

Reporter/Name(from Bugbase): Claude Schnéegans / Claude Schnéegans (Claude)

Created: 03/01/2012

Components: Document Management

Versions: 9.0.1

Failure Type:

Found In Build/Fixed In Build: 9.0.1 /

Priority/Frequency: Major / All users will encounter

Locale/System: English / Win XP All

Vote Count: 0

Problem Description: CFDOCUMENT into pdf including special characters like † or † are not endered.

Steps to Reproduce: CFDOCUMENT into pdf including special characters like † or †

Actual Result: characters not rendered

Expected Result:characters should be rendered



Any Workarounds: none

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3127827

External Customer Info:
External Company:  
External Customer Name: Claude
External Customer Email:  
External Test Config: My Hardware and Environment details: Windows 7, CF 9.01

Attachments:

  1. March 03, 2012 00:00:00: 1_testPDF.ZIP

Comments:

I am can see the characters are rendered when I try this <cfdocument format="PDF" > pdf including special characters like &dagger; or &#8224 </cfdocument> Is your scenario different? (Comment added from ex-user id:evelinv)
Comment by Adobe D.
20446 | March 02, 2012 06:01:36 AM GMT
OK, here is a test file that will illustrate problems CF-3127840 and CF-3127807. It also contains &dagger; or &#8224;, but in this simple environment it seems to be working indeed. I'll check further why it is not in my code. Thanks.
Comment by External U.
20447 | March 02, 2012 02:41:28 PM GMT
Hi, I finally found why the dagger didn't show. During the process I have a Javascript function supposed to retrieve document.body.innerHTML. The whole HTML is returned correct exept that representation of unicode characters like &dagger; are not return as such but as unicode values, so that the character is lost for the rest of the process. I was able to work aoround this, and now it works beautyfully. So, you can cancel this bug, but there still are the two others (greyscale and margin) Thanks.
Comment by External U.
20448 | March 02, 2012 06:34:35 PM GMT