PDF/A-3 support, validation fails about birt

[merks]

Here are reports that show for which things there are major updates:

• https://github.com/eclipse-orbit/orbit-simrel/blob/main/report/maven-bnd/merged-target/REPORT.md
• https://github.com/eclipse-orbit/orbit-simrel/blob/main/report/maven-osgi/merged-target/REPORT.md

I don't generally add them if there is no explicit request. Shall I add this one?

https://repo1.maven.org/maven2/com/github/librepdf/openpdf/2.0.2/

It's actually only a month newer. We won't know what if anything is broken until we try to use it...

[merks]

I’ll handle it tomorrow. Nothing else is required.

[merks]

FYI, generally BIRT is always using the latest dependencies, here in tabular format:

https://download.eclipse.org/tools/orbit/simrel/orbit-aggregation/table.html

So currently this version:

Orbit updates to the latest version available from Maven Central semi-automatically...

To see what's definitely there now, you can use the Repository Explorer in advanced mode:

[hvbtup]

Hmm, that answers my first question. At least in theory, because I get the same error from a PDF generated with a BIRT release that still uses OpenPDF 1.3.0.

[speckyspooky]

The latest version of openPDF is version 2.0.2 but I don't know whether the release containce the fix.
Or if there an option to set the CIDSet then of course we can add a new user property.

[merks]

Orbit doesn’t generally update to new major versions because they are assumed to break API. But it could provide both.

[speckyspooky]

Yes, I request the change to the newer version.
Please let me know when I can support to open a ticket for Orbit.

[hvbtup]

I didn't find a clear explanation about the differences between the 1.3.x, 1.4.x and 2.0.x releases of OpenPDF, except that the require Java 8, Java 11 and Java 17. Since BIRT itself now requires Java 17, we should use 2.0.x.

@speckyspooky Probably, if you are going to add support for PDF/A-3 in the PDF emitter, then for PDF/A-3 (opposed to PDF/A-1), you need to call the new API font.setIncludeCidSet(false); for each font. The documentation says

/**
 * Indicates if a CIDSet stream should be included in the document for {@link TrueTypeFontUnicode}.
 * When set to <CODE>true</CODE>, a CIDSet stream will be included in the document.
 * When set to <CODE>false</CODE>, and {@link PdfWriter#getPDFXConformance()} does not require it,
 * no CIDSet stream will be included.
 *
 * @param includeCidSet new value of {@link BaseFont#includeCidSet}
 */

Not sure about PDF/A-2, but I think it should work like PDF/A-3.

[merks]

If you re-resolve the target platform (Help -> Perform Setup Tasks...) today it will contain the 2.0.2 version. It does not cause any compile errors.

I'm currently investigating this issue which blocks publishing any new master builds:

#1819

[merks]

FYI, my local Tycho build with 2.0.2 was successful.

[merks]

The latest nightly build is using 2.0.2: