Hi Paul,

the only way I could see the etteplan TB has only EN and FI was by opening it with Multlterm and seeing that onlyEN and FI mdf's and mtf.s were created. That's quite hidden from the standard user who might not even have Multiterm, but certainly it is not normal practice to look there...

In my case, can just disable the use of etteplan.

By the way, I found out that the markers to the right of the TB's behave strangely when I toggle the enable/disable TB

Also, I set the etteplan TB to used again and default and tried to add a term to it, hoping it would know that a Dutch term is added - but alas, the term is added but with language FI, although it is a Dutch word...

Hope this helps to narrow down all problems...

Best regards,

Henk

Hi  

I think the problem is clear, and your solution is to merge your termbases as I mentioned. You can tell which languages are there when you open it and look at the termbase definition.  And of course you can tell when you open the project in Studio since you'll see more languages in this view:

Here I have an EN -> FR project with two termbases that I might assume are EN, FR until I see the Finnish language.  If the project is multilingual then this isn't so clear since you'd see the additional languages listed anyway, but if not then it's clear.

I'll raise this one with the team and see if we can get a fix scheduled.

Regards

Paul

Hi Paul,

I beg to disagree with you about how I oculd see the languages in the TB.

I removed the ettelplan TB and added it again, then the Termbase window does not tell me that ettelplan does contain EN and FI, but not NL: actually it does not show FI at all, but it DOES show NL.

Also, when you get a TB within a package from an agency, it is not the first thing you do to look at the TB definition - you would suppose it supports the project languages...

So there should be a function in the Studio TB view that tells the user that a certain TB does not contain one (or even both) of the project languages.

Maybe such a check could be added - now it cost me hours to find out the error made by the PM.

Best regards,

Henk

Hi  

You're right, sorry.  I must have added Finnish to my project already when I was testing.  Perhaps this would help though?

Hi  

You're right, sorry.  I must have added Finnish to my project already when I was testing.  Perhaps this would help though?

HiPaul,

thanks for the enlightenment.

Only problem: when I am looking for what is causing my problem, the problem is there only when I have already added the EN-NL termbase, and in that case, also NL is shown in that list, besides EN and FI.

Besides, how should I know that that "Not specified"  exists, and even if I knew, how should I know to explain the result of what I see - the Help is not helping me further.

The real problem is, however, we translators are not forensic detectives, we have a translation to deliver.

And Studio should ideally warn us if a termbase is not fit for the language pair we need, but in the first place, if the termbase is not fit, Studio should not cripple the function of another termbase and leave us translators completely in the dark about what is going on.

Best regards, and have a nice trip to Assia and Australia.

Henk Sanderson

Hi  ,

Of course... I was just explaining how you can tell without having to refer to the existence of the index files. Studio should of course handle this in the first place... no arguments there at all!

Cheers

Paul