Hi Thirumani, As planned we start preparing the release now. So, we expect it will be out yet in January.

It has already been in the pre-release stage since mid-December.

Best regards, Boris

From: thirumani t thirumani@gmail.com Sent: Wednesday, January 13, 2021 7:23 PM To: Boris Doubrov boris.doubrov@duallab.com Cc: users@lists.verapdf.org Subject: Re: [veraPDF-users] Info on Release of verapdf-greenfield-2.0.59-installer.zip

Hi Team,

With regards to this email chain, could you please let me know the timeline planned for the release of version 2.0.59 and above?

Thanks in advance.

Thanks & Regards, Thirumani

On Tue, Sep 1, 2020 at 4:56 PM Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> wrote: Hi Thirumani,

There were indeed several fixes related to the use of .notdef glyphs. If you could submit the document9s) in question, we could verify if indeed there was an issue in 1.12.1, which is now fixed.

Would you also check the latest stable release of veraPDF, which is 1.16.1 at the moment?

We do tentatively plan to release the new version of veraPDF by the end of 2020 or early 2021.

Best regards, Boris

From: Users <users-bounces@lists.verapdf.orgmailto:users-bounces@lists.verapdf.org> On Behalf Of thirumani t Sent: Monday, August 31, 2020 8:31 PM To: users@lists.verapdf.orgmailto:users@lists.verapdf.org Subject: [veraPDF-users] Info on Release of verapdf-greenfield-2.0.59-installer.zip

Hi Team,

We are using the verapdf tool for checking PDFA compliance. Currently we are using version 1.12.1 and that reports the below error. While analyzing we noticed that this error is not being reported in the latest development version 2.0.59. So we are wondering if this is being reported incorrectly in the version 1.12.1 and has been fixed in the latest development version. Can you confirm if that is the case and also let us know if there is any tentative timeline on when you are planning to release the next version and will that be as that of a build after version 2.0.59?

6.2.11.8-1 - A PDF/A-2 compliant document shall not contain a reference to the .notdef glyph from any of the text showing operators, regardless of text rendering mode, in any content stream

Thanks & Regards, Thirumani

Hi Thirumani,

The numbers 2.0.* were used for the development version with PDF/UA-1 support. In the end this version was released as 1.18, as in fact there were no interface breaks.

I do understand this might be a bit confusing, but yes, the closest release for 2.0.59 is 1.18.6.

Best regards, Boris

From: thirumani t thirumani@gmail.com Sent: Wednesday, June 2, 2021 4:25 PM To: Boris Doubrov boris.doubrov@duallab.com Cc: users@lists.verapdf.org Subject: Re: [veraPDF-users] Info on Release of verapdf-greenfield-2.0.59-installer.zip

Hi Team,

With regards to this email chain, it looks like version 2.0.59 is still not released. Could you please let me know the timeline planned for the release of version 2.0.59 and above?

Thanks in advance.

Thanks & Regards, Thirumani

On Fri, Jan 15, 2021 at 12:16 PM Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> wrote: Hi Thirumani, As planned we start preparing the release now. So, we expect it will be out yet in January.

It has already been in the pre-release stage since mid-December.

Best regards, Boris

From: thirumani t <thirumani@gmail.commailto:thirumani@gmail.com> Sent: Wednesday, January 13, 2021 7:23 PM To: Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> Cc: users@lists.verapdf.orgmailto:users@lists.verapdf.org Subject: Re: [veraPDF-users] Info on Release of verapdf-greenfield-2.0.59-installer.zip

Hi Team,

With regards to this email chain, could you please let me know the timeline planned for the release of version 2.0.59 and above?

Thanks in advance.

Thanks & Regards, Thirumani

On Tue, Sep 1, 2020 at 4:56 PM Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> wrote: Hi Thirumani,

There were indeed several fixes related to the use of .notdef glyphs. If you could submit the document9s) in question, we could verify if indeed there was an issue in 1.12.1, which is now fixed.

Would you also check the latest stable release of veraPDF, which is 1.16.1 at the moment?

We do tentatively plan to release the new version of veraPDF by the end of 2020 or early 2021.

Best regards, Boris

From: Users <users-bounces@lists.verapdf.orgmailto:users-bounces@lists.verapdf.org> On Behalf Of thirumani t Sent: Monday, August 31, 2020 8:31 PM To: users@lists.verapdf.orgmailto:users@lists.verapdf.org Subject: [veraPDF-users] Info on Release of verapdf-greenfield-2.0.59-installer.zip

Hi Team,

We are using the verapdf tool for checking PDFA compliance. Currently we are using version 1.12.1 and that reports the below error. While analyzing we noticed that this error is not being reported in the latest development version 2.0.59. So we are wondering if this is being reported incorrectly in the version 1.12.1 and has been fixed in the latest development version. Can you confirm if that is the case and also let us know if there is any tentative timeline on when you are planning to release the next version and will that be as that of a build after version 2.0.59?

6.2.11.8-1 - A PDF/A-2 compliant document shall not contain a reference to the .notdef glyph from any of the text showing operators, regardless of text rendering mode, in any content stream

Thanks & Regards, Thirumani

Hi Thirumani,

I see that these reports differ a lot. The issue with .notdef is just one difference. But, for example, version 1.18.6 reports:

* 15280 occurrences of prohibited use of DeviceCMYK * 41216 occurrences of prohibited use of DeviceRGB * 10640 occurrences of prohibited use of DeviceGray

At the same time version 2.0.59 is reporting only a single error on DeviceCMYK and none on DeviceRGB and DeviceGray. So, the only idea is that probably the development version 2.0.59 was doing something completely incorrect.

Unfortunately, I can’t say whether the error on the use of .notdef character is a false negative or not without inspecting a test document. So, for the moment I can only suggest that you either compare releases 1.16 and 1.18 or sequentially compare all dev versions and find out when exactly this error with .notdef character appears on your document. Then we could probably trace the relevant code changes and double check them.

Best regards, Boris

From: thirumani t thirumani@gmail.com Sent: Thursday, June 3, 2021 7:19 AM To: Boris Doubrov boris.doubrov@duallab.com Cc: users@lists.verapdf.org Subject: Re: [veraPDF-users] Info on Release of verapdf-greenfield-2.0.59-installer.zip

Thanks Boris for the quick response. I compared the results of version 2.0.59 which is not yet released and the version 1.18.6 that was released as you requested. Please find attached the reports using the PDF that I was testing.

The issue which I was specifically looking for is "A PDF/A-2 compliant document shall not contain a reference to the .notdef glyph from any of the text showing operators, regardless of text rendering mode, in any content stream." If you look at the report for 2.0.59, this issue isn't reported, but the released version 1.18.6 reports the issue.

Could you please let me know why this difference in the validation results. When we did the analysis earlier, since the issue wasn't reported in version 2.0.59, we thought it was a false positive in the version 1.12.1 that we are currently using. Hence was waiting for version 2.0.59 to be released.

Would appreciate if you can clarify this and let us know when the fix for handling this issue in version 2.0.59 will be released.

Unfortunately because of data sensitivity I will not be able to share the PDF with you.

Thanks & Regards, Thirumani

On Wed, Jun 2, 2021 at 7:29 PM Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> wrote: Hi Thirumani,

The numbers 2.0.* were used for the development version with PDF/UA-1 support. In the end this version was released as 1.18, as in fact there were no interface breaks.

I do understand this might be a bit confusing, but yes, the closest release for 2.0.59 is 1.18.6.

Best regards, Boris

From: thirumani t <thirumani@gmail.commailto:thirumani@gmail.com> Sent: Wednesday, June 2, 2021 4:25 PM To: Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> Cc: users@lists.verapdf.orgmailto:users@lists.verapdf.org Subject: Re: [veraPDF-users] Info on Release of verapdf-greenfield-2.0.59-installer.zip

Hi Team,

With regards to this email chain, it looks like version 2.0.59 is still not released. Could you please let me know the timeline planned for the release of version 2.0.59 and above?

Thanks in advance.

Thanks & Regards, Thirumani

On Fri, Jan 15, 2021 at 12:16 PM Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> wrote: Hi Thirumani, As planned we start preparing the release now. So, we expect it will be out yet in January.

It has already been in the pre-release stage since mid-December.

Best regards, Boris

