Termbases and the project glossary

Terms in the grid from the Project Glossary and a termbase, and which wins. A termbase is created and an existing one attached; entries are edited, added and deleted; terms are added while translating to the termbase or the glossary. Use in MT makes the AI model use the company's terms, and Error Check stops a forbidden term. A multilingual MultiTerm file is imported and exported.

1. Termbase or Project Glossary: the glossary wins

   bAIbel AV keeps terms in two places. The Project Glossary belongs to one project, and its words win there. A termbase stands on its own: any number of projects can use it, and it has fields and statuses. Where the two give the same term, the glossary wins.

   

2. Open the document and click in segment 5 to see Termbase Hits

   Open the manual. Glossary terms are underlined in green, termbase terms in the termbase's own colour. Click in segment 5: Termbase Hits lists both, and says where each came from. grass box is in both, and the glossary's Grasfangbox wins over the termbase's Grasfangkorb.

   

3. In Termbases, click New; tick Read and Write

   In the project, open Termbases and click New. Name the termbase; the language pair opens on the project's. Leave Read ticked and tick Write, so terms you add while translating go into it. The table shows its place in the list: where termbases give the same term, the one higher up wins.

   

4. Click Add, Local Drive, tick a termbase and Add Selected

   A termbase made for one project serves others too. In the French quick start card's project, click Add, then Local Drive. The list gives each termbase's entries and pairs: tick Thistlecombe multilingual and Add Selected. Read only is enough here.

   

5. Click the pencil to open the termbase editor; search

   Click the pencil on a termbase's row to open it. Each term carries its status: Approved, Provisional or Forbidden. D marks a definition, N a note. Search looks in the terms, their other forms, definitions and notes: blade gives 4 of 39, operator presence control by its definition.

   

6. Click an entry to edit it and Save

   Click an entry to edit it. Fangsack is Forbidden, with a note saying why: a Forbidden target is never sent to the AI model, and Error Check stops a segment that uses it. Here cutting height gets another form, Schnitthöhen, and a note. Save is greyed until something changes.

   

7. Click Add Entry; select one and Delete

   Add Entry opens an empty form: leaf mulch → Laubmulch, marked Provisional until it is agreed, and Save. To delete, select idle → Leerlauf and click Delete. AV asks first; it cannot be undone.

   

8. Press Ctrl+Shift+A, untick Glossary, keep Termbase

   While translating, press Ctrl+Shift+A and type the source term and its target. Untick Glossary and leave Termbase ticked: the term goes into every termbase with Write on for this pair. owner's manual → Betriebsanleitung is the company's word, so it belongs in the termbase.

   

9. Press Ctrl+Shift+A, tick Glossary, untick Termbase

   A term for this job only goes in the glossary: tick Glossary and untick Termbase. Harbrook wants its own heading, Safety first → Sicherheit zuerst. It is underlined in green, and it stays with this project.

   

10. Open Project Glossaries: edit, copy to termbase, delete

    In the project, Project Glossaries lists the glossary by language pair. Each entry can be edited in place (✎, Enter to save), copied to a termbase, or deleted. customer helpline is now the company's word: the copy button puts it in the termbase, and the glossary keeps its entry, which still comes first here.

    

11. Translate with Use in MT off (Ctrl+Shift+M)

    The termbase's Use in MT is off, so the AI model is sent the glossary but no termbase terms. Click in segment 4's target and press Ctrl+Shift+M. The AI model picks its own word for the operator presence control: Totmannschalter.

    

12. Tick Use in MT and translate again

    In Termbases, tick Use in MT on Thistlecombe terms and translate segment 4 again. The AI model is now sent the termbase terms found in the segment, blade → Messer and operator presence control → Sicherheitsbügel, and uses the company's word.

    

13. The glossary wins over the termbase

    grass box is Grasfangkorb in the termbase and Grasfangbox in the glossary. The grid underlines it in green, and the tooltip says the glossary overrides the termbase. The glossary's word is the one sent to the AI model and the one Error Check expects.

    

14. Press Ctrl+Enter: Error Check stops a forbidden term

    Segment 5's target uses Fangsack and leaves out Sicherheitsschlüssel. Press Ctrl+Enter to confirm it: with Error Check on, AV stops the confirm and marks the segment. Click the stop icon to see why: a forbidden term used, and two approved terms missing. It looks for each term as written, with the other forms the termbase lists: an ending that changes the word can defeat it.

    

15. Click Import MultiTerm XML and choose the file

    In Termbases, click Import MultiTerm XML and choose the file. AV lists the languages in it and how many terms each has: this one has British and American English, German and French. With Merge variants off, each locale is its own row and column.

    

16. Tick Merge variants, choose the pairs and Import

    Tick Merge variants: the matrix is now by language, and the mapping counts EN-GB and EN-US as English (for this import only). Click EN → DE and EN → FR. Then Import, create Thistlecombe multilingual, and Import. Both pairs go into the one termbase.

    

17. Check the import message and both pairs

    The import message says what was kept (definitions, notes, statuses, parts of speech) and what was not (creator and date records, Subject). Open the termbase: English → German has 17 entries, English → French 14. Choose any two of its languages in the editor's menus to see and edit that pair.

    

18. The other pair in another project

    The same termbase, attached to the French quick start card's project, gives French for the same English terms: safety key → clé de sécurité, grass box → bac de ramassage. A project uses the pair it needs.

    

19. The other direction

    And in the German dealer note (German → English), the same termbase gives English: Grasfangkorb → grass box, Sicherheitsbügel → operator presence control. A link between two terms has no direction, so no DE → EN pair was needed.

    

20. Tick the termbase and click Export MultiTerm XML

    To give the termbase to someone else, tick it in Termbases and click Export MultiTerm XML. AV writes every language it holds, one entry per concept, with statuses, parts of speech, definitions and notes, and no user names or dates. There is no XDT: MultiTerm reads the file into a termbase whose fields are named Definition, Note, Status, Part of Speech and Other forms.

    

21. Two places for terms, one rule for which wins

    Two places for terms, one rule for which wins, and a check before you confirm.