EngageOne

Top tips for optimizing EngageOne® Designer / Generate PDF output and performance

  • 1.  Top tips for optimizing EngageOne® Designer / Generate PDF output and performance

    Pitney Bowes
    Posted 08-30-2019 14:14
    Introduction
    EngageOne® Designer / Generate PDF is a feature rich set of input and output formats and options.

    When the EngageOne® Designer user creates a New PDF Output device for Publishing , the Device options selected by default are the "best fit" default compromise between performance and functionality.

    As with all Device options however, they should be reviewed based on your Design requirements for Fonts / Images and your Output delivery platform to ensure that the options used are the "best fit" for your requirements.

    Reviewing the tips below , should in most cases result in a Generate performance improvement and smaller file sizes.

    Tip #1 - Create your OWN PDF Device - NOT the "Default PDF"
    By default , when you install a New Designer 6.x database​, and create a New Project , you will get a "Default PDF" device.
    If you look at the Dependencies on this Device, you will see that this is tied directly to the "Preview" Production Job , meaning that this "Default PDF" device has been optimized for the Designer Preview (PDF) function.

    Use of this "Preview" Default PDF for Publishing will result in :
    - All Documents ending up in one Physical "COMPOUND" file , with only the LAST document immediately visible , thus  requiring a subsequent DIME PDF Split run.

    - Inefficient "ASCII850" compression through use of the "Translate to 7 Bit" option resulting in a much larger PDF filesize

    When you create your OWN PDF Device , the "Translate to 7 Bit" option is turned off , meaning that the much more efficient Default "FLATE" Compression will kick in instead.


    Tip #2 - Review PDF Device setting for Compression
    Earlier DOC1 5.x Designer versions supported only the "LZW" compression format.

    Having upgraded to EngageOne Designer 6.x review your PDF Device "Compression" option and update it to to more efficient "FLATE" compression.

    Updating from "LZW" to "FLATE" compression usually results in a much smaller output PDF filesize and consequently a faster Generate execution.


    Tip #3 - Review PDF Device Font Embedding settings  - Where Font embedding is required
    Earlier DOC1 5.x Designer versions supported only the Font "Embed" option.

    This option is useful where the PDF contains fonts that are not available to the Target PDF Reader, or are required to adhere to the PDF Archive (PDF/A) standard,  and therefore had to be embedded.

    Review your Designer PDF Device "Font" section and ensure that where Font embedding is required, this is updated to "Subsetting" instead.

    This will result in the Embedded font comprising only those characters used in the output.
    This is therefore  usually much smaller than embedding the whole font  also resulting in a quicker Generate execution.


    Tip #4 - Consider  PDF Device "Font / Do not embed"   -  Where the fonts are available to the Target PDF Reader
    If you are designing using a known set of fonts that will exist on the Target PDF Reader environment ,

    Examples:
    • If your Target PDF Reader will always be used on a Windows O/S , you can safely use a Windows font 
    • If your Target PDF Reader can be used on ANY Web enabled Device, the use of "Web safe" fonts such as Arial , Courier, Times, etc is advised. Use your preferred Search Engine to see more "web safe" font examples.
    .. then you can use the Designer PDF Device "Font / Do not embed" option , as the output fonts will be rendered correctly using the fonts that exist on the Target PDF Reader device.

    This results in the Smallest PDF output and the Fastest Generate execution.


    Tip #5 - Review PDF Device Image format settings
    • Consider if "CMYK" color space is required for your PDF Image output
      • If an "RGB" (Bitmap image) color space is acceptable , then ensure that PDF Device options
        • "Image / Preserve color space"
        • "Image / Optimize output file size "

    .. are Deselected.

    • Usage of these options will result in the Conversion of Design Images to less efficient PDF JPEG (/DCTDecode) compression format instead of the more efficient PDF FLATE compression used for RGB (Bitmap) images.


    Tip #5 - Review PDF Device Image scaling and Resolution settings

      • Earlier DOC1 5.x Designer versions had the Image Scaling Up and Down options enabled and the Image resolution set to 0 or 72.
        • Depending on the Native Image resolution and the PDF Device Image resolution
          • A degraded low quality image will be  output for Higher resolution images 
          • A larger than necessary resolution / size image can be output for lower resolution images

      • Typically best results are obtained by 
        • Turning the Image scaling options OFF if the Native Image resolution output is acceptable
        • Increasing the Designer PDF Device Image resolution to 300 and using the Scaling up option for lower resolution images which require "improvement"


    Tip #6 - Clear the Publish for EngageOne cache when Publishing Device changes for EngageOne Server
    Designer "Publish for EngageOne" (Publishing to EngageOne Server) caches the Device and Resource Map settings for a faster republish.

    Consequently , all changes to any Designer Device / Resource Map will be ignored when Publishing to EngageOne Server unless Designer Client option :
    • Tools / Resource Cache Management / Cache clearing / Printer Identifier 
     ..is selected and cleared before Republishing any Device / Resource Map update.

    ​​
    Tip #7 - Use the Current Designer / Generate release
    Improvements, fixes and updates are released on a regular basis for Designer / Generate PDF output.

    Make sure you are on a current (6.6.x) version to take advantage of the latest feature changes and improvements for PDF Output.

    Contact your regional support representative to obtain the latest release.


    Feedback!
    Was this post useful ?
    Are there any follow up questions ?
    Let us know!

    ------------------------------
    Paul Barron
    Principal QA
    EngageOne Compose (Designer / Generate)
    Watford, United Kingdom
    ------------------------------