Image File Names

[dcrouse10]

Is there any way to tell RH to NOT rename image files when importing/linking to a FrameMaker document?  It would help the poor image quality problem if I could copy the originals into the RH folders, replacing the severly downsampled images RH is using with the better quality ones, but renaming the originals is time consuming and annoying (particularly if RH changes the names).

Failing that, since most of the images in FM are linked, is there a way to have RH also link to those images instead of creating its own versions?

Thanks for the help.

[Peter Grainge]

You will do much better to post Framemaker to RoboHelp questions in the Framemaker Integration forum. I am moving this post there now.

---

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Message was edited by Peter Grainge: I guess Rick got there first and moved it!

[Matt-Tech Comm Tools]

That's an interesting suggestion!!

I suggest posting it (soon) in the Adobe wish list at www.adobe.com/go/wish

I think that maintaining the filenames would be a great improvement in terms of workflow.

You do have Image settings in the conversion setting dialog, and you can choose different default formats, whether or not Distiller should be involved in the conversion, and also choose not to regenerate images.

Have you played with the various combinations on these settings?

-Matt

[dcrouse10]

I have played with just about everything at some point to combat the image quality issue.

I have found that, if the images in FM are linked instead of embedded, it does maintain the file name but adds underscores between words.  The extension gets changed if the format isn't one that RH likes but the name bit is the same.

Images embedded in the FM doc seem to fare better in the conversion than linked images do, but the filenames are generated by RH.  Why would embedded images convert better than ones with a live link?

Pasting the orignal files (in PNG format) over RHs converted version works, but all sizing is lost.  Sizing it manually, again, mangles the image.  The problem appears to be with RHs scaling algorithm.  Importing an embedded image works because there is no scaling:  RH just converts whatever it finds in FM.  Linked images may need to be scaled during the conversion, so RH mangles the corpse.

How does that sound?  And is there any fix or workaround?

I am currently thinking of using Conditional tags in the FM doc, putting in 2 images for each image.  The second is for RH only, using the same image file, but imported at 96dpi and sized sligthly bigger and with no text wrapping.  Seems a bit clunky, but the end result is much better.