LEARN@IGP

Infogrid Pacific-The Science of Information

IGP:Digital Publisher 3.6.0

April 2014

Update Patch Release Notes


IGP:DP 3.6.0 - Updates, Upgrades & Enhancements

The following updates have been implemented in this release:

  1. Font Manager updates
    1. View Scheme Map - A new button named View Scheme Map is introduced on the Published Font Scheme interface. On clicking this button users can view which font is applied to a particular class, without having to Unpublish a particular font scheme and then going back to the Font Schemes interface to view the Map Scheme.

      The interface that expands after clicking the View Map Scheme button is in a Readonly mode. No edits can be done in this interface.
    2. Copy Scheme - A new button named Copy Scheme is introduced on the Published Font Schemes and Font Schemes interface. You can copy an existing font scheme by clicking the Copy Scheme button and assign a name to this scheme. The copied font scheme will appear under the Font Schemes interface.

      This new option makes it easy to modify an existing Font Scheme by simply copying and renaming it, editing when required,mapping the scheme and publishing it so that it can be further used in the document.
  2. Manuscript Importer - lang attribute processing for parent processing elements in the CSV file.

IGP:DP 3.6.0 - Bug Fixes

  1. Font Manager fixes -
    1. Change font property, jumped to the screen top position. Due to this the font context is lost on the screen.
    2. 404 error occured when searching by keyword in Font Manager2
  2. Document Designer fixes -
    1. DD writes CSS for .dedication-rw to F09 now instead of F02 for IGP Master Presentation Templates.
    2. Fonts were dropping from C03 section on DD Save.
    3. DD creates hyphens: null; and hyphenate-lines: null; This was caused by Chrome returning null value for the hypen and hyphenate-lines style.
  3. TIB Merge failure. The Merge was also wrapping text inside the tags when user set a no-hyphen rule to a single character. The fix is to apply no-hyphen replacement only on the content.

comments powered by Disqus