how to create a new project
- Do one of the following, depending on the part of the user interface you are using:
Ribbon Select File>New Project.
- Menu Select File>New Project.
Standard Toolbar Click
.To open the Standard toolbar from the menu view, you can select View>Toolbars>Standard.
- Keyboard Shortcut Press CTRL+SHIFT+N.
The Start New Project Wizard opens.
-
In the Name field, type an appropriate name for your project.
example
example
If you have an English version of a Flare project called "FictionSoftPro," and you intend to translate the project into German, you might name your Lingo project something like "FictionSoftPro German."
Or maybe you are translating that project into many languages. Therefore, you might name the project "FictionSoftPro Translated."
- By default, a path to the Documents\My Translated Projects folder on your hard drive is entered in the Folder field. (Lingo creates the My Translated Projects folder when you install the program.) All subfolders and files related to the translated project will be placed in this folder as you work on the project.
- Click
. - Navigate to the folder you want, select it, and click Select Folder.
noteNote: In some operating systems, the folder is called "My Documents" instead of "Documents."
- Click
-
(Optional) In the Domain field, you can type a subject category for your project, or select one from the drop-down. If you enter your own custom category in the Domain field, it will appear in the drop-down the next time you create a new project. Domain metadata appears throughout the project, such as when you select a suggestion in the translation memory.
example
example
If you have a project called "FictionSoftPro," and it is for a company that writes software for publishing companies, you might choose to categorize your project using the domain "Art/Literary" or "Tech/Engineering."
Alternatively, you could also create a new domain called "Fiction" by typing Fiction in the Domain field. The next time you want to use that domain, you can select it from the drop-down.
-
(Optional) In the Client field, you can type the name of the client you are creating a translation project for. When you enter a client name in the field, it will appear in the Client drop-down the next time you create a new project. Client metadata appears throughout the project, such as when you select a suggestion in the translation memory.
example
example
If you are creating a translation project for FictionSoft, the company that makes "FictionSoftPro," enter FictionSoft in the Client field. The next time you create a translation project for FictionSoft, you can select their client name from the Client drop-down.
- In the Source Language drop-down, select the original language that is used in the project you are translating. Make sure this language matches the source exactly. For example, you might select English (en) here, but the source files are actually in the English United States (en-us) language. Therefore, you should instead select English (United States) in this field.
-
In the Target Languages grid, select the language(s) that you want to use for the translation and click
to move it to the Selected Languages grid. If you need to remove a language from the Selected Languages grid, click 
. example
example
If your project needs to be translated into French, Italian, and Spanish, select these three languages from the Target Languages grid, then click
.
notes
Note: The languages displayed in bold are supported for spell check. This does not mean that you cannot translate in a particular language if it is not displayed in bold font in this page of the wizard. Also, you can import dictionaries for spell checking purposes. See Importing Dictionaries.
Note: If you select multiple languages, you can switch between them in the File List window pane and other areas in Lingo. This makes it easy for you to create projects that need to be translated into multiple languages. You can add new languages to or remove languages from a project at any time. See About Multilingual Projects
- Click Next.
-
Add Files to a Lingo Project
-
Click Add File.
-
In the dialog that opens, navigate to the project or files that you want to translate. You may need to click the file type drop-down to view and select the appropriate kind of files you want to add.
-
If you need to select only one file, you can double-click it. If you need to select multiple files (e.g., multiple Word documents) in the same folder, you can hold your SHIFT or CTRL key and select either a range or individual files; then click Open. The various types of files that you can open to translate include: MadCap Flare; MadCap Mimic; Madcap Capture; Madcap Contributor; MadCap bundles (ZIP files); TXT; Rich Text files; HTM, HTML, and XML; DITA; XML files; Microsoft .NET Resource files; Microsoft Word; Adobe Adobe FrameMaker; Adobe InDesign; Microsoft PowerPoint; SDL Trados; Wordfast; and XLIFF.
notes
Note: Individual image files can be selected and translated in their own Lingo projects. However, if the images are included in Flare projects, you can translate the callout text for those images at the same time that you are translating the other parts of the Flare project.
Note: You must have Adobe FrameMaker installed in order to work with FM and BOOK files. However, if you are adding MIF files, you do not need FrameMaker installed. FrameMaker 8 and above are supported.
Note: When you create a project from a bundle (ZIP file) in Lingo, the files are extracted and converted to XLIFF format.
-
(Optional) If you want to add more files from another location, you can repeat the previous steps. Keep in mind that if you select MadCap project type files, you cannot also add other types of files (e.g. Word documents). However, if you have not selected MadCap project files, you can add any other types of files to the same Lingo project (e.g., you can add Word, FrameMaker, and PowerPoint documents to the same project).
Notes
Note: You can also add files to your project later using the Add Files to Project button.
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.
- (Optional) If you need to remove a file from the project, click Remove.
-
(Optional) If you want to filter the translated files, you can create a file type filter. Use the Filter drop-down to select an existing filter, or select Create New to create a new one. You can add file type filters to XML, Word, or text files.
How to Create a File Type Filter—Word Files
-
From the Filter drop-down, select Create New.
-
Enter a name for your filter and click OK. The File Filters dialog opens.
- (Optional) If you want to open an existing filter, create a new filter, or delete a filter, do one of the following:
- Import a Filter Click Import. In the dialog that opens, locate the filter you want to import, then click Open.
- Select a Filter From the Filter drop-down, select an existing filter.
- Create a New Filter Click
. -
Delete a Filter Select a filter from the Filter drop-down, then click
.Note: If you delete a filter, it will be removed from all translation projects where it is currently in use.
- In the Segmentation area, select an option for how to import soft breaks and tabs into the translation project:
Insert tag Select this option to keep soft breaks or tabs together with the rest of the segment. Lingo adds a tag where the soft break or tab appears in the segment.
Example
The two segments pictured below include a soft break and a tab, respectively. The Word file type filter in Lingo has been set to add a tag when there is a tab or a soft break, but it will not split the segment. When translating the segment, you can drag the tag into the target segment where it needs to appear.
Insert tag and create new segment Select this option to create a new segment wherever there is a soft break or a tab in your project.
Example
The two segments pictured below include a soft break and a tab, respectively. The Word file type filter in Lingo has been set to add a tag when there is a tab or a soft break, and it will also create a new segment at the location where the tab or soft break appears. When translating the segment, you can drag the tag into the target segment where it needs to appear.
- In the Content area, select the check boxes for the content you want to include in the translation project:
Include hidden text Select this option to include hidden text in the Lingo project so it can be translated.
Example
The segment below includes hidden text. Lingo places a tag where the hidden text appears in the original Word document, so the location of the text is clearly visible in the Translation Editor. However, in this example, the Lingo file type filter is set so hidden text is not included for translation. When translating the segment, you can drag the tag into the target segment where it needs to appear.
In the segment below, the filter has been changed so hidden text is included. Notice that the word "HIDDEN" is now visible. Lingo also places a tag on either side of the hidden text so the text is clearly visible in the Translation Editor. You can drag the yellow tags onto the target segment to mark the hidden text in the target segment.
Include comments Select this option to include comments as separate segments in the Lingo project so they can be translated. If you do not select this option, comments will not be included.
Example
The segment below includes a comment. Lingo places a tag on either side of the phrase that was marked with a comment in the original Word document, so the location of the comment is clearly visible in the Translation Editor. However, in this example, the Lingo file type filter is set so the comment itself is not included for translation.
In the segment below, the filter has been changed so the comment itself is included. Notice that the comment is visible in a second segment. This allows you to translate the comment separately. You can also still see the comment tag in the first segment that indicates where the comment was marked in the original Word document. When translating the sentence, you can drag the yellow tag onto the phrase that needs the comment in the target segment. Later, when you export the document, the comment will appear in the finished project, attached to the appropriate location in the document.
Include index Select this option to include index entries as separate line items in the Lingo project so they can be translated. If you do not select this option, index entries will not be included.
Example
The segment below includes words that are marked as index entries. Lingo places a tag next to the text that was marked with a keyword in the original Word document, so the location of the index keywords are clearly visible in the Translation Editor. When translating the segment, you can drag the tag into the target segment where it needs to appear. However, in this example, the Lingo file type filter is set so the index entry itself is not included for translation.
In the segment below, the filter has been changed so the index entries itself are included. Notice that each word in the index is visible, so three additional segments follow the original segment. This allows you to translate each index entry separately. You can also still see the keyword tags in the first segment that indicates where the keywords were marked in the original Word document.
Include footnotes/endnotes Select this option to include footnotes or endnotes as separate segments in the Lingo project so they can be translated. If you do not select this option, footnotes or endnotes will not be included.
Example
The segment below includes a footnote. Lingo places a tag next to the sentence that was marked with a footnote in the original Word document, so the location of the footnote is clearly visible in the Translation Editor. When translating the segment, you can drag the tag into the target segment where it needs to appear. However, in this example, the Lingo file type filter is set so the footnote itself is not included for translation.
In the segment below, the filter has been changed so the footnote is included as a separate segment. This allows you to translate the footnote separately. You can also still see the footnote tag in the first segment that indicates where the footnote was marked in the original Word document.
-
In the Styles/Markup area, select the check box if you want to include minor formatting changes in your translation project.
Example
The segment below includes a text effect, and also includes bold formatting. However, in this example, the Lingo file type filter is set so the text effect is not visible in Lingo. You can only see the bold formatting.
In the segment below, the filter has been changed so the text effect is visible. Lingo places a tag next to the word that was marked with a text effect in the original Word document, so the location of the effect is clearly visible in the Translation Editor. When translating the sentence, you can drag the yellow tag onto the word that needs the text effect in the target segment. Later, when you export the document, the text effect will appear in the finished project.
- Click OK.
How to Create a File Type Filter—XML Files
-
From the Filter drop-down, select Create New.
- Enter a name for your filter and click OK. The File Filters dialog opens.
- (Optional) If you want to open an existing filter, create a new filter, or delete a filter, do one of the following:
- Import a Filter Click Import. In the dialog that opens, locate the filter you want to import, then click Open.
- Select a Filter From the Filter drop-down, select an existing filter.
- Create a New Filter Click .
-
Delete a Filter Select a filter from the Filter drop-down, then click
.Note: If you delete a filter, it will be removed from all translation projects where it is currently in use.
-
(Optional) If you want to associate a DTD or XML schema with the XML file, click
. In the dialog that opens, locate the schema or DTD file you want to use, then click Open.
-
In the Candidate Tags section, select the tags from XML file that you want to translate. If a tag can be translated, it will be checked in the Translatable column. If you do not want to translate a tag, remove the checkmark from this column.
Example
Example
You might want to translate tags that are words, but tags that consist of all numbers might not be good candidates for translation. You should remove the checkmark from the Translatable column for these tags.
- In the Add Tag field, enter any additional tags you want to add to the XML file. These tags do not need to be in the XML file at this time, but if you know that they may be in the file in the future, you can add them here. Enter a name for the tag, then click to add the tag. If you want to remove a tag, select it from the list, then click .
-
In the Candidate Attributes section, select the attributes from XML file that you want to translate.
Note: If a tag does not have any attributes, nothing displays in this section. If you do not see any attributes in the Candidate Attributes section, try selecting a different tag.
- If you want to translate an attribute, select the check box in the Translatable column. If you do not want to translate an attribute, remove the checkmark from this column.
- In the Add Attribute field, enter any additional attributes you want to associate with a tag. These attributes do not need to be in the XML file at this time, but if you know that they may be in the file in the future, you can add them here. Enter the name for the attribute, then click to add the attribute. If you want to remove an attribute, select it from the list, then click .
-
(Optional) When you are adding a filter to an XML file, you can place restrictions on the attributes in the file to tell Lingo when to include or exclude an element for translation. You can also remove restrictions if you no longer need them.
How to Add a Restriction to an XML Attribute
-
Click Restriction. The Attribute Restriction dialog opens.
-
Select the restriction you want to apply. You can include or exclude the element if the attribute value is listed.
-
In the Add Attribute Value field, enter any additional attribute values you want to add. These tags do not need to be in the XML file at this time, but if you know that they may be in the file in the future, you can add them here. Enter the name for the attribute value, then click
to add the value. If you want to remove a value, select it from the list, then click . -
Click OK. The restriction appears in the File Filters dialog.
How to Remove a Restriction from an XML Attribute
-
In the Candidate Attributes area of the File Filters dialog, select the attribute with a restriction.
-
Click Restriction. The Attribute Restriction dialog opens.
- Click Clear Restriction.
-
- Click OK.
How to Create a File Type Filter—Text Files
-
From the Filter drop-down, select Create New.
- Enter a name for your filter and click OK. The File Filters dialog opens.
- (Optional) If you want to open an existing filter, create a new filter, or delete a filter, do one of the following:
- Import a Filter Click Import. In the dialog that opens, locate the filter you want to import, then click Open.
- Select a Filter From the Filter drop-down, select an existing filter.
- Create a New Filter Click .
Delete a Filter Select a filter from the Filter drop-down, then click
.Note: If you delete a filter, it will be removed from all translation projects where it is currently in use.
-
In the Segment field, enter a regular expression to identify the text you want to translate.
-
In the Note field, enter a regular expression to identify the text you want to include as a note for each segment.
Example
Let's say you have a text file that looks like this:
You want to include everything on the left side of the text file (between the quotation marks) as a note in your translatable file, and everything on the right side of the text file (after the equal sign) as the segment for translation.
To accomplish this, you would create a filter using regular expressions that look like this:
When you create the project, it will look like this:
- Click OK.
-
Add Folders to a Lingo Project
-
In the Start New Project Wizard, click Add Folder.
-
In the dialog that opens, navigate to the folder that contains the files that you want to translate and click Select Folder.
-
(Optional) Select the file types you want to import for translation.
-
In the File Types column, click File Types if you want to select the kinds of files to import for translation. The Translatable File Types dialog opens.
-
In the Translate column, all the file types in the folder are selected by default. Deselect any file types you do not want to import. To quickly toggle all the check boxes in the Translate column, click the Select All check box.
Note: If you select a folder that contains a MadCap project, such as a Flare or Mimic project, only translatable file types will display in the Translatable File Types dialog. For example, a Flare project may display Capture images (PNG or JPG files) and Flare topic files (HTM files), but not Flare glossary files (FLGLO files).
- Click OK. The file types you are importing display in the File Types column.
-
- (Optional) If you need to remove a folder from the project, click Remove.
-
(Optional) If you want to create file type filters for the files within the folder, from the Filter drop-down, select Customize Folder. The File Types Filters dialog opens.
If you want to filter the translated files, you can create a file type filter. Use the Filter drop-down to select an existing filter, or select Create New to create a new one. You can add file type filters to XML, Word, or text files.
For more information about creating file filters, see How to Create a File Type Filter—Word Files.
-
(Optional) If you want to copy all files in the folders you added, select Copy all files in selected folders.
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.
-
- Click Next.
-
(Optional) Available translation memory (TM) databases are listed in a grid, and you can select the ones you want to use for the current project
add/remove tm databases to/from grid
If you have additional TM databases that are not shown in the grid, you can add them. Click Add and from the drop-down select one of the following:
- Local Select this option if you want to use SQLite for a local TM database. This option opens a simple dialog that lets you give the new database a name and choose where to store it. By default, the location for SQLite databases is in Documents\Lingo Translation Memories on your computer. However, you can choose a different location if you like.
-
Server Select this option if you want to use SQL Server Express for a TM database to be stored on a server. This opens a dialog with fields for the name, server, and security information related to the database.
Note: If you do not already have SQL Server Express installed and you try to install a server
In addition, you can remove TM databases from the grid if you do not want to see them. This does not delete the databases altogether; it simply removes them from the interface. To remove a TM database, select the row in the grid and click Remove.
example
The following shows how you might add or remove TM databases:
create new tm databases
You can also create new TM databases. This is different from the option to add databases. Adding a database simply makes sure a TM that already exists is shown in the grid so you can select it. On the other hand, creating a database builds a brand new database, adds it to the grid, and automatically selects the Use check box so that it will be associated with the project. To create a new TM database, click Create and select Local or Server, depending on whether you want to create a SQLite or SQL Express database, respectively. Then complete the fields in the appropriate dialog.
example
Let's say you are creating a new Lingo project and you already have one local TM database that you plan to use.
However, you want to create an additional local database to use in the project. So you select Create and select Local.
The New Local Translation Memory Database dialog opens. You give the database a name and keep the default location where it will be stored.
When you are finished, the new database is shown in the grid and the Use check box is automatically selected.
import tmx files
If you already have a Translation Memory eXchange (TMX) file containing translations, you can import it into any of the TM databases shown in the grid. To do this, select the database in the grid, then click Import. Complete the fields in the dialog and click Start Import.
example
Let's say you are creating a new project and you have created a new TM database. The new database is obviously empty. However, you have a TMX file with lots of translations, and you want the new database to have these translations. So with the database selected in the grid, you click Import.
Finally, you would use the dialog that opens to find and select the TMX file to import.
choose tm database(s) for the project
You might have several TM databases shown in this grid, but they will not be associated with the project until you click Use next to them. After you do this, those databases will be associated with the project, allowing you to use matching translation suggestions from them.
example
Here is an example where two TM databases are selected for use in a new project:
specify access—read & write versus read only
In the grid listing TM databases, there is a drop-down field to specify the access rights for each database. There are options for Read & Write, as well as for Read Only. By default all databases are set to Read & Write, which means they can be altered once they are loaded into the Lingo project. However, you can change any of the databases to Read Only access if you want. In order to switch to Read Only access, the Use check box must first be selected for that database.
example
Let's say you are connecting your new Lingo project to four different TM databases, like this:
You want to receive translation suggestions from all of the databases. However, when you confirm new translations and upload them to TM, let's say you only want to upload them to the database called "Local1." Therefore, even though the Lingo project will be connected to all four databases, three of them should be set as Read Only, and Local1 should be set to Read & Write.
Select Machine Translation Providers
If you want to apply translation suggestions from a machine translation (MT) provider, you can select the provider(s) you want to use when you are setting up your Lingo project.
From the Select Machine Translation Providers drop-down, select the check box(es) for the provider(s) you want to use to machine translate your project. If you need to enter machine translation credentials for these providers, you can add that information after you create the project, in the Options dialog or by selecting Resources>Choose MT. See Translating Projects with Machine Translation.
pre-translate files
You can automatically apply matching translations from a TM database, and if there are spots where you do not have matches, you can choose to have Lingo fill in those segments with matches from a machine translation provider. After the project is created, you can review those segments in the Translation Editor and confirm them if you don't want to make any further changes to them.
From the Pre-translate options drop-down, select the option to use for pre-translation:
- No pre-translation Do not pre-translate the project
- Pre-translate with TM Apply matches from the translation memory to segments in the project
- Pre-translate with TM then MT Apply matches from the translation memory to segments in the project, then apply machine translation to any segments that are not translated
example
Let’s say you have performed a great deal of translation work for a particular client. Once in a while, the source files from that client contain identical segments to those you have already translated in previous projects, and you have uploaded those translations to TM. One day, this client sends you some source files for a new translation project, and these source files include 73 segments that you have already translated for them in the past. During the process of creating the new Lingo project, you select the TM database containing those translations and you click Pre-translate. When Lingo finishes creating the new project, it automatically applies matching translations to all 73 of those segments.
example
Let’s say you are translating a project using a TM that has been passed along to you from a former colleague. It was assembled using translations from lots of other projects, and you're not sure exactly how accurate it will be, but you want to make a first pass through your project to see what matches there are.
You build a new project and add the TM, then tell Lingo to pre-translate the project using matches from the TM only. When it finishes, you have a few solid matches and a lot of fuzzy matches. However, you also have quite a few empty segments.
You decide to rebuild the project and add an MT provider as a backup for the pre-translation option, because you know it will fill in the gaps where you are missing translations. You also know it will provide machine translated suggestions in the TM Suggestions area for all your segments, so you can refer to these when updating your fuzzy translations later.
When the new project finishes, you have translations for most of your segments. Now you can review the MT suggestions and make any necessary adjustments, and then add new translations where needed. When you're done, you can add all the completed translations to the existing TM so you'll have a better database to work with in the future.
Note: Lingo will use your existing fuzzy match settings to fill in matches using the TM. In the Options dialog (File>Options or Tools>Options), you can change the percentage for fuzzy matches to be filled in.
Note: In the Options dialog, you can select a check box labeled "Accept Exact Matches upon applying TM." This option automatically confirms matching segments that are applied at the project or file level.
Note: If you apply TM to a project with multiple TM databases selected, Lingo applies matching translations from the first database selected.
Note: If you apply TM and a segment has multiple exact or context matches, Lingo applies the first one it finds in the TM database.
- Click Next.
-
(Optional) Available termbases are listed in a grid, and you can select the ones you want to use for the current project
add/remove Termbases to/from grid
If you have additional termbases that are not shown in the grid, you can add them. Click Add and from the drop-down select one of the following:
- Local Select this option if you want to use SQLite for a local termbase. This option opens a simple dialog that lets you give the new database a name and choose where to store it. By default, the location for SQLite databases is in Documents\Lingo Termbases on your computer. However, you can choose a different location if you like.
-
Server Select this option if you want to use SQL Server Express for a termbase to be stored on a server. This opens a dialog with fields for the name, server, and security information related to the database.
Note: If you do not already have SQL Server Express installed and you try to install a server
In addition, you can remove termbases from the grid if you do not want to see them. This does not delete the termbase altogether; it simply removes them from the interface. To remove a termbase, select the row in the grid and click Remove.
example
The following shows how you might add or remove termbases:
create new Termbases
You can also create new termbases. This is different from the option to add termbases. Adding a termbase simply makes sure a termbase that already exists is shown in the grid so you can select it. On the other hand, creating a termbase builds a brand new termbase, adds it to the grid, and automatically selects the Use check box so that it will be associated with the project. To create a new termbase, click Create and select Local or Server, depending on whether you want to create a SQLite or SQL Express termbase, respectively. Then complete the fields in the appropriate dialog.
example
Let's say you are creating a new Lingo project and you already have one local termbase that you plan to use.
However, you want to create an additional local termbase to use in the project. So you select Create and select Local.
The New Local Termbase dialog opens. You give the termbase a name and keep the default location where it will be stored.
When you are finished, the new termbase is shown in the grid and the Use check box is automatically selected.
import Termbase files
If you already have a termbase file containing definitions and terms, you can import it into any of the termbases shown in the grid. To do this, select the termbase in the grid, then click Import. Complete the fields in the dialog and click Start Import. You can import Termbase eXchange (TBX), comma-separated value (CSV), and Microsoft Excel (XLS and XLSX) files.
example
Let's say you are creating a new project and you have created a new termbase. The new termbase is obviously empty. However, you have a TBX file with lots of definitions, and you want the new termbase to have these definitions. So with the termbase selected in the grid, you click Import.
Finally, you would use the dialog that opens to find and select the TBX file to import.
choose Termbase(s) for the project
You might have several termbases shown in this grid, but they will not be associated with the project until you click Use next to them. After you do this, those termbases will be associated with the project, allowing you to insert matching definitions from them.
example
Here is an example where two termbases are selected for use in a new project:
specify access—read & write versus read only
In the grid listing termbases, there is a drop-down field to specify the access rights for each database. There are options for Read & Write, as well as for Read Only. By default all termbases are set to Read & Write, which means they can be altered once they are loaded into the Lingo project. However, you can change any of the termbases to Read Only access if you want. In order to switch to Read Only access, the Use check box must first be selected for that termbase.
example
Let's say you are connecting your new Lingo project to four different termbases, like this:
You want to see terms and definitions from all of the termbases. However, when you add new terms to the termbase, let's say you only want to upload them to the termbase called "LocalTB4." Therefore, even though the Lingo project will be connected to all four termbases, three of them should be set as Read Only, and LocalTB4 should be set to Read & Write.
- Click Next.
-
(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.
more information
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.
- Click Finish.
When you create a new Lingo project, a file with an .liprj extension is automatically generated (e.g., My Project Italian.liprj). This is the main file for the project and is stored at the root level of the project folder in Windows (e.g., Documents\My Translated Projects\My Project Italian\My Project Italian.liprj). You can open the project by double-clicking this file.
