Convert All Variables to Text

[Ken S]

Is there a way to convert all variables in a Flare project to text in a single step?

[LTinker68]

Yes. Build the project.

The only way to convert all instances of a variable into text in the authoring environment is to do a find-and-replace in Flare. Open one of the topics containing a variable in the Internal Text Editor and look for the variable tag. It would look something like <MadCap:variable name="MyVariables.CompanyName" />, where "MyVariables" is the name of your variable set and "CompanyName" is the name of a specific variable. In the find-and-replace pane, put that code in the find and type the text you want to replace it with (e.g., "MadCap Software"). In the middle of the FAR pane, enable the option "Find in source code". Select to find in all topics then click Start.

I'd make a copy of the project before you do that, though, just as a precaution.

[ChoccieMuffin]

That would convert all instances of a single variable, Lisa, but if you have several hundred dotted around, I don't think I'd fancy having to do several hundred search and replace actions.

Why would you need to convert all variables into text? (Just curious in case I bump into the same situation, you understand, not being critical.)

[Ken S]

This was a request from our translation manager. The vendor is having some difficulties with variables and the manager was wondering if this would be a potential solution to these problems.

[LTinker68]

You might want to look into MadCap's Lingo software. It's to assist with translations so I'm guessing it has some way to allow for translating variables.

[LTinker68]

... but if you have several hundred dotted around...

Several hundred instances of a few variables, or several hundred variables? I can't imagine having that many variables in a variable set, but I suppose it's possible.

[alt_jennifer]

There's no way that I know of to convert all variables to text in one step. Variables do make translation more difficult, but they don't make it impossible -- unless you're using variables all over the place, and for ordinary, everyday words. We usually leave all the variables intact when we translated our clients' Flare projects. They do have to be repositioned, and in some cases, they might need to be converted to text on a topic by topic basis -- if the variable that was setup doesn't work well with that language's grammatical rules. I haven't seen that happen very often, but I could imagine "doomsday scenarios" when it might happen all the time

Is there a specific reason the variables aren't working for them?

[Ken S]

Thanks Jennifer. We've discussed this with our translators and come to a mutual understanding that will allow us to continue to use variables.

That said, we have run into a minor issue with East Asian languages and variables. Specifically, when we receive content back from the translators, there are spaces before and after the variables. According to our translation manager, this can impact legibility in these languages. Is there something we can do in Flare before translation or that the translator can do in Lingo to remove these spaces?