Poor quality reference page images in HTML5 output

Question

I have been struggling with poor image quality output for all of my graphics that are stored on my reference pages when publishing to html5 or other digital format.

Here are the details:

I have several high quality svg images that are stored in my reference pages for automatic placement above and below paragraphs.
These images look great on screen and in pdf output
All options have been set correctly in Publish output (Outputs->Optimization-Convert SVG to Raster Image not selected, Style Mapping->Image settings-Use distiller to generate image not selected, default format as is)
I have tried changing preferred dimensions to 0 , 0 - no change
Framemaker is converting all of the svg files embedded in the reference pages to horrid quality jpeg images
If I copy and paste the images from the reference page to a body page, everything works fine (the output is a good quality svg)
Text in the reference pages is also blurry and poor quality jpeg images

Is there a way to get Framemaker to output svg images on the reference pages as true svg images or am I out of luck?

Bob_Niland · Accepted Answer

The practice of placing images individually in the body pages defeats the whole purpose of reference pages and goes against good document management techniques as each image is then independent and difficult to manage creating overrides throughout the document.
Have tried using high quality jpg files in the reference pages and get the same result. Again, everything looks great if these same images are placed in the body pages.

This is a huge setback for my project and I am not sure how to proceed. Is there any hope of this being fixed in the near future?

>> Would it be possible to use a temporary workaround of:
>> using them directly on the body page

Presumably as imported-by-reference in anchored frames. That, of course, cannot be easily emulated if the RefPage implementation was via FrameAbove, given that FM has no anchor frame position option for AboveCurrentLine (despite people asking for it for a quarter century or so).

> This is a huge setback for my project and I am not sure how to proceed.

What's the output delivery format? If it's some plain text format, like HTML5 or XML, I'd seriously look at writing a script to use late in workflow to replace whatever raster rubbish Adobe is generating with the original SVG. Since it appears that these images are notice and/or safety admonishment panels, there's probably a very small number of identical data patterns to search and replace on.

> Is there any hope of this being fixed in the near future?

I can't recall seeing Adobe commit to such a thing in this forum, which is understandable for multiple reasons. Given how long it took them to support such SVG pass-through preservation as actually works (relative to when SVG import was first supported, and that was years), I would begin implementing a Plan B, and maybe a Plan C immediately.

Bob_Niland · Answer

What version of FM?

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded