Skip to main content
M
matsb99251617
Inspiring
August 8, 2022
Question

Script for importing variables

  • August 8, 2022
  • 1 reply
  • 416 views

Hello,

 

Thought I'd recommend a smart little script that is available from the Swedish company www.mallverkstan.se.

 

Once you have set up your variables in FM, you can update these quickly by invoking the script via File > Script > Run, which prompts you to select a tab-separated text file in two columns, where column 1 is the variable name and column 2 is the variable definition.

 

A typical user scenario could be to update translated manuals with translated software strings. Obviously you can import variables via File > Import > Variable Definitions, but this script lets you maintain variables in, e.g., Excel that you then save as a *.tsv file. I don't think the script is actively marketed, but should be available by contacting the company. The script is called "VariableImportFrameMaker". I've tested it in FM2020 (v16.0.4.1062) where it works fine.

 

Regards,

Mats B (no affiliation with Mallverkstan).

 

    This topic has been closed for replies.

    1 reply

    K.Daube
    Community Expert
    K.DaubeCommunity Expert
    Community Expert
    August 8, 2022

    IMHO the mentioned script (I can not read Swedish, ...) works in Indesign, not in FrameMaker. There is no "File > Import > Variable Definitions" menu item in FrameMaker.

    Bob_Niland
    Community Expert
    Bob_NilandCommunity Expert
    Community Expert
    August 8, 2022

    As the OP points out, any script would have to offer more than FM's built-in bulk:
    File » Import » Formats…
    ☑ Variable Definitions
    Allowing the user to pick&choose individual variables would be useful, if the script runs in FM, of course.

    In my work, having a template.fm for the project, containing all the key project Vars, has allowed the built-in bulk-import to suffice.

    M
    matsb99251617Author
    Inspiring
    August 9, 2022

    Bob,

     

    My personal view is that this script offers an advantage by acting directly on an external text file (*.tsv) and an active FM file, especially if you deal with hundreds or thousands of user interface strings that need to be switched to translated versions once a set of translated manuals are arriving from the LSP. Maintaining variables (especially user interface strings) in Excel is a strong case. I don't think the script replaces the File > Import > Formats > Variable Definition workflow for all user scenarios, but for user interface strings I think it does - and is better, as the user interface strings localization workflow is typically often Excel-centric (or in formats that are easly ported to Excel).

     

    Best regards,

    Mats

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices