1

After looking in my ZUGFeRD-PDF's metadata, I found out that iText# defined the wrong/old namespaceURI for ZUGFeRD in the PdfAXmpWriter.

The namspaceUri for zf is urn:ferd:pdfa:CrossIndustryDocument:invoice:1p0#which is correctly defined in the regular iText (for Java), but in iText# is defined urn:ferd:pdfa:invoice:1p0#

https://github.com/itext/itextpdf/blob/master/pdfa/src/main/java/com/itextpdf/text/xml/xmp/PdfAXmpWriter.java

https://github.com/itext/itextsharp/blob/master/src/extras/itextsharp.pdfa/iTextSharp/text/xml/xmp/PdfAXmpWriter.cs

Could you check this?

Vad1mo
  • 5,156
  • 6
  • 36
  • 65
AndreasGloeckner
  • 292
  • 3
  • 5
  • 18
  • 1
    Thanks. This actually isn't a question, but a bug report. I'll post it on our internal tracker. – Bruno Lowagie Apr 14 '16 at 14:09
  • I'm sorry, didn't know where to post it. For next time: Where do I have to open a ticket? – AndreasGloeckner Apr 14 '16 at 16:45
  • Only customers can create a ticket. That's why I created one for you. – Bruno Lowagie Apr 14 '16 at 21:23
  • Do I have a chance to change the namespaceURI by iText? I tried replacing the "PdfAXmpWriter.zugferdSchemaNS" through the correct namespaceURI, but an error occurs that says "Unregistered schema namespace URI". – AndreasGloeckner Apr 15 '16 at 06:48
  • I'm not sure if I understand the question. The best way to fix the problem is to correct the iText or iTextSharp code. Is that what you tried? Is this what causes the error? – Bruno Lowagie Apr 15 '16 at 07:00
  • Well that would have been an option, but I tried this way: `copy.XmpWriter.SetProperty("urn:ferd:pdfa:CrossIndustryDocument:invoice:1p0#", PdfAXmpWriter.zugferdDocumentFileName, "ZUGFeRD-invoice.xml");` `copy` is an instance of PdfCopy. – AndreasGloeckner Apr 15 '16 at 07:31
  • I know, but that's a "hack" and even if it works, it doesn't help other people with the same problem. It's better to remove the root cause of the problem. I see that the ticket was accepted and that it will be taken care of in the next sprint. – Bruno Lowagie Apr 15 '16 at 08:56
  • I was about to do that to solve this for me so far (hotfix) and wait for the next release. How shall **I** remove the root cause?^^ – AndreasGloeckner Apr 15 '16 at 09:37

0 Answers0