Glossary service

1 min read

The tasks of the translation glossary service are to:

  1. Load glossary from file for the languages involved in translation i.e. source_language and target_language

  2. Analyse the text to be translated and identify words that are part of the glossary

  3. Prepare a glossary prompt part that is added to the prompt of the translation task sent to the LLM

Prerequisites

An .xlsx containing the desired translation must be uploaded to the Knowledge Base. A template for this glossary can be downloaded here:

example_glossary.xlsxExcel spreadsheetDownload

When uploading the document it will be automatically associated with a scope and the ID of this scope will be used as the scope_id to retrieve the glossary during translation.

You can obtain the Scope ID from the URL highlighted in the screenshot below.

image-20250803-205039.png

The first row must contain the name of the language as in between the “..” in the table below

  • "Albanian"

  • "Arabic"

  • "Armenian"

  • "Basque"

  • "Belarusian"

  • "Bosnian"

  • "Breton"

  • "Bulgarian"

  • "Catalan"

  • "Chinese"

  • "Croatian"

  • "Czech"

  • "Danish"

  • "Dutch"

  • "English"

  • "Estonian"

  • "Finnish"

  • "French"

  • "Georgian"

  • "German"

  • "Greek"

  • "Greenlandic"

  • "Hebrew"

  • "Hindi"

  • "Hungarian"

  • "Icelandic"

  • "Indonesian"

  • "Irish"

  • "Italian"

  • "Japanese"

  • "Korean"

  • "Kurdish"

  • "Latin"

  • "Latvian"

  • "Limburgish"

  • "Lithuanian"

  • "Luxembourgish"

  • "Macedonian"

  • "Maltese"

  • "Mongolian"

  • "Nepali"

  • "Norwegian"

  • "Persian"

  • "Polish"

  • "Portuguese"

  • "Punjabi"

  • "Quechua"

  • "Romanian"

  • "Romansch"

  • "Russian"

  • "Sanskrit"

  • "Sardinian"

  • "Serbian"

  • "Serbo-Croatian"

  • "Slovak"

  • "Slovene"

  • "Somali"

  • "Spanish"

  • "Sundanese"

  • "Swedish"

  • "Tamil"

  • "Thai"

  • "Tibetan"

  • "Turkish"

  • "Ukrainian"

  • "Vietnamese"

  • "Welsh"

  • "Yiddish"

Configuration

Default

json
{
    "scope_id": null,
    "filename": null,
    "active": false
}

Pseudo Example

json
{
    "scope_id": "scope_111111111111111111111111",
    "filename": "glossary.xlsx",
    "active": true
}

Parameter Description

Parameter

Description

Default Value

scope_id

The scope id within the knowledge base where the glossary file is stored

""

filename

The filename of the .xlsx file

""

active

If the glossary is used or not

false

Last updated