Boxes in PDF from Postscript

We have a PostScript files with with “FontBBox” and spaces elements, which result in the final PDF with boxes.

The conversion from PostScript to PDF is based on the default example and executed in the current version 26.5.
The attached file needs to be renamed to ps (I could only upload a pdf)

postscriptAnonymous.ps.pdf (1.3 MB)

@stud0r
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): PAGENET-913

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

Update — this is resolved. Posting for anyone who finds this thread from a search.

PAGENET-913 was fixed in Aspose.Page for .NET 26.8. Apologies for not coming back to this thread when it shipped.

PostScript text containing the affected accented character now converts to PDF as text instead of appearing as boxes.

Your code does not need to change — update the package and rebuild:

dotnet add package Aspose.Page

Release notes: Aspose.Page for .NET 26.8 Release Notes

If you still see the problem on 26.8 or later, post your input file and the full stack trace and we will take a look.

Dear @skolod
I have testet it with the latest Java version 26.9 and the issue still exists.
Could you please check again?
PostscriptAnonymous.ps.pdf (21.1 KB)

@stud0r

I’ve just tested conversion of initial postscriptAnonymous.ps, that was in your first post and the result is exellent. The “postscriptAnonymous.ps.pdf” file you’ve sent in the last post is not PS but PDF. So I may conclude that you sent me the resulting PDF. But it’s not the result of conversion with Aspose.Page for Java 26.9, because I’ve just downloaded JAR from Aspose Repository Browser /java/repo/com/aspose/aspose-page/26.9/ and run the test app against initial PS file.
postscriptAnonymous.pdf (22.9 KB)

Hi @skolod
Sorry my bad, the Test-PDF was not regenerated.
If I regenerate it with version 26.9, it looks good.
Thank you!

@stud0r
No worries at all — mistakes happen!