Importing graphics does not work properly

[default38z3gcnx1min]

We have recently switched from Framemaker 12 to Framemaker 2022 in our company.
With Framemaker 2022, the import of graphics no longer works properly. It works with Framemaker 12 with the same graphics.

When a graphic with a resolution of 300dpi is imported, Framemaker 2022 sets the DPI number in the object settings of the image to random values (308dpi, etc.). The value must then be manually reset to 300dpi.

In the default settings for image import, “300dpi” is already selected, but this apparently has no effect.

Do you have any idea what the problem could be?

Thanks in advance.

[Winfried Reng]

Hi,

Some comments:

Do you have the latest update of FM 2022? I do not think that this is an issue here, but I would always update.

What's the graphics format? And did the width/height of the graphics change? Did it change to a defined width, e.g. table column width, text frame width?

If you use TIFF, then check also this thread:

https://community.adobe.com/t5/framemaker-discussions/imported-tiffs-have-different-dimensions-than-...

In the FrameMaker Preferences in Graphics there is the option Auto-Scale Image Along Width. Is this option activated? This might change the scaling/dpi, when you import e.g. into a narrow table cell. I do not know, if this option affects the scaling, when you just open an old FM file. You might deactivate this option and then open the file.

Do you use structured or unstructured FrameMaker? Any scripts when opening a file?

Best regards, Winfried

[default38z3gcnx1min]

Thanks for you fast answer Winfried.

I am using Framemaker 17.0.5, but i can contact my IT department to update it to the latest version.

Graphics format is ".jpg" (Created with Photoshop / Illustrator and SolidWorks Composer) and the image width changes after the import from "14,8cm x 10,465 cm / 300dpi" to "14,377 cm x 10,166 cm / 308dpi" for example. Seems like the change is random, cause some images get changed to 304dpi also.

Auto-Scale Image Along Width is not activated.

We use structured Framemaker and there are no Scripts when opening files.

[Winfried Reng]

Hm. I have files from FM 2012, but I used EPS for pixel and vector graphics, and their sizes did not change.

When you use structured FrameMaker, do you save your files as *.fm or *.xml? If *.xml, FrameMaker would have to do some interpretation of your content and might change also the resolution of your graphics files.

Do all your jpg files change? Or only some of them? Do the files which change have something in common (e.g. rather old, created with another Photoshop version, etc.)?

What happens, when you insert a jpg file now and save and reopen your FrameMaker file? Are there any changes?

Apart from this I do not know what you could do. Sorry.

[Bob_Niland]

default38…: Graphics format is ".jpg" (Created with Photoshop / Illustrator and SolidWorks Composer)
Checking into the format details of a few might be worthwhile. JPEG has a surplus of options, not all supported by FM.

While this is almost certainly not your situation, I reported a case, on the now-gone FM forum here, of what appeared to be a photo-res grayscale image that looked fine in FM, but collapsed to a very blocky 10dpi at the print shop. It turned out to be a JPEG2000, RGB color space, Indexed color, with all R,B&G values identical. FM doesn't support indexed jpg. Re-save from Photoshop fixed it.

[default38z3gcnx1min]

My Files are .xml-Files. There might be some problem with the .edd or some other .xml interpretations, thats actually a good clue i think. Strange that it worked with FM12 though ...

All .jpg files change, there is no exception. We have Photoshop CS4 files and also Photoshop 2025 files, but there is no difference.

There is no change after saving the file.

I guess i'll have a conversation with our service provider. Maybe they can check the .edd, .tpl and dtd files and find something there.

I'll let you guys know if we can solve the problem.

Thanks for your help so far Winfried.