Skip to main content

How does Glossary term matching work?

Glossary matching rules define how LingoHub detects Glossary terms within source texts. Configuring matching and case sensitivity settings determines when LINA and translators receive terminology suggestions in the Editor.

How to configure matching settings

You can set or adjust matching parameters for any individual Glossary entry via the Term info side panel:

  1. Click AI in the top navigation bar and select Glossary under Context in the left panel.

  2. Select your Glossary from the list.

  3. Click the Term info icon in the top right corner or the Matching icon in the toolbar.

  4. In the Matching section of the side panel:

    • Select your preferred Matching type (Fuzzy, Prefix, Exact, or Custom).

    • Select your Case sensitive preference (Yes, Permissive, or No).

To learn more about managing term properties, see our our Glossary term info overview.

Matching types

LingoHub provides four matching methods to control term detection:

  • Prefix (Default): Detects the term when the source text starts with the exact term entry.

    • Glossary Term: project

    • Matches: project, projects

    • Does not match: project-specific, catalog

  • Exact: Detects the term only when it matches the source word exactly. For example, "project" matches "project", but ignores "projects" or "project-specific".

  • Fuzzy: Detects the term even with small variations or within compound words. For example, "color" matches "colour", and "state" is detected inside "understatement".

  • Custom: Allows wildcards to match word variations:

    • Use a pipe (|) to mark a variable ending (e.g., color| matches "color" and "colors").

    • Use an asterisk (*) after characters (e.g., color* matches "color", "colors", and "coloring").

Case sensitivity

  • Yes: Strictly enforces case matching. A term matches only if the source text uses the exact same capitalization.

  • Permissive: Capital letters in the term must be capitalized in the source text. Lowercase letters in the term match both lowercase and uppercase occurrences.

  • No: Case is completely ignored. The term matches regardless of whether it is written in small caps, ALL CAPS, or Title Case.

Examples & behavior matrix

Suppose our Glossary contains the terms: "Projects", "user", and "Car". Below is how LingoHub detects these terms in the Editor under each configuration:

1. Exact + Case sensitive (Yes)

Only exact words with exact capitalization are recognized:

Term

Matches

Does Not Match

Projects

Projects

Project, projects

user

user

User, Users

Car

Car

car, Cars, CAR


2. Exact + Case insensitive (No)

Matches exact word forms regardless of capitalization:

Term

Matches

Does Not Match

Projects

Projects, projects

Project

user

user, User

Users

Car

car, Car, CAR

Cars

3. Exact + Case permissive

Matches exact terms while enforcing capital letters:

Term

Matches

Does Not Match

Projects

Projects

projects

user

user, User

Users

Car

Car, CAR

car, Cars

4. Fuzzy + Case sensitive (Yes)

Matches term variations while enforcing exact case:

Term

Matches

Does Not Match

Projects

Projects, Project

projects

user

user

User

Car

Car

car, cars

5. Fuzzy + Case insensitive (No)

Matches term variations across all capitalizations:

Term

Matches

Does Not Match

Projects

projects, Projects, Project

None

user

user, User

None

Car

car, Car, cars, CAR

None

Need more help?

Couldn't find what you were looking for? We are here to help! Reach out to our team at [email protected], and we will gladly assist you.

Did this answer your question?