[Bug 53912] New: PDF/A-1b compliance is broken in 1.1RC1

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=53912

          Priority: P2
            Bug ID: 53912
          Assignee: fop-dev@xmlgraphics.apache.org
           Summary: PDF/A-1b compliance is broken in 1.1RC1
          Severity: normal
    Classification: Unclassified
          Reporter: Oliver.Moehrke@web.de
          Hardware: PC
            Status: NEW
           Version: 1.1dev
         Component: pdf
           Product: Fop

While the patch for Bug #51270 fixed a PDF/A-1b compliance issue some time ago,
the actual v1.1RC1 breaks the PDF/A-1b compliance again.

Adobe Preflight 9.2.0 finds two new issues, if I use FOP v1.1RC1 instead of the
patched v1.0:

- CIDSet in subset font is incomplete (5 matches on 1 page)
- XMP property not predefined and no extension schema

I created a ready-to-run test-FO-file with a suitable configuration in the
attachment for v1.0, v1.0HF1 and v1.1RC1. I also added the resulting PDF-files
and the (german) reports of Adobe Preflight 9.2.0.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 53912] PDF/A-1b compliance is broken in 1.1RC1

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=53912

Mehdi Houshmand <me...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|                            |All

--- Comment #2 from Mehdi Houshmand <me...@gmail.com> ---
You haven't attached an FO, you've attached an XSL style-sheet without the
corresponding XML file.

I used PDFBox preflight and it came up with the following warnings:
7.1 : Error on MetaData, An error has occured when processing the underlying
XMP source
1.4.9 : Trailer Syntax error, Outline Hierarchy doesn't have Count entry

These warning don't seem to be the same as Acrobat Pro. I'll try running that
PDF in Acrobat Pro, but in the meantime could you attach the FO you used
please?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 53912] PDF/A-1b compliance is broken in 1.1RC1

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=53912

--- Comment #1 from Oliver.Moehrke@web.de ---
Created attachment 29402
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=29402&action=edit
FO-test-file, fonts and configuration to reproduce the non-compliant PDF/A-1b
output.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 53912] PDF/A-1b compliance is broken in 1.1RC1

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=53912

--- Comment #4 from Oliver Moehrke <Ol...@web.de> ---
Created attachment 29424
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=29424&action=edit
Updated FO test file.

I removed the XSL-part from "foptest.fo" so that this file can now be used with
the -fo option of fop.bat.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 53912] PDF/A-1b compliance is broken in 1.1RC1

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=53912

--- Comment #3 from Oliver.Moehrke@web.de ---
The provided "foptest.fo" from attachment 29402 is in fact a combination of an
XSL and an XSL-FO part to benefit from the <xsl:attribute-set> tag of XSL. In
Java, I use an identity transformer to produce the PDF output. On the
commandline I use the following to produce the PDF/A-1b output:

fop.bat -c conf\fop_conf.xml -xml foptest.fo -xsl foptest.fo -pdfa1b
foptest.pdf

The created output of FOP v1.1 RC1 produces the above stated two errors (see
foptest_11rc1_report.pdf - I translated the error messages for you).

To create a PDF/A-1b file that Adobe Preflight tests without errors from the
same "foptest.fo" you need to apply the patch from #51270 to the original v1.0
FOP source tree (see foptest_10hf1_report.pdf - no errors in here).

Other tools, like CABAReT Stage from Intarsys, warn about other issues (e.g.
EAAAAI+DroidSans and EAAAAJ+DroidSans-Bold do that do not have a valid metadata
entry). But these are only warnings.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 53912] PDF/A-1b compliance is broken in 1.1RC1

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=53912

Vincent Hennebert <vh...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |54038

-- 
You are receiving this mail because:
You are the assignee for the bug.