Fuzzy: Use this value to get hits independently of prefix or suffix matching. In the case of German, for instance, you have “Mutter” in your term base. With the Fuzzy setting, it also finds “Mütter.” German has a lot of compounds like “Festplattenspeicherplatz.” When your term base contains “Festplatte” and “Speicher,” it will highlight in the source cell containing the word “Festplattenspeicherplatz.”

Prefix: this is a default setting. Use this value to set the prefix matching of the selected term base entry as permissive. In the case of “project,” Lingohub will find both project and projects, but it will not find project-specific.

Exact: Use this value to set the prefix matching sensitivity of the selected term base entry to insensitive. In the case of “project,” Lingohub will find project, but it will not find projects or project-specific.

Custom: Use this value to allow wildcards in the term base. Use the pipe (|) to specify the beginning of a variable part in a word, or use the asterisk (*) to specify that anything can come after the last character. If your term is Wassert|urm, Lingohub will find Wasserturm and Wassertürme but it will not find Wasserschutz. You can enter several terms with pipes and asterisks. For example bankovn|í operac|e will retrieve bankovních operací and bankovními operacemi as well.
​

Yes: Use this value to set the case sensitivity of the selected term base entry to sensitive. The term can contain small caps, capital letters or both. Later it will be offered as a translation result only if the same word, strictly typed in the very same way, occurs in the source document. For example, if you create a new term base entry for the name Will, it is worth setting its case sensitivity to Yes as you probably do not want it as a translation result every time a segment is written in future tense.
​

Permissive: Lingohub will be sensitive to capital letters only. Uppercase letters in the term must be uppercase in the text, too, otherwise Lingohub will not return a match. On the other hand, lowercase letters in the term will be matched by uppercase or lowercase letters, Lingohub will not be sensitive there. For example, if the term base contains the term ‘ALPAC’, the text must also contain ‘ALPAC’ to receive a match. However, if the term base contains the term ‘Alpac’, the text can be ‘ALPAC’, ‘Alpac’, ‘AlPac’ etc., as long as the initial A is in uppercase: ‘alpac’ will not match.
​

No: Use this value to set the case sensitivity of the selected term base entry to insensitive. No matter how the term is typed in the source text, the results will include the same term written either in small caps or in capital letters, or both. Case is simply not relevant with this

“Projects”,

“user”,

“car”