Hi Pascal,

ok - I believe this problem is known and scheduled to be fixed.  I don't have a due date though unfortunately.  However, there is an interesting workaround using fields for the variants instead of using sub-languages in the termbase itself.  So your terms could be entered like this for example:

This brings a number of advantages:

1. You can use the term verifier to make sure you always use the correct variant when translating
2. You will always be able to ensure the terms are added to the correct variant
3. You can create an input model so that the variant is automatically completed when you add terms

I rejigged the termbase you sent me to reflect these changes and will send it back to you after I post this.  You can also find more info on this approach here if you're interested:

Hope this helps.

Paul

Unknown said:

...I asked your collegue from the helpdesk about this issue and he said that using your version is certainly a workaround but definitely not the best way to go and that I should better not try it.

Hi Pascal,

That does surprise me... the workaround I gave you is the recommended way to deal with sub-languages when you ask our product managers!  I am sure this issue is already logged but I'll double check this.

Thanks

Paul

Hello Pascal,

Thank you for following up on this.

Regarding the workaround:

I do recommend the approach Paul explained (using fields for sub-languages).

Migrating existing termbases can be a challenge. Luckily, Paul has written a guide that explains how to do this.

Regarding the defect:

The issue that we were aware of has indeed been fixed in Studio some time ago. I will contact you via a ticket (since I will need some more details) to investigate whether there are remaining issues.

Raphael

For reference:

If

- you use sub-languages in your termbase and

- the project's sub-language is not present in the termbase,

the term might not be added to the sub-language set at Project Settings > Language Pairs > All Language Pairs > Termbases (applies to Studio 2015 SR2 CU05 and before).

While I hope that we can fix this in a future Studio update, the recommended approach to get around this issue is using a field to track sub-languages (see Paul Filkin's blog post or our KB).

Raphael