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.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.org> On Behalf Of thirumani t
Sent: Monday, August 31, 2020 8:31 PM
To: 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