I tried to create a termbase but the sublanguage I need it not available.
I need English (Switzerland). This culture (en-CH) has been only recently added to Windows 10. Maybe that’s the reason it’s not available in MultiTerm?
When will it be available? How do I add it?
I need it because I use the sublanguage in Trados and my company’s authoring tool.
Thanks for your help.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hello, I have an additional question. I am not sure how to use variants in my case.
I have the following languages:
I understand how I would use variants if en-US and en-CH were both based on de-AT.
I also have:
Both fr-CH and it-CH are supported by MultiTerm, so that's no problem. But I do not have "generic" French or Italian.
Hello, I have an additional question. I am not sure how to use variants in my case.
I have the following languages:
I understand how I would use variants if en-US and en-CH were both based on de-AT.
I also have:
Both fr-CH and it-CH are supported by MultiTerm, so that's no problem. But I do not have "generic" French or Italian.
I'm a bit confused by this... I don't understand how you can have EN based on DE for example? All I would do is create a termbase with the main languages first, like this:
Then add a field and make it a picklist, finally adding the variants for all languages to the list:
Add this new field to your termbase definition:
That should be enough... you should now have a structure like this that you can use in the way described:
I also attached the termbase so you see for yourself. No terms in there yet:
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Thank you! I will take a look at that.
What I meant by "based on" is that de-AT is the source language for de-CH and de-DE. We have translation projects in Trados for these language pairs:
de-AT -> de-CH
de-AT -> de-DE
de-AT -> en-US
de-CH -> "en-CH"
de-CH -> fr-CH
de-CH -> it-CH
We currently use sublanguages in our MultiTerm Termbase (apparently not a good idea) and added the termbase to the projects. But now we can't just add en-CH because it doesn't exist.
Thanks for your help.
Got it...
Unknown said:What I meant by "based on" is that de-AT is the source language for de-CH and de-DE. We have translation projects in Trados for these language pairs:
de-AT -> de-CH
de-AT -> de-DE
de-AT -> en-US
de-CH -> "en-CH"
de-CH -> fr-CH
de-CH -> it-CH
The termbase I created would work for all of these projects and you could use the verifier function to make sure the correct variants were being used for each one.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Translate
