Hi Kara - yes, we have this - you can use the option "show sublanguages" when creating a termbase:

However, we generally recommend that users use the main language and decorate any relevant terms with picklist attribute fields instead - so if you have "colour" and "color", for instance, you would keep them both using "English" as a main language and decorate them with a picklist field "Region" and use "en-us" and "en-gb" in this case. For the majority of terms, such a decoration would not be needed, but when you do have variants, then you can use that field. This might not work in all cases, though, and so this is why you can also use sublanguages fully as depicted above.

Thanks, Daniel

PS: It's not MultiTerm in the background, it's a new development, but we've carried over MultiTerm design principles as required - for instance, concept orientation, free termbase structure, term autonomy etc.

Hi Kara - yes, we have this - you can use the option "show sublanguages" when creating a termbase:

However, we generally recommend that users use the main language and decorate any relevant terms with picklist attribute fields instead - so if you have "colour" and "color", for instance, you would keep them both using "English" as a main language and decorate them with a picklist field "Region" and use "en-us" and "en-gb" in this case. For the majority of terms, such a decoration would not be needed, but when you do have variants, then you can use that field. This might not work in all cases, though, and so this is why you can also use sublanguages fully as depicted above.

Thanks, Daniel

PS: It's not MultiTerm in the background, it's a new development, but we've carried over MultiTerm design principles as required - for instance, concept orientation, free termbase structure, term autonomy etc.

Thank you! I missed this checkbox. I'll show this to the students. And thanks for the information about the background implementation.