Term bases - Inside an entry

These properties describe the concept across all languages:

• ID: A unique identifier for the entry. This is auto-generated and you can't change it.

• Note: A text field where you can add comments or references related to the entry. For example, you can include a reference to the source of the terms.

• Project: The translation project identifier where the entry was created. Defaults to the current project but can be customized.

• Domain: The broader category or subject area. Inherited from project settings by default.

• Client: The client for whom the term base entry was created.

• Subject: A more specific description, sub-topic, or field within the domain.

  When you add or edit a term base entry from inside a project (for example, by adding new terms in the translation grid), memoQ automatically fills in the Project, Domain, Client, and Subject fields using the project’s details. You’re free to change these values afterwards if they don’t fit this specific entry.

• Created by: The user who created the entry.

• Modified by: The user who last modified the entry.

• Created at: The date and time when the entry was created.

• Modified at: The date and time when the entry was last modified.

  memoQ automatically updates the creation and modification dates, IDs, and author names for you. However, you can edit the Subject, Domain, and Note fields yourself whenever needed.

• Image: An optional image illustrating the concept represented by the entry.

Each language version of an entry can have its own definition. It's a description of the concept in that language. You may add exactly one description per language.

This ensures clarity and consistency across terms describing the same concept.

Each term within a language version can have specific properties that control how memoQ handles them during translation:

• Matching: When you add a term to a term base, you can choose how flexibly the system should match it in the text.

  Here are the options:

  • Fuzzy: Use this when the beginning of a term can change in different forms.

    For example (German), the plural of "Mutter" is "Mütter". With Fuzzy matching, both forms will match.

    It’s also useful for compound words. If your term base contains "Festplatte" and "speicher", they will be highlighted in a word like "Festplattenspeicherplatz".

  • 50% prefix (default): Allows partial prefix matching.

    For example, with "project", it will match "project" and "projects", but not "project-specific".

    This is the standard setting for most terms.

  • Exact: Matches only the exact form of the term.

    For example, with "project", it will match only "project", not "projects" or "subproject".

  • Custom: Lets you use wildcards for more advanced matching.

    For example:

    "Wassert|urm" → matches "Wasserturm" and "Wassertürme", but not "Wasserschutz".

    "bankovn|í operac|e" → matches "bankovních operací" and "bankovními operacemi".

  No matter which option you choose, matches only occur when the term appears at the start of the expression - it must be a prefix of the word or phrase.

• Case sensitivity: This setting determines whether memoQ considers uppercase and lowercase letters when matching a term.

  Properties that control case-sensitivity: 

  • Yes: Choose this option to make the term fully case-sensitive.

    The term will only match if it appears exactly as you typed it in the term base, including uppercase and lowercase letters.

    For example: If you add the term "Will", it will only match "Will", not "will" or "WILL". This setting is useful for proper names or terms where case matters.

    It's also good for abbreviations like "TBD" or "XML".

  • Permissive: Choose this option to tell memoQ that uppercase letters must match and lowercase letters are flexible.

    • Uppercase letters in the term must match exactly in the text.

      For example, "ALPAC" in the term base will only match "ALPAC" in the text).

    • Lowercase letters are flexible, they can match either uppercase or lowercase.

      For example, "Alpac" in the term base will match "ALPAC", "Alpac", "AlPac" etc., as long as the first letter "A" is uppercase. The word "aplac" won't match because the first letter isn't uppercase.

  • No: Use this option to ignore capitalization (make the term case-insensitive).

    The term will match regardless of how it appears in the text - uppercase, lowercase, or mix. This option is useful for regular words or imported glossaries that use initial uppercase letters.

    For example: If the term is "memoQ", it will match "memoQ", "MEMOQ", or "Memoq".

• Forbidden term: A forbidden term is a word or phrase that shouldn't be used in the translation.If a source term is marked as forbidden, it won’t appear in the Translation results pane.If a target term is forbidden, it will still appear in the Translation results pane, but it won’t be highlighted - it will just show up in plain black text.Forbidden terms are never highlighted in the text itself. This helps make sure that incorrect or unwanted terms are avoided during translation.

For more examples and explanations, see the Create a term base entry topic.

These fields let you add helpful details about a term:

• Example: Use this field to give an example - a sample phrase or sentence showing how the term is used.

• Part of speech (POS): Displays the grammatical category of the term, such as noun, adjective, adverb, verb, etc.

• Gender: Displays whether the term is masculine, feminine, or neutral (useful in gendered languages).

• Number: Displays whether the term is singular or plural.