With a glossary, you can create, store, and manage all the project terminology in one place. The main aim of terminology is to explain some specific terms or the ones often used in the project to be translated properly and consistently.
Each glossary term is displayed as an underlined word in the Editor. Hover over the underlined term to highlight it and see its translation, part of speech, and definition (if they are provided).
Besides the project glossaries that are automatically created along the respective projects, you can also create separate glossaries, fill them with the appropriate content by uploading your existing glossaries in TBX, XLSX, or CSV format, and then assign these glossaries to the needed projects.
To create a glossary, follow these steps:
Depending on your project needs, you can use a simpler approach with one term per language or make your glossary more detailed and complete using the advanced functionality that glossary concepts can offer.
Concept – the highest-level terminology element that contains concept-level data (e.g., concept definition, subject, etc.), including language-level (i.e., term language) and term-level data (e.g., term, the term’s part of speech, type, etc.). Simply put, a concept incorporates glossary terms and their variations with multiple translations and other relevant information.
You can specify the following concept and term details when adding glossary concepts.
To add a new glossary concept, follow these steps:
To add glossary concepts via the Editor, follow these steps:
To allow translators and proofreaders to manage terms in the Editor, follow these steps:
You can edit existing glossary concepts of a particular glossary.
To edit a glossary concept, follow these steps:
You can delete one, multiple, or all the glossary concepts at once.
To delete all the concepts from the glossary, follow these steps:
To download or upload the glossary, follow these steps:
The project owner and managers can upload and download the glossary in the following file formats: TBX (v2), TBX (v3), CSV, XLSX.
If you upload a glossary in CSV or XLS/XLSX file formats, select the language for each column and the column value (term, description, or part of speech) in the configuration dialog.
When downloading a glossary from Crowdin, some browsers may add an XML extension to the downloaded file so that the file may be named sample.tbx.xml.
To import such a file back to Crowdin, rename it to sample.tbx.
Once you upload your glossary file in CSV or XLSX formats, the system automatically detects the file scheme based on the column names specified in the first row. The identification is performed in a case-insensitive manner. Columns that weren’t detected automatically will be left as Not used/Not chosen for manual configuration. Automatic column identification is especially helpful when you upload glossary spreadsheets that contain many languages and additional columns (e.g., Status, Type, Gender, etc.).
To get the most out of the automatic column detection, we recommend that you name the columns in your CSV or XLSX glossary files using the patterns described below:
Part of Speech [en], etc.).
Concept Note, etc.).
To redetect the glossary file scheme, click Detect Configuration.
To assign a glossary to your project, follow these steps:
To change your project’s default glossary, follow these steps:
To share your glossaries between all of the projects you own, follow these steps:
Translate your project’s glossary, so all the terms can be used and translated consistently in all the target languages.
To translate the project glossary, follow these steps:
The glossary will be automatically formed into one file and placed in Sources > Files to be translated along with the other source files. Term translations will be synchronized with the glossary.