The M050 maintenance release of APP Version 11.1 is now available for download.

The release notes say this:

  • Added support for Cyrillic numbering scheme.
  • Added support for custom XMP Metadata to the PDF printer driver.
  • Fixing issue with empty pseqstart/pseqend commands not getting skipped correctly (SPR 4700098)
  • Fixed crash and performance issues caused by hyphens in PDF Tagging when PDF Tagging hasn’t been enabled. (SPR 6208118)
  • Fixed crash using PDF Notes when enabling PDF standards. (SPR 6186286)
  • Adding hyphenation type = 2, to allow hyphenation purely using an exception dictionary (SPR 6164142)
  • Fixed rendering of “Double Solid 2” rule. Left “Double Solid” rule unchanged for backwards compatability. (SPR 5799133)
  • Fixed FOM fStyle, fParagraph, fBlock, and fTable objects to ensure the properties return undefined if they have not been set explicitly.

The FOM release notes say this:

  • Added merge parameter to fContent.loadNamespace() method.
  • Added fContent.NamespaceMergeModes constant group.
  • Added fNamespace.jsGlobalVariable property.
  • Replaced inline parameter on fFormatting.addImage() method with place parameter.
  • Replaced inline parameter on fFormatting.addU3D() method with place parameter.
  • Added fFormatting.ImagePlaces constant group.
  • Added fFootnote.ignoreRules property.
  • Added fContent.createStoredObject() method.
  • Added fContent.storedObjects property.
  • Added fTag.TYPE_JS_OBJECTS constant.
  • Added Serializer object.
  • Added fTemplate.serializer property.
  • Added fFormatState object.
  • Added fFormatting.currentState property.

There are a couple of new features in this release.

  • XMP metadata – you can now ask APP to include custom XMP in your PDF. The print options have a file picker for you to select an XMP instance (or APP tag) to use as the basis for the metadata embedded in the PDF created by APP. Document properties and the information APP generates will be merged with this metadata. This addition is in response to a number of customers who have asked for custom XMP inclusion.
  • Stored objects – many FOM objects are representations of APP tags, but there are also a really large number which don’t have a tag, especially those used to apply style. When creating a template it has often been necessary to write code to create these object – often every time one is needed. Now, with stored objects, these can be saved in the template and recreated when the template is opened again. This means you only need to create them once and use them many times, which will help to reduce the amount of code in your templates.

Please also note a slight change in behaviour – some FOM objects will now *correctly* return ‘undefined’ if a property has not been explicitly set. We have found in our testing that some templates did not test for this properly and output changed because of this. This is a bug fix in our JavaScript interface, not a feature change. Please ensure you check your documents for this as we will not be reverting to old behaviour.