Issues with Graphic Quality

Many users report less-than-desirable image quality in their ePublisher output. This is often paired with a long conversion time, specifically in the Image stage/pipeline. The most common factors that lead to poor image quality are scaling and rasterization.

If the original image file was imported into FrameMaker and scaled (either by reducing the size as a percentageof the original or increasing the DPI) to fit better on the page, then the scaled dimensions of the anchored frame will be passed on to ePublisher (and thus your HTML output) by default. This means the full-size (and full quality) image might be copied by reference into the output, but the dimensions defined in the HTML image tag will instruct the user's browser to shrink the image on the screen. Browsers don't specialize in scaling images, and you'll likely get a "smushed," distorted picture when you view the output. To correct this, it's best in most cases to ignore the smaller image dimensions and to display the graphics at full size in the online output. In the ePublisher Pro Style Designer, select the affected Graphic Style (e.g., Default), and disable the "By reference graphics use document dimensions" setting on the Options tab.

If text and curved lines appear blurry in your images, it's likely that they have been rasterized during the conversion. This happens for a number of reasons, including the use of unsupported file types, multiple images in a single anchored frame, or the addition of callouts, annotations, or other graphic elements in FrameMaker. In all of these cases, a new image must be created by the WebWorks Rasterizer printer in order to display the full contents of the frame in output. The time it takes to render all of your images varies according to the size and number of frames that require rasterization, as well as available computer resources and other factors. As long as there is still printer activity, and there have not been any errors, then it's probable that your conversion is still continuing normally.

For more information concerning graphics quality, including tips for avoiding rasterization and getting better images in your output, please see our online Wiki article here:


LaurenLever/@Solutions/Graphics/Image quality is bad or image pipeline is slow (last edited 2009-06-02 19:11:47 by LaurenLever)