Bug 708190

Summary:	Empty embedded file
Product:	Ghostscript	Reporter:	Julien Brunet <jbrunet>
Component:	PDF Writer	Assignee:	Default assignee <ghostpdl-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	P2
Version:	10.04.0
Hardware:	PC
OS:	Linux
Customer:		Word Size:	---
Attachments:	To reproduce the issue

Description Julien Brunet 2024-12-12 09:52:41 UTC

Created attachment 26283 [details]
To reproduce the issue

Hello,
We are using gs to produce zugferd compliant .pdf files.
We used this page to help us build the command we are using to call gs : https://www.ghostscript.com/blog/zugferd.html

Everything was working great on 10.02 but now we have an issue on 10.04. The xml file attached to the pdf is empty and unnamed.

We followed this ticket and updated the zugferd.ps file used to make the process, but the result is still the same : https://bugs.ghostscript.com/show_bug.cgi?id=708066

I attache a example to reproduce the case.
Here is the command :

gs --permit-file-read=${PWD}/ -sDEVICE=pdfwrite -dPDFA=3 -sColorConversionStrategy=RGB -dPDFACompatibilityPolicy=1 -sZUGFeRDXMLFile=${PWD}/invoice.xml -sZUGFeRDProfile=${PWD}/rgb.icc -sZUGFeRDVersion=2p1 -sZUGFeRDConformanceLevel=BASIC -o ${PWD}/zugferd.pdf ${PWD}/zugferd.ps ${PWD}/original.pdf


For now, we found a solution with a rollback to the 10.02.


Thank in advance and have a good day !

Comment 1 Ken Sharp 2024-12-12 10:01:58 UTC

Works with current code. The /AF array is incorrect with 10.04.0, it needs this commit 5d9b000c70f66f5be7bfaed1f16ef4e50d820dc6 to generate the array correctly.

*** This bug has been marked as a duplicate of bug 708066 ***

Comment 2 Ken Sharp 2024-12-12 10:02:26 UTC

I forgot to say thanks for the comprehensive report, which made it much easier and faster to check.

Comment 3 Julien Brunet 2024-12-12 10:07:54 UTC

Thank you for your quick response. 
If I understand well, the correction will be in an future release ?

Comment 4 Ken Sharp 2024-12-12 10:09:10 UTC

(In reply to Julien Brunet from comment #3)
> Thank you for your quick response. 
> If I understand well, the correction will be in an future release ?

Yes it will be in the next release, currently expected to be 10.05.0 in March 2025.

Comment 5 Julien Brunet 2024-12-12 10:10:43 UTC

(In reply to Ken Sharp from comment #4)
> (In reply to Julien Brunet from comment #3)
> > Thank you for your quick response. 
> > If I understand well, the correction will be in an future release ?
> 
> Yes it will be in the next release, currently expected to be 10.05.0 in
> March 2025.

Nice, thank you !