Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Bad quality NativePDF

  1. Issue
0
Votes
Undo
  1. Roy Bungert
    Roy Bungert
  2. PowerBuilder
  3. Wednesday, 19 July 2017 13:33 PM UTC

One of our major reasons to switch to PB2107 was that we can get rid of Ghostscript.  After we made our first tests with NativePDF we are very disappointed: The quality of the PDF created via NativePDF is very bad compared with the one created via Ghostscript.

I hope that the fault is on our side and there are some settings which we didn't saw until now.  Are there any special parameters for making the qualilty of the output better?

 A lot of our customers have a jpg in the header of their invoices. With JPGs (in picture controls) you can see significant differences in the quality. 

You can reproduce that with every JPG (which has a certain quality).

One other point is that the size of customfonts like barcode is different between Ghostscript an NativePDF (nearly the half).

The current setting in our ob.ini:

[Data Window]
NativePDF_Valid=1
NativePDF_IncludeCustomFont=1

I hope that somebody can give me a solution for make the quality better. Perhaps: NativePDF_Quality=HIGH

 

Thank you

Roy

  1. PDF
  2. NativePDF
  3. Script
How to execute VB Script when PB app compiled in 6...
Why are both msvcp80.dll and msvcp100.dll needed f...
Responses (3)
Roy Bungert
Roy Bungert Accepted Answer Pending Moderation
  1. Thursday, 20 July 2017 07:07 AM UTC
  2. PowerBuilder
  3. # 1

Is there any easy way to install Ghostscript on Windows10 without signing the driver? Or is there a signed Ghostscript-Driver anywhere?

Until today we do it in this way (Thanks to Chris), which not so easy to manage for our customers:

https://blogs.sap.com/2015/08/26/installing-ghostscript-for-powerbuilder-on-windows-10/

 

Comment
Patrick Sohr
  1. Patrick Sohr
  2. Monday, 24 July 2017 07:37 AM UTC
You can install the newest gs version in 32 bit and copy it over the 8.71 version. After you have done this, create the Sybase DataWindow PS printer and use an actual PS Driver from HP (like the HP Color LaserJet 2800 Series PS or a different one with PS ... sometime you need to try more then one). I know this is not an "easy way" but if you are not able to re-start the computer or don't want to allow unsigned drivers then that is a possible solution.  

  1. Helpful
There are no comments made yet.
Ashutosh Varshney
Ashutosh Varshney Accepted Answer Pending Moderation
  1. Wednesday, 19 July 2017 16:16 PM UTC
  2. PowerBuilder
  3. # 2

I believe this is a bug with PB2017 and Appeon is in the process for fixing it. 

https://www.appeon.com/standardsupport/search/view?id=213

 

Comment
Daniel Vivier
  1. Daniel Vivier
  2. Wednesday, 19 July 2017 21:44 PM UTC
Standard fonts (like Arial), especially boldface, are also a bit fuzzier in NativePDF than in the standard 3rd-party PDF printer.

  1. Helpful
Ashutosh Varshney
  1. Ashutosh Varshney
  2. Thursday, 20 July 2017 14:23 PM UTC
Dan,



You should open a support ticket with Appeon. I am sure they will really appreciate the feedback. https://www.appeon.com/standardsupport/

  1. Helpful
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Wednesday, 19 July 2017 14:30 PM UTC
  2. PowerBuilder
  3. # 3

I hope someone has an answer for this, you aren't the first to have this issue.

I would like to repeat something I said recently. All instances of the pb.ini file being used to control runtime behaviors should be eliminated and replaced by a well documented function call so that it can be added to application code. Perhaps something like this:

SetProgramOption ( optionname, optionvalue )

 

Comment
Andreas Mykonios
  1. Andreas Mykonios
  2. Wednesday, 19 July 2017 14:42 PM UTC
Hi Chris.



This is a great point. Pb.ini is also confusing, as we don't know if it is necessary to deploy it with the application (in this case it should be). I usually don't deploy it with my applications! As you speak of well documented functions, I have to add that SAP added some options to recent releases of powerbuilder that are also not documented (I can give an example). As they are not documented in PowerBuilder 2017, we don't know a) if they are included in Powerbuilder 2017, b) if they are in Powerbuilder 2017 we cannot use them as they may be documented only in SAP KBA articles. And here is another question... Does Appeon have access to those KBA Articles? They will be migrated to some Appeon subsystem?



Finally, about the pdf issue mentioned in the original message, we are still using GhostScript or PDF Creator. The issue about poor quality when using NativePDF with images is mentioned I believe in Appeon's Bulletin as a known issue.



Andreas.

  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.