Mobile menu

Now for a question: creating multilingual glossaries
Thread poster: Timothy Barton

Timothy Barton
Local time: 01:24
Member (2006)
French to English
+ ...
Apr 7, 2006

I translate from three languages: Catalan, Spanish and French. I imported an Excel file into a terminology database, and selected Spanish as the main lemma, and Catalan and English as my translations.

My text was Catalan to English. I assumed that if EN_1 is a translation of ES_1, and CA_1 is a translation of ES_1, then the program would realise that EN_1 is also a translation of CA_1. But it does not come up with the translation. It only looks up terms where the lemma is that of the source text.

Obviously the short-term solution is to import Catalan as the main lemma, and English and Spanish as a translation, but if I then get a similar text in Spanish, I don't see why I should have to do another import, this time with Spanish as the main language.

One of the reasons I splashed out on DVX was the multilingual terminology management, but it looks like I have to import for each source language, and if I choose to do it in the same database I end up with repeated entries, with the lemma and translation the other way round.

Is there some kind of setting I've not found? Could it be something in Database->Properties?


Direct link Reply with quote
 

Victor Dewsbery  Identity Verified
Germany
Local time: 02:24
German to English
+ ...
What languages are defined in the project? Apr 7, 2006

Hi Timothy,

Was the project in question defined as Catalan to English?
If you go to Project>Properties>Languages, what is given as the source language? DVX searches from the index for the source language (or should do). At least, I know that this works for reversing a single language pair. Can't check the multilingual capability, 'cos I only use one language pair.

Other possibilities:
- Losing the link to the database: sometimes DVX "forgets" what databases it should be looking at. Solution: go to Project>Properties>Databases, make sure the appropriate boxes are ticked and confirm (sometimes this jogs DVX's memory even if the settings were right all along).
- Incomplete indexing: I know that the translation memory (MDB) has separate index files which should be almost as big as the main memory file. Not sure how the indexing is done for the terminology database. But it may be worth repairing the database (sorry, a copy of the database!) periodically.

Is there anything on your problem in the Atril knowledge base or at http://necco.ca/dv/ ?

[Edited at 2006-04-07 06:29]


Direct link Reply with quote
 


To report site rules violations or get help, contact a site moderator:

Moderator(s) of this forum
Pavel Tsvetkov[Call to this topic]

You can also contact site staff by submitting a support request »

Now for a question: creating multilingual glossaries

Advanced search






Across v6.3
Translation Toolkit and Sales Potential under One Roof

Apart from features that enable you to translate more efficiently, the new Across Translator Edition v6.3 comprises your crossMarket membership. The new online network for Across users assists you in exploring new sales potential and generating revenue.

More info »
SDL MultiTerm 2017
Guarantee a unified, consistent and high-quality translation with terminology software by the industry leaders.

SDL MultiTerm 2017 allows translators to create one central location to store and manage multilingual terminology, and with SDL MultiTerm Extract 2017 you can automatically create term lists from your existing documentation to save time.

More info »



All of ProZ.com
  • All of ProZ.com
  • Term search
  • Jobs