Import and export a glossary
Bring glossary terms in from a CSV or TBX file, preview the changes first, and download the glossary as a file.
Import is the way to set the wording each language must use for a term, and to bring a termbase over from another tool. Export gives you the whole glossary as a file.
Owners, Admins and Developers can import and export, on Starter and above.
Import a file
Open the import
On the project's Glossary page, select Import CSV or TBX. The Import terms from a file dialog explains the columns a CSV can have.
Start from the template (optional)
Select Download a CSV template for a file with the right columns and one column per target language of this project.
Choose your file
Select Choose a file and pick a CSV or TBX file of up to 20 MB. Nothing is imported yet: transglot reads the file and shows what it would change.
Check the preview
Import these changes? counts the New terms, Changed terms, terms Already the same, and Rows skipped, and lists each change under What changes. Read the skipped rows and any columns the import will not read.
Import
Select Import 12 terms. The notice confirms what happened, for example "Imported 12 terms: 9 added, 3 updated."
CSV columns
The first row is the header. Column names are not case-sensitive.
| Column | Required | What it holds |
|---|---|---|
source_term | Yes | The term as it appears in your source text. Up to 255 characters. |
| One column per language | No | Headed by the language code, such as fr or de_DE. Each cell holds the wording that language must use. |
part_of_speech | No | The kind of word, such as noun. Up to 30 characters. |
notes | No | A note for translators. Up to 2,000 characters. |
case_sensitive | No | 1 for yes, 0 for no. |
do_not_translate | No | 1 for yes, 0 for no. |
forbidden | No | 1 for yes, 0 for no. |
source_term,part_of_speech,case_sensitive,do_not_translate,forbidden,notes,de,fr
Checkout,noun,0,0,0,The payment page.,Kasse,Paiement
Acme Cloud,,1,1,0,Product name.,,TBX files
A TBX file exported from a terminology tool works too. Each entry needs a term in the project's source language; entries without one are skipped.
How an import changes the glossary
- A term already in the glossary is updated, not added twice. This is how you add wording to terms you created in the console.
- An empty cell, or a column the file does not have, leaves what is already there. Wording in languages the file leaves out is kept.
- Marking a term do not translate or forbidden removes its wording, because those terms carry none. The preview warns you before you import.
- Importing does not approve a candidate. A term waiting under Review candidates stays there. A term you rejected earlier stays rejected.
- Your language access applies. If your access is limited to some languages and the file changes wording in others, the import is refused: "This file changes wording in languages you do not have access to, so it cannot be imported." Remove those changes from the file, or ask a project admin to import it.
Export the glossary
Select Export on the Glossary page to download every approved term as glossary-{project}.csv, in the same columns the import reads. The file can be edited and imported again.
To export as TBX, use the API with a deploy token that has the read ability:
curl "https://api.transglot.ai/v1/glossary/export?format=tbx" \
-H "Authorization: Bearer $TRANSGLOT_TOKEN" \
-o glossary.tbxThe API also accepts an import at POST https://api.transglot.ai/v1/glossary/import. See the API reference.
If it doesn't work
- "The columns in this file were not recognised, so no row can be read.": the file has no
source_termcolumn. Check the header row. - "These columns are not read": a column is neither one of the fixed fields nor a language code. Head each language column with its code, such as
frorde_DE. - "That file is larger than 20 MB.": split it into smaller files.
- "That file could not be read.": check it is a CSV or TBX file.
- Rows skipped: the preview gives each skipped row's number and reason, such as "Row 7: no source term."