Good news from Annotum support, we’ll still wait at least a week before implementing version 2.0 in the event it has unforseen bugs

We have made every effort to ensure backward compatibility with existing Annotum sites and content, but in some cases newly-edited articles may be ‘un-published’ if they contain invalid XML. Please be sure to keep a complete backup of all WordPress and Annotum code as well as your WordPress database prior to installing this upgrade.

Key Features of v2.0

• Entirely revamped editor with full XML validation and schema enforcement for “bulletproof” JATS-compliant XML
• Support for multiple-level sections and subsections
• Support for rich text formatting in article abstract
• Article templates (standard headings for new articles)
• Article tree viewer to navigate article structure
  
• Syntax-aware XML code editor for power users
  
• Now uses WordPress standard dialog for figures (images)
• Better support for WordPress revisions and version compare

Known Issues

• In PDF output, images that cross a page boundary may be cut off. This can be avoided by forcing a new page prior to every image by making the following change to the assets/main/css/pdf.css file:
• PDF output support for non-latin character sets may be limited. As a workaround, replace the PDF fonts in plugins/anno-pdf-download/lib/dompdf/lib/fonts with fonts containing the desired character set. You will also need to update assets/main/css/pdf.css (see line 212).

The Annotum group has finished Alpha and Beta versions, and is now on to Release Candidate 1 They write:

We’re pleased to announce the initial release candidate for Annotum 2.0. Barring any major issues, v2.0 will be released on WordPress.org in the coming days.

The OAS will wait until the official release has matured before porting it to it’s servers. In the meantime, the demo version 1.1 is in place.