Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Text overlay in generated PDF for field "Spezifikationskennung" #499

Closed
zeratools opened this issue Oct 2, 2024 · 2 comments · Fixed by #500
Closed

Text overlay in generated PDF for field "Spezifikationskennung" #499

zeratools opened this issue Oct 2, 2024 · 2 comments · Fixed by #500

Comments

@zeratools
Copy link
Contributor

zeratools commented Oct 2, 2024

Hello,

I generate a PDF from this UBL XRechnung XML file https://github.com/itplr-kosit/xrechnung-testsuite/blob/master/src/test/business-cases/standard/01.01a-INVOICE_ubl.xml
It's working fine except there is a text overlay at the end on the "Spezifikationskennung" field
See screen capture and full XML generated bellow.

This test is based on master branch code.

image
01.01a-INVOICE_ubl.xml.pdf

Best regards

@zeratools
Copy link
Contributor Author

zeratools commented Oct 2, 2024

After some research in the code base, this overlay is caused by the presence of both CustomizationID and ProfileID in the XML:

    <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</cbc:CustomizationID>
    <cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>

This section layout in PDF is 2 column but the URN used as ID are too long for tha
t display.
I provided a pull request to switch this section on single column layout #500

This is the result with the changes I made:
image
01.01a-INVOICE_ubl.xml.pdf

@jstaerk jstaerk closed this as completed in d00aa62 Oct 5, 2024
jstaerk added a commit that referenced this issue Oct 5, 2024
@jstaerk
Copy link
Collaborator

jstaerk commented Oct 5, 2024

thank you, merged, I hope it is non destructive :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants