Skip to main content
Inspiring
April 24, 2026
Question

Framemaker automation dtp process

  • April 24, 2026
  • 4 replies
  • 23 views

Hi everyone,

I’m looking for advice and possible solutions to help automate parts of our Adobe FrameMaker workflow, especially anything related to reducing manual DTP effort after translation.

A bit of context: we produce operator manuals in FrameMaker (unstructured). Our current workflow is quite manual and time-consuming. We export MIF files, send them for translation, and then re-import them.

We have already made some progress on automation. For example, we have automated the conversion from MIF to FM files, including the renaming of file extensions (e.g. adding “_ES” for Spanish versions). We are now trying to build on this approach and see where else we can follow the same path of automation.

After re-importing translated files, the most time-consuming remaining tasks are:

  • Re-linking text insets
  • Re-establishing cross-references
  • Fixing layout issues after translation

The biggest pain point is re-linking text insets and repairing broken references. Reducing or eliminating this would significantly reduce our DTP time..

What I’m really looking for is:

  • A way to automate or significantly reduce the effort of re-linking text insets after importing translated MIF files
  • Ideally some kind of “one-click” or near one-click solution to restore structure (text insets, refs, links) after translation
  • Any tools, scripts, plugins, AI-based workflows, or FrameMaker best practices that could help
  • Even partial automation ideas are welcome if full automation isn’t realistic
  • If anyone could also suggest courses, training, or learning resources that helped them solve similar problems (especially if coding like ExtendScript, scripting, or APIs were involved), that would be really helpful as well

If anyone has solved similar problems or has ideas (even unconventional ones), I would really appreciate your input.

Thanks in advance!

    4 replies

    Community Expert
    April 24, 2026

    FrameMaker has an in-built dedicated translation tool which can be found under File->Translation-Export to XLIFF and Import XLIFF. Using this tool will save you from relinking and all the other manual stuff.

    You may have some minor layout adjustments, but those may be for a large part be taken care of if you have templates for the different languages.

    If it is the first time you use it, you may have to a little fiddling around and make sure your translation company is in on the deal, but they ought to be able to handle the XLIFF files no problem. 

    Bjørn Smalbro - FrameMaker.dk
    Two-fer
    Inspiring
    April 24, 2026

    I work with unstructured FM for Japanese-to-English using MIF files, but I am also the translator, so I also have the CAT tool. In my CAT tool, any cross-reference and formatting codes (‘placeables’) are shown in each sentence, so I add them to each translated sentence in the correct location. By doing this, when I then open the translated files in FM, everything ends up in the right place and formatted like it should be--cross-references, index markers, formatting, etc.

    (But I would guess that any translation company would charge extra to place these markers in the correct location in each sentence. And since some sentences would have multiple markers, getting the markers in the right place could be tricky (impossible) for someone if they are not familiar with how FM works.)

    Not sure that there is a good way to automate the post-translation layout issues--Spanish is longer than English, and English is much longer than Japanese. One indirect method might be to have more white space on each page, then if the translated text ends up being longer, it may still fit on the page (in a perfect world, anyway….).  

    Best of luck finding a solution.

    Robbie.NAuthor
    Inspiring
    April 24, 2026

    This is probably the one area i think is unavoidable, we will always have some post translation formatting to carry out. If our manuals were just text we could get away with it but we have tables, diagrams, photos etc. We have a template for each language that has a set font size to combat the length of sentences, so its reduced in the languages that have longer words and sentences. When we get our files back from the LSP they basically have the translations inserted into the correct locations, were just fine tuning them. when your manuals are a 100-200 pages long its more time consuming.

    The ENTIRE DTP process for a 150page manual, including it been reviewed by someone after we first export & amended/re exported is about 6-8hrs. Not even sure how good or bad this is in comparison to other peoples workflows?

    frameexpert
    Community Expert
    Community Expert
    April 24, 2026

    You can sometimes solve this by your folder and file naming conventions. For example, say you have two books:

    Widgets-English.book

    • Chapter01-EN.fm
    • Chapter02-EN.fm
    • etc.

    Widgets-Polish.book

    • Chapter01-PL.fm
    • Chapter02-PL.fm
    • etc.

    Assuming that the books and documents are in different folders, it may be best to not add the language suffixes to the file names. If the localized file names stay the same as the English files, then cross-references should be preserved when the files are localized (assuming that the links are relative).

     

    The same would be the case with localized images and text insets. If the languages are indicated at the folder level instead of for each file, relinking can be much easier.

    www.frameexpert.com
    frameexpert
    Community Expert
    Community Expert
    April 24, 2026

    Hi Robbie. I have an off-the-shelf solution called PathChanger for updating cross-references, text insets, and referenced graphics. It essentially uses a spreadsheet that you can quickly update with the new paths and apply to your FrameMaker book. See www.frameexpert.com.

    If you need further automation, we can explore how custom scripts would benefit you. Please contact me offlist if you would like to meet. rick at frameexpert dot com.

    www.frameexpert.com
    Robbie.NAuthor
    Inspiring
    April 24, 2026

    Hi Rick, we actually purchased two tools off you, the convert docs tool (which is perfect) and the path changer one. I found the path changer one works, but I guess I’m just seeing if there's an even better solution available. Ideally as simple to use as convert docs.

    Having spent some time looking into this I’m starting to realise the way we store our files may not be ideal. right now our text insets are all stored with the English version, with the relevant extension ‘_PL’ for example. I’m now thinking it would probably be best to have all polish text insets in the one location ‘Text insets>PL’. That would benefit us in some ways but would also make it more difficult when making changes to text insets, jumping file locations to open each one and update it.

    Id like to hear about other peoples workflows and see if there's anything we could potentially adjust to simplify/speed the process up.