There are any number of ways to accomplish caption-below-figure in FM. The simple an obvious one, Anchored Frame above current paragraph, does not exist. So here's one way to do it. This example presumes that what's desired are centered figures & captions. Two task-specific Paragraph Formats are needed, arbitrarily named: FigureAnchor and Caption. For the test I ran, these were derived from the current Body format, with the following differences:   ¶FigureAnchor: /Basic\ Alignment: Center ☑ Next Para Tag: [Caption] /Pagination\ Keep with: ☐ Previous ☑ Next Widow/Orphan Lines: 4 (or whatever your largest caption is +1) /Numbering\ {probably none, due to shoving AF around}   ¶Caption: /Basic\ Alignment: Center ☑ Next Para Tag: [Body] {if any} /Pagination\ Keep with: ☑ Previous ☐ Next Widow/Orphan Lines: 4 (or whatever your largest caption is +1) /Numbering\ {as desired}   ⊥Select the FigureAnchor para. Insert🞃 Anchored Frame… Position: At Insertion Point Width: / Height: {as desired}   It would be important for the preceding/following paras to not have Keep With Next/Prev set. Once in place, the fig+cap acts like a single object on reflow. ... Ver mais

Susan: Are you saying that there are still features that were relevent and helpful on the UNIX platform that don't translate over well to Windows? No, just that there are corridors in the FM House that don't lead to where you probably are trying to go. While the Equation tools still exists, and works, there were a few things it never did. It was never updated to emit equations as EPS, SVG or MathML. Instead, Adobe had an arrangement to use a 3rd-party MathML editor, which may not still even work (bug report FRMAKER-11189). My guess is that the current solution, as with graphics, is to use an arbitrary external MathML editor, and import an XML or SVG object from it. Another apprently darkening corridor is Unicode. FM only supports BMP (FRMAKER-10976), which is now only 42.3% of populated Unicode space. This is becoming an increasing annoyance in my work, as the work-around is😱. re: I'm old enough to remember UNIX. I cant remember the name of the app I used to create my college papers, but it involved a bunch of tag-like commands at the beginning of the document to get the very basic formatting down. Perhaps nroff or troff? I was delighted to dispense with those when FM came along. ... Ver mais

Susan: There are lots of weird things like this in FrameMaker. It's like the Winchester Mystery house of desktop publishing. Long hallways and doors that lead nowhere. It's due to the history of the app, which began in the mid-1980s as a Unix-based X-windows WYSIWYG interface to generating PostScript. There was no MS Windows then, nor any PDF, HTML, XML or eBook. Ps is very strict, so people working with it were used to having to architect documents to some degree. While being able to cause overrides is likely necessary (if only during format development), having those toolbar buttons, and assorted menu items that routinely generate new overrides willy-nilly, is problematic. I never use them for anything more complex than a one-page single-use memo. On the Winchester House theme, I hope you don't need to work with equations… ... Ver mais

Susan: I just wanted a single instance of a graphic and it's figure description underneath it to be on the same page. FM lacks an Anchored Frame option for "Above Current Para", which would be the simple and obvious way to implement captions. You can search the forum on [caption] for the myriad ways that people work around this. I tend to use either a Table for both image & caption, or a pair of paras, ¶FrameAnchor (empty, run-in) kept with a following ¶Caption. ... Ver mais

Susan: …you select "Update Style?" But then it would have all of the text with that style tag start at the top of the next page, and I don't want that. Yep. Quick fix: if the para you want to start at top is, for example, Body, create a new format called Body.Top that is identical to Body except for Pagination. That way, no overrides are created. A recent project of mine ended up needing ¶Body, ¶Body.First & ¶Body.Flush for various reasons having to do with indents, keeps, etc. ... Ver mais

The current FM2022 (rev 17.xxx) is supported on both Windows 10 & 11, and of course all documents port forward. It's probably straightforward to download & install FM2022, then transition the license. Perhaps a looming question is the remaining support life of Win10Ent itself, which might have less than a year to go now, and will require a subscription fee for security updates after EndOfLife. ... Ver mais