Images in DITA documents do not publish as PDF in correct location under FM22

[tim_6130]

I am having publishing issues with Framemaker  Version: 17.0.5.725.  I have a 400 page structured document originally designed in Framemaker 2019. After upgrading to Framemaker 2024 (Version: 17.0.5.725) the files when view in Framemaker are formatted correct. When the document is published most, but not all of the tasks in the document are not placing images within the text. In many of the tasks the images are simply tagged on to the end of the task, not inbetween the  steps, as the images appear when viewed in Framemaker. What am I missing here?

[Bob_Niland]

Tim: Framemaker 2024 (Version: 17.0.5.725)

There is no FM2024, so I presume that's FM2022.

To what output formats are you publishing?
(PDF is mentioned, but also HTML, XML, eBook?)

Are you using the File🞃Publish workflow, or one of the Save or Print workflows?

[tim_6130]

Bob, 
Yes, I am using Framemaker 2022.  I only publish to PDF.  I have tried both the Publish workflow and "Save as PDF" workflow.  Each time same issue. Images are not placed with the text. Issue seems to be somewhat random. Most of the files are DITA Task or DITA concepts. 
Thanks,

Tim

[Bob_Niland]

On the Publish workflow, you might make a backup of the FM2022 .sts file for the project, and try copying over the .sts from FM2019 (if still available). And if that fixes it, then dig into why. In my limited experience with Publish, .sts files port forward, but not necessarily backward.

There may also be some things in
File🞃Print Setup… (with the PDF printer configured)
⚙Printer Properties & Preferences in Windows
both paths may allow a drill-down to
SettingsName🞃Images, but all the menus need a gander.
You may have already done much of this.

[tim_6130]

We recently upgraded to FM22. I maintain a structured book composed mainly of DITA tasks, concepts and topics. The document was originally designed in FM19.  When document is published or saved to a PDF many of the individual documents don't place the images in the  documents as they appear in FrameMaker flow.
As Shown in FrameMaker:

As Published as PDF:

[Jeff_Coatsworth]

@tim_6130 instead of starting a new duplicate post, I've merged that one with the existing thread you started already. I'll edit your title to reflect the new info that @Matt-Tech Comm Tools was looking for.

[Matt-Tech Comm Tools]

Can you also share the structure view of those graphics?

[Matt-Tech Comm Tools]

Hi Tim, it sounds like you're using DITA. If so, can you please edit your topic title to reflect that?

Producing PDF from DITA is different for topics, ditamaps, and bookmaps. 

Which are you trying to output?

Can you post screenshots of the topic within Fm and of the resulting PDF?

[tim_6130]

Matt:
Photo below is of structed view of page typical of issue.

[Matt-Tech Comm Tools]

An aside: It appears you're using a Topic to represent this, though Task might be more accurate.

In any case, in testing on my default setup, I created a topic with an OL, LI, and Image, and had success producing the PDF of the topic. I didn't test output of a ditamap or bookmap.

Can you elaborate on how your process may have deviated from my test?

Can you perform a similar test to see if your output matches expectations?

[tim_6130]

The only difference I can think of is that these documents were first created in FM19.  When published in FM19 on a WIN10 machine the resulting document places the images correctly.  When the same document is published via FM22 on a WIN11 machine the images do not get placed into the text flow as designed.  Interestingly, using FM22,  if I open an individual file and delete all of the images and frames, replace the image elements and images,  and save, then publish the resulting PDF is properly rendered. 

[Matt-Tech Comm Tools]

Are your files .fm or .dita?

[tim_6130]

Matt,

Files display in FM22 as .xml files.
Tim

[Matt-Tech Comm Tools]

So the windows file extension is .xml?

[frameexpert]

Are the authoring and output templates different page sizes, etc.?

[rubab_4079]

It sounds like the issue is related to how FrameMaker 2024 is handling structured elements and image placement during publishing. Here are a few things to check and try:

1. Check the Read/Write Rules (EDD & DTD)

• Ensure that your Element Definition Document (EDD) and Document Type Definition (DTD) files are correctly configured.
• If FrameMaker is not interpreting the placement of images correctly, you may need to adjust the Read/Write Rules for structured publishing.

2. Verify Anchoring of Images

• Open the structured view and check how images are anchored within the XML structure.
• Ensure that the images are within the correct elements (e.g., within a <Step> element instead of after it).

3. Check Publishing Settings

• Go to File → Publish Settings and verify the settings for Structured Publishing.
• Check if "Retain Anchored Frame Positions" is enabled (if applicable).

4. Try a Different Output Format

• If you're publishing to PDF, try exporting to another format (e.g., HTML, XML) and see if the issue persists.
• If the problem only appears in PDF, check your Stylesheet (CSS or XSLT) for any unintended modifications.

5. Reimport Images

• If images were linked instead of embedded, try reimporting them as embedded graphics.
• Go to Graphics → Object Properties and confirm image placement.

6. Test with a Smaller File

• Try creating a smaller test document with a few pages and images.
• See if the issue happens there to isolate the problem.

7. Check for FrameMaker Bugs

• Since this happened after upgrading, it could be a FrameMaker 2024 bug.
• Check Adobe forums or update FrameMaker to the latest patch.

8. Try Saving as MIF & Reopening

• Save As → MIF (Maker Interchange Format)
• Reopen the MIF file and then try publishing again.

If none of these work, let me know more details, such as which format you’re publishing to (PDF, HTML, etc.), and I can suggest further steps! :rocket:

[Matt-Tech Comm Tools]

Hi Tim, my guess is that you're using .fm files, rather than .dita files. 

If so, use Save As... to save the files to DITA and then reopen.

When publishing PDF .dita you're using the templates specified in the Publish panel.

When publishing PDF from Fm, you're using the definitions stored in your current Fm document.

If you'd like to see an extensive overview of this, join me for my Adobe webinarat 9 Pacific tomorrow, as publishing DITA is the second half of the material.

Migrating technical content from Word to DITA with Adobe FrameMaker (step-by-step guide)

[tim_6130]

Matt,

Yes, the documents that make up the individual chapters are windows .xml files. 
Per an earlier suggestion you made, I set up a new book - but this time as a ditabook.  This placed the images in the right places. However, it created another problem. The book is composed of mulitpage chapters. I can not figure out how to get each new chapter to start on a new page. How do I do this.
Thanks,

Tim

[tlc4321 · Accepted solution]

Matt,

After watching the Word to Dita with Adobe Framemaker twice it directed me to a solution. I have been able to solve my issue! Here are the steps that solved it.
1. Created DitaBook Map 

2. Added files - files are mostly dita concepts saved as .xml

3. Saved DitaBookMap as Book 2022 with fm components

Resulting FM files contains all the documents in the right order with the images in the desired spaces.

Thanks for your help.

Tim

[Matt-Tech Comm Tools]

I had a feeling that you'd like the walkthrough of the template management I did in that webinar! We'll be doing another similar topic in August, but focusing on moving .fm unstructured content to DITA.

I like the format we're using for the webinars, since (as with my previous Fm Essentials courses), I can add the  component topics to my online courses.
Sort of a topic-based course content management system.
(Ouch, sorry for the bad DITA humor) 🙂