From: thirumani t <thirumani@gmail.commailto:thirumani@gmail.com> Sent: Wednesday, January 13, 2021 7:23 PM To: Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> Cc: users@lists.verapdf.orgmailto:users@lists.verapdf.org Subject: Re: [veraPDF-users] Info on Release of verapdf-greenfield-2.0.59-installer.zip

Hi Team,

With regards to this email chain, could you please let me know the timeline planned for the release of version 2.0.59 and above?

Thanks in advance.

Thanks & Regards, Thirumani

On Tue, Sep 1, 2020 at 4:56 PM Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> wrote: Hi Thirumani,

There were indeed several fixes related to the use of .notdef glyphs. If you could submit the document9s) in question, we could verify if indeed there was an issue in 1.12.1, which is now fixed.

Would you also check the latest stable release of veraPDF, which is 1.16.1 at the moment?

We do tentatively plan to release the new version of veraPDF by the end of 2020 or early 2021.

Best regards, Boris

From: Users <users-bounces@lists.verapdf.orgmailto:users-bounces@lists.verapdf.org> On Behalf Of thirumani t Sent: Monday, August 31, 2020 8:31 PM To: users@lists.verapdf.orgmailto:users@lists.verapdf.org Subject: [veraPDF-users] Info on Release of verapdf-greenfield-2.0.59-installer.zip

Hi Team,

We are using the verapdf tool for checking PDFA compliance. Currently we are using version 1.12.1 and that reports the below error. While analyzing we noticed that this error is not being reported in the latest development version 2.0.59. So we are wondering if this is being reported incorrectly in the version 1.12.1 and has been fixed in the latest development version. Can you confirm if that is the case and also let us know if there is any tentative timeline on when you are planning to release the next version and will that be as that of a build after version 2.0.59?

6.2.11.8-1 - A PDF/A-2 compliant document shall not contain a reference to the .notdef glyph from any of the text showing operators, regardless of text rendering mode, in any content stream

Thanks & Regards, Thirumani

Hi Thirumani,

We have verified that indeed we had a bug in versions from 2.0.35 to 2.0.63 (fixed in 2.0.64) which could result in missing checks performed for some graphics elements. This probably explains your case.

So, I would say that the released version 1.18 is correct and your documents most likely have the issue with the .notdef glyph. Of course, I can’t be sure without seeing the PDF documents in question.

Best regards, Boris

From: thirumani t thirumani@gmail.com Sent: Saturday, June 5, 2021 10:16 AM To: Boris Doubrov boris.doubrov@duallab.com Cc: users@lists.verapdf.org Subject: Re: [veraPDF-users] Info on Release of verapdf-greenfield-2.0.59-installer.zip

Hi Boris,

I checked the versions and found the below issue which I was analyzing is getting reported up until the development version 2.0.34 and isn't reported from version 2.0.35. Also all released versions are reporting this issue. I would appreciate if you can look at the differences between versions 2.0.34 and 2.0.35 and let me know what went in to the version 2.0.35 that wouldn't report this issue.

A PDF/A-2 compliant document shall not contain a reference to the .notdef glyph from any of the text showing operators, regardless of text rendering mode, in any content stream.

Thanks in advance.

Thanks & Regards, Thirumani

On Thu, Jun 3, 2021 at 6:47 PM Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> wrote: Hi Thirumani,

I see that these reports differ a lot. The issue with .notdef is just one difference. But, for example, version 1.18.6 reports:

* 15280 occurrences of prohibited use of DeviceCMYK * 41216 occurrences of prohibited use of DeviceRGB * 10640 occurrences of prohibited use of DeviceGray

At the same time version 2.0.59 is reporting only a single error on DeviceCMYK and none on DeviceRGB and DeviceGray. So, the only idea is that probably the development version 2.0.59 was doing something completely incorrect.

Unfortunately, I can’t say whether the error on the use of .notdef character is a false negative or not without inspecting a test document. So, for the moment I can only suggest that you either compare releases 1.16 and 1.18 or sequentially compare all dev versions and find out when exactly this error with .notdef character appears on your document. Then we could probably trace the relevant code changes and double check them.

Best regards, Boris

From: thirumani t <thirumani@gmail.commailto:thirumani@gmail.com> Sent: Thursday, June 3, 2021 7:19 AM To: Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> Cc: users@lists.verapdf.orgmailto:users@lists.verapdf.org Subject: Re: [veraPDF-users] Info on Release of verapdf-greenfield-2.0.59-installer.zip

