WordBee Glossary Translation

Stefan Zeidler

• 31. Juli 2023 16:26
• Bearbeitet

Hi everyone,

I had a few questions about translating glossaries. We are using the new terminology extraction tool to create a glossary.

We are planning on exporting to an Excel file, uploading to WB, and translating. Then using the translated Excel file to create a term base. 

My questions are:

1) Is there a more direct way to do this? To go from terminology extraction > glossary translation > termbase?

2) Is there a way during translation to add additional lemma to a term? For instance, English may have just singular and plural, but German would have multiple declinations. 

3) Is there a way to have translators add term definitions to the term base during translation? Or a way to upload them instead of manually copying them?

 

Thank you!

 

Kind regards,
Stefan

4

• 

  Sara Méndez

  • 31. August 2023 14:53
  • Bearbeitet

  Hello Stefan,

  After reading your post, I understand you are using both modules available for terminology work in Wordbee Translator (the Term Extraction tool and the Term Management Editor).

  Let me answer your questions one by one:

  1) Is there a more direct way to do this? To go from terminology extraction > glossary translation > termbase?

  The steps you describe seem appropriate. There are two possible ways to address your scenario:
  A) Since the term extractor can detect term candidates in up to 8 languages, you may want to send first the content you already have translated for the initial phase of your terminology creation process. This way you could start with some terms available in both languages (source and target). However, we only recommend going this route if the quality of your translations is high. 
  B) Alternatively, you could use the terms extracted in one language and translate them into all other languages you require. Then you can import the resulting file into Wordbee Translator to create a glossary.

  2) Is there a way during translation to add additional lemma to a term? For instance, English may have just singular and plural, but German would have multiple declinations. 

  Documenting multiple lemmas or term expressions that relate to the same concept is possible with our Excel import. Find the related documentation here (especially the section about how to customize the Excel working template): Work cycle with the Terminology Extraction module

  Using the Excel file on the Term Collection page is enough if you just plan to capture several terms per concept (and per language) and an example to illustrate their use. However, if your intention is to create terminology in 3 or more languages, working with Excel worksheets can be cumbersome.

  We recommend using the TBX import if you intend to upload additional information related to the term (such as 'Definitions' or 'Term type'). Merging all information in one big TBX file (or several bilingual files that have the same structure) could help you address this operation in a more efficient way, with a single import that can contain all the details required for your company.

  3) Is there a way to have translators add term definitions to the term base during translation? Or a way to upload them instead of manually copying them?

  As suggested in the previous point, the only way to feed and keep documenting a termbase in one or more languages, with multiple lemmas AND term definitions is by working with the TBX standard. 
  - If you want your translators to enter definitions during translation, they will need to access the Terminology Editor.
  - Uploading definitions to an existing termbase can only be achieved via TBX import. The data must be in TBX v3 format to keep feeding the structure originally laid down when the database was created. Using an existing database as a template seems the right way to go, if you want to make sure translators address a minimum amount of fields for the concept or the term(s) available. 
  If you are keen on adding 'definitions', note the TBX v3 standard allows for several options. Definitions can be added for both, terms or concepts. Depending on how specific you want to be, the TBX property needs to be added to one or another level.

  This article may help you get started making use of the current feature set: How to create a Terminology Database that is concept-oriented

  Note that Wordbee Translator supports +30 TBX Fields (in addition to native Custom Fields) so there is a lot of flexibility in defining the database structure that works best for your company. We always recommend working with TBX v3 samples to design a template you can take as a reference for your team.

  Cheers,

  Sara Méndez
  Product Manager

  0
• 

  Stefan Zeidler

  • 6. November 2023 16:03

  Hi Sara,

  I apologize for the long delay in my response. Thank you very much for the detailed information!

  Regarding your point about TBX import, how would we develop the initial TBX file? 

  For instance, we have collected the terms we would like, but we would like to add additional grammatical information, definitions, context, deprecated terms. etc. 

  Should we create the the English termbase in WordBee with all the included information? I'm not sure how to get the information for all the other terms from the linguists. I believe you said we need to give access to the terminology manager to the linguists, is the proper way? Or if we export the tbx, is there a way we could use WordBee to get all the information from the linguists?
  
  Thank you!

  Kind regards,
  Stefan

   

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.