1. RAJESH POOJARI
  2. PowerBuilder
  3. Monday, 29 April 2019 12:05 PM UTC
Hi,
 
Query rgd issue Adobe font embeding : Identity-H
 
This issue started popping after upgrade "Powerbuilder 12.6" to "Powerbuilder V2017 R3 Build 1880"
 
Our powerbuilder application generate Adobe PDF file via older version Rich Text Edit Control.
 
Powerbuilder build s/w version 12.6 with below combination List was - Working Fine
1. Windows7
2. Acrobat version XI

New Powerbuilder build s/w version 2017  R3 Build 1880 with below combination List- creating issue – Identity-H
1. Windows10
2. Acrobat version 2017
 

Does anything has changed in Powerbuilder 2017  vR3 Build 1880 the way it works with
Acrobat version XI vs Acrobat version 2017 ...?

Thanks,
Rajesh
Attachments (1)
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 2 May 2019 14:55 PM UTC
  2. PowerBuilder
  3. # 1

You are comparing Windows 7 to Windows 10.  It may not be a difference between PB 12.6 and PB 2017 but rather something that is Windows 10 specific.  It could be either bug or incompatibility on the PowerBuilder side or Adobe side.  But you can't narrow that down which product unless you use the exact same environment to test the PB 12.6 and PB 2017 apps.  

Comment
  1. RAJESH POOJARI
  2. Monday, 6 May 2019 16:47 PM UTC
Hi Armeen,



Yes agree issue could be "Adobe Acrobat 2017" or "Windows10"



Powerbuilder version 12.6 executed below test combination

Test#1: Windows7 and Adobe Acrobat ver XI -> Works Fine

Test#2: Windows10 and Adobe Acrobat ver 2017 -> Font Issue "Identity-H"



Powerbuilder version 2017 R3 MR02 executed below test combination

Test#1: Windows7 and Adobe Acrobat ver XI -> Works Fine

Test#2: Windows10 and Adobe Acrobat ver 2017 -> Font Issue "Identity-H"



Discussion going on with Adobe Team to resolve the issue.....

Will update you....



Thanks

Rajesh
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Monday, 6 May 2019 17:03 PM UTC
I would also try testing Acrobat version 2017 on Windows 7 to see if that works or not. You want to only have one variable and control the other things.
  1. Helpful
There are no comments made yet.
RAJESH POOJARI Accepted Answer Pending Moderation
  1. Thursday, 2 May 2019 14:17 PM UTC
  2. PowerBuilder
  3. # 2

Hi Chris,

As advice by you we trying to get touch with Adobe to determine resolution for Font Issue - Identity-H

If Adobe has any querys rgd Appeon PowerBuilder will touch base with you...

Thanks for guidance.

Rajesh

 

 

Comment
  1. Chris Pollach @Appeon
  2. Monday, 6 May 2019 16:52 PM UTC
Hi Rajesh;

Thank you for keeping use up-to-date on your dealings with Adobe! I am sure that other PB developers will be interested on the final solution to this problem.

Regards ... Chris
  1. Helpful
There are no comments made yet.
RAJESH POOJARI Accepted Answer Pending Moderation
  1. Monday, 29 April 2019 19:01 PM UTC
  2. PowerBuilder
  3. # 3
Hi Chris,

I have switched PB2017R3 MR02 to older TX Control.
Now the older TX Control blob data creation works fine.
But the problem we are facing while generating Adobe PDF file with printdatawindow().
It does create Adobe PDF file but with Font encoding issue like "Identity-H"

My Question 
Does anything has changed in Powerbuilder 2017  R3 MR02 the way it works with
Acrobat version XI vs Acrobat version 2017 ...??
 
Powerbuilder 2017  vR3 Build 1880  works Fine Adobe version XI but does'not work properly with Adobe version 2017.

Thanks,
Rajesh
 
 
 
 
 
 
Comment
  1. Chris Pollach @Appeon
  2. Monday, 29 April 2019 19:28 PM UTC
Hi Rajesh;

I am glad that the TX setting with PB2017R3 now behaves the same as PB 12.6 with Adobe XI. At least we now know that the TE control does not. The big question now could be: "What are the technical differences between Adobe XI and 2017"? That is what I do not know. This might be worth discussing with Adobe. Also, maybe opening up a Support Ticket with Appeon.

The only work around that I can think of at the moment might be to try a RTE DataWindow instead of the RTE control. That is on the PDF generation - copy the RTF datum into a the DWO and perform a SaveAs() from there.. The DW now has other PDF generation features like the "NativePDF" feature that might work better. Food for thought.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 29 April 2019 18:39 PM UTC
  2. PowerBuilder
  3. # 4

Hi Rajesh;

   Yes, Appeon PB2017 by default was using the new TE 3rd party control under-the-hood. Since PB2017R3 MR02, the PB IDE comes with both the older TX Control and the new TE Control. Either one can be used for the RTE Control support & PDF generation.

   PB 12.6 defaulted to the TX Control. You can see what your App is using by opening up the Application Painter => Additional Properties => RichText tab page. If the selection is "built-in" - then its the TE control. Try switching to the TX Control if the TE control is defaulted to return back to the PB 12.6 processing mode and see if that helps.

Regards ... Chris

Comment
  1. RAJESH POOJARI
  2. Monday, 6 May 2019 16:43 PM UTC
Hi Chris,



Apologize for not getting back to earlier...

As per your Advice pulled in Adobe Team and they are still looking in to the Issue.



Powerbuilder version 12.6 executed below test combination

Test#1: Windows7 and Adobe Acrobat ver XI -> Works Fine

Test#2: Windows10 and Adobe Acrobat ver 2017 -> Font Issue "Identity-H"



Powerbuilder version 2017 R3 MR02 executed below test combination

Test#1: Windows7 and Adobe Acrobat ver XI -> Works Fine

Test#2: Windows10 and Adobe Acrobat ver 2017 -> Font Issue "Identity-H"



Adobe Team suggested few "adobe printer properties" which has not resolved our issue.



We are expecting new suggestion from Adobe Team to resolve the issue...

Will update you promptly in future.



Thanks for Checking.

Rajesh
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.