Thanks Boris for the quick response. I compared the results of version 2.0.59 which is not yet released and the version 1.18.6 that was released as you requested. Please find attached the reports using the PDF that I was testing.

The issue which I was specifically looking for is "A PDF/A-2 compliant document shall not contain a reference to the .notdef glyph from any of the text showing operators, regardless of text rendering mode, in any content stream." If you look at the report for 2.0.59, this issue isn't reported, but the released version 1.18.6 reports the issue.

Could you please let me know why this difference in the validation results. When we did the analysis earlier, since the issue wasn't reported in version 2.0.59, we thought it was a false positive in the version 1.12.1 that we are currently using. Hence was waiting for version 2.0.59 to be released.

Would appreciate if you can clarify this and let us know when the fix for handling this issue in version 2.0.59 will be released.

Unfortunately because of data sensitivity I will not be able to share the PDF with you.

Thanks & Regards, Thirumani

On Wed, Jun 2, 2021 at 7:29 PM Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> wrote: Hi Thirumani,

The numbers 2.0.* were used for the development version with PDF/UA-1 support. In the end this version was released as 1.18, as in fact there were no interface breaks.

I do understand this might be a bit confusing, but yes, the closest release for 2.0.59 is 1.18.6.

Best regards, Boris

From: thirumani t <thirumani@gmail.commailto:thirumani@gmail.com> Sent: Wednesday, June 2, 2021 4:25 PM To: Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> Cc: users@lists.verapdf.orgmailto:users@lists.verapdf.org Subject: Re: [veraPDF-users] Info on Release of verapdf-greenfield-2.0.59-installer.zip

Hi Team,

With regards to this email chain, it looks like version 2.0.59 is still not released. Could you please let me know the timeline planned for the release of version 2.0.59 and above?

Thanks in advance.

Thanks & Regards, Thirumani

On Fri, Jan 15, 2021 at 12:16 PM Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> wrote: Hi Thirumani, As planned we start preparing the release now. So, we expect it will be out yet in January.

It has already been in the pre-release stage since mid-December.

Best regards, Boris

From: thirumani t <thirumani@gmail.commailto:thirumani@gmail.com> Sent: Wednesday, January 13, 2021 7:23 PM To: Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> Cc: users@lists.verapdf.orgmailto:users@lists.verapdf.org Subject: Re: [veraPDF-users] Info on Release of verapdf-greenfield-2.0.59-installer.zip

Hi Team,

With regards to this email chain, could you please let me know the timeline planned for the release of version 2.0.59 and above?

Thanks in advance.

Thanks & Regards, Thirumani

On Tue, Sep 1, 2020 at 4:56 PM Boris Doubrov <boris.doubrov@duallab.commailto:boris.doubrov@duallab.com> wrote: Hi Thirumani,

There were indeed several fixes related to the use of .notdef glyphs. If you could submit the document9s) in question, we could verify if indeed there was an issue in 1.12.1, which is now fixed.

Would you also check the latest stable release of veraPDF, which is 1.16.1 at the moment?

We do tentatively plan to release the new version of veraPDF by the end of 2020 or early 2021.

Best regards, Boris

From: Users <users-bounces@lists.verapdf.orgmailto:users-bounces@lists.verapdf.org> On Behalf Of thirumani t Sent: Monday, August 31, 2020 8:31 PM To: users@lists.verapdf.orgmailto:users@lists.verapdf.org Subject: [veraPDF-users] Info on Release of verapdf-greenfield-2.0.59-installer.zip

Hi Team,

We are using the verapdf tool for checking PDFA compliance. Currently we are using version 1.12.1 and that reports the below error. While analyzing we noticed that this error is not being reported in the latest development version 2.0.59. So we are wondering if this is being reported incorrectly in the version 1.12.1 and has been fixed in the latest development version. Can you confirm if that is the case and also let us know if there is any tentative timeline on when you are planning to release the next version and will that be as that of a build after version 2.0.59?

6.2.11.8-1 - A PDF/A-2 compliant document shall not contain a reference to the .notdef glyph from any of the text showing operators, regardless of text rendering mode, in any content stream

Thanks & Regards, Thirumani