Let's say you have already created a Lingo project for an earlier version of a particular project or document. You have already translated it, exported it to a new project or file, and given it to the author. Sometime after this, the author makes many changes to the project or file (in the source language). Now the author needs you to translate those changes into the target language. To do this, you can update your Lingo project.
(Optional) If you are translating a Madcap Flare project and do not want to keep variables in the Lingo project, you can select Replace MadCap variables with their definitions in plain text. If a drop-down field is also shown below the check box, you need to select the Flare target whose definition you want to use.
You might use this feature if a variable definition has different meanings in the translation language, depending on the context (e.g., "cash" versus "currency" in German). If you do not convert variables to plain text, you can only translate the variable with a single term, and it will be used everywhere in the project wherever the variable is inserted. On the other hand, if you convert variables to text, you will then be able to translate each term separately when it appears in the Translation Editor.
example
If you do not convert variables to text, you will see something like this.
If you do convert variables to text, you will see something like this.
If the Flare author created a target override for a variable (i.e., one Flare target will use a particular variable definition while another target will use a different one), there will be a drop-down with a check box. This allows you to select the target whose variable definition you want to use when converting to text.
Note: If the changed source file has segments that exactly match those in TM, the segments automatically receive those translations. If there are changes where matches do not occur in TM, those changes are reflected in the Lingo project in a couple of ways. First, the Difference column in the File List window pane indicates whether a file has changed. Also, if you switch to Preview mode in the Translation Editor (for files such as Word documents, PowerPoint files, and Flare topics, which can be displayed in that mode), icons are displayed next to segments that have been changed.
Note: When you use this feature, Lingo only scans files that have been changed, instead of all files in the project. This results in quicker updates.
Note: Update Project is disabled if you created a project in the following ways: (1) from individual folders and individual files; or (2) from individual folders, and later you added additional files using the Add Project Files Wizard.
After updating a project, you can open a list of files that require translation (see Viewing Files Requiring Translation). If the Difference column indicates a change was made to a particular file, you can open that file to translate the new text (you may need to drag the divider in the File List window pane to see the Difference column).