TD-20891: SalReportPrintToFile to PDF

[aeintveld]

I have problems with PDF's in 6.2.
I have a test app created in 5.2 to create a PDF using SalReportPrintToFile.
This results in a 184Kb PDF that opens correctly.
Using the samen app and qrp on 6.2 creates a 654Kb pdf...
That in itself is strange, but the biggest issue is that te 6.2 is unreadable when send as an attachment and openend by a mac user.
I tried 6.1 as well: different size and also not readable.
I attached the source and screenshots.

Another problem is have with PDF is when a print multiple images to a report that the position the images are printed on the PDF is mixed up.
This is a real showstopper for moving from 5.2 to 6.2!

[Mike Vandine]

I've tried to run the attached application, but the program is looking for a QRP file:

Set lv_sQRP = 'TEST_Layout.QRP'

and the file supplied in the zip file is: VrachtA4.qrp

I tried using that file instead, but got a variable mismatch. Can you please supply the correct file?

BTW, have you running this with SP1 or production release of TD6.2?

[Dietmar]

We have the same problem.
We tried 6.2 without sp, and with sp1.
The problem is the same in both cases.

We have moved to 6.2 and did not recognize this problem in the beginning.
Now its too late to go back to 5.2 and we are in trouble with some customers.
So we really need a solution for this problem in the near future.

Dietmar Teich

[aeintveld]

Sorry for the QRP, here it is.

Hope you can help us!

Alexander

[Mike Vandine]

Yes, I can reproduce this problem.

I need to check into some things, but will get this reported.

Best regards,

[aeintveld]

Thanks, hope to hear from you.
I hope you can look into the issue with the wrong images.
A sample app is a bit more complicated, but i can send some sample output.

Alexander

[H3PO4]

Hi,

I tried some funny: Change the font of all items to Verdana -> the pdf file size will only be 242 kb.

- Verdana fontfile is smaller
- When choosing Arial, a subset of Arial Unicode is also embedded - no Unicode with Verdana, maybe this is one reason the pdf grows up so much with Arial?

Regards
Henning

[Dietmar]

Hi Mike,

i do not agree with you concerning the pdf problem on apple systems.
My son uses mac computers for a very long time and he NEVER saw these errors in pdf files created by other systems.
When printing invoices from our application to an external pdf printer the files are readable and printable on mac systems without problems.
When printing the same invoices with td functions the files are definitely not readable/printable on mac systems.

We are loosing customers because of this problem, and loosing customers means loosing money.
If you really say that gupta will definitely not fix this problem we will not be able to use team developer in the future.

Dietmar Teich

[H3PO4]

Hi Mike,

regarding to the Apple-Problem with pdf,

---
Regarding the PDF file not showing correctly when sending to MAC, I can reproduce this using a plain PDF file created outside of TD, so Engineering have said that this is NOT an issue with TD or Report Builder creating the file incorrectly.
---

Could you please give testcase how you can reproduce the unreadability of well formed PDF-Files on Apple Systems? That would be great.

I have the same problem Dietmar has, PDF-Files generated by Gupta's PDF-Generator are not readable on Apple-Computers, when I let the work do by e.g. PDFCreator on the same system, the file is readable on Apple-Computers.

Please help, printing PDF's directly is very important and will be more important in the near future. More and more companies are sending pdf's to their customers or let the paperwork do by another company.

Regards
Henning

[Mike Vandine]

Hi guys,

Hmmmm. I can't seem to reproduce this now.

So, I will again ask either of you for a repro case and I will log a bug.

Best regards,

[H3PO4]

Mike,

can you please define how the repro-case should look like? I could create a small app that prints a report a) to printer b) to file,
we are using PDFCreator when we are creating PDF-Files via printer.

And, it was no joke, when I asked:

Could you please give testcase how you can reproduce the unreadability of well formed PDF-Files on Apple Systems? That would be great.

I am very interested in this, because it could help me in writing a workaround.

Best regards
Henning

[Mike Vandine]

Hi Henning,

I went back to try to reproduce what I did before and everything worked perfectly! Grrrrr. So I have no testcase for you.

For your testcase:

Give me a a small app that produces a PDF file which doesn't transfer to an iPad.

Just a clarification of what is going wrong for you:

1. You use TD to create a PDF file and you send that to an Apple machine. > Garbage
2. You use TD that send the report to a 'printer' that is really PDFCreator and send that to an Apple machine. > Works fine

Is that what you are seeing?

Best regards,

[Dietmar]

Hi Mike,

here is a small testcase for pdf problem on apple systems.
It will create a pdf which gives a very strange print on apple computers (tested on OSX 10.9.2).
Preview of this pdf on the screen is ok, but printing is not readable.
I added a scanned print for the case that it looks different on your system.

With our software we also got pdf documents with unredable preview on the screen.
At the moment we cannot reproduce this behavior, but i hope that this problem has the same reason.

Testcase.zip

[Mike Vandine]

So a further clarification:

>>Preview of this pdf on the screen is ok, but printing is not readable.<<

1. You can preview it ON THE APPLE MACHINE but not print it. Is that right?

2. On a Windows machine you can both preview and print OK.

[Dietmar]

Yes, both correct.

Dietmar Teich