USER GUIDEMADCAP LINGO 10.2

What's New

Copyright 2018 MadCap Software. All rights reserved.
Information in this document is subject to change without notice. The software described in this document is furnished under a license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of those agreements. No part of this publication may be reproduced, stored in a retrieval system,or transmitted in any form or any means electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of MadCap Software.
MadCap Software
7777 Fay Avenue
La Jolla, California 92037
858-320-0387
www.madcapsoftware.com

THIS PDF WAS CREATED US ING M ADCAP FL ARE.

CONTENTS

CHAPTER 1
Introduction

6

Summary of Lingo 10 Major New Features7

Summary of Lingo 10 Additional New Features8

Summary of Lingo 10.1 New Features10

Summary of Lingo 10.2 New Features

11

CHAPTER 2
DITA Translation Enhancements

12

Content References

13

Dynamic Attribute Filtering

16

New Element Types Supported for Translation

22

CHAPTER 3
Dynamic Filtering

23

Filtering Out Conditions

24

Filtering by Target

30

Settings

34

CHAPTER 4
Flare Integration Enhancements
Font Mapping

CONTENTS

35
36

iii

Index and Glossary Sort Orders

39

Language Skins

42

CHAPTER 5
Flattening

44

Flattening Snippets

45

Flattening Variables

50

Settings

56

CHAPTER 6
Source Control

57

CHAPTER 7
Additional New Features

58

64-bit Support

59

Command Line60

Dictionaries (Global) and Spell Check Enhancements

61

File Type Support Enhancements

70

Help—Live or Local

78

Image Replacement

81

Project Export Enhancements

93

Project Properties Dialog

94

Report Enhancements

99

Smart Quotes

106

TOC View Window Pane

107

Translation Editor Enhancements

111

CHAPTER 8

CONTENTS

New Features for Lingo 10.1

122Filter by Multiple Targets

123

iv

Show/Hide Spaces in Editors

125

Microsoft Bing Machine Translation Changes

127

Importing Alternate Tag Segments

129

CHAPTER 9
New Features for Lingo 10.2

130

Adobe FrameMaker 2017 Support

131

Custom Installation

132

Find and Replace Enhancements

134

Microsoft TFS 2017/2018 Support

138

APPENDIX
PDFs

CONTENTS

139v

CHAPTER 1

Introduction
This release of Lingo contains several new features and enhancements.
For more information about each feature discussed in this manual, open the online Help and refer tothe "What's New" topic. Links are provided in some feature descriptions, taking you to topics that
contain additional information and steps.
This chapter discusses the following:

CHAPTER 1

Summary of Lingo 10 Major New Features7

Summary of Lingo 10 Additional New Features8

Summary of Lingo 10.1 New Features10

Summary of Lingo 10.2 New Features116

Summary of Lingo 10 Major New Features
Following are the major new features introduced in this version of Lingo.
FeatureDITA Translation
Enhancements

Dynamic Filtering

Flare Integration
Enhancements

Flattening

Source Control

CHAPTER 1

What's New?
n

ConfrefsnDynamic attribute filteringn

New element types
supportedn

ConditionsnTargetsn

Font mappingnIndex and glossary
sort ordersnLanguage skinsnFlatten snippetsn

Flatten variablesnApache Subversion

n

Git

n

Microsoft Team
Foundation ServernPerforce

For More Information
See "DITA Translation Enhancements"
on page 12.

See "Dynamic Filtering" on page 23.

See "Flare Integration Enhancements"
on page 35.

See "Flattening" on page 44.

See "Source Control" on page 57.

7

Summary of Lingo 10 Additional New
Features
Following are several additional new features and enhancements introduced this version of Lingo.
Feature64-Bit Support

What's New?

For More Informationn

Lingo is now 64-bitnBetter access to RAMnExport a Lingo projectn

Export a Lingo project ina specific languagenUpdate/sync a Lingo project with the source filenGlobal or project dictionariesn

Redesigned Spell Checkwindow panen

Import unrecognized filetypes as text filesnFrameMaker files sent
for reviewnFlare target files for PDF
and EPUB

Help—Live or
Local

n

Choice between live
See "Help—Live or Local" on page 78.
external or local Help system

Image ReplacementnBatch and multi-language image replacementn

Skin image replacement

Command Line

Dictionaries andSpell Check

File Type Support

CHAPTER 1

See "64-bit Support" on page 59.

See "Command Line" on page 60.

See "Dictionaries (Global) and Spell Check
Enhancements" on page 61.

See "File Type Support Enhancements" onpage 70.

See "Image Replacement" on page 81.

8Feature

What's New?

For More Information

Project ExportnUpdate previously exported versions

See "Project Export Enhancements" on page
93.

Project Properties DialognBasic information

See "Project Properties Dialog" on page 94.

nProject settings

Reportsn

New QA reportsnStyling updates

Smart QuotesnReplace quotes basedon target language

See "Smart Quotes" on page 106.

TOC View Window Panen

Filter files according to
TOC from Flare project

See "TOC View Window Pane" on page 107.

Translation EditornImproved conditional
text support

See "Translation Editor Enhancements" onpage 111.

n

Cleaner index andconcept tags

CHAPTER 1

See "Report Enhancements" on page 99.

9Summary of Lingo 10.1 New Features
Following are the new features introduced in Lingo 10.1.
FeatureFilter by Multiple Targets

What's New?
nChoose more than one target
to filtern

Used when creating projector performing dynamic filtering

Show/Hide Spaces in
Editorsn

New button in editorsn

Shows or hides spaces
between words

Microsoft Bing
Machine Translation
Changesn

Provide API keyn

Can also provide category

Importing Alternate
Tag SegmentsnUseful when importing TMX
files previously used in thirdparty tools

CHAPTER 1

For More Information
See "Filter by Multiple Targets" onpage 123.

See "Show/Hide Spaces in Editors" on page 125.

See "Microsoft Bing MachineTranslation Changes" on page
127.
See "Importing Alternate Tag Segments" on page 129.

10

Summary of Lingo 10.2 New Features
Following are the new features introduced in Lingo 10.2.
FeatureWhat's New?

For More Information

Adobe FrameMaker
2017nSupport for new version

See "Adobe FrameMaker 2017
Support" on page 131.

Custom Installationn

Option to install local Help or use
server Help only

See "Custom Installation" onpage 132.

Find and Replace
EnhancementsnLimit results to the first instancein each file

See "Find and Replace Enhancements" on page 134.

nDrop-down with options added toquick find and replace widgetn

Support for newer versions

Microsoft TFS
2017/2018

CHAPTER 1

See "Microsoft TFS 2017/2018
Support" on page 138.

11

CHAPTER 2

DITA Translation
Enhancements
Lingo now supports content references and parses them for translation. You can also flatten content references to text and translate them in the Translation Editor. Additionally, many new element
types have been added, and you can now filter your project content based on several
DITA attributes.
This chapter discusses the following:

CHAPTER 2

Content References

13

Dynamic Attribute Filtering

16

New Element Types Supported for Translation

22

12

Content References
If the conref is flattened, translators can edit the translation to make it more appropriate for the segment where it appears. Flattened conrefs appear as normal text in the Translation Editor, while
unflattened conrefs appear as tags. Transltors can move these tags to their correct location in thetarget segment.
Similarly, you may have multiple versions of content based on the document you are writing. This isoften the case if you have content that needs to be translated differently for different audiences.
You can flatten conrefs when creating a new project, or you can change an existing project's flattening settings using the Project Properties dialog. Settings are updated dynamically, so you do notneed to update the project to apply the settings.

CHAPTER 2

13

EXAMPLE
You use content references throughout your DITA project. You know that your existingtranslation memory (TM) already includes some of the segments in your project, but
the segments in your TM do not use content references; instead, the text is written as
part of the segment. Because of this, you decide to flatten the content references inyour entire project. This way, when you send the project to your translator, she will get
the most accurate matches from your existing TM. This will also let her account forcontext in the segment when translating the content references.

CHAPTER 2

14

NOTE: The DITA file associated with a conref must be part of your ditamap, otherwise
Lingo will not be able to locate the file when importing the DITA project.

NOTE: As a best practice, you should always translate conrefs in the associated DITA file,even if you have flattened them and translated them in the segment. Lingo will use thetranslation from these files for instances of the conref that are not included in the segment(e.g., conrefs that are removed from the Translation Editor).

NOTE: You can flatten both inline and block conrefs. Flattening block conrefs may add additional tags to the segment in order to preserve the formatting found in the block of content.

CHAPTER 2

15

Dynamic Attribute Filtering
You can filter DITA files to include one or more conditional attributes. The resulting Lingo project will
include all of the translatable files that are marked with the selected attributes (while excluding
those that are not selected). Additionally, because Lingo supports block-level and inline attributes,
content within a segment that is marked with an excluded attribute will also be excluded from afiltered Lingo project.
If you use conditional attributes to filter your Lingo project, the filtered content and files will be usedthroughout your project when running reports, creating bundles, and performing other tasks. For
example, if you pull a report, you will only see data from the filtered content. If you make a bundle,
you will only be able to select from files that are included in the project.
You can filter a project when creating a new project, or you can make changes to an existing project's filtering settings using the Project Properties dialog. Settings are updated dynamically, so you
do not need to update the project to apply the settings.

CHAPTER 2

16

EXAMPLE
Your DITA files include information for Mac, Windows, and Linux operating systems. In
your DITA files, you used the platform attribute to mark the content applicable to eachof these operating systems. Additionally, you used the audience attribute to mark content for expert and novice users.

CHAPTER 2

17

When creating your Lingo project, you have the option to filter your content by either
the platform or audience attributes. You could also filter the content using both attributes.
You need to translate all of the content that is applicable to all of your users who use
Windows. You select the windows platform attribute to include this attribute type(excluding Mac and Linux) and leave the audience attribute set to All (including bothexpert and novice users).

CHAPTER 2

18

Your project looks like this in Lingo:

CHAPTER 2

19

You then use Lingo to create a bundle and send the Windows files to your translator.

CHAPTER 2

20

You also need to translate content for expert Linux users, but this content goes to a different translator. You open the Project Properties dialog and adjust the filter settings
so the platform attribute is set to linux (excluding Mac and Windows) and the audience
attribute is set to expert (excluding novice users).

Your project dynamically updates, and now it looks like this in Lingo:

Because your project now displays only the expert-level Linux files, you can create abundle with these files and send them to the other translator.

NOTE: If you update the filter settings for an existing project, the translation status ofchanged segments is set to Untranslated. You also have the option to completely clear any
existing translations for these segments.

CHAPTER 2

21

New Element Types Supported forTranslation
Lingo now parses several new DITA element types for translation. The following elements are now
translatable:
n

<alt>

n

<author>n<codeblock>n<desc>

n<glossaryacronym>n<glossarysurfaceform>n<glossdef>n<glossterm>n<indexterm>n<mainbooktitle>n<ph conref>

n<publisher>n<refsyn>n<related-links conref>

n<stepresult>n<xref>

NOTE: For more detailed information about DITA, please refer to:www.oasis-open.org/committees/dita/.

CHAPTER 2

22

CHAPTER 3

Dynamic Filtering
You can now filter a source Flare project by target or conditions. Filtering by target allows you to create a Lingo project that includes files in a specific Flare target, while filtering by condition removes
files and content marked with specific conditions. Using filtering options narrows down large Flareprojects or more easily breaks down large projects into smaller chunks based on conditions or targets.
You can filter a project when creating a new project, or you can make changes to an existing project's filter settings using the Project Properties dialog. Settings are updated dynamically, so you do
not need to update the project to apply the settings.
This chapter discusses the following:

CHAPTER 3

Filtering Out Conditions

24

Filtering by Target

30

Settings

34

23

Filtering Out Conditions
You can filter Flare projects to exclude one or more conditions. You can also select conditions
based on the entire condition set, or you can pick the specific conditions in the set that you want tofilter by. The resulting Lingo project will include all of the translatable files that are not marked withthe selected conditions. Additionally, because Lingo supports block-level, inline, glossary, snippet,and CSS conditions, content within a file or segment that is marked with an excluded condition tag
will also be excluded from a filtered Lingo project.
If you use condition tags to filter your Lingo project, the filtered content and files will be usedthroughout your Lingo project when running reports, creating bundles, viewing glossary terms, andperforming other tasks. For example, if you pull a report, you will only see data from the filtered content. If you make a bundle, you will only be able to select from files that are included in the project.

CHAPTER 3

24

EXAMPLE
You are an author with a very large Flare project, but you only need to send specificfiles to your translator. Rather than exporting your entire project to Lingo and thensearching for the individual files that you need to export for translation, you insteadmark the files and folders you do not need to translate with a "Do Not
Translate" condition tag as you create each item in Flare.

CHAPTER 3

25

In Lingo, you then filter the project to exclude the condition tag, creating a new Lingo
project that only includes the files you need to send to your translator.

CHAPTER 3

26

When you open the project in Lingo, it looks like this:Because you applied the "Do Not Translate" condition throughout your project, you see
only a handful of topics and images. You also see a few project files, such as your glossary, variables file, and TOCs.

CHAPTER 3

27

EXAMPLE
The content author filtered her Flare project to exclude a "Do Not Translate" condition
tag. Of the nine lines in the original topic (including the heading), four were marked witha "Do Not Translate" condition tag.

CHAPTER 3

28

When you view the topic in the Translation Editor, only five segments appear in Lingo.
This is because four lines were excluded when the project was created. Additionally,
you see blue condition tag indicators in some segments where individual words wereconditioned out and excluded from a segment.

NOTE: Conditions that "unbind" rather than "exclude" content will not be excluded when you
filter out a condition in Lingo. If you notice that content has not been removed but you thinkthat it should be, check to be sure that the condition is not marked as an "unbind" conditionin Flare.

CHAPTER 3

29

Filtering by Target
You can filter your Flare projects by one or more targets. The resulting project will include all of thetranslatable files that are part of the selected target(s), such as topics, images, skins, and variables.
A good reason to use target filters is if you need to maintain different translations for different targets. Additionally, you could filter to a specific target and use variable flattening if you need use different definitions of a variable in different targets.
EXAMPLEYou are preparing Lingo projects for your translators. You have two translators: asenior translator who translates your PDF manuals and online Help; and an assistanttranslator who translates shorter documents, like brochures.
When you import your Flare project to Lingo, you decide to filter by target. Rather thancreating a big Lingo project and then trying to remember which files go in the brochures and which go in the online Help, it's faster for you to use the targets you alreadycreated in Flare to quickly filter the project.
First, you need to send files to your assistant translator, who is working on a brochure
about lists. To do this, you filter by the Brochure target.

CHAPTER 3

30

CHAPTER 3

31

Lingo automatically adds the correct files to the project, and you can easily bundle thefiles and send them to the assistant translator.

CHAPTER 3

32

Additionally, since the variable definitions used in the project are determined by the target filter, your translator will see the correct variables when translating the project.

NOTE: If you filter by target, target-specific variables can be translated in the target filefrom the File List. Default variable definitions are translated in the variable set file (they are
not considered target-specific, even if selected for a target).
All other variables (and variables in projects not filtered by target) can be translated in thevariables file.
As a best practice, you should translate variables in the variable set or target file, even if you
have flattened them and translated them in the segment. Lingo will use the translation fromthese files for instances of the variable that are not included in the segment (e.g., variabletags that are removed from the Translation Editor).

CHAPTER 3

33

Settings
You can filter conditions and targets when creating a new project, or you can update an existing project's filtering settings on the Flare Settings tab of the Project Properties dialog (File>Project Properties). The settings are the same in both locations.
nFilter by target Select this option, then select the target whose files you want to include in the
Lingo project. Any files that are not part of that target will not be shown in the File List. If you
want to replace variable definitions for a specific target, you can select variables from theSelect variables to flatten grid.

nFilter out condition Select this option, then click Select conditions. In the dialog that opens,select the condition tag set(s) you want to exclude from the Lingo project from the grid on theleft side of the dialog. Then select or deselect individual condition tags in each set from thegrid on the right side of the dialog.

NOTE: You can also filter DITA projects using conditional attributes.

NOTE: If you update the filter settings for an existing project, the translation status ofchanged segments is set to Untranslated. You also have the option to completely clear any
existing translations for these segments.

CHAPTER 3

34

CHAPTER 4

Flare Integration
Enhancements
Enhancements have been made to improve the way Lingo projects integrate with MadCap Flare.
These features include the ability to create font maps, sort index and glossary terms, and create language skins.
This chapter discusses the following:

CHAPTER 4

Font Mapping

36

Index and Glossary Sort Orders

39

Language Skins

42

35

Font Mapping
If you are translating a project into multiple languages, you may need to use different fonts for eachlanguage. Using fonts appropriate for the language's character set ensures that the characters display correctly when viewed in the output. You can use Lingo's font mapping feature to locate thefonts already used in the source Flare project and map them to fonts that are supported by each target language.
To do this, open the Manage font Maps dialog (Resources>Manage Font Mapping) and create afont map, then edit it. In the dialog that opens, select the files you want to scan. Lingo will searchthese files and list the fonts currently being used. Then you can select the font you want to map toeach original font. You can do this for each language in your project.
When the translated project is exported, the Flare project will use the mapped fonts for each language.
EXAMPLEYou are translating a Flare project that was originally written in English. You need totranslate it into French and Arabic. You know that each of these documents will use different fonts in the final output, so you use Lingo to create a font map.
First you scan your project files for fonts. The files are currently using Arial, Calibri, andCambria. This is fine for French, which does not need to display a special character set,
and therefore does not need a special font. However, you need to use a different fontfor Arabic in order to support the language's character set. You switch the language to
Arabic and map each of the fonts in your project to B Fantezy, which is an Arabic font.

CHAPTER 4

36

CHAPTER 4

37

When the author exports the Arabic project back to Flare, the output uses B Fantezy
and all of the characters are supported.

NOTE: Lingo scans the following file types for fonts:n

Master pages (.flmsp)

nPage layouts (.flpgl)

nSnippets (.flsnp)nStylesheets and table stylesheets (.css)nTopics (.htm)

NOTE: Some fonts (like Arial) include characters used in other languages. However, there is
no guarantee that these fonts will work well in all programs or in all browsers. For best results, you should always map fonts to an appropriate character set

CHAPTER 4

38

Index and Glossary Sort Orders
There may be times that you want to create a custom sort order for your Flare index or glossary.
You can do this by adding a "Sort As" term to the index or glossary term. Custom sort orders areespecially important when translating a Flare project because terms in each translated language
may have different spellings or pronunciations that are not automatically picked up by Flare.
Because of this, you may need to specify how the index or glossary should sort a term, so the term isidentified correctly when the Lingo project is exported back to Flare.
After you translate the index or glossary file, open the Project Properties dialog and select the Sort
Order tab. From here, you can see all of the index or glossary terms in your project, as well as thecustom terms set for the source project, if applicable. If any of the translated terms need to be sorted using a different letter, you can add an entry in the Sort As column. When the author exports thetranslated project to Flare, the index or glossary will use the new terms to alphabetize the entries.

CHAPTER 4

39

EXAMPLE
You are translating a project into Japanese, which uses three different charactertypes. You are translating mostly in kanji, but you want to use katakana in your index
and glossary because these characters are phonetic.
Because of this, you use Lingo's sort as feature to add katakana "Sort As" terms foreach index and glossary word in the Lingo project.

CHAPTER 4

40

Later, when the project is exported back to Flare, the index and glossary are sorted
using the katakana alphabet instead of the kanji alphabet.

NOTE: If your project has been filtered by a target or condition tag, the glossary file only displays terms that have not been excluded.

CHAPTER 4

41

Language Skins
When you create your Lingo project, you have the option to add a language skin to your project. This
generates a language skin file (LanguageSkin.fllng) containing several terms used in different Flareskins (e.g., "Table of Contents," "Glossary," "Home"). Translators can open the language skin file totranslate these terms. This is especially useful if there are custom terms in the Flare skin and theyneed to be translated to match the custom interface.
When you export the project back to Flare, the language skin can be seen by opening the Project
Organizer, then selecting the Advanced folder. Additional changes can be made to the languageskin in Flare, if necessary. When the output is generated, the translations in the language skinreplace Flare's default translations for interface elements.
NOTE: If your project's target language has an available spell check dictionary, some translations will be pre-populated when you create your language skin. The available translations
vary depending on the language you are using. Languages with an available spell check dictionary are displayed in bold when you select a language during project creation.

CHAPTER 4

42

NOTE: When translating language skin segments, the interface element value is added tothe segment as a segment note for your reference.

NOTE: You can only add language skins to a project if there are not language skins alreadyin the source Flare project. If the source Flare project already includes one or more language skins, they will be added to the Lingo project and can be translated.

CHAPTER 4

43

CHAPTER 5

Flattening
You can now replace Flare variables and snippets with text in the Translation Editor. This is referred
to as "flattening."
If the content is flattened, translators can edit the translation to make it more appropriate for thesegment where it appears.
Similarly, you may have multiple versions of content based on the document you are writing. This isoften the case if you have content that needs to be translated differently for different audiences.
You can flatten snippets and variables when creating a new project, or you can change an existing
project's flattening settings using the Project Properties dialog. Settings are updated dynamically,
so you do not need to update the project to apply the settings.
This chapter discusses the following:

CHAPTER 5

Flattening Snippets

45

Flattening Variables

50

Settings

56

44

Flattening Snippets
You can flatten sub-segment snippets (i.e., snippets that are part of a segment, as opposed to theirown tag). This means that snippet content will be included as text in the segment in Lingo. Translating a snippet as part of the segment allows translators to account for context, rather than translating each snippet individually. This also makes sure that you have the most accurate translationsin the translation memory.
Flattened snippets appear as normal text in the Translation Editor, while unflattened snippets
appear as tags. Translators can move these tags to their correct location in the target segment.
EXAMPLE
There are several short snippets in your Lingo project. Sometimes they appear as partof a segment. Other snippets appear as their own segments.

CHAPTER 5

45

If you do not flatten the snippets...

CHAPTER 5

46

...the content in Lingo looks as follows. Because the snippets are unflattened, you seetags where the snippets appear in the segments. You can drag each tag into the target
segment. Snippets that are part of their own segment do not appear as tags in theTranslation Editor.

You can translate all of the snippets in the snippet files, which are found in the File List.

CHAPTER 5

47

If you do flatten your snippets...

CHAPTER 5

48

...the content in Lingo looks as follows. Content from each snippet appears in theTranslation Editor as text.

NOTE: You can flatten both inline and block snippets. Flattening block snippets may add
additional tags to the segment in order to preserve the formatting found in the block of content.

NOTE: As a best practice, you should always translate snippet content in the snippet files,
even if you have flattened them and translated them in the segment. Lingo will use thetranslation from these files if it finds instances of the snippet that are not included in thesegment (e.g., snippet tags that are removed from the Translation Editor).

CHAPTER 5

49

Flattening Variables
Replacing variables with their definitions is referred to as "flattening." You can flatten variables froma specific variable set, and you can select certain variables in a set. This gives the translator greater
flexibility when translating, because some variables (like a company name) may never need to betranslated, but others may always need to be translated.
Flattened variables appear as normal text in the Translation Editor, while unflattened variables
appear as tags. Translators can move these tags to their correct location in the target segment.
Additionally, you can use variable flattening in conjunction with target filtering if you need use different definitions of a variable in different targets.

CHAPTER 5

50

EXAMPLE
You are a Flare author writing a short manual for a company that has two internalteams: Red and Blue. One of the variables in your project is a target-specific"Team" variable with two definitions: "Red" and "Blue."
You need your manual translated into Spanish. When creating your Lingo project, youfilter the Flare project by target so you only see the appropriate topics and variables foreach team.
The first document you produce is the one for the Blue team. To do this, you filter by
the "Blue" target when creating the Lingo project. You do not flatten the variables forthis project.

CHAPTER 5

51

The variable definition for "Blue" that was specified in your Flare project is included in
the Lingo project. When finished, you bundle the project and send it to your translator.
Because you did not flatten the variables in the project, your translator will translate thevariable in the target file (because it is target-specific).

CHAPTER 5

52

When translating segments, he simply moves the "Blue" tag in the source segment to
the target segment. He does not need to translate the variable each time he encounters it in a topic.

When you create the Lingo project for the Red team, you decide to flatten the "Red" variable. Unlike "Blue," which does not take on a different gender depending on the words it
modifies, "Red" might be masculine or feminine. You know that you may need tochange the variable slightly to use correct gender agreement.

CHAPTER 553

To do this, you update the project's settings on the Flare Settings tab of the Project
Properties dialog (File > Project Properties). You choose to filter by the Red target. You
also select the "Team" variable (which has the "Red" definition in this target) from theSelect variables to flatten area at the top of the tab.

CHAPTER 5

54

When finished, you bundle the project and send it to your translator.
By flattening the variable, your translator can translate it directly in the segment andmake changes based on the context of the sentence.

The variable also appears in the target file, because Lingo will use this translation if thevariable is used elsewhere in the project.

NOTE: If you filter by target, target-specific variables can be translated in the target filefrom the File List. Default variable definitions are translated in the variable set file (they are
not considered target-specific, even if selected for a target).
All other variables (and variables in projects not filtered by target) can be translated in thevariables file.
As a best practice, you should translate variables in the variable set or target file, even if you
have flattened them and translated them in the segment. Lingo will use the translation fromthese files for instances of the variable that are not included in the segment (e.g., variabletags that are removed from the Translation Editor).

CHAPTER 5

55

Settings
You can flatten snippets and variables when creating a new project, or you (or the translator) can
update an existing project's flattening settings on the Flare Settings tab of the Project Properties dialog (File>Project Properties). The settings are the same in both locations.
n

Flatten a Variable Select the variable set(s) you want to flatten from the grid on the left side ofthe dialog. Then select or deselect individual variables from the grid on the right side of the dialog. If you want to replace variable definitions for a specific target, you can optionally select atarget from the Filter to target drop-down.

nFlatten a Snippet Select Convert sub-segment snippets to text at the bottom of the dialog.
This will convert all inline snippets to text.

NOTE: If you update the flattening settings for an existing project, the translation status ofchanged segments is set to Untranslated. You also have the option to completely clear any
existing translations for these segments.

NOTE: You can also flatten DITA content references.

CHAPTER 5

56

CHAPTER 6

Source Control
Lingo provides integrated source control support for Subversion, Git, Team Foundation Server, andPerforce.
Source control is a process where you store a copy of your project on a server, allowing you to“check in” and “check out” files and keep your local changes in sync with the server version fo theproject, and with changes from other writers. Source control is even useful for single authors
because it provides a means for maintaining a constant backup of all project files.
For more information about Lingo's integrated source control support, please refer to the online
Help.
IMPORTANT: If you are using source control, do not include your local termbase (.litdb3)
and translation memory (.db) files in your project folder. These files do not function correctly when used with source control, and can cause conflicts. Instead, you should use aserver termbase or translation memory. This will allow other users to have access to theterms in the database while avoiding possible conficts.

CHAPTER 6

57

CHAPTER 7

Additional New Features
In addition to the features already discussed, some additional new features are being introduced inthis version.
This chapter discusses the following:

CHAPTER 7

64-bit Support

59

Command Line60

Dictionaries (Global) and Spell Check Enhancements

61

File Type Support Enhancements

70

Help—Live or Local

78

Image Replacement

81

Project Export Enhancements

93

Project Properties Dialog

94

Report Enhancements

99

Smart Quotes

106

TOC View Window Pane

107

Translation Editor Enhancements

111

58

64-bit Support
Lingo is now a 64-bit application. This is beneficial because 64-bit applications provide better
access to your computer's memory (RAM). This is especially useful if you have a large project oroften work with multiple files at once, because Lingo will run faster and more efficiently.
NOTE: If you have any mappings to the Lingo application (e.g., shortcuts), you will need to
update them so they point to the Program Files folder. Previous versions of Lingo were native 32-bit applications and were installed in the Program Files (x86) folder.
For example, the new location of the Lingo application is C:\Program Files\MadCap Software\MadCap Lingo 10\Lingo.app\Lingo.exe.

NOTE: If you want to import Doc-To-Help projects to a 64-bit version of Lingo, you will needto download Microsoft Access Database Engine 2010 x64 edition. If you do not already havethis add-in, Lingo will prompt you to install it from the Microsoft Download Center.

CHAPTER 7

59

Command Line
Lingo now supports the command line for managing your projects. Depending on the command(s)used, you can accomplish any of the following.
n

Export a Lingo projectn

Export a Lingo project in a specific languagenUpdate/sync a Lingo project with the source file

The best way to use the command line feature is to create a batch file with the necessary commands in it. Then you can use a scheduling tool (such as the Task Scheduler utility in Windows) to
run the batch file automatically whenever you want.
NOTE: Arguments in the command line are case sensitive.

CHAPTER 7

60

Dictionaries (Global) and Spell Check
Enhancements
Some enhancements have been made to dictionaries and the spell checking feature they support.

Dictionaries—Global or Project
In previous versions, Lingo supported only project-level custom dictionaries for spell checking purposes. By "project-level," we mean that the dictionaries you created were tied to specific projects.
These types of dictionaries are still supported. But now you also have the option of creating global
dictionaries.
A global dictionary is a file that contains words and can be used for spell checking by any Lingo project you open on your computer. This is a convenient way to ensure that all of your projects areusing the same spellings for terms, rather than having each project rely on a different dictionary.
By default, a new global dictionary is stored in your AppData folder, like all of your built-in dictionaries.
However, you can use the Options dialog to choose another location for your global dictionary. For
example, you might be working with a team of translators and want to make sure you are all using
the same spellings for certain terms. By choosing a network directory, your entire team can use thesame global dictionary.

CHAPTER 7

61

You can even use a global dictionary as well a project dictionary. If this is the case, the Spell Checkwindow pane combines and displays suggested spellings from both dictionaries, as well as from thebuilt-in dictionary for that language.

CHAPTER 7

62

Spell Check Changes
The Spell Check window pane has been redesigned, and several new options have been added to it.
This includes the following:n

Look in more locations (e.g., content document, documents in the same folder, whole project).

n

Add spellings to global or project dictionaries.

nOpen the Options dialog to set global dictionary settings, as well as to tell Lingo to ignore certain types of words or circumstances during spell check.

The process has also changed somewhat. Previously, you used the Spell Check window pane tomove from file to file to see each questionable spelling. Starting with this version, the questionable
spellings are listed in a grid at the bottom of the window pane after you start the spell check process. Click on a row to deal with a specific misspelling, then select the following row to move to thenext one, and so on.
This is desirable because you can perform all of your spell check work in one place, without having
to open a bunch of different files. However, you always have the option to open a particular filewhere a questionable spelling occurs.

CHAPTER 7

63

Also, if you press F7, the Spell Check window pane opens and automatically displays the first questionable spelling it finds in the current file.
Following are the main sections in the redesigned Spell Check window pane. Many of the fields andoptions in these sections are new or changed.

CHAPTER 7

64

SPELL CHECKIn the first drop-down,select the location where you want to perform the spell check (if you have a
Lingo project open):ncurrent document Lingo checks the spelling in the active file only.

ndocuments in the same folder Lingo checks the spelling in all files located in the same folder
as the current one.

nwhole project Lingo checks the spelling in every file in the project.

You can use the buttons to the right to initiate or stop the spell check process, as well as open thefile where a questionable spelling occurs:nStart/Cancel Display all occurrences of questionable spellings in a grid at the bottom of thewindow pane. Each time you select a row in the grid, the "Not In Dictionary" and "Suggestions"fields are populated with the results.
If the process is in progress, the label changes to "Cancel," which you can click to stop the process.

nView In File Open the file where the current questionable spelling occurs, and highlight it.

CHAPTER 7

65

CHAPTER 7

66

NOT IN DICTIONARYThis field displays each questionable spelling in its context with red, underlined font.

You can use the buttons and drop-down field to the right in order to take action on the questionable
spelling.
n

Ignore Lingo ignores the spelling of the word for the current session.

n

Ignore All Lingo ignores the spelling of the word and adds the spelling of this word to the
Ignored Words Editor (which can be opened from the Tools ribbon). This means that if otheroccurrences of the word are found in any other files in future sessions, they will not be flagged
as questionable spellings. This is similar to adding words to a dictionary. The difference is that
this feature simply ignores questionable spellings of certain words, whereas a dictionary also
lists spellings as suggestions.

n

Add To Dictionary Lingo adds the word to the dictionary so that it is not flagged as a questionable spelling in the future. The word will also be displayed as a suggestion for future questionable spellings that are very similar. The kind of dictionary (Global or Project) to which it isadded is determined by the selection in the next field.

nGlobal/Project If you select Global, spellings of words are added to a dictionary that can beused by any projects pointing to it. If you select Project, spellings of words are added to a dictionary that can be used only by the current project.

CHAPTER 7

67

SUGGESTIONSThis field displays alternative suggestions for each questionable spelling.

CHAPTER 7

68

You can use the buttons to the right in order to replace the current spelling with a suggestion, or to
set other options.
nChange Lingo changes only the current instance of the misspelled word with the alternative
word selected in the Suggestions field.

nChange All Lingo changes all instances of the misspelled word with the alternative word selected in the Suggestions field.

nOptions This opens the Spelling tab of the Options dialog.
If using a global dictionary, you can use fields at the top of the dialog to choose a location for it.
You can also use fields at the bottom to ignore any of the following when spell checking files:l

Ignore repeated wordsl

Ignore words with numbersl

Ignore uppercase wordsl

Ignore URLsl

Ignore mixed case wordsl

Ignore email addresses

WARNING: When you use a spell check suggestion to change the spelling in a file, the edit
is made on disk, not in the editor. Therefore, you cannot undo the action if you change yourmind. Instead, you will need to open the affected file and change the text manually.

CHAPTER 7

69

File Type Support Enhancements
Improvements have been made to Lingo's file type support. Flare target files are now supported,and Framemaker files—previously supported only for translation—are now also supported for review.
Additionally, you can now import any unrecognized file type, including custom file types, by using atext file filter.

Import Unrecognized File Types as Text Files
Lingo now allows you to import any file type as a text file by using a text file filter and regular expressions. This is helpful if you work with files that use uncommon or custom file extensions.
To import any file type, create a new Lingo project and add your file to Lingo. If you add a file typethat Lingo does not recognize, you will see a warning image next to the file filter drop-down.
To resolve this error, select an existing text file filter or create a new one using regular expressions.
Adding a text file filter will treat the file as a text file and allow you to import and translate the file. If
you do not select a filter, the file will be discarded when you create the project.
You can also add unrecognized file types as part of a folder. If you do this, Lingo will notify you toapply a text filter to the appropriate files within the folder. If you do not apply a filter to the unrecognized files, they will be discarded from the folder upon project creation.
IMPORTANT: Creating file type filters is recommended for advanced Lingo users. This feature requires an understanding of advanced topics such as regular expressions, XML, andsegmentation rules.
Additionally, it is recommended that you are familiar with the file(s) you are importing priorto adding a filter. Some file type filters require you to select the specific content that you
want to import (e.g., sheet labels, headers and footers, comments).

CHAPTER 7

70

EXAMPLE
You need to translate an ODF file. However, Lingo does not recognize this file type.
When you add the file to your project, you see a yellow warning icon.

To resolve this error, select the Filter drop-down and select Create New.

CHAPTER 7

71

The File Filters dialog opens, and you can create a new text file filter using regularexpressions.

When you select the new text file filter from the drop-down, the error is resolved.

CHAPTER 7

72

The file is imported for translation.

CHAPTER 7

73

FrameMaker Files Sent for Review
In previous versions of Lingo, FrameMaker files were supported for translation, but you could notsend translated files for review. In Lingo 10, you can now send translated FrameMaker files forreview using Lingo's internal review process.
When working with FrameMaker files in Lingo, you can save these files as a review package(File>Review>Save Review Package). In the dialog that opens, select the files you want to send,
then click Finish. The files will be saved as a Lingo review package (.lirev).

CHAPTER 7

74

Flare Target Files
You can now translate Flare target files (.fltar) for PDF and EPUB targets. This allows you to translate the target's metadata fields, such as the document title or description. This metadata is important when distributing content, because it helps publishers correctly categorize information, and it
helps users find the document.
You can translate the following metadata:
n

PDF
l

Keywordsl

Subjectl

Title

CHAPTER 7

75

n

EPUB
l

Description

l

Genre

l

Subjectl

Title

CHAPTER 7

76

NOTE: When you translate metadata in a PDF or EPUB target file, the metadata type isadded to the segment as a segment note.

CHAPTER 7

77

Help—Live or Local
Lingo's online and dynamic Help system has changed, pointing to files hosted externally. This allows
for live updates to the Help. Also, there is a new local Help option that lets you view Help located onyour computer instead.

Live External Help System
By default, Lingo's dynamic Help is now hosted online, rather than inside the application. This allows
topics to be updated on an as-needed basis with the most current information. In previous versionsof Lingo, the dynamic Help was only updated when there was a new product release.
To open the dynamic Help for the active element in the interface, select Help>Dynamic Help.

You can also open the full online Help in your browser. To do this, you can click the Open Topic in
Browser button at the top of the dynamic Help window pane.

CHAPTER 7

78

CHAPTER 7

79

You can also select Help>Open Help.

Local Help System
Because the Help system is hosted online, you may not be able to access it if you are behind a firewall or if you have a slow connection. In that case, you can use a local version of the Help. Lingo will
even switch to the local Help automatically if it detects that you cannot connect to the external Helpsystem.
If you want to use the local Help manually, open the Options dialog (File > Options), and on the General tab select Prefer Local Help.
NOTE: The local Help system is only updated when the application is updated. If you want
to be sure that you have the most current version of the Help, disable the local Help.

CHAPTER 7

80

Image Replacement
In previous versions of Lingo, if you wanted to replace images in your project, you would need toreplace them individually, or you could replace them in you original Flare project and then update
your Lingo project. New methods to replace images have been added to Lingo 10. You can now
replace several images at once using a batch. This method also supports multilingual projects. You
can also replace images in skins.

Batch and Multi-Language Image Replacement
You can replace an image in Lingo instead of deleting and adding the image manually. You can also
create a batch that lets you replace many images at the same time, without needing to retranslate
their callouts.
If you are working in a multilingual project, you can replace the original images with different images
for each language in your project. This is very useful if you need to localize images for different languages or countries.
To open the Batch Replace Images dialog, select Home>Batch Replace Images, or selectin theFile List's local toolbar. The dialog that opens, you can select the folder containing the original
images and sync them to a folder containing replacement images. If the images in the replacement
folder have the same names as the images in the original folder, the replacement images will automatically be linked to the original images. You can also manually replace images by clicking the linkin an image's cell. If you click on the original or replacement image in the grid, you can view a preview of the image at the bottom of the dialog.

CHAPTER 7

81

CHAPTER 7

82

Batch image replacement supports multilingual projects. The currently selected active language isshown in the dialog by default. To replace images for a different language in your project, select a
new language from the drop-down at the top of the language column.

When you click OK, the original images will be replaced with the new images that you selected. Anytranslated callouts that were part of the original images will be transferred to the replacement
images.

CHAPTER 7

83

EXAMPLE
You are translating documentation for a company whose products are used in both
English- and Spanish-speaking countries. You need to localize the images in the documentation so the text on the images is appropriate for the language used in the documentation. To do this, you can use the Batch Image Replace dialog to sync theimages from the English source project with the localized Spanish images.

CHAPTER 784

To do this, you create a folder with the localized Spanish images. After you click the
button in the Batch Replace Images dialog, you select the Spanish Images folder.

CHAPTER 7

85

Any images that have identical file names to those in the original Images folder areautomatically replaced with your localized Spanish images.

NOTE: If there are not any images in your project, batch image replacement is disabled.

NOTE: Callouts from the original image are transferred to the replacement image and canbe translated in Lingo. However, if your replacement image also contains callouts, these callouts will be flattened during the replacement process, and will no longer be editable. As abest practice, choose replacement images that do not include callouts.

NOTE: When performing a batch replacement, you can replace images in subfolders. To
sync correctly, the subfolders must have the same names in the original folder and thereplacement folder. Folders with different names will not sync.

CHAPTER 7

86

NOTE: If you have localized images and you update your Lingo project, a confirmation dialog will ask you if you want to replace the localized images with the images from the source
project.

NOTE: If you are translating a MadCap Mimic movie, you can replace frame backgroundimages. However, image objects are not replaceable.

NOTE: If you localize an image and then reopen the Batch Image Replacement dialog, thereplacement link next to the original image will say "localized." This alerts you that you havealready replaced that image with a new image. However, you can still click the link andreplace the image with a new image.

CHAPTER 7

87

Skin Image Replacement
In addition to replacing images in topics, you can also replace images used in skins. You can replacelogos in Flare's HTML5 skins, and you can replace the About box in Mobile and WebHelp skins.
To replace the skin image, open the skin in the Translation Editor, then clickin the local toolbar.
The Replace Skin Images dialog opens. You can see a preview of the current skin image in the dialog. Click Browse to select a new image.
EXAMPLEYou need to localize hundreds of images in a Flare project. You have already used the
Batch Image Replace dialog to localize images in the topic files, but you also need to
localize the skin files, so the online Help will show the correct version of your company
logo. To do this, you set the current target language in the Project Properties dialog...

CHAPTER 7

88

...then you open the skin file for that language. In the local toolbar, select Replace Skin
Images.

In the dialog that opens, replace the current logo...

CHAPTER 7

89

...with the new logo.

CHAPTER 7

90

You do this for each target language. When the project is exported back to Flare andthe file outputs are generated, the online Help shows the correct logo for each skin.

CHAPTER 7

91

NOTE: You can replace skin images with .gif, .jpeg, .jpg, and .png image types.

NOTE: If you need to localize images in your skins, you can select a different target language for the project from the Project Properties dialog (File>Project Properties). Then forthat language, open the skin file(s).

CHAPTER 7

92

Project Export Enhancements
Project export has been updated so Lingo will update previously exported versions of the project. In
previous versions of Lingo, if you wanted to re-export an existing project, you would need to create asecond copy of the project, or delete the previous export.
When you update a project in Lingo 10, a confirmation dialog will alert you if the export destination
already exists. When exporting the project to an existing location, only changed and new files will be
exported.

You can view saved export logs in the Project Properties dialog. If an export fails, these logs provide
information about what caused the failure. You can save and view these logs.

CHAPTER 7

93

Project Properties Dialog
In previous versions, you could view and change basic project information using the Project Editor.
You can now access these and other project-related settings using the Project Properties dialog.
The Project Properties dialog organizes project settings and information into the following tabs:nGeneral View the project's name, folder, domain, client, and log files. You can also open the
Lingo project folder.

CHAPTER 7

94

n

Project Language View and change the project's current target language and the source file's
language. You can also add and remove languages from the project and select the language(s) to use when compiling statistics and applying the translation memory and machine translations.

CHAPTER 7

95

n

Flare Settings Select the variable sets or individual variables you want to flatten, select project filtering options, and choose whether or not you want to convert inline snippets to text.
This tab is only available in Flare projects.

CHAPTER 7

96

n

DITA Settings Select conditional attributes to filter a DITA project. This tab is only available in
DITA projects.

nSort Order Add "Sort As" entries for index and glossary terms. These terms will be used when
you export the project back to Flare to create a custom index and glossary sort order. This tab
is only available in Flare projects.

CHAPTER 7

97

n

Source Control Select options related to source control, such as binding and unbinding a project. If the project is already bound, you can use the source control button to perform tasks on
files in your project.

CHAPTER 7

98

Report Enhancements
Improvements have been made to Lingo's reporting features. These include new quality assurance(QA) reports and report styling updates to improve readability.

New Quality Assurance Reports
Two new quality assurance reports have been added in Lingo 10:nLocalized image files This report shows the localization status of all of the images in your project. The report shows the languages for which you have chosen a new image ("localized"
images), as well as those still using the original source file ("unlocalized" images).
EXAMPLE
Let's say you are translating a project into 10 different languages. As part of thetranslation process, you need to localize all of the images in the project. During
the course of your project, several new topics are added to the source project,and you receive new images that you need to localize.
Because there have been so many changes to the project, you periodically run
the localized image files report to see the localization status of each image in the
project. When you run the report, you can see each original image, what languages have been localized for each image, and what languages have not been
localized for each image. This helps you keep track of which images you stillneed to update.

CHAPTER 7

99

The following image shows how such a report might look.

CHAPTER 7

100

nTranslations that match machine translation This report compares the translated target segment with any available machine translations (MTs). This allows you to review your translations against the machine translations and make changes if necessary. You can change thethreshold for the minimum MT match percentage, and you can set a minimum number ofwords in the segment (to prevent obvious matches, such as names or short phrases, fromappearing in the results).
NOTE: This report is unavailable if an MT provider is not connected to the project.

EXAMPLE
Let's say you regularly send your Lingo projects out for translation. You want tomake sure that your translators are not relying too heavily on MT, because yourcompany uses several company-specific terms that are located in your concordance and in your translation memories, but would not be found in a translation from an MT.
When you get your translations back from the translators, you run a QA report tosee which translations match the MT. You set the percent match at 90% and theminimum word match to 4 words.
When you look at the report, you can see which translations are at least a 90%
match to the MT. You may want to review these translations to make sure thatyour translators made the appropriate adjustments to the machine-generated
translations.

CHAPTER 7

101

CHAPTER 7

102

Report Styling Updates
Lingo's quality assurance (QA) and statistics reports have been restyled with spacing and formatting improvements so they are easier to read.

QA REPORTS
Lingo's QA report has been updated to use better spacing and alternating row colors to improvereadability. The location of the target segment has been moved to the first column so it is the firstthing you see. If you run multiple QA reports, lines help to separate each report.

CHAPTER 7

103

STATISTICS REPORTS
Lingo's statistics report has been updated to use more defined tables with clearer spacing. Eachtable uses grid lines to provide visual distinction between each row, and colors help you quickly
identify the match percentages in the table. Lines help to separate individual statistics reports foreach topic in the project.

CHAPTER 7

104

CHAPTER 7

105

Smart Quotes
Improvements have been made to the way Lingo handles smart quotes when translating a segment. Previously, Lingo would automatically replace straight quotes with curly quotes, regardless of
the language being translated. However, Lingo now replaces quotes based on your project's current
target language.

NOTE: Selecting the smart quote option does not automatically replace all of the straightquotes that you already have in your project. Likewise, existing smart quotes are not automatically replaced with language-specific smart quotes. If you need to update the quotes inyour project, It is recommended that you use the Find and Replace in Files window pane tofind all of the files in the project containing straight quotes (or existing smart quotes) andthen enter smart quotes in their place.

CHAPTER 7

106

TOC View Window Pane
You can now filter the topics in your Lingo project using the TOC View window pane. This view
allows you to filter the topics in your project by any table of contents (TOC) in the source Flare project. This is especially useful if you are working with a very large Lingo project, because not only
does it let you filter by topic files and by TOC, but it also lets you see the order of the topics and theway the topics fit together in the final output.
When in TOC View, you can also view topics' conditional indicators, save linked files for review, andcreate or merge translation bundles.
EXAMPLEYou are working with a large Lingo project. It includes many different file types: images,
skins, page layouts, and topics. There are several TOCs in the source Flare project, anddifferent reviewers are responsible for the content that belongs in each TOC. You needto send the appropriate review packages to each reviewer.
You open the TOC View window pane and filter the files to show a specific table of contents. This lets you see only the topic files that belong in that TOC.

CHAPTER 7

107

Then you can create a review package and send the topics in that TOC to the reviewer.

CHAPTER 7

108

Later, when the reviewer sends their review package back to you, you can merge thereview package back into Lingo. If you want, you can do this from TOC View, as well.

CHAPTER 7

109

When you are ready to create a bundle for your another translator, select a different
TOC from the TOC drop-down. The files in the list update, and you can prepare a new
bundle.

CHAPTER 7

110

Translation Editor Enhancements
Improvements have been made to how the Translation Editor handles conditional text and concept
and index tags. Condition tags are now supported on block level and inline text, and also on glossary
and index terms. Additionally, concept and index tags, which have always been supported, havebeen cleaned up to improve usability in the Translation Editor.

Improved Conditional Text Support
Condition tag support has been enhanced in Lingo 10. In previous versions, conditional text was only
supported on files. Lingo 10 also supports block level and inline conditional text, as well as condition
tags on glossary terms, snippets, and CSS styles.
When you are working with segments in the Translation Editor, you will see yellow condition tags oneither side of the content that is conditioned. Translators can drag these tags to the appropriate location in the target segment to indicate where the conditional text indicator should appear in theexported project.
Additionally, you can now filter content using condition tags. When creating a new Lingo project, you
can filter out one or more conditions.

CHAPTER 7

111

EXAMPLE
The segment below includes a condition tag.

Lingo places yellow conditional text tags on either side of the text that were marked
with a condition tag indicator in the source document. You can hover over the tags to
see information about the condition that is applied to the text.

When the translator translates the segments, he can drag the yellow tags into the target segments, so the translation will also include the condition tag. Later, when thetranslator exports the document back to Flare, the condition tag will appear in the finished project.

CHAPTER 7

112

EXAMPLE
You create your glossary in Flare with the intent of using the same glossary file for multiple outputs. To do this, you apply condition tags to each term that indicate whichterms belong in which output. Some terms are used in multiple targets, others are usedin single targets.

CHAPTER 7

113

Later, when you need to send a specific target to your translator, you can filter your
Lingo project by the target you need to produce.

CHAPTER 7

114

When you do this, the condition text rules set in the Flare target are applied to the Lingo
project. Because you applied condition tags to your glossary as well as to your topics,
when your translator opens the glossary file in your Lingo project, she will only see theterms that need to be translated for that output.

CHAPTER 7

115

She will also only see the terms for that ouput when she opens the Project Properties
dialog and views the Sort Order information for the glossary.

CHAPTER 7

116

EXAMPLE
You use expanding text throughout your Flare project. You do not want your expanding
headers to appear in your printed outputs, so you create a style class in your stylesheetthat has an OnlineOnly condition tag applied to it, and then set this style class on yourexpanding headers.

CHAPTER 7

117

Later, you need to send one of your printed outputs for translation. When you create a
Lingo project, you can exclude the OnlineOnly condition tag from the project.

CHAPTER 7

118

This way, the expanding headers in your online outputs are not included in the content
you send to your translator.

NOTE: Although you can filter out condition tags, Lingo does not explicitly include the condition tags that you have not excluded. For example, if you have condition tags A and B inyour project, and you filter out A, you will see content marked with tag B in the project.
However, if there is content marked with both tags in your project, it will also be excluded.
This is because Lingo excludes anything marked with the A tag, even if the B tag was notalso excluded.
If you need to exclude some content and include other content, you can do this by filtering
your project using a Flare target with your desired condition filters. Filtering by a Flare target
respects both include and exclude condition tag filters.

NOTE: Conditions that "unbind" rather than "exclude" content will not be excluded when you
filter out a condition in Lingo. If you notice that content has not been removed but you thinkthat it should be, check to be sure that the condition is not marked as an "unbind" conditionin Flare.

CHAPTER 7

119

Cleaner Index and Concept Tags
In Lingo 10, if an index or concept tag appears at the beginning or end of a segment, it is no longer
displayed in the Translation Editor. Removing these tags makes segments look cleaner in the Translation Editor, and prevents translators from needing to move tags that are not related to the segment. Additionally, these tags are no longer displayed in Live Preview mode. Tags are still displayed
if they appear between two words.
All tags in a project are translatable when you open their associated file (e.g., index map, conceptmap) from the File List window pane. This content is added back to the segment when the project isexported.
EXAMPLEWhen an author writes topics, she includes all of her topic's concept and index tags at
the beginning of the topic, by the topic title. That way, when people click an index or
related topic link in the output, they are directed to the top of the topic in the online
Help.

CHAPTER 7

120

When the author imports her Flare project into Lingo, these tags are automaticallyremoved from the segment. This way the tags do not clutter the beginning of each segment and you can translate just the important content. However, you can still translatethese tags when you open the index keyword and concept keyword files in the File List.

NOTE: Existing translation memories (TMs) that include a translated segment and any typeof tag may no longer show a 100% match if they are applied to a segment where the tag has
been removed in the Translation Editor. To fix this, update the target segment in the TM toremove the tags.

NOTE: Tags (e.g., spans) are removed from a segment if they wrap the entire translation
unit. The exception to this is condition tags, which are not removed if they span the entire
unit (this is because condition tags can affect translation status).
Similarly, unflattened snippets, conrefs, and variables will be removed from the Translation
Editor if they span the entire translation unit (e.g., a snippet that makes up an entire segment).
This content will be added back into the project when you export it. Be sure to translate thecontent in the associated content file in the File List so it will be translated in the finishedproject.

CHAPTER 7

121

CHAPTER 8

New Features for Lingo 10.1
There are also a few new features added in Lingo 10.1.
This chapter discusses the following:

CHAPTER 8

Filter by Multiple Targets

123

Show/Hide Spaces in Editors

125

Microsoft Bing Machine Translation Changes

127

Importing Alternate Tag Segments

129

122

Filter by Multiple Targets
Previously you could select a single Flare target in the Start New Project Wizard when creating a
new Lingo project. This allows you to limit the files to only those related to a certain target, rather
than importing all of the files from the project.
This feature has been enhanced to let you choose multiple Flare targets in the wizard. When you
select the drop-down on this page of the wizard, simply click the check boxes next to the appropriate targets.

CHAPTER 8

123

After making your selections, click elsewhere on the page to close the drop-down.
When you finish in the wizard, Lingo will import only the files or segments necessary for those targets.

CHAPTER 8

124

Show/Hide Spaces in Editors
There is a new space option in the local toolbar of the Translation Editor and Translation Memory
Editor. When you turn this feature on, you can see markers that show where space exists between
text in a segment.

CHAPTER 8125

CHAPTER 8126

Microsoft Bing Machine Translation
Changes
The Microsoft Bing machine translation (MT) API has changed. This means that you must provide
the API key when you integrate Lingo with the MT, rather than the user ID and password that wererequired previously.

CHAPTER 8

127

In addition, a new field lets your provide a category that you have previously set up in your Microsoft
MT account.

CHAPTER 8

128

Importing Alternate Tag Segments
There is a new field in the Import TMX dialog that lets you import alternate tag segments.

EXAMPLE
Let’s say you are importing a TMX file that was previously used for a third-party translation tool. That tool might have treated the <strong> tag differently than Lingo, so
after you import the TMX file you might discover that some match results are not what
you expect. By selecting this new option, Lingo will consolidate those tags, which willproduce better match results.

CHAPTER 8

129

CHAPTER 9

New Features for Lingo 10.2
There are also a few new features added in Lingo 10.2.
This chapter discusses the following:

CHAPTER 9

Adobe FrameMaker 2017 Support

131

Custom Installation

132

Find and Replace Enhancements

134

Microsoft TFS 2017/2018 Support

138

130

Adobe FrameMaker 2017 Support
If you are translating Adobe FrameMaker files, be aware that Lingo now supports FrameMaker
2017.

CHAPTER 9

131

Custom Installation
When you install this version of Lingo, you can simply use the default settings, or you can complete a
custom installation.

CHAPTER 9132

After you choose Custom and click Next, you can select the following option:nLocal Documentation If you do not select this option, only the external Help for Lingo will beavailable. This is beneficial because you are ensured of seeing the latest documentation,
which is updated periodically on a server. Also, it reduces the overall size of the Lingo installation. However, if you want to include the Help system on your computer, select this option.
You might choose to do this if you have limited access to the Internet or are behind a firewall.

CHAPTER 9

133

Find and Replace Enhancements
A couple of enhancements have been made to the find and replace features in Lingo.

FIRST RESULT PER FILE
When you use the Find and Replace in Files window pane, there is a new option for customizing results. This option is called “First result per file.”

CHAPTER 9134

By selecting this option, you can limit the results shown so that a file displays only once, even if theterm is found multiple times in it.
EXAMPLE
Let’s say you search in all your source segments for the word “content,” with the “First
result per file” option disabled. In several files, the word is found multiple times, so a
unique row is displayed for each occurrence. For example, the word is found six times
in the file Appendix.htm, so there are six rows in the results for that file.

CHAPTER 9

135

Next, you enable the “First result per file” option and try again. This time, there are far
fewer rows in the Find Results window pane, including just one for the Appendix.htm
file.

After opening one of these files that contains the word multiple times, you can use the
Quick Find widget to locate each concurrence of the word in the file.

CHAPTER 9136

QUICK FIND AND REPLACE WIDGET DROP-DOWN
The Quick Find and Replace widgets have been updated to offer a drop-down arrow next to the Filter
button. Clicking this drop-down arrow gives you specific filtering options. This widget displays within
a file.

CHAPTER 9

137

Microsoft TFS 2017/2018 Support
If you are using Microsoft Team Foundation Server (TFS) for source control, be aware that Lingo
now supports TFS 2017/2018.

CHAPTER 9138

APPENDIX

PDFs
The following PDFs are available for download from the online Help.
Alignment Guide
Getting Started Guide
Key Features Guide
Shortcuts Guide
Source Control Guide: Git
Source Control Guide: Perforce
Source Control Guide: Subversion
Source Control Guide: Team Foundation Server
Termbases Guide
Touring the Workspace Guide
Translation Guide
What's New Guide

APPENDIX